Control and User Plane Separation Architecture of BNG
draft-gu-nfvrg-cloud-bng-architecture-01

Document Type Active Internet-Draft (individual)
Last updated 2017-07-02
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)
NFVRG                                                              R. Gu
Internet-Draft                                                     S. Hu
Intended status: Informational                              China Mobile
Expires: January 3, 2018                                    July 2, 2017

         Control and User Plane Separation Architecture of BNG
                draft-gu-nfvrg-cloud-bng-architecture-01

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 componenet.  Both BNG-CP
   and BNG-UP are core components for fixed broadband services and
   deployed separately at different network layer in actual network.

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 http://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 January 3, 2018.

Copyright Notice

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

Gu & Hu                  Expires January 3, 2018                [Page 1]
Internet-Draft       C/U Separated BNG Architecture            July 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Definition of terms . . . . . . . . . . . . . . . . . . . . .   2
   4.  C/U separated BNG architecture  . . . . . . . . . . . . . . .   3
   5.  C/U separated BNG use case  . . . . . . . . . . . . . . . . .   4
   6.  Advantages of C/U seperated BNG . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

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

   The basic idea of control plane and user plane separation is to
   extract and centralize the user management function of multiple BNG
   devices forming a separate and concentrated CP, while UP takes
   function as traditional router's control plane and BNG forwarding
   plane.  Thus a BNG is constructed of CP and UP which is benefit in
   cloud-based BNG with the advantages of resource utilization
   improvement, resource control centralization, new service rapid
   provision and so on.

2.  Terminology

   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 [RFC2119].

3.  Definition of terms

   AAA:Authentication Authorization Accounting

   BNG:Broadband Network Gateway

   CP:Control Plane

   DHCP:Dynamic Host Configuration Protocol

Gu & Hu                  Expires January 3, 2018                [Page 2]
Internet-Draft       C/U Separated BNG Architecture            July 2017

   MANO:Management and Orchestration

   NFV:Network Function Virtualization

   PPPoE:Point to Point Protocol over Ethernet
Show full document text