Problem Statement and Use Cases of Application-aware IPv6 Networking (APN6)
draft-li-apn6-problem-statement-usecases-01

Document Type Expired Internet-Draft (individual)
Last updated 2020-05-06 (latest revision 2019-11-03)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
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-apn6-problem-statement-usecases-01.txt

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. However, network operators are typically unaware of which applications are traversing their network infrastructure, which means that only coarse-grained services can be provided to users. As a result, network operators are only evolving their infrastructure to be large but dumb pipes without corresponding revenue increases that might be enabled by differentiated service treatment. As network technologies evolve including deployments of IPv6 and SRv6, the programmability provided by IPv6 and SRv6 encapsulations can be augmented by conveying application related information into the network. Adding application knowledge to the network layer allows applications to specify finer granularity requirements to the network operator. This document analyzes the existing problems caused by lack of application awareness, and outlines various use cases that could benefit from an Application-aware IPv6 Networking (APN6) architecture.

Authors

Zhenbin Li (lizhenbin@huawei.com)
Shuping Peng (pengshuping@huawei.com)
Daniel Voyer (daniel.voyer@bell.ca)
Chongfeng Xie (xiechf.bri@chinatelecom.cn)
Peng Liu (liupengyjy@chinamobile.com)
Chang Liu (liuc131@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.)