%% You should probably cite draft-li-apn-problem-statement-usecases-08 instead of this revision. @techreport{li-apn-problem-statement-usecases-02, number = {draft-li-apn-problem-statement-usecases-02}, 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-problem-statement-usecases/02/}, author = {Zhenbin Li and Shuping Peng and Daniel Voyer and Chongfeng Xie and Peng Liu and Zhuangzhuang Qin and Gyan Mishra and Kentaro Ebisawa and Stefano Previdi and Jim Guichard}, title = {{Problem Statement and Use Cases of Application-aware Networking (APN)}}, pagetotal = 14, year = 2021, month = may, day = 24, abstract = {Network operators are facing the challenge of providing better network services for users. As the ever-developing 5G and industrial verticals evolve, more and more services that have diverse network requirements such as ultra-low latency and high reliability are emerging, and therefore differentiated service treatment is desired by users. On the other hand, as network technologies such as Hierarchical QoS (H-QoS), SR Policy, and Network Slicing keep evolving, the network has the capability to provide more fine- granularity differentiated services. However, network operators are typically unware of the applications that are traversing their network infrastructure, which means that not very effective differentiated service treatment can be provided to the traffic flows. As network technologies evolve including deployments of IPv6, SRv6, Segment Routing over MPLS dataplane, the programmability provided by IPv6 and Segment Routing can be augmented by conveying application related information into the network satifying the fine- granularity requirements. This document analyzes the existing problems caused by lack of service awareness, and outlines various use cases that could benefit from an Application-aware Networking (APN) framework.}, }