Data-driven Accounting in Application-aware IPv6 Networking
draft-du-apn6-data-driven-accounting-00

Document Type Active Internet-Draft (individual)
Authors Zongpeng Du  , Peng Liu  , Liang Geng 
Last updated 2020-11-02
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. Du
Internet-Draft                                                    P. Liu
Intended status: Standards Track                                 L. Geng
Expires: May 6, 2021                                        China Mobile
                                                        November 2, 2020

      Data-driven Accounting in Application-aware IPv6 Networking
                draft-du-apn6-data-driven-accounting-00

Abstract

   This document introduces a new usecase of Application-aware IPv6
   Networking to enable data-driven accounting.

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 May 6, 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
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Du, et al.                 Expires May 6, 2021                  [Page 1]
Internet-Draft       Data-driven Accounting in APN6        November 2020

   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.  Current Mechanism in APN6 . . . . . . . . . . . . . . . . . .   2
   3.  Data-driven Accounting Usecase  . . . . . . . . . . . . . . .   3
   4.  General Process of the Data-driven Accounting . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Application-aware IPv6 Networking is a kind of self-identified
   mechanism per packet.  In the mechanism of APN6
   [I-D.li-apn6-problem-statement-usecases], an IPv6 packet can carry
   the APP ID information and SLA requirements of the traffic in its
   Extension Headers.  Therefore, the network equipment can analyze them
   in each packet and handle the packet accordingly.

   In this mechanism, different user traffic can get different
   treatments so that the network resource can be used more efficiently.
   As the emergence of various new services with various requirements,
   the same treatment for all traffic cannot continue to be sustainable
   in future.

   Current usecases in APN6 only mention different treatments of the
   traffic, but do not mention the way to account, which is essential
   for the operator.  If the operators can charge for APN services
   properly, the APN technologies will be adopted more quickly.

   This document introduces the usecase and the general process about
   the data-driven accounting in APN6.

2.  Current Mechanism in APN6

   As shown in Figure 1, the APN framework [I-D.li-apn-framework]
   includes App (Client and Server), App-aware Edge, App-aware-process
   Head-End, App-aware-process Mid-Point, and App-aware-process End-
   Point.

Du, et al.                 Expires May 6, 2021                  [Page 2]
Internet-Draft       Data-driven Accounting in APN6        November 2020

  Client                                                         Server
  +-----+                                                        +-----+
  |App x|-\                                                   /->|App x|
  +-----+ |   +-----+ +---------+   +---------+   +---------+ |  +-----+
Show full document text