%% You should probably cite draft-li-rtgwg-apn-framework instead of this I-D.
@techreport{li-apn-framework-03,
    number =    {draft-li-apn-framework-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-li-apn-framework/03/},
    author =    {Zhenbin Li and Shuping Peng and Daniel Voyer and Cong Li and Peng Liu and Chang Cao and Gyan Mishra and Kentaro Ebisawa and Stefano Previdi and Jim Guichard},
    title =     {{Application-aware Networking (APN) Framework}},
    pagetotal = 15,
    year =      2021,
    month =     may,
    day =       24,
    abstract =  {A multitude of applications are carried over the network, which have varying needs for network bandwidth, latency, jitter, and packet loss, etc. Some new emerging applications have very demanding performance requirements. However, in current networks, the network and applications are decoupled, that is, the network is not aware of the applications' requirements in a fine granularity. Therefore, it is difficult to provide truly fine-granularity traffic operations for the applications and guarantee their SLA requirements. This document proposes a new framework, named Application-aware Networking (APN), where application-aware information (i.e. APN attribute) including APN identification (ID) and/or APN parameters (e.g. network performance requirements) is encapsulated at network edge devices and carried in packets traversing an APN domain in order to facilitate service provisioning, perform fine-granularity traffic steering and network resource adjustment.},
}