VxLAN Extension Requirement for Signaling Exchange Between Control and User Plane of vBras
draft-huang-nvo3-vxlan-extension-for-vbras-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-01
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)
NVO3                                                       L. Huang, Ed.
Internet-Draft                                                     S. Hu
Intended status: Informational                              China Mobile
Expires: September 2, 2017                                 March 1, 2017

 VxLAN Extension Requirement for Signaling Exchange Between Control and
                          User Plane of vBras
             draft-huang-nvo3-vxlan-extension-for-vbras-00

Abstract

   This document briefly describes the architecture of control plane and
   user plane separated BRAS and the VxLAN extension requirement for
   Signaling Exchange between control plane and user plane.  It also
   describes some possible solutions.

Status of This Memo

   This Internet-Draft is submitted to IETF 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 September 2, 2017.

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.

Huang & Hu              Expires September 2, 2017               [Page 1]
Internet-Draft        vxlan-extension-for-vbras-00            March 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Requirement . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Analysis on solutions . . . . . . . . . . . . . . . . . . . .   4
     4.1.  VxLAN header solution . . . . . . . . . . . . . . . . . .   4
     4.2.  Combination of VxLAN and NSH  . . . . . . . . . . . . . .   5
     4.3.  Assign VNIs for every port  . . . . . . . . . . . . . . .   5
     4.4.  Summury of these soluitlons . . . . . . . . . . . . . . .   5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   For migration of vBRAS, one way is separating the control and user
   plane of traditional BRAS.  Control plane is deployed in centrolized
   cloud DC and user plane is fulfilled by high performance hardware
   device, e.g. router, switch, etc.  VxLAN is used to transfer some of
   signaling packets between CP and user UP.  For carrying information
   of access user VxLAN need to be extended or combined with other
   protocols/mechanisms.

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.  Requirement

   The architecture of C/U separated BRAS is shown as the following
   figure.

Huang & Hu              Expires September 2, 2017               [Page 2]
Internet-Draft        vxlan-extension-for-vbras-00            March 2017

                   +----------------------------------+
                   |                                  |
                   |              BRAS-CP             |
                   |                                  |
                   +--+--------------+--------------+-+
                      |              |              |
            Signaling |   Management | Configuration|
            Interface |   Interface  |    Interface |
                |     |       |      |        |     |
              VxLAN   |    OpenFlow  |      NETCONF |
                      |              |              |
                   +--+--------------+--------------+-+
                   |                                  |
Show full document text