Requirements for Protocol between Control and User Plane on BNG
draft-wadhwa-rtgwg-bng-cups-protocol-requirements-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
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)
rtgwg                                                         S. Wadhwa
Internet Draft                                               K. DeSmedt
Intended status: Informational                                 P. Muley
Expires: Apr 21, 2019                                             Nokia
                                                              R. Shinde
                                                           Reliance Jio
                                                              J. Newton
                                                               Vodafone
                                                             R. Hoffman
                                                                  TELUS
                                                                S. Pani
                                                       Juniper Networks
                                                           Oct 22, 2018

      Requirements for Protocol between Control and User Plane on BNG
         draft-wadhwa-rtgwg-bng-cups-protocol-requirements-00.txt

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), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

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

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on April 22, 2019.

Copyright Notice

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

Wadhwa, et al           Expires April 22, 2019                 [Page 1]
Internet-Draft        Architecture for BNG CUPS            October 2018

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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.

Abstract

   Traditionally, the BNG provides aggregation of fixed access nodes
   (such as DSLAM and OLTs) over Ethernet and provides subscriber
   management and traffic management functions for residential
   subscribers. The BNG has however evolved to become a multi-access
   edge device that also provides termination of subscribers over
   fixed-wireless and hybrid access. An overall architecture and
   interfaces required between separated control and user-plane for a
   multi-access BNG are described in draft-wadhwa-rtgwg-bng-cups-
   01.txt. This document discusses requirements for protocol between
   subscriber-management control-plane and user-plane for BNG to
   achieve separation.

Contents
   1. Introduction...................................................3
      1.1. Requirements Language.....................................3
   2. Requirements for "CUPS protocol"...............................3
      2.1. State Control Interface Requirements......................5
      2.2. Extensibility.............................................8
      2.3. Scalability and Performance...............................9
      2.4. Transport Protocol.......................................10
      2.5. In-band Control Channel Requirements.....................10
      2.6. Resiliency...............................................12
      2.7. Security.................................................13
   3. "CUPS protocol" candidate.....................................13
   4. Security Considerations.......................................14
   5. IANA Considerations...........................................14

Wadhwa, et al.          Expires April 22, 2019                 [Page 2]
Internet-Draft        Architecture for BNG CUPS            October 2018
Show full document text