Problem statement and use cases of Application-aware IPv6 Networking (APN6)
draft-li-apn6-problem-statement-usecases-00
Network Working Group Z. Li
Internet-Draft S. Peng
Intended status: Standards Track Huawei Technologies
Expires: March 28, 2020 D. Voyer
Bell Canada
C. Xie
China Telecom
P. Liu
China Mobile
C. Liu
China Unicom
K. Ebisawa
Toyota Motor Corporation
Y. Ueno
NTT Communications Corporation
S. Previdi
Individual
J. Guichard
Futurewei Technologies Ltd.
September 25, 2019
Problem statement and use cases of Application-aware IPv6 Networking
(APN6)
draft-li-apn6-problem-statement-usecases-00
Abstract
Operators are facing the challenges 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 accessing the network, differentiated service treatments
are desired by users. However, operators are still not aware of
applications, which cause that only coarse-grained services can be
provided to users. As a result, operators are only evolving to be
large but dumb pipes without corresponding revenue increase. As the
network technologies evolve including deployments of IPv6 and SRv6,
the programmability provided by IPv6 and SRv6 encapsulations can be
augmented by conveying the application related information into the
network. Adding application knowledge to the network layer, allow
applications to specify finer granularity requirements, which
eventually bridges network and applications.
This document analyzes the existing problems of the current operators
in the application awareness, and outlines various use cases that
could benefit from the Application-aware IPv6 Networking (APN6).
Li, et al. Expires March 28, 2020 [Page 1]
Internet-Draft Problem Statement and Use cases of APN6 September 2019
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
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 https://datatracker.ietf.org/drafts/current/.
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 28, 2020.
Copyright Notice
Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) 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