Requirements for Protocol between Control and User Plane on BNG
draft-wadhwa-rtgwg-bng-cups-protocol-requirements-02

Document Type Expired Internet-Draft (individual)
Last updated 2019-09-12 (latest revision 2019-03-11)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-wadhwa-rtgwg-bng-cups-protocol-requirements-02.txt

Abstract

Traditionally, the BNG provides aggregation of fixed access nodes (such as DSLAM and OLTs) over Ethernet and provides subscriber management and traffic management functions for residential subscribers. The BNG has however evolved to become a multi-access edge device that also provides termination of subscribers over fixed-wireless and hybrid access. An overall architecture and interfaces required between separated control and user-plane for a multi-access BNG are described in draft-wadhwa-rtgwg-bng-cups- 01.txt. This document discusses requirements for protocol between subscriber-management control-plane and user-plane for BNG to achieve separation. Contents 1. Introduction...................................................3 1.1. Requirements Language.....................................3 2. Requirements for "CUPS protocol"...............................3 2.1. State Control Interface Requirements......................5 2.2. Extensibility.............................................8 2.3. Scalability and Performance...............................9 2.4. Transport Protocol.......................................10 2.5. In-band Control Channel Requirements.....................10 2.6. Resiliency...............................................12 2.7. Security.................................................13 3. "CUPS protocol" candidate.....................................13 4. Security Considerations.......................................14 5. Management Interface Requirements.............................14 6. IANA Considerations...........................................15 7. References....................................................15 7.1. Normative References.....................................15 7.2. Informative References...................................16

Authors

Sanjay Wadhwa (sanjay.wadhwa@nokia.com)
Praveen Muley (praveen.muley@nokia.com)
Rajesh Shinde (rajesh.a.shinde@ril.com)
Jonathan Newton (jonathan.newton@vodafone.com)
Ryan Hoffman (ryan.hoffman@telus.com)
Subrat Pani (spani@juniper.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)