Application-aware IPv6 Networking
draft-li-6man-app-aware-ipv6-network-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-08
Replaces draft-li-6man-service-aware-ipv6-network
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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: January 9, 2020                                          C. Xie
                                                                   C. Li
                                                           China Telecom
                                                            July 8, 2019

                   Application-aware IPv6 Networking
                draft-li-6man-app-aware-ipv6-network-00

Abstract

   A multitude of applications are carried over the network, which have
   varying needs for network bandwidth, latency, jitter, and packet
   loss, etc.  Some applications such as online gaming and live video
   streaming have very demanding network requirements thereof require
   special treatments in the network.  However, in current networks, the
   network and applications are decoupled, that is, the network is not
   aware of the applications' requirements in a finer granularity.
   Therefore, it is difficult to provide truly fine-granular traffic
   operations for the applications and guarantee their SLA requirements.

   This document proposes a new framework, named Application-aware IPv6
   Networking, and also the solution to guarantee SLA for applications,
   which makes use of IPv6 extensions header in order to convey the
   application related information including its requirements along with
   the packet to the network so to facilitate the service deployment and
   network resources adjustment.  Then, it defines the application-aware
   options which can be used in the different IPv6 extension headers for
   the purpose.

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/.

Li, et al.               Expires January 9, 2020                [Page 1]
Internet-Draft           App-aware IPv6 Network                July 2019

   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 January 9, 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.  Terminologies . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Demanding Applications  . . . . . . . . . . . . . . . . . . .   4
     3.1.  Online Gaming . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Video streaming . . . . . . . . . . . . . . . . . . . . .   4
   4.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   4
   5.  App-aware IPv6 Networking Framework . . . . . . . . . . . . .   5
   6.  Application-aware Options . . . . . . . . . . . . . . . . . .   6
     6.1.  Application-aware ID Option . . . . . . . . . . . . . . .   7
     6.2.  Service-Para Option . . . . . . . . . . . . . . . . . . .   8
   7.  Locations for placing the Application-aware Options . . . . .  11
     7.1.  Hop-by-Hop Options Header (HBH) . . . . . . . . . . . . .  11
     7.2.  Destination Options Header (DOH)  . . . . . . . . . . . .  11
     7.3.  Segment Routing Header (SRH)  . . . . . . . . . . . . . .  12
       7.3.1.  SRH TLV . . . . . . . . . . . . . . . . . . . . . . .  12
       7.3.2.  SID Arguments Field . . . . . . . . . . . . . . . . .  12
       7.3.3.  SRH TAG field . . . . . . . . . . . . . . . . . . . .  12
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
Show full document text