Application-aware Networking (APN) Framework
draft-li-apn-framework-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Zhenbin Li  , Shuping Peng  , Daniel Voyer  , Cong Li  , Liang Geng  , Chang Cao  , Kentaro Ebisawa  , Stefano Previdi  , Jim Guichard 
Last updated 2020-09-06 (latest revision 2020-03-05)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Additional Resources
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-li-apn-framework-00.txt

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 (e.g. 5G) 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 characteristic information such as application identification and its network performance requirements is carried in the packet encapsulation in order to facilitate service provisioning, perform application-level traffic steering and network resource adjustment.

Authors

Zhenbin Li (lizhenbin@huawei.com)
Shuping Peng (pengshuping@huawei.com)
Daniel Voyer (daniel.voyer@bell.ca)
Cong Li (licong@chinatelecom.cn)
Liang Geng (gengliang@chinamobile.com)
Chang Cao (caoc15@chinaunicom.cn)
Kentaro Ebisawa (ebisawa@toyota-tokyo.tech)
Stefano Previdi (stefano@previdi.net)
Jim Guichard (jguichar@futurewei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)