Requirements for BNG Control-plane And User-plane Separation
draft-cups-rtgwg-cu-separation-requirement-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-08
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)
Bcause Workgroup                                                   T. Yu
Internet-Draft                                             March 8, 2019
Intended status: Informational
Expires: September 9, 2019

      Requirements for BNG Control-plane And User-plane Separation
             draft-cups-rtgwg-cu-separation-requirement-00

Abstract

   This document aims to abstract reqruriment of an extensible and
   flexible Control Plane (CP) and User Plane (UP) Separated BNG
   Architecture.

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 September 9, 2019.

Copyright Notice

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

Yu                      Expires September 9, 2019               [Page 1]
Internet-Draft          Requirements for BNG CUSP             March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Specification of Requirements . . . . . . . . . . . . . . . .   2
   3.  CU Seperation Basic Model . . . . . . . . . . . . . . . . . .   3
   4.  Protocol Independent Relay (PIR)  . . . . . . . . . . . . . .   3
   5.  Generic-Service Flow Protocol (GSF) . . . . . . . . . . . . .   4
   6.  Management Interface  . . . . . . . . . . . . . . . . . . . .   8
   7.  Resiliency  . . . . . . . . . . . . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   10. Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The architecture aims to decouple CP and UP.

   CP focus on protocol signaling processing, service info management,
   and communication with external servers (e.g.  Radius, DHCP servers).

   Up focus on packet forwarding based on forwarding instructions from
   CP.

   CUPS architecture brings significant benefits below:

   o  Simplified management: UP is simplified focus on forwarding
      behavior.  Interactions with service platforms are decoupled to
      CP.

   o  Higher Resiliency: CPUS architecture allows CP inter-site
      resiliency and UP multi-homing active-active resiliency.

   o  Fast service provisioning: with a highly abstracted service based
      interface between CP and UP, CUPS architecture allows fast
      innovation on CP with minimum changes on UP.

   o  Higher IP address utilization: As IP address management
      centralized into CP, CP can have the intelligence to optimize the
      best subnet allocated to UP.

2.  Specification of Requirements

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Yu                      Expires September 9, 2019               [Page 2]
Internet-Draft          Requirements for BNG CUSP             March 2019

3.  CU Seperation Basic Model

   To support communication between the Control Plane and User Plane,
   several interfaces are involved.  Figure 1 illustrates the three
   communication interfaces between CP and UP BNG.

                     +----------------------------------+
                     |                                  |
                     |               BNG-CP             |
                     |                                  |
                     +--+--------------+--------------+-+
                        |              |             |
                  1.PIR |         2.GSF|   3.Magment |
                        |              |             |
Show full document text