Architecture for Control and User Plane Separation on BNG
draft-wadhwa-rtgwg-bng-cups-02

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                                    Nokia
Expires: April 21, 2019                                       R. Shinde
                                                           Reliance Jio
                                                              J. Newton
                                                               Vodafone
                                                             R. Hoffman
                                                                  TELUS
                                                               P. Muley
                                                                  Nokia
                                                            Subrat Pani
                                                       Juniper Networks
                                                           Oct 21, 2018

         Architecture for Control and User Plane Separation on BNG
                    draft-wadhwa-rtgwg-bng-cups-02.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 January 22, 2019.

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

Copyright Notice

   Copyright (c) 2018 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
   (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

   This document discusses separation of subscriber-management control
   plane and data-plane for BNG. 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. Therefore,
   this document proposes interfaces between control and user-plane of
   a BNG that can support multi-access BNG.

Table of Contents

   1. Introduction...................................................3
      1.1. Requirements Language.....................................3
   2. CUPS for BNG...................................................3
      2.1. Convergence...............................................6
   3. Interfaces for CUPS............................................7
      3.1. In-band Signaling Channel.................................7
      3.2. State Control Interface...................................8
         3.2.1. Session level state management.......................9
         3.2.2. Session level event notifications...................14
         3.2.3. Node level management...............................15

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

         3.2.4. Node level event notifications......................16
      3.3. Management Interface.....................................17
   4. Protocol Selection for CUPS Interfaces........................17
Show full document text