@techreport{wadhwa-rtgwg-bng-cups-protocol-requirements-02,
    number =    {draft-wadhwa-rtgwg-bng-cups-protocol-requirements-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-wadhwa-rtgwg-bng-cups-protocol-requirements/02/},
    author =    {Sanjay Wadhwa and Praveen Muley and Rajesh Shinde and Jonathan Newton and Ryan Hoffman and Subrat Pani},
    title =     {{Requirements for Protocol between Control and User Plane on BNG}},
    pagetotal = 19,
    year =      2019,
    month =     mar,
    day =       11,
    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},
}