Architecture for Control Plane and User Plane Separated BNG
draft-cuspdt-rtgwg-cu-separation-bng-architecture-02

Document Type Active Internet-Draft (individual)
Last updated 2018-10-22
Stream (None)
Intended RFC status (None)
Formats plain text xml 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. Hu
Internet-Draft                                                    F. Qin
Intended status: Informational                                     Z. Li
Expires: April 25, 2019                                     China Mobile
                                                                 T. Chua
                                    Singapore Telecommunications Limited
                                                        Donald. Eastlake
                                                                 Z. Wang
                                                                 J. Song
                                                                  Huawei
                                                        October 22, 2018

      Architecture for Control Plane and User Plane Separated BNG
          draft-cuspdt-rtgwg-cu-separation-bng-architecture-02

Abstract

   This document defines the new architecture of BNG devices with
   control plane (CP) and user plane (UP) separation.  BNG-CP is a user
   control management component while BNG-UP takes responsibility as the
   network edge and user policy implementation component.  Both BNG-CP
   and BNG-UP are core components for fixed broadband services and are
   deployed separately at different network layers.

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 April 25, 2019.

Copyright Notice

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

Hu, et al.               Expires April 25, 2019                 [Page 1]
Internet-Draft      Architecture for CU Separated BNG       October 2018

   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
   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
     1.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Concept and Terminology . . . . . . . . . . . . . . . . . . .   3
     2.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  CU separated BNG architecture . . . . . . . . . . . . . . . .   4
     3.1.  Internal interfaces between the CP and UP . . . . . . . .   6
   4.  The usage of CU separation BNG  . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   A BNG device is defined as an Ethernet-centric IP edge router, and
   the aggregation point for the user traffic.  It performs Ethernet
   aggregation and packet forwarding via IP/MPLS, and supports user
   management, access protocols termination, QoS and policy management,
   etc.

   This document introduce an architecture for BNG devices with control
   plane (CP) and user plane (UP) separation.  BNG-CP is a user control
   management component while BNG-UP takes responsibility as the network
   edge and user policy implementation components.  Both BNG-CP and BNG-
   UP are core components for fixed broadband services and deployed
   separately at different network layer in actual network.

1.1.  Motivation

   The rapid development of new services, such as 4K, IoT, etc, and
   increasing numbers of home broadband service users present some new
   challenges for BNGs such as:

Hu, et al.               Expires April 25, 2019                 [Page 2]
Internet-Draft      Architecture for CU Separated BNG       October 2018

      Low resource utilization: The traditional BNG acts as both a
Show full document text