Requirements for Control Plane and User Plane Separated BNG Protocol
draft-cuspdt-rtgwg-cusp-requirements-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-02-26 (latest revision 2017-10-26)
Stream (None)
Intended RFC status (None)
Formats 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)
rtgwg                                                              S. Hu
Internet-Draft                                                     R. Gu
Intended status: Informational                              China Mobile
Expires: August 30, 2018                                   Victor. Lopez
                                                              Telefonica
                                                               Jun. Song
                                                           Michael. Wang
                                                                  Huawei
                                                       February 26, 2018

  Requirements for Control Plane and User Plane Separated BNG Protocol
                draft-cuspdt-rtgwg-cusp-requirements-01

Abstract

   This document introduces the Control Plane and User Plane separated
   BNG architecture and defines a set of associated terminology.  What's
   more, this document focuses on defining a set of protocol
   requirements for the BNG-CP and BNG-UPs communication in the Control
   Plane and User Plane Separated BNG.

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 August 30, 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
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Hu, et al.               Expires August 30, 2018                [Page 1]
Internet-Draft            Requirements for CUSP            February 2018

   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.  Concept and Terminology . . . . . . . . . . . . . . . . . . .   3
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  CU Separated BNG Model  . . . . . . . . . . . . . . . . . . .   3
     3.1.  Internal interfaces between the CP and UP . . . . . . . .   5
   4.  The usage of CU separation BNG protocol . . . . . . . . . . .   6
   5.  Control Plane and User Plane Separation Protocol Requirements   7
     5.1.  Transmit information tables . . . . . . . . . . . . . . .   7
     5.2.  Scalability . . . . . . . . . . . . . . . . . . . . . . .   7
     5.3.  Message Priority  . . . . . . . . . . . . . . . . . . . .   7
     5.4.  Reliability . . . . . . . . . . . . . . . . . . . . . . .   8
     5.5.  Support for Secure Communication  . . . . . . . . . . . .   8
     5.6.  Version negotiation . . . . . . . . . . . . . . . . . . .   8
     5.7.  Capability Exchange . . . . . . . . . . . . . . . . . . .   9
     5.8.  CP primary/backup capability  . . . . . . . . . . . . . .   9
     5.9.  Event Notification  . . . . . . . . . . . . . . . . . . .   9
     5.10. Query Statistics  . . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   BNG is an Ethernet-centric IP edge router, and the aggregation point
   for the user traffic.  To provide centralized session management,
   flexible address allocation, high scalability for subscriber
   management capacity, and cost-efficient redundancy, the CU separated
   BNG is introduced [TR-384].  The CU separated Service Control Plane
   could be virtualized and centralized, which is responsible for user
   access authentication and setting forwarding entries to user planes.
   The routing control and forwarding plane, i.e. BNG user plane
   (local), could be distributed across the infrastructure.

   This document introduces the Control Plane and User Plane separated
   BNG architecture and modeling.  This document also defines the
Show full document text