APN Scope and Gap Analysis
draft-peng-apn-scope-gap-analysis-00

Document Type Active Internet-Draft (individual)
Authors Shuping Peng  , Zhenbin Li 
Last updated 2020-12-14
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                                            S. Peng
Internet-Draft                                                     Z. Li
Intended status: Informational                       Huawei Technologies
Expires: June 19, 2021                                 December 16, 2020

                       APN Scope and Gap Analysis
                  draft-peng-apn-scope-gap-analysis-00

Abstract

   The APN work in IETF is focused on developing a framework and set of
   mechanisms to derive, convey and use an identifier to allow for
   implementing fine-grain user-, application-, and service-level
   requirements at the network layer.  This document describes the scope
   of the APN work and the solution gap analysis.

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 June 19, 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
   (https://trustee.ietf.org/license-info) in effect on the date of

Peng & Li                 Expires June 19, 2021                 [Page 1]
Internet-Draft         APN Scope and Gap Analysis          December 2020

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminologies . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  APN Framework and Scope . . . . . . . . . . . . . . . . . . .   3
   4.  Example Use Case and Existing Issues  . . . . . . . . . . . .   4
   5.  Basic Solution and Benefits . . . . . . . . . . . . . . . . .   5
   6.  Solution Gap Analysis . . . . . . . . . . . . . . . . . . . .   6
     6.1.  IPv6/MPLS Flow Label  . . . . . . . . . . . . . . . . . .   6
     6.2.  SFC ServiceID . . . . . . . . . . . . . . . . . . . . . .   7
     6.3.  IOAM Flow ID  . . . . . . . . . . . . . . . . . . . . . .   8
     6.4.  Binding SID . . . . . . . . . . . . . . . . . . . . . . .   8
     6.5.  FlowSpec Label  . . . . . . . . . . . . . . . . . . . . .   8
     6.6.  Summary . . . . . . . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   9.  Informative References  . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   Application-aware Networking (APN) is introduced in
   [I-D.li-apn-framework] and [I-D.li-apn-problem-statement-usecases].
   APN conveys an identifier along with data packets into network
   [I-D.li-6man-app-aware-ipv6-network] and make the network aware of
   fine-grain user-, application-, and service-level requirements.

   Such identifier is acquired, constructed in a structured value, and
   then encapsulated in the packets.  Such structured value is treated
   as an opaque object in the network, to which the network operator
   applies policies in various nodes/service functions along the path
   and provide corresponding services.  The identifier may represent the
   application traffic of a particular user but does not identify the
   actual user nor the actual application for network operators.

   The example use-case presented in this draft further expands on the
   rationale for such identifier and how it can be derived and used in
   that specific context.

   This document describes the scope of the APN work and the solution
   gap analysis.

Peng & Li                 Expires June 19, 2021                 [Page 2]
Internet-Draft         APN Scope and Gap Analysis          December 2020

2.  Terminologies
Show full document text