Problem Statement and Use Cases of Application-aware Networking (APN)

Document Type Active Internet-Draft (individual)
Last updated 2020-09-06
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                              Z. Li
Internet-Draft                                                   S. Peng
Intended status: Standards Track                     Huawei Technologies
Expires: March 11, 2021                                         D. Voyer
                                                             Bell Canada
                                                                  C. Xie
                                                           China Telecom
                                                                  P. Liu
                                                            China Mobile
                                                                  Z. Qin
                                                            China Unicom
                                                              K. Ebisawa
                                                Toyota Motor Corporation
                                                              S. Previdi
                                                             J. Guichard
                                             Futurewei Technologies Ltd.
                                                       September 7, 2020

 Problem Statement and Use Cases of Application-aware Networking (APN)


   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, 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.  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 Networking (APN) architecture.

Li, et al.               Expires March 11, 2021                 [Page 1]
Internet-Draft   Problem Statement and Use cases of APN   September 2020

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 11, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   ( in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Large but Dumb Pipe . . . . . . . . . . . . . . . . . . .   4
     3.2.  Network on Its Own  . . . . . . . . . . . . . . . . . . .   4
Show full document text