idnits 2.17.1 draft-cuspdt-rtgwg-cu-separation-bng-protocol-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 2399 has weird spacing: '... s-cusp tbd...' -- The document date (April 30, 2019) is 1821 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2863' is defined on line 2659, but no explicit reference was found in the text ** Obsolete normative reference: RFC 793 (Obsoleted by RFC 9293) Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT S. Hu 2 Intended status: Proposed Standard China Mobile 3 D. Eastlake 4 M. Chen 5 Huawei Technologies 6 F. Qin 7 Z. Li 8 China Mobile 9 J. Song 10 Huawei Technologies 11 T. Chua 12 Singapore Telecommunications 13 Expires: October 29, 2019 April 30, 2019 15 Control-Plane and User-Plane Separation BNG 16 Simple Control Channel Protocol 17 draft-cuspdt-rtgwg-cu-separation-bng-protocol-05.txt 19 Abstract 21 This document specifies the Simple Control Plane (CP) and User Plane 22 (UP) Separation Broadband Network Gateway (BNG) control channel 23 Protocol (S-CUSP) for communications between a CP and a UP. S-CUSP is 24 designed to be flexible and extensible so as to easily allow for the 25 addition of further messages and data items, should requirements be 26 expressed in the future. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Distribution of this document is unlimited. Comments should be sent 34 to the authors or the RGTWG working group mailing list: 35 rtgwg@ietf.org. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF), its areas, and its working groups. Note that 39 other groups may also distribute working documents as Internet- 40 Drafts. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 The list of current Internet-Drafts can be accessed at 48 http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft 49 Shadow Directories can be accessed at 50 http://www.ietf.org/shadow.html. 52 Table of Contents 54 1. Introduction............................................5 56 2. Terminology.............................................6 57 2.1 Acronyms...............................................6 59 3. Protocol Overview.......................................8 60 3.1 S-CUSP Configuration...................................8 61 3.2 S-CUSP Session Establishment...........................9 62 3.3 Overview of S-CUSP Procedures..........................9 63 3.4 Network Resource Report...............................11 64 3.5 BNG Access Procedures.................................11 65 3.5.1 IPoE Access.........................................12 66 3.5.2 PPPoE Access........................................13 67 3.5.3 L2TP LAC Access.....................................14 68 3.5.4 L2TP LNS Access.....................................14 69 3.5.5 L2TP LTS Access.....................................16 70 3.6 Setting the User's QoS Information....................16 71 3.7 CP and UP Synchronization.............................17 72 3.8 CGN Address Allocation................................18 74 4. S-CUSP Message Formats.................................19 75 4.1 Common Message Header.................................19 76 4.1.1 Control Messages....................................20 77 4.1.2 Table Messages......................................20 78 4.1.3 Resource Reporting Message..........................20 79 4.1.4 Event Reporting Message.............................20 80 4.1.5 Vendor Message......................................21 81 4.1.6 Resource Allocation Messages........................21 82 4.2 Common Message TLV Format.............................21 83 4.3 Basic Data Fields.....................................22 84 4.4 Sub-TLV Format and Specific Sub-TLVs..................23 85 4.4.1 VRF-Name............................................23 86 4.4.2 Ingress-QoS-Profile.................................23 87 4.4.3 Egress-QoS-Profile..................................24 88 4.4.4 User-ACL-Policy.....................................24 89 4.4.5 Multicast-Profile-v4................................24 90 4.4.6 Multicast-Profile-v6................................24 91 4.4.7 Ingress-CAR.........................................24 92 4.4.8 Egress-CAR..........................................25 93 4.4.9 NAT-Instance........................................25 94 4.4.10 Pool-Name..........................................25 95 4.4.11 If-Desc............................................26 97 5. Basic TLVs.............................................27 98 5.1 Interface Information TLV.............................27 99 5.2 Basic User Information TLVs...........................29 100 5.2.1 Basic User Information TLV..........................29 101 5.2.2 User PPP Information TLV............................31 102 5.3 User IPv4 Information TLV.............................32 104 Table of Contents (continued) 106 5.4 User IPv6 Information.................................33 107 5.5 User QoS Policy Information TLV.......................34 108 5.6 Routing Table TLVs....................................35 109 5.6.1 IPv4 Routing Information TLV........................35 110 5.6.2 IPv6 Routing Information TLV........................36 111 5.7 Static User Information TLVs..........................37 112 5.7.1 Static IPv4 User Information TLV....................38 113 5.7.2 Static IPv6 User Information TLV....................39 114 5.8 L2TP User Information TLVs............................40 115 5.8.1 L2TP-LAC User Information TLV.......................40 116 5.8.2 L2TP-LNS User Information TLV.......................40 117 5.8.3 L2TP-LAC Tunnel TLV.................................41 118 5.8.4 L2TP-LNS Tunnel TLV.................................42 119 5.9 NAT User Information TLV..............................42 120 5.10 Vendor Defined TLV...................................43 122 6. Control TLVs...........................................45 123 6.1 Hello TLV.............................................45 124 6.2 Error Information TLV.................................46 126 7. Resource Reporting TLVs................................47 127 7.1 Interface Resource Information TLV....................47 128 7.2 UP Board Status Report Information TLV................47 130 8. Event TLVs.............................................49 131 8.1 User Traffic Statistics Report TLV....................49 132 8.2 User Detection Result Report TLV......................50 133 8.3 User Basic Table Operation Result TLV.................51 135 9. Resource Allocation TLVs...............................52 136 9.1 Request Address Allocation TLV........................52 137 9.2 Address Assignment Response TLV.......................52 138 9.3 Address Renewal Request TLV...........................53 139 9.4 Address Renewal Response TLV..........................54 140 9.5 Address Release Request TLV...........................54 141 9.6 Address Release Response TLV..........................55 143 10. Implementation Status.................................56 144 10.1 Implementations......................................56 145 10.1.1 Huawei Technologies................................56 146 10.1.2 ZTE................................................57 147 10.1.3 H3C................................................57 148 10.2 Hackathon............................................57 149 10.3 EANTC Testing........................................58 151 11. Security Considerations...............................59 153 12. IANA Considerations...................................60 154 12.1 Service Name and Port Number.........................60 156 Table of Contents (continued) 158 12.2 S-CUSP Parameters....................................60 159 12.2.1 Message Types......................................60 160 12.2.2 TLV Types..........................................61 161 12.2.3 TLV Operation Codes................................62 162 12.2.4 Sub-TLV Types......................................62 163 12.2.5 ERRID Codes........................................63 165 Contributors..............................................65 167 Normative References......................................66 168 Informative References....................................66 170 Authors' Addresses........................................68 172 1. Introduction 174 A fixed network Broadband Network Gateway (BNG) is an Ethernet- 175 centric IP edge router, and the aggregation point for user traffic. 176 To provide centralized session management, flexible address 177 allocation, high scalability for subscriber management capacity, and 178 cost-efficient redundancy, the Control/User (CU) separated BNG 179 framework is described in [TR-384]. The CU separated Service Control 180 Plane (CP), which is responsible for user access authentication and 181 setting forwarding entries in User Planes (UPs), can be virtualized 182 and centralized. The routing control and forwarding plane, i.e. the 183 BNG user plane (local), can be distributed across the infrastructure. 184 Other structures can also be supported such as both CP and UP being 185 virtual or both being physical. 187 This document specifies the simple CU Separation BNG control channel 188 Protocol (S-CUSP) for communications between a BNG Control Plane (CP) 189 and a set of User Planes (UPs). S-CUSP is designed to be flexible 190 and extensible so as to easily allow for additional messages and data 191 items, should further requirements be expressed in the future. 193 2. Terminology 195 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 196 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 197 "OPTIONAL" in this document are to be interpreted as described in BCP 198 14 [RFC2119] [RFC8174] when, and only when, they appear in all 199 capitals, as shown here. 201 2.1 Acronyms 203 ACK: Acknowledgement message. 205 BNG: Broadband Network Gateway. A broadband remote access server 206 (BRAS (BRoadband Access Server), B-RAS or BBRAS) routes traffic 207 to and from broadband remote access devices such as digital 208 subscriber line access multiplexers (DSLAM) on an Internet 209 Service Provider's (ISP) network. BRAS can also be referred to 210 as a Broadband Network Gateway (BNG). 212 BRAS: BRoadband Access Server (BNG). 214 CAR: Committed Access Rate. 216 CBS: Committed Burst Size. 218 CGN: Carrier Grade NAT. 220 Ci: Control Interface. 222 CIR: Committed Information Rate. 224 CP: Control Plane. CP is a user control management component which 225 supports the management of the UP's resources such as the user 226 entry and forwarding policy. 228 CU: Control-plane / User-plane. 230 CUSP: Control and User Plane Separation Protocol. 232 DEI: Drop Eligibility Indicator. A bit in a VLAN tag after the 233 priority and before the VLAN ID. (This bit was formerly the CFI 234 (Canonical Format Indicator).) 236 IPoE: IP over Ethernet. 238 L2TP: Layer 2 Tunneling Protocol [RFC2661]. 240 LAC: L2TP Access Concentrator 241 LNS: L2TP Network Server 243 Mi: Management Interface. 245 MSS: Maximum Segment Size. 247 MRU: Maximum Receive Unit. 249 NAT: Network Address Translation [RFC3022]. 251 ND: Neighbor Discovery. 253 PBS: Peak Burst Size. 255 PD: Prefix Delegation. 257 PIR: Peak Information Rate. 259 PPP: Point to Point Protocol [RFC1661]. 261 PPPoE: PPP over Ethernet. 263 S-CUSP: Simple Control and User Plane Separation Protocol. 265 Si: Service Interface. 267 TLV: Type, Length, Value. See Section 4.2. 269 UP: User Plane. UP is a network edge and user policy implementation 270 component. The traditional router's Control Plane and Forwarding 271 Plane are both preserved on BNG devices in the form of a user 272 plane. 274 URPF: Unicast Reverse Path Forwarding. 276 user: Equivalent to "customer". 278 VRF: Virtual Routing and Forwarding. 280 3. Protocol Overview 282 This section shows example message exchanges. 284 3.1 S-CUSP Configuration 286 To support Control Plane and User Plane separation, as defined in 287 [SCUSP-architecture], three interfaces are defined. These are 288 referred to as the Control Interface (Ci), Service Interface (Si) and 289 Management Interface (Mi). 291 NETCONF [RFC6241] is the protocol used on the Management Interface 292 between a CP and UP. It is used to configure the parameters of the 293 Control Interface, Service Interface and the Access interfaces. The 294 parameters are defined in [SCUSP-YANG]. 296 UP CP 297 | | 298 | Configure Control Interface | 299 |<-----------via NETCONF-----------| 300 | | 301 | Configure Service Interface | 302 |<-----------via NETCONF-----------| 303 | | 304 | Configure Access Interfaces | 305 |<-----------via NETCONF-----------| 306 | | 307 | Configure QOS Template | 308 |<-----------via NETCONF-----------| 309 | | 311 Once the parameters are configured, a UP can start to establish S- 312 CUSP session(s) with the specified CP(s) through the S-CUSP Session 313 Establishment as defined Section 3.2 of this document. 315 3.2 S-CUSP Session Establishment 317 UP CP 318 | | 319 | TCP Session Establishment | 320 |<------------------------------->| 321 | | 322 | | 323 | HELLO (version, capability) | 324 |-------------------------------->| 325 | | 326 | | 327 | HELLO (version, capability) | 328 |<--------------------------------| 329 | | 331 The S-CUSP session establishment consists of two successive steps: 333 1) Establishment of a TCP [RFC793] connection (3-way handshake) 334 between the CP and the UP using port tbd1. 336 2) Establishment of a S-CUSP session over the TCP connection. 338 Once the TCP connection is established, the CP and the UP initialize 339 the S-CUSP session during which the version negotiation is performed. 340 The version information is carried within Hello messages (see Section 341 6.2). If the S-CUSP session establishment phase fails because the CP 342 or UP disagree on the version parameters or one of the CP or UP does 343 not answer after the expiration of the establishment timer. When the 344 S-CUSP session establishment fails, the TCP connection is promptly 345 closed. 347 3.3 Overview of S-CUSP Procedures 349 The five sequences below give a high level view of the S-CUSP message 350 sequences. These sequences are covered in more detail below as 351 indicated. 353 UP CP 355 1. 356 | UP reports the Statistic INFO | 357 |-----to CP via S-CUSP---------------->| 358 | | 359 | UP reports the Event INFO | 360 |-----to CP via S-CUSP---------------->| 361 | | 362 | UP reports Resource INFO | 363 |-----to CP via S-CUSP---------------->| 364 | | 366 1. See Sections 3.4 and 4.1.3 for more details on Resource reporting. 367 See Section 4.1.4 for more details on Event reporting. Traffic 368 statistics are also reported using the Event message. 370 2. 371 | UP relays User Dial-up Request | 372 |-----to CP via Si-------------------->| 373 | | 374 | CP sends User Dial-up Response | 375 |<----to UPs via Si--------------------| 376 | | 378 2. This interaction is via the Service Interface and corresponds to 379 the initial interaction in the message sequence charged in the 380 sub-sections of Section 3.5. 382 3. 383 | CP sends User INFO | 384 |<----to UP via S-CUSP-----------------| 385 | | 386 | CP sends User Policy INFO | 387 |<----to UP via S-CUSP-----------------| 388 | | 389 | CP sends Route INFO | 390 |<----to UP via S-CUSP-----------------| 391 | | 392 | CP sends Tunnel INFO | 393 |<----to UP via S-CUSP-----------------| 394 | | 396 3. See Section 4.1.2 for more detail on CP messages updating UP 397 tables. 399 4. 400 | CGN Address Allocation via S-CUSP | 401 |<------------------------------------>| 402 | | 404 4. See Sections 3.8 and 4.1.8 for more detail on CGN Address 405 Allocation. 407 5. 408 | Data Synchronization via S-CUSP | 409 |<------------------------------------>| 410 | | 412 5. See Sections 3.7 and 4.1.1 for more detail on CP and UP 413 Synchronization. 415 3.4 Network Resource Report 417 Once an S-CUSP session is established between a CP and an UP. The UP 418 will begin to report the status/attributes of its slots, interfaces, 419 and sub-interfaces. 421 UP CP 422 | | 423 | Slot attributes report | 424 | via S-CUSP | 425 |-------------------------------->| 426 | | 427 | Port attributes report | 428 | via S-CUSP | 429 |-------------------------------->| 430 | | 431 | Sub-interface attributes report | 432 | via S-CUSP | 433 |-------------------------------->| 434 | | 436 Details of the Resource Report Messages can be found in Sections 437 4.2.3 and 7. 439 3.5 BNG Access Procedures 441 The subsection below give an overview of various "dial up" 442 interactions over the Service Interface followed by the setting of 443 various informatiion in the UP by the CP using S-CUSP over the 444 Control Interface. 446 3.5.1 IPoE Access 448 UP CP 449 | | 450 | DHCP Negotiation Messages | 451 |<-----------via Si-------------------->| 452 | | 453 | CP sends USER_BASEC_INFO | 454 |<---to UPs via S-CUSP------------------| 455 | | 456 | CP sends USER_POLICY_INFO | 457 |<---to UP via S-CUSP-------------------| 458 | | 459 | CP sends USER_IPV4/6_INFO | 460 |<---to UPs via S-CUSP------------------| 461 | | 462 | CP sends ROUTEV4/6 INFO | 463 |<---to UPs via S-CUSP------------------| 464 | | 465 | UP reports USER_DETECT_RESULT_INFO | 466 |----to CP via S-CUSP------------------>| 467 | | 468 | UP reports USER_TRAFFIC_INFO | 469 |----to CP via S-CUSP------------------>| 470 | | 472 3.5.2 PPPoE Access 474 UP CP 475 | | 476 | PPPoE Negotiation Messages | 477 |<-----------via Si-------------------->| 478 | | 479 | LCP Negotiation Messages | 480 |<-----------via Si-------------------->| 481 | | 482 | User Authentication Messages | 483 |<-----------via Si-------------------->| 484 | | 485 | IPCP Negotiation Messages | 486 |<-----------via Si-------------------->| 487 | | 488 | CP sends USER_BASEC_INFO | 489 |<----to UP via S-CUSP------------------| 490 | | 491 | CP sends USER_POLICY_INFO | 492 |<----to UP via S-CUSP------------------| 493 | | 494 | CP sends USER_IPV4/6_INFO | 495 |<----to UP via S-CUSP------------------| 496 | | 497 | CP sends ROUTEV4/6 INFO | 498 |<----to UP via S-CUSP------------------| 499 | | 500 | CP sends USER_PPP_INFO | 501 |<----to UP via S-CUSP------------------| 502 | | 503 | UP reports USER_DETECT_RESULT_INFO| 504 |-----to CP via S-CUSP----------------->| 505 | | 506 | UP reports USER_TRAFFIC_INFO | 507 |-----to CP via S-CUSP----------------->| 508 | | 510 3.5.3 L2TP LAC Access 512 UP CP LNS 513 | | | 514 | PPPoE Negotiation Messages | | 515 |<-----------via Si------------------>| | 516 | | | 517 | LCP Negotiation Messages | | 518 |<-----------via Si------------------>| | 519 | | | 520 | User Authentication Messages | | 521 |<-----------via Si------------------>| | 522 | | | 523 | LAC Tunnel Negotiation Messages | | 524 | -----------via Si------------------>| | 525 | /\ | | 526 | || forward | | 527 | \/ | | 528 | ------------------ LAC Tunnel Negotiation ---------->| 529 | | | 530 | LAC Session Negotiation Messages | | 531 |<-----------via Si------------------>| | 532 | /\ | | 533 | || forward | | 534 | \/ | | 535 | ------------------ LAC Session Negotiation --------->| 536 | | | 537 | CP sends USER_BASIC_INFO | | 538 |<----to UP via S-CUSP----------------| | 539 | | | 540 | CP sends LAC_TUNNEL_INFO | | 541 |<----to UP via S-CUSP----------------| | 542 | | | 543 | CP sends LAC_USER_INFO | | 544 |<----to UP via S-CUSP----------------| | 545 | | | 546 | | | 547 | UP reports USER_TRAFFIC_INFO | | 548 |-----to CP via S-CUSP--------------->| | 549 | | | 551 3.5.4 L2TP LNS Access 552 |UP CP| LAC| 553 | LNS Tunnel Negotiation Messages | | 554 |<-----------via Si------------------>| | 555 | /\ | | 556 | || forward | | 557 | \/ | | 558 | ------------------ LNS Tunnel Negotiation --------->| 559 | | | 560 | LNS Session Negotiation Messages | | 561 |<-----------via Si------------------>| | 562 | /\ | | 563 | || forward | | 564 | \/ | | 565 | ------------------ LNS Session Negotiation -------->| 566 | | | 567 | LCP Negotiation Messages | | 568 |<-----------via Si------------------>| | 569 | | | 570 | User Authentication Messages | | 571 |<-----------via Si------------------>| | 572 | | | 573 | IPCP Negotiation Messages | | 574 |<-----------via Si------------------>| | 575 | | | 576 | CP sends LNS_TUNNEL_INFO | | 577 |<----to UP via S-CUSP----------------| | 578 | | | 579 | CP sends USER_BASEC_INFO | | 580 |<----to UP via S-CUSP----------------| | 581 | | | 582 | CP sends USER_IPV4/6_INFO | | 583 |<----to UP via S-CUSP----------------| | 584 | | | 585 | CP sends ROUTEV4/6 INFO | | 586 |<----to UP via S-CUSP----------------| | 587 | | | 588 | CP sends USER_PPP_INFO | | 589 |<----to UP via S-CUSP----------------| | 590 | | | 591 | CP sends LNS_USER_INFO | | 592 |<----to UP via S-CUSP----------------| | 593 | | | 594 | CP sends USER_POLICY_INFO | | 595 |<----to UP via S-CUSP----------------| | 596 | | | 597 | UP reports USER_DETECT_RESULT_INFO | | 598 |-----to CP via S-CUSP--------------->| | 599 | | | 600 | UP reports USER_TRAFFIC_INFO | | 601 |-----to CP via S-CUSP--------------->| | 603 3.5.5 L2TP LTS Access 605 UP CP LAC/LNS 606 | | | 607 | LAC/LTS Tunnel Negotiation Messages | | 608 |<-----------via Si------------------>| | 609 | /\ | | 610 | || forward | | 611 | \/ | | 612 | ------------------ LAC/LTS Tunnel Negotiation ----->| 613 | | | 614 | LAC/LTS Session Negotiation Messages| | 615 |<-----------via Si------------------>| | 616 | /\ | | 617 | || forward | | 618 | \/ | | 619 | ------------------ LAC/LTS Session Negotiation ---->| 620 | | | 621 | CP sends LAC_TUNNEL_INFO | | 622 |<----to UP via S-CUSP----------------| | 623 | | | 624 | CP sends LNS_TUNNEL_INFO | | 625 |<----to UP via S-CUSP----------------| | 626 | | | 627 | CP sends USER_BASEC_INFO | | 628 |<----to UP via S-CUSP----------------| | 629 | | | 630 | CP sends LAC_USER_INFO | | 631 |<----to UP via S-CUSP----------------| | 632 | | | 633 | CP sends LNS_USER_INFO | | 634 |<----to UP via S-CUSP----------------| | 635 | | | 637 3.6 Setting the User's QoS Information 638 UP CP AAA 639 | | | 640 | Configure QOS template | | 641 |<-----via NETCONF--------------------| | 642 | | | 643 | User dials up via Si | | 644 |<----------------------------------->| | 645 | | | 646 | CP sends USER_QOS_INFO | | 647 |<---to UPs via S-CUSP----------------| | 648 | |<--COA request--| 649 | CP sends USER_QOS_INFO | | 650 |<---to UPs via S-CUSP----------------| | 651 | | | 652 | UP sends ACK message | | 653 |----to CP via S-CUSP---------------->|--COA response->| 654 | | | 656 Once an S-CUSP session has been established, if a user's Quality of 657 Service (QoS) needs to be set dynamically, the CP initiate a NETCONF 658 session to configure the requested User's QoS template. Then the 659 user dials up via the Si, the CP sends the USER_BASIC_INFO message, 660 USER_IPV4_INFO message, and USER_ROUTEV4_INFO messages to the UP, the 661 UPs report the user detection results and user's traffic status. 663 Once the above process has been accomplished, the CP sends the 664 USER_QOS_AUTH_INFO message to the UPs; this message contains a 665 variety of objects that specify the set of constrains and attributes 666 for the user's required QoS. (The format of these QoS attributes 667 should be parallel to the QoS configuration templates.) 669 3.7 CP and UP Synchronization 671 Under some circumstances it is necessary to synchrnoize state between 672 the CP and UP, for example if a CP fails and the UP is switched to a 673 different CP. There may be multiple Resource INFO messages between 674 the Synchronization Begin and Synchronization End. 676 UP CP 677 | | 678 | CP sends Synchronization Request | 679 |<-----to UP via S-CUSP---------------| 680 | | 681 | UP sends Synchronization Begin | 682 |------to CP via S-CUSP-------------->| 683 | | 684 | UP reports Resource INFO | 685 |------to CP via S-CUSP-------------->| 686 | | 687 | UP sends Synchronization End | 688 |------to CP via S-CUSP-------------->| 689 | | 691 | UP sends NAT Address Renew Req. | 692 |------to CP via S-CUSP-------------->| 693 | | 694 | CP sends NAT Address Renew Res. | 695 |<-----to UP via S-CUSP---------------| 696 | | 698 | UP sends Synchronization Request | 699 |------to CP via S-CUSP-------------->| 700 | | 701 | CP sends Synchronization Begin | 702 |<-----to UP via S-CUSP---------------| 703 | | 704 | CP sends User/Route/Tunnel. INFO | 705 |<-----to UP via S-CUSP---------------| 706 | | 707 | CP sends Synchronization End | 708 |<-----to UP via S-CUSP---------------| 709 | | 711 3.8 CGN Address Allocation 713 UP CP 714 | | 715 | UP sends Address Allocation Req. | 716 |------to CP via S-CUSP-------------->| 717 | | 718 | CP sends Address Allocation Res. | 719 |<-----to UP via S-CUSP---------------| 720 | | 722 See Section 4.1.6 724 4. S-CUSP Message Formats 726 This section specifies the format of the common S-CUSP message 727 header, the format of the TLVs that appear in S-CUSP messages, the 728 format of the sub-TLVs that appear within the values of some TLVs, 729 and the format of some basic data fields. 731 An S-CUSP message consists of a common header followed by a variable- 732 length body consisting entirely of TLVs. Receiving an S-CUSP message 733 with a missing mandatory TLV MUST trigger an Error message (see 734 Section 5.6). Conversely, if a TLV is optional, the TLV may or may 735 not be present. 737 Network byte order is used for all multi-byte fields. 739 4.1 Common Message Header 741 Common header: 742 0 1 2 3 743 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 744 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 745 | Ver | Resv | Message-Type | Message-Length | 746 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 747 | Reserved | Transaction-ID | 748 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 750 S-CUSP Message Common Header 752 Ver (4 bits): The major version of the protocol. This document 753 specifies version 1. Different major versions of the 754 protocol may have significantly different message 755 structure and format except that the Ver field will 756 always be in the same place at the beginning of each 757 message. A successful S-CUSP session depends on the CP 758 and UP both using the same major version of the 759 protocol. 761 Resv (4 bits): Reserved. MUST be sent as zero and ignored on 762 receipt. 764 Message-Type (8 bits): The set of message types specified in this 765 document is listed in Section 12.2.1. 767 Message-Length (16 bits): Total length of the CUSP message 768 including the common header, expressed in number of 769 bytes as an unsigned integer. 771 Transaction ID (16 bits): This field is used to identify 772 requests. It is echoed back in any corresponding ACK / 773 response / Error message. 775 4.1.1 Control Messages 777 Control messages are listed below. 779 Type Name Notes and TLVs that can be carried 780 ---- ---- ------------------------------------ 781 1 Hello Capability negotiation. 782 2 Keepalive Keepalive. 783 3 Synch_Request Synchronization request. 784 4 Sync_Begin Synchronization starts. 785 5 Sync_Data Synchronization data: TLVs specified in 786 Section 5. 787 6 Sync_End End synchronization. 789 4.1.2 Table Messages 791 Table messages are listed below. 793 Type Name Notes and TLVs that can be carried 794 ---- ---- ------------------------------------ 795 7 Update_Request TLVs specified in Section 5. 796 8 Update_Response TLVs specified in Section 5. 798 4.1.3 Resource Reporting Message 800 The Resource Reporting message is as follows: 802 Type Name Notes and TLVs that can be carried 803 ---- ---- ------------------------------------ 804 9 Report Interface-Info, Board-Info. 806 4.1.4 Event Reporting Message 808 The Event Reporting message is as follows: 810 Type Name Notes and TLVs that can be carried 811 ---- ---- ------------------------------------ 812 10 Event Traffic-Info, Detect-Info. 814 4.1.5 Vendor Message 816 The Vendor message is as follows: 818 Type Name Notes and TLVs that can be carried 819 ---- ---- ------------------------------------ 820 11 Vendor Vendor-Defined, any other TLV(s) as 821 implemented by the vendor. 823 4.1.6 Resource Allocation Messages 825 The Resource Allocation messages are listed below. 827 Type Name Notes and TLVs that can be carried 828 ---- ---- ------------------------------------ 829 200 Addr_Allocation_Req Addr-Alloc-Req 830 201 Addr_Allocation_Ack Addr-Alloc-Resp 831 202 Addr_Renew_Req Addr-Renew-Req 832 203 Addr_Renew_Ack Addr-Renew-Resp 833 204 Addr_Release_Req Addr-Release-Req 834 205 Addr_Release_Ack Addr-Release-Resp 836 4.2 Common Message TLV Format 838 CUSP messages consist of the common header specified in Section 4.1 839 followed by TLVs formatted as specified in this section. 841 0 1 2 3 842 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 843 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 844 | Oper | TLV-Type | TLV-Length | 845 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 846 | Value | 847 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-... 849 Oper (4 bits): For Message-Types that indicate an operation on a 850 data set, the Oper field is interpreted as Update, 851 Delete, or Reserved as specified in Section 12.2.3. 852 For all other Message-Types, the Oper field MUST be 853 sent as zero and ignored on receipt. 855 TLV-Type (12 bits): The Type of a TLV, that is the meaning and 856 format of the Value part, are determined by the TLV- 857 Type of the TLV. See Section 12.2.2. 859 TLV-Length (2 bytes): The length of the Value portion of the TLV 860 in bytes as an unsigned integer. 862 Value (variable length): This is the value portion of the TLV 863 whose size is given by TLV-Length. 865 4.3 Basic Data Fields 867 This section specifies the binary format of several standard basic 868 data fields that are used within other data structures in this 869 specification. 871 STRING 872 0 to 255 octets. Will be encoded as a sub-TLV (see Section 873 4.4) to provide the length. 875 MAC-Addr 876 6 octets. Ethernet MAC Address. 878 IPv4 Address 879 8 octets. 4 octets of the IPv4 address value followed by a 880 4 octet address mask in the format XXX.XXX.XXX.XXX. 882 IPv6 Address 883 20 octets. 16 octets of IPv6 address followed by a 4 octet 884 integer n in the range of 0 to 128 which gives the address 885 mask as the one's complement of 2**(128-n) - 1. 887 VLAN ID 888 2 octets. As follows: 890 0 1 891 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 892 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 893 | PRI |D| VLAN-ID | 894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 896 PRI: Priority. Default value 7. 898 D: Drop Eligibility Indicator (DEI). Default value 0. 900 VLAN-ID: Unsigned integer in the range 1-4094. 902 4.4 Sub-TLV Format and Specific Sub-TLVs 904 In some cases, the Value portion of a TLV, as specified above, can 905 contain one or more Sub-TLVs formatted as follows: 907 0 1 2 3 908 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 909 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 910 | Type | Length | 911 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 912 | Value | 913 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-... 915 Type (2 bytes): The Type of a Sub-TLV, that is the meaning and 916 format of the Value part, are determined by the Type 917 of the TLV. Sub-TLV Types numbers have the same 918 meaning regardless of the TLV Type of the TLV within 919 which the Sub-TVL occurs. See Section 12.2.4. 921 Length (2 bytes): The length of the Value portion of the TLV in 922 bytes as an unsigned integer. 924 Value (variable length): This is the value portion of the TLV 925 whose size is given by Length. 927 The sub-TLVs currently specified are specified in the following 928 subsections. 930 4.4.1 VRF-Name 932 The name of the VRF (Virtual Routing and Forwarding instance) that 933 the BNG user accesses. Optional. 935 Sub-TLV Type: 1, VRF Name 936 Length: 1-255 octets. 937 Value: STRING. 939 4.4.2 Ingress-QoS-Profile 941 Indicates the upstream QoS Profile Name. Optional. 943 Sub-TLV Type: 2, Ingress QoS Profile Name 944 Length: 1-255 octets. 945 Value: STRING. 947 4.4.3 Egress-QoS-Profile 949 Indicates the downstream QoS Profile Name. Optional. 951 Sub-TLV Type: 3, Egress QoS Profile Name 952 Length: 1-255 octets. 953 Value: STRING. 955 4.4.4 User-ACL-Policy 957 Indicates the name of the ACL policy group to which the user belongs. 958 Optional. 960 Sub-TLV Type: 4, User ACL Policy Name 961 Length: 1-255 octets. 962 Value: STRING. 964 4.4.5 Multicast-Profile-v4 966 Name of the IPv4 multicast program list a user can order. Optional. 968 Sub-TLV Type: 5, Multicast Profile of IPv4. 969 Length: 1-255 octets. 970 Value: STRING. 972 4.4.6 Multicast-Profile-v6 974 Name of the IPv6 multicast program list a user can order. Optional. 976 Sub-TLV Type: 6, Multicast Profile of IPv6. 977 Length: 1-255 octets. 978 Value: STRING. 980 4.4.7 Ingress-CAR 982 Indicates the authorized upstream Committed Access Rate (CAR) 983 parameters. Optional. 985 Sub-TLV Type: 7, Ingress CAR. 986 Length: 16 Octets. 987 Value: The following four fields in the order given: 989 Name Type Description 990 ------ ------- --------------------------------- 991 CIR 4 bytes Guaranteed rate in bits/second. 992 PIR 4 bytes Burst rate in bits/second. 993 CBS 4 bytes The token bucket in bytes. 994 PBS 4 bytes Burst token bucket in bytes. 996 4.4.8 Egress-CAR 998 Indicates the authorized downstream Committed Access Rate (CAR) 999 parameters. Optional. 1001 Sub-TLV Type: 8, Egress CAR. 1002 Length: 16 Octets. 1003 Value: The following four fields in the order given: 1005 Name Type Description 1006 ------ ------- --------------------------------- 1007 CIR 4 bytes Guaranteed rate in bits/second. 1008 PIR 4 bytes Burst rate in bits/second. 1009 CBS 4 bytes The token bucket in bytes. 1010 PBS 4 bytes Burst token bucket in bytes. 1012 4.4.9 NAT-Instance 1014 Name of the Network Address Translation (NAT) Instance to which the 1015 user belongs. Optional. 1017 Sub-TLV Type: 9, NAT Instance Name. 1018 Length: 1-255 octets. 1019 Value: STRING. 1021 4.4.10 Pool-Name 1023 Indicates the name of the address pool to which the public network 1024 segment belongs. Optional. 1026 Sub-TLV Type: 10, IP Address Pool Name. 1027 Length: 1-255 octets. 1028 Value: STRING. 1030 4.4.11 If-Desc 1032 Description of an interface. Mandatory. 1034 Sub-TLV Type: 11, Interface Description 1035 Length: 12 1036 Value: Several fields structured as follows: 1038 0 1 2 3 1039 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1040 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1041 | If-Type 4 bytes | 1042 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1043 | Chassis | 1 byte 1044 +-+-+-+-+-+-+-+-+ 1045 | Slot | 1 byte 1046 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1047 | Port Information | 2 bytes 1048 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1049 | Sub-Port Number 4 bytes | 1050 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1052 If-Type: Interface Type: 1053 0 = Reserved, 1 = FE, 2 = GE, 3 = 10GE, 4 = 100GE, 5: Eth- 1054 Trunk, 6: Tunnel, 7: VE 1055 Chassis: Subrack Number 1056 Slot: Slot 1057 Port Information: 1058 If-Type = Physical, the Port Information consists of a 1-byte 1059 Physical Slot number followed by a 1-byte Physical port 1060 number. 1061 If-Type - virtual port, the Port Information consists of a 2 1062 byte logical number of the virtual interface. 1063 Sub-Port: Sub-port Number 1065 5. Basic TLVs 1067 This section describes basic TLVs. 1069 5.1 Interface Information TLV 1071 The Interface Information TLV can be used by a CP to control the 1072 access mode, authentication methods, and other related functions of 1073 an interface. 1075 The format of the Interface Information TLV value part is as below: 1077 0 1 2 3 1078 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1079 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1080 | If-Index | 1081 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1082 | Access-Mode | Auth-Method4 | Auth-Method6 | Reserved | 1083 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1084 | Flags | 1085 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1086 ~ sub-TLVs (optional) ~ 1087 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1089 Figure 5.1: Interface Information TLV 1091 Function: Service information about the user access interface 1092 on the BNG. 1093 TLV Type: 1 1094 TLV Length: variable 1096 TLV fields: 1097 If-Index: 4 bytes in length, a unique identifier of an interface 1098 of a BNG. 1099 Access-Mode: 1 byte in length, indicates the access mode of the 1100 interface; this document defines following values: 1101 0: Layer 2 subscriber; 1102 1: Layer 3 subscriber; 1103 2: Layer 2 leased line; 1104 3: Layer 3 leased line; 1105 4-255: Reserved. 1107 Auth-Method4: 1 byte in length, for IPv4 scenario, indicates the 1108 authentication on this interface; this field is defined 1109 as a bitmap, this document defines following values 1110 (other bits are reserved and MUST be sent as zero and 1111 ignored on receipt): 1112 0x1: PPPoE authentication; 1113 0x2: DOT1X authentication; 1114 0x4: Web authentication; 1115 0x8: Web fast authentication; 1116 0x10: Binding authentication. 1118 Auth-Method6: 1 byte in length, for IPv6 scenario, indicates the 1119 authentication on this interface; this field is defined 1120 as a bitmap, this document defines following values 1121 (other bits are reserved and MUST be sent as zero and 1122 ignored on receipt): 1123 0x1: PPPoE authentication; 1124 0x2: DOT1X authentication; 1125 0x4: Web authentication; 1126 0x8: Web fast authentication; 1127 0x10: Binding authentication; 1129 The flags field is defined as below: 1131 0 1 2 3 1132 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1134 | MBZ |Y|X|P|I|N|A|S|F| 1135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1137 Figure 5.2: Interface Flags 1139 Where: 1141 F (IPv4 Trigger) bit: Indicates whether IPv4 packets can trigger a 1142 subscriber go to online. 1143 1: enabled, 0: disabled. 1145 S (IPv6 Trigger) bit: Indicates whether IPv6 packets can trigger a 1146 subscriber go to online. 1147 1: enabled, 0: disabled. 1149 A (ARP Trigger) bit: Indicates whether ARP packets can trigger a 1150 subscriber go to online. 1151 1: enabled, 0: disabled. 1153 N (ND Trigger) bit: Indicates whether ND packets can trigger a 1154 subscriber go to online. 1155 1: enabled, 0: disabled. 1157 I (IPoE-Flow-Check): Used for UP detection. IPoE 1: Enable traffic 1158 detection. 0: Disable traffic detection. 1160 P (PPP-Flow-Check) bit: Used for UP detection. PPP 1: Enable traffic 1161 detection. 0: Disable traffic detection. 1163 X (ARP-Proxy) bit: 1: The interface is enabled with ARP proxy and can 1164 process ARP requests across different Port+VLANs. 1165 0: The ARP proxy is not enabled on the interface, and 1166 only the ARP requests of the same Port+VLAN are 1167 processed. 1169 Y (ND-Proxy) bit: 1: The interface is enabled with ND proxy and can 1170 process ND requests across different Port+VLANs. 1171 0: The ND proxy is not enabled on the interface, and only 1172 the ND requests of the same Port+VLAN are processed. 1174 MBZ: Reserved bits that MUST be sent as zero and ignored on receipt. 1176 5.2 Basic User Information TLVs 1178 The Basic User Information TLVs are defined for a CP to carry the 1179 basic information about a user to an UP. 1181 5.2.1 Basic User Information TLV 1183 The format of the Basic User Information TLV value part is as below: 1185 0 1 2 3 1186 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1188 | User ID | 1189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1190 | Session ID | 1191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1192 | User MAC | 1193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1194 | User MAC | Oper ID | Reserved | 1195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1196 | Access Type |Sub-access Type| Account Type | Address Family| 1197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1198 | C-VID | P-VID | 1199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1200 | Detect Times | Detect Interval | 1201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1202 | If-Index | 1203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1204 ~ sub-TLVs (optional) ~ 1205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1207 Figure 5.3: Basic User Information TLV 1209 Function: Basic information about a BNG user. 1210 TLV Type: 2 1211 TLV Length: variable in length; 1213 TLV Fields: 1214 Name Length Description 1215 -------------- ------ ---------------------- 1216 User-ID 4 bytes User ID. 1217 User-Mac MAC-Addr User MAC Address. 1218 Oper-ID 1 byte Indicates the ID of an operation performed 1219 by a user. This field is carried in the 1220 response from the UP. 1221 Session-ID 4 bytes Session ID of a PPPoE user. Zero for non- 1222 PPPoE user. 1223 Access-Type 1 byte See Section 5.2.1.1. 1224 Sub-Access-Type 1 byte Indicates whether PPP termination or PPP 1225 relay is used. 0: N/A 1: PPP2 on the LAC 1226 side: Termination, PPP on the LNS side 1227 Account-Type 1 byte IPv4/IPv6 charging: 0 separate charging: 1228 Collects statistics on IPv4 and IPv6 traffic 1229 of terminals independently. 1: Statistics 1230 and charging Collects statistics on IPv4 and 1231 IPv6 traffic of terminals. 1232 User-IP-Type 1 byte 1:IPv4 stack and 2:IPv6 stack 3: dual stack 1233 C-VID VLAN-ID Indicates the inner VLAN ID. The value 0 1234 indicates that the VLAN ID is invalid. The 1235 default value of PRI is 7, the value of DEI 1236 is 0, and the value of VID is 1~4094. The 1237 PRI value can also be obtained by parsing 1238 terminal packets. 1239 P-VID VLAN-ID Outer VLAN ID. The value 0 indicates that 1240 the VLAN ID is invalid. The format is the 1241 same as that the C-VID. 1242 Detect-Times 2 bytes Number of detection timeout times. The value 1243 0 indicates that no detection is performed. 1244 Detect-Interval 2 bytes Detection interval in seconds. 1245 If-Index 4 bytes Interface index. 1247 The Reserved field MUST be sent as zero and ignored on receipt. 1249 5.2.1.1 Access Types Table 1251 Value Meaning 1252 ----- --------- 1253 1 PPP access (PPP) 1254 2 PPP over Ethernet over ATM access (PPPoEoA) 1255 3 PPP over ATM access (PPPoA) 1256 4 PPP over Ethernet access (PPPoE) 1257 5 PPPoE over VLAN access (PPPoEoVLAN) 1258 6 PPP over LNS access (PPPoLNS) 1259 7 IP over Ethernet DHCP access (IPoE_DHCP) 1260 8 IP over Ethernet EAP authentication access (IPoE_EAP) 1261 9 IP over Ethernet Layer 3 access (IPoE_L3) 1262 10 IP over Ethernet Layer 2 Static access (IPoE_L2_STATIC) 1263 11 Layer 2 Leased Line access (L2_Leased_Line) 1264 12 Layer 2 VPN Leased Line access (L2VPN_Leased_Line) 1265 13 Layer 3 Leased Line access (L3_Leased_Line) 1266 14 Layer 2 Leased line Sub-User access 1267 (L2_Leased_Line_SUB_USER) 1268 15 L2TP LAC tunnel access (L2TP_LAC) 1269 16 L2TP LNS tunnel access (L2TP_LNS) 1271 5.2.2 User PPP Information TLV 1273 The User PPP Information TLV is defined to carry PPP information of a 1274 User, from a CP to an UP. 1276 The format of the TLV value part is as below: 1278 0 1 2 3 1279 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1281 | User ID | 1282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1283 | MSS | Reserved |M| 1284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1285 | MRU | Reserved | 1286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1287 | Magic Number | 1288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1289 | Peer Magic Number | 1290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1292 Figure 5.4: User PPP Information TLV 1294 Function: PPP [RFC1661] information for a BNG user. 1295 TLV Type: 3 1296 TLV Length: 20 bytes in length 1297 TLV Fields: 1298 Name Type Description 1299 -------------- ------ ---------------------- 1300 User-ID 4 bytes User ID. 1301 MSS-Value 2 bytes Indicates the MSS value. 1302 MSS-Enable 1 bit Indicates whether the MSS is enabled. 0: The 1303 function is disabled. 1: Enable 1304 MRU 2 bytes PPPoE local MRU. 1305 Magic-Number 4 bytes Local magic number in PPP negotiation 1306 packets. 1307 Peer-Magic-Number 4 bytes Remote peer magic number. 1309 The Reserved fields MUST be sent as zero and ignored on receipt. 1311 5.3 User IPv4 Information TLV 1313 The User IPv4 Information TLV is defined to carry IPv4 related 1314 information for a BNG user. 1316 The format of the TLV value part is as below: 1318 0 1 2 3 1319 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1321 | User ID | 1322 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1323 | User IPv4 Address | 1324 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1325 | Gateway IPv4 Address | 1326 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1327 | MTU | Reserved |U|E|W|P| 1328 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1329 ~ sub-TLVs ~ 1330 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1332 Figure 5.5: User IPv4 Information TLV 1334 Function: IPv4 information for a BNG user. 1335 TLV Type: 4 1336 TLV Length: variable 1338 TLV fields: 1339 Name Type Description 1340 -------------- ------ ---------------------- 1341 User-ID 4 bytes User ID. 1342 User-IPv4 IPv4 User IPv4 address. 1343 Gateway-IPv4 IPv4 User gateway. 1344 Portal Force 1 bit (P) Push advertisement switch, 0: off, 1: 1346 on. 1347 Web-Force 1 bit (W) IP4 Web push flag. 0: off, 1: on. 1348 Echo-Enable 1 bit (E) Compatible with PPP/ARP and the UP 1349 returns ARP Req or PPP Echo. 0: off, 1: on. 1350 IPv4-URPF 1 bit (U) Unicast Reverse Path Forwarding (URPF) 1351 flag of a user. 0: off, 1: on. 1352 MTU 2 bytes MTU value. The default value is 1500. 1353 VRF-Name Sub-TLV VRF name. 1355 The Reserved field MUST be sent as zero and ignored on receipt. 1357 5.4 User IPv6 Information 1359 The User IPv6 Information TLV is defined to carry IPv6 related 1360 information of a BNG user. 1362 The format of the TLV value part is as below: 1364 0 1 2 3 1365 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1366 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1367 | User ID | 1368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1369 ~ User PD-Address ~ 1370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1371 ~ Gateway ND-Address ~ 1372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1373 | User IANA Address | 1374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1375 | IPv6 Interface ID | 1376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1377 | IPv6 Interface ID (cont.) | 1378 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1379 | MTU | Reserved |U|E|W|P| 1380 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1381 ~ sub-TLVs (VRF Name sub-TLV) ~ 1382 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1384 Figure 5.6: User IPv6 Information TLV 1386 Function: IPv6 information for a BNG user. 1387 TLV Type: 5 1388 TLV Length: variable 1389 TLV fields: 1390 Name Type Description 1391 -------------- ------ ---------------------- 1392 User-ID 4 bytes User ID. 1393 PD-Address IPv6 Prefix Delegation (PD) address. 1394 ND-Address IPv6 Neighbor Discovery (ND) address. 1395 IANA-Address IPv6 IANA address. 1396 Interface-ID 8 bytes IPv6 interface ID. 1397 Portal Force 1 bit (P) Push advertisement switch, 0: off, 1: 1398 on. 1399 Web-Force 1 bit (W) IP6 Web push flag. 0: off, 1: on. 1400 Echo-Enable 1 bit (E) Compatible with PPP/ARP and the UP 1401 returns ARP Req or PPP Echo. 0: off, 1: on. 1402 IPv6-URPF 1 bit (U) User Reverse Path Forwarding (URPF) flag 1403 of a user. 0: off, 1: on. 1404 MTU 2 bytes MTU value. The default value is 1500. 1405 VRF-Name Sub-TLV VRF name. 1407 The Reserved field MUST be sent as zero and ignored on receipt. 1409 5.5 User QoS Policy Information TLV 1411 The format of the TLV value part is as follows: 1413 0 1 2 3 1414 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1415 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1416 | User ID | 1417 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1418 | I-Priority | E-Priority | Reserved | 1419 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1420 ~ sub-TLVs ~ 1421 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1423 Figure 5.7: User QoS Policy Information TLV 1425 Function: BNG user authorization information. 1426 TLV Type: 6 1427 TLV length: variable in length 1429 TLV Fields: 1430 Name Type Description 1431 -------------- ------ ---------------------- 1432 User-ID 4 bytes User ID. 1433 Ingress-Priority 1 byte Indicates the upstream priority. The value 1434 is 0~7. 1435 Egress-Priority 1 byte Indicates the downstream priority. The value 1436 is 0~7. 1438 Ingress-CAR Sub-TLV Upstream CAR. 1439 Egress-CAR Sub-TLV Downstream CAR. 1440 Ingress-QoS-Profile Sub-TLV Indicates the name of the QoS-Profile 1441 profile in the upstream direction. 1442 Egress-QoS-Profile Sub-TLV Indicates the name of the QoS-Profile 1443 profile in the downstream direction. 1444 User-ACL-Policy Sub-TLV All ACL user policies, including v4ACLIN, 1445 v4ACLOUT, v6ACLIN, v6ACLOUT, v4WEBACL, 1446 v6WEBACL, v4SpecialACL, and v6SpecialACL. 1447 Multicast-Profile4 Sub-TLV IPv4 multicast policy name. 1448 Multicast-Profile6 Sub-TLV IPv6 multicast policy name. 1449 NAT-Instance Sub-TLV Indicates the instance ID of a NAT user. 1451 The Reserved field MUST be sent as zero and ignored on receipt. 1453 5.6 Routing Table TLVs 1455 5.6.1 IPv4 Routing Information TLV 1457 The format of the TLV value part is as below: 1459 0 1 2 3 1460 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1462 | User ID | 1463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1464 | Dest-Address | 1465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1466 | Next-Hop | 1467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1468 | Out-If-Index | 1469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1470 | Cost | 1471 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1472 | Tag | 1473 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1474 | Route Type | Reserved |A| 1475 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1476 ~ sub-TLVs ~ 1477 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1479 Figure 5.8: IPv4 Routing Information TLV 1481 Function: IPv4 routing information. 1482 TLV Type: 7 1483 TLV Length: Variable length 1484 TLV Fields: 1485 Name Type Description 1486 -------------- ------ ---------------------- 1487 User-ID 4 bytes User ID. This field is filled with all Fs 1488 when a non-user route is delivered to the 1489 UP. 1490 Dest-Address IPv4 Destination address. 1491 Next-Hop IPv4 Next hop address. 1492 Out-If-Index 4 bytes Indicates the interface index. 1493 Cost 4 bytes Cost value of the route. 1494 Tag 4 bytes Route tag value. 1495 Route-Type 2 bytes Route type. The options are as follows: 1496 HOST_RT = 0 user host route 1497 FRAME_RT = 1 Radius authorization FrameRoute 1498 NET_RT = 2, network segment route 1499 GATEWAY_RT = 3, gateway route 1500 RADIUS_IP_RT = 4, Radius authorized IP route 1501 LNS_USER_RT = 5 L2TP LNS side user route 1502 Advertise-Flag 1 bit Indicates the route advertisement flag. 0: 1503 Not advertised, 1: advertised. 1504 VRF-Name Sub-TLV VRF name. 1506 The Reserved field MUST be sent as zero and ignored on receipt. 1508 5.6.2 IPv6 Routing Information TLV 1510 The format of the TLV value part is as follows: 1512 0 1 2 3 1513 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1515 | User ID | 1516 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1517 ~ IPv6 Dest-Address ~ 1518 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1519 ~ IPv6 Next-Hop ~ 1520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1521 | Out-If-Index | 1522 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1523 | Cost | 1524 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1525 | Tag | 1526 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1527 | Route Type | Reserved |A| 1528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1529 ~ VRF-Name sub-TLVs ~ 1530 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1531 Figure 5.9: IPv6 Routing Information TLV 1533 Function: IPv4 routing information. 1534 TLV Type: 8 1535 TLV Length: Variable 1537 TLV Fields: 1538 Name Type Description 1539 -------------- ------ ---------------------- 1540 User-ID 4 bytes User ID. This field is filled with all Fs 1541 when a non-user route is delivered to the 1542 UP. 1543 Dest-Address IPv6 Destination address. 1544 Next-Hop IPv6 Next hop address. 1545 Out-If-Index 4 bytes Indicates the interface index. 1546 Cost 4 bytes Cost value of the route. 1547 Tag 4 bytes Route tag value. 1548 Route-Type 2 bytes Route type. The options are as follows: 1549 HOST_RT = 0 user host route 1550 FRAME_RT = 1 Radius authorization FrameRoute 1551 NET_RT = 2, network segment route 1552 GATEWAY_RT = 3, gateway route 1553 RADIUS_IP_RT = 4, Radius authorized IP route 1554 LNS_USER_RT = 5 L2TP LNS side user route 1555 Advertise-Flag 1 bit Indicates the route advertisement flag. 0: 1556 Not advertised, 1: advertised. 1557 VRF-Name Sub-TLV VRF name. 1559 The Reserved field MUST be sent as zero and ignored on receipt. 1561 5.7 Static User Information TLVs 1562 5.7.1 Static IPv4 User Information TLV 1564 0 1 2 3 1565 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1566 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1567 | If-Index | 1568 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1569 | C-VID | P-VID | 1570 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1571 | User Address | 1572 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1573 | Gateway Address | 1574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1575 | User MAC | 1576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1577 | User MAC (cont.) | Reserved | 1578 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1579 ~ VRF-Name sub-TLVs ~ 1580 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1582 Figure 5.10: Static IPv4 User Information TLV 1584 Function: User information which is used proactively to detect 1585 and go on line. 1586 TLV Type: 9 1587 TLV Length: variable 1589 TLV Fields: 1590 Name Type Description 1591 -------------- ------ ---------------------- 1592 If-Index 4 bytes Indicates the interface index. 1593 C-VID VLAN-ID Indicates the inner VLAN ID. The value 0 1594 indicates that the VLAN ID is invalid. The 1595 valid value is 1~4094. 1596 P-VID VLAN-ID Outer VLAN ID. The value 0 indicates that 1597 the VLAN ID is invalid. The format is the 1598 same as that the C-VID. The valid value is 1599 1~4094. For a single-layer VLAN, set this 1600 parameter to PeVid. 1601 User Address IPv4-Addr Terminal IP address. 1602 Gateway Address IPv4-Addr Gateway IP Address. 1603 User-MAC MAC-Addr MAC address of the terminal. 1604 VRF-Name Sub-TLV VRF Name. 1606 The Reserved field MUST be sent as zero and ignored on receipt. 1608 5.7.2 Static IPv6 User Information TLV 1610 0 1 2 3 1611 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1612 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1613 | If-Index | 1614 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1615 | C-VID | P-VID | 1616 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1617 ~ User Address ~ 1618 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1619 ~ Gateway Address ~ 1620 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1621 | User MAC | 1622 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1623 | User MAC (cont.) | Reserved | 1624 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1625 ~ sub-TLVs ~ 1626 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1628 Figure 5.11: Static IPv6 User Information TLV 1630 Function: User information which is used proactively to detect 1631 and go on line. 1632 TLV Type: 10 1633 TLV Length: variable 1635 TLV Fields: 1636 Name Type Description 1637 -------------- ------ ---------------------- 1638 If-Index 4 bytes Indicates the interface index. 1639 C-VID VLAN-ID Indicates the inner VLAN ID. The value 0 1640 indicates that the VLAN ID is invalid. The 1641 valid value is 1~4094. 1642 P-VID VLAN-ID Outer VLAN ID. The value 0 indicates that 1643 the VLAN ID is invalid. The format is the 1644 same as that the C-VID. The valid value is 1645 1~4094. For a single-layer VLAN, set this 1646 parameter to PeVid. 1647 User Address IPv6-Addr User IP address. 1648 Gateway Address IPv6-Addr Gateway IP Address. 1649 User-MAC MAC-Addr MAC address of the terminal. 1650 VRF-Name Sub-TLV VRF Name. 1652 The Reserved field MUST be sent as zero and ignored on receipt. 1654 5.8 L2TP User Information TLVs 1656 5.8.1 L2TP-LAC User Information TLV 1658 0 1 2 3 1659 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1661 | User ID | 1662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1663 | Local Tunnel ID | Local Session ID | 1664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1665 | Remote Tunnel ID | Remote Session ID | 1666 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1668 Figure 5.12: L2TP-LAC User Information TLV 1670 Function: Information about the L2TP-LAC for a BNG user. 1671 TLV Type: 11 1672 TLV Length: 12 1674 TLV Fields: 1675 Name Type Description 1676 -------------- ------ ---------------------- 1677 User-ID 4 bytes The User identifier. 1678 Local-Tunnel-ID 2 bytes The local ID of the L2TP tunnel. 1679 Local-Session-ID 2 bytes The local session ID with the L2TP tunnel. 1680 Remote-Tunnel-ID 2 bytes The remote ID of the L2TP tunnel. 1681 Remote-Session-ID 2 bytes The remote session ID with the L2TP 1682 tunnel. 1684 5.8.2 L2TP-LNS User Information TLV 1686 0 1 2 3 1687 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1688 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1689 | User ID | 1690 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1691 | Local Tunnel ID | Local Session ID | 1692 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1693 | Remote Tunnel ID | Remote Session ID | 1694 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1696 Figure 5.13: L2TP-LNS User Information TLV 1698 Function: Information about the L2TP tunnel for a BNG user. 1699 TLV Type: 12 1700 TLV Length: 12 1702 TLV Fields: 1703 Name Type Description 1704 -------------- ------ ---------------------- 1705 User-ID 4 bytes The User identifier. 1706 Local-Tunnel-ID 2 bytes The local ID of the L2TP tunnel. 1707 Local-Session-ID 2 bytes The local session ID with the L2TP tunnel. 1708 Remote-Tunnel-ID 2 bytes The remote ID of the L2TP tunnel. 1709 Remote-Session-ID 2 bytes The remote session ID with the L2TP 1710 tunnel. 1712 5.8.3 L2TP-LAC Tunnel TLV 1714 0 1 2 3 1715 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1716 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1717 | Local Tunnel ID | Remote Tunnel ID | 1718 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1719 | Source Port | Destination Port | 1720 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1721 ~ Tunnel Source Address ~ 1722 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1723 ~ Tunnel Destination Address ~ 1724 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1725 ~ sub-TLVs (VRF Name sub-TLV) ~ 1726 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1728 Figure 5.14: L2TP-LAC Tunnel TLV 1730 Function: Information about the L2TP tunnel for a BNG user. 1731 TLV Type: 13 1732 TLV Length: variable 1734 TLV Fields: 1735 Name Type Description 1736 -------------- ------ ---------------------- 1737 Local-Tunnel-ID 2 bytes The local ID of the L2TP tunnel. 1738 Remote-Tunnel-ID 2 bytes The remote ID of the L2TP tunnel. 1739 Source-Port 2 bytes Indicates the source UDP port number of an 1740 L2TP user. 1741 Dest-Port 2 bytes Indicates the destination UDP port number of 1742 an L2TP user. 1743 Source-IP IPv4/v6 The source IP address of the tunnel. 1744 Dest-IP IPv4/v6 The destination IP address of the tunnel. 1745 Tunnel-VRF-Name Sub-TLV L2TP user tunnel VRG name. 1747 5.8.4 L2TP-LNS Tunnel TLV 1749 0 1 2 3 1750 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1751 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1752 | Local Tunnel ID | Remote Tunnel ID | 1753 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1754 | Source Port | Destination Port | 1755 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1756 ~ Tunnel Source Address ~ 1757 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1758 ~ Tunnel Destination Address ~ 1759 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1760 ~ sub-TLVs (VRF Name sub-TLV) ~ 1761 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1763 Figure 5.15: L2TP-LNS Tunnel TLV 1765 Function: Information about the L2TP tunnel for a BNG user. 1766 TLV Type: 14 1767 TLV Length: variable 1769 TLV Fields: 1770 Name Type Description 1771 -------------- ------ ---------------------- 1772 Local-Tunnel-ID 2 bytes The local ID of the L2TP tunnel. 1773 Remote-Tunnel-ID 2 bytes The remote ID of the L2TP tunnel. 1774 Source-Port 2 bytes Indicates the source UDP port number of an 1775 L2TP user. 1776 Dest-Port 2 bytes Indicates the destination UDP port number of 1777 an L2TP user. 1778 Source-IP IPv4/v6 The source IP address of the tunnel. 1779 Dest-IP IPv4/v6 The destination IP address of the tunnel. 1780 Tunnel-VRF-Name Sub-TLV L2TP user tunnel VRG name. 1782 5.9 NAT User Information TLV 1784 0 1 2 3 1785 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1786 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1787 | User ID | 1788 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1789 | NAT Port Start | NAT Port End | 1790 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1791 | NAT Address | 1792 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1794 Figure 5.16: NAT User Information TLV 1796 Function: NAT [RFC3022] public network information for a BNG user. 1797 TLV Type: 15 1798 TLV Length: 12 1800 TLV Fields: 1801 Name Type Description 1802 -------------- ------ ---------------------- 1803 User-ID 4 bytes User ID. 1804 NAT-Port-Start 2 bytes NAT start port number. 1805 NAT-Port-End 2 bytes NAT end port number. 1806 NAT-Sub-IP 4 bytes NAT public network address. 1808 5.10 Vendor Defined TLV 1810 0 1 2 3 1811 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1813 | Vendor ID | 1814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1815 | Sub-Type | Sub-Type-Version | 1816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1817 ~ sub-TLVs (optional) | 1818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1820 Figure 5.17: Vendor Defined TLV 1822 Function: Used to indicate vendor, sub-type, and version for a 1823 Vendor Defined message. 1824 TLV Type: 1024 1825 TLV Length: variable 1827 TLV Fields: 1828 Name Type Description 1829 -------------- ------ ---------------------- 1830 Vendor-ID 4 bytes Vendor ID, which is defined in the RADIUS 1831 [RFC2865]. 1832 Sub-Type 2 bytes Used by the Vendor to distinguish multiple 1833 different vendor messages. 1834 Sub-Type-Version 2 bytes Used by the Vendor to distinguish different 1835 versions of a Vendor Defined message sub- 1836 type. 1838 Since Vendor code will be handling the TLV after the Vendor ID field 1839 is recognized, the remainder of the TLV value can be organized 1840 however the vendor wants. But it desirable for a vendor to be able to 1841 define multiple different vendor messages and to keep track of 1842 different versions of its vendor defined messages. Thus, it is 1843 RECOMMENDED that the vendor assign a Sub-Type value for each vendor 1844 message that it defines different from other Sub-Type values that 1845 vendor has used. Also, when modifying a vendor defined messages in a 1846 way potentially incompatible with a previous definition, the vendor 1847 SHOULD increase the value it is using in the Sub-Type-Version field. 1849 6. Control TLVs 1851 6.1 Hello TLV 1853 0 1 2 3 1854 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1855 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1856 | VerSupported | 1857 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1858 | Vendor ID | 1859 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1860 | Capabilities | 1861 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1863 Figure 6.1: Hello TLV 1865 Function: Hello Message. 1866 TLV Type: 100 1867 TLV Length: 12 1869 TLV Fields: 1870 Name Type Description 1871 -------------- ------ ---------------------- 1872 VerSupported 32 bits This is a bit map of the Sub-Versions of the 1873 S-CUSP protocol that the sender supports. 1874 This document specifies Sub-Version zero of 1875 Major Version 1, that is, Version 1.0. The 1876 VerSupported field MUST be non-zero. Bit 0 1877 indicates support of Sub-Version zero, bit 1 1878 indicates support of Sub-Version one, etc. 1879 Vendor-ID 4 bytes Vendor ID, which is defined in RADIUS 1880 [RFC2865]. 1881 Capabilities 32 bits Flags that indicate the support of 1882 particular capabilities by the sender of the 1883 Hello. 1885 After the exachange of Hello messages, the CP and UP each perform a 1886 logical AND of the Sub-Version supported and of the Capabilities bits 1887 fields. 1889 If the result of the AND of the Sub-Versions supported is zero, then 1890 no session can be established and the connection is torn down. If the 1891 result of the AND of the Sub-Versions supported is non-zero, then the 1892 session uses the highest Sub-Version supported by both the CP and UP. 1894 For example, if one side supports Sub-Versions 1, 3, 4, and 5 1895 (VerSupported = 0x5C000000) and the other side supports 2, 3, and 4 1896 (VerSupported = 0x38000000) then 3 and 4 are the Sub-Versions in 1897 common and 4 is the highest Sub-Version supported by both sides. So 1898 Sub-Version 4 is used for the session that has been negotiated. 1900 The result of the logical AND of the Capabilities bits will show what 1901 additional capabilities both sides support. If this result is zero, 1902 there are no such capabilities so none can be used during the 1903 session. If this result is non-zero, it shows the additional 1904 capabilities that can be used during the session. 1906 6.2 Error Information TLV 1908 0 1 2 3 1909 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1910 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1911 | Message Type | 1912 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1913 | Status Code | 1914 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1916 Figure 6.2: Error TLV 1918 Function: Error response. 1919 TLV Type: 101 1920 TLV Length: 8 1922 TLV Fields: 1923 Name Type Description 1924 -------------- ------ ---------------------- 1925 Message-Type 4 bytes Message category. Set this parameter to the 1926 corresponding processing message code. 1927 Status-Code 4 bytes Error Code (see Section 12.2.5). 1929 7. Resource Reporting TLVs 1931 7.1 Interface Resource Information TLV 1933 0 1 2 3 1934 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1935 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1936 | If-Index | 1937 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1938 | MAC Address (upper part) | 1939 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1940 | MAC Address (lower part) | Phy-State | Reserved | 1941 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1942 | MTU | 1943 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1944 ~ sub-TLVs (optional) ~ 1945 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1947 Figure 7.1: Interface Resource TLV 1949 Function: BNG interface resource information. 1950 TLV Type: 200 1951 TLV Length: variable 1953 TLV Fields: 1954 Name Type Description 1955 -------------- ------ ---------------------- 1956 If-Index 4 bytes Indicates the interface index. 1957 MAC-Address MAC-Addr Interface MAC address. 1958 Phy-State 1 byte Physical status of the interface. 0: down, 1959 1: Up 1960 MTU 4 bytes Interface MTU value. 1962 The Reserved field MUST be sent as zero and ignored on receipt. 1964 7.2 UP Board Status Report Information TLV 1966 0 1 2 3 1967 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1968 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1969 | Chassis | Slot | Sub-Slot | Board-Type | 1970 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1971 | State | Reserved | 1972 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1974 Figure 7.2: Interface Resource TLV 1976 Function: Board information reported by the UP, including the 1977 board type and in-position status 1978 TLV Type: 201 1979 TLV Length: 8 1981 TLV Fields: 1982 Name Type Description 1983 -------------- ------ ---------------------- 1984 Chassis 1 byte Subrack number. 1985 Slot 1 byte Slot number. 1986 Sub-Slot 1 byte Sub-slot number. 1987 Board-Type 1 byte 1: CGN service card, 2: Interface board. 1988 State 1 byte Board status 0: Normal, 1: Abnormal. 1990 The reserved field must be sent as zero and ignored on receipt. 1992 8. Event TLVs 1994 8.1 User Traffic Statistics Report TLV 1996 0 1 2 3 1997 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1998 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1999 | User-ID | 2000 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2001 | Statistics Type | 2002 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2003 | Ingress Packets (upper part) | 2004 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2005 | Ingress Packets (lower part) | 2006 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2007 | Ingress Bytes (upper part) | 2008 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2009 | Ingress Bytes (lower part) | 2010 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2011 | Ingress Loss Packets (upper part) | 2012 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2013 | Ingress Loss Packets (lower part) | 2014 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2015 | Ingress Loss Bytes (upper part) | 2016 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2017 | Ingress Loss Bytes (lower part) | 2018 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2019 | Egress Packets (upper part) | 2020 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2021 | Egress Packets (lower part) | 2022 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2023 | Egress Bytes (upper part) | 2024 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2025 | Egress Bytes (lower part) | 2026 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2027 | Egress Loss Packets (upper part) | 2028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2029 | Egress Loss Packets (lower part) | 2030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2031 | Egress Loss Bytes (upper part) | 2032 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2033 | Egress Loss Bytes (lower part) | 2034 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2036 Figure 8.1: User Traffic Statistics Report TLV 2038 Function: User traffic statistics report. 2039 TLV Type: 300 2040 TLV Length: 72 2042 TLV Fields: 2043 Name Type Description 2044 -------------- ------ ---------------------- 2045 User-ID 4 bytes User ID. 2046 Statistics-Type 4 bytes Traffic type. The options are as follows: 0: 2047 IPv4 traffic, 1: IPv6 traffic, 2: Dual stack 2048 traffic. 2049 Ingress-Packets 8 bytes Upstream traffic: number of packets 2050 (UNIT64). 2051 Ingress-Bytes 8 bytes Upstream traffic: byte count (UINT64). 2052 Ingress-Loss-Packets 8 bytes Upstream packet loss: number of data 2053 packets (UNIT64). 2054 Ingress-Loss-Bytes 8 bytes Upstream packet loss: byte count (UINT64). 2055 Egress-Packets 8 bytes Downstream traffic: number of packets 2056 (UNIT64). 2057 Egress-Bytes 8 bytes Downstream traffic: byte count (UINT64). 2058 Egress-Loss-Packets 8 bytes Downstream packet loss: number of data 2059 packets (UNIT64). 2060 Egress-Loss-Bytes 8 bytes Downstream packet loss: byte count 2061 (UINT64). 2063 8.2 User Detection Result Report TLV 2065 0 1 2 3 2066 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2067 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2068 | User-ID | 2069 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2070 | Detect Type | Detect Result | Reserved | 2071 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2073 Figure 8.2: User Detection Result Report TLV 2075 Function: Report BNG user detection. 2076 TLV Type: 301 2077 TLV Length: 8 2079 TLV Fields: 2080 Name Type Description 2081 -------------- ------ ---------------------- 2082 User-ID 4 bytes User ID. 2083 Detect-Type 1 byte 0: IPv4 detection, 2084 1: IPv6 detection, 2085 2: PPP detection. 2087 Detect-Result 1 bytes 0: indicates that the detection is 2088 successful, 1: Detection failure. The UP 2089 needs report only when the detection fails. 2091 The Reserved field MUST be sent as zero and ignored on receipt. 2093 8.3 User Basic Table Operation Result TLV 2095 0 1 2 3 2096 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2097 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2098 | User-ID | 2099 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2100 | Oper ID | Oper Code | Oper Result | Reserved | 2101 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2102 | Error Code | 2103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2105 Figure 8.3: User Detection Result Report TLV 2107 Function: Report the operation result of a table update. 2108 TLV Type: 302 2109 TLV Length: 12 2111 TLV Fields: 2112 Name Type Description 2113 -------------- ------ ---------------------- 2114 User-ID 4 bytes User ID. 2115 Oper-ID 1 byte When a user connection number, dual stack, 2116 or Modify operation is performed, the 2117 response message carries the ConnectID 2118 carried in the following table. The CP 2119 verifies the corresponding operation. 2120 Oper-Code 1 byte Operation code. 1: update, 2: delete. 2121 Oper-Result 1 byte Operation Result. 0: Success, Others: 2122 Failure 2123 Error-Code 4 bytes Operation failure cause code. For details, 2124 see Section 12.2.5. 2126 The Reserved field MUST be sent as zero and ignored on receipt. 2128 9. Resource Allocation TLVs 2130 9.1 Request Address Allocation TLV 2132 0 1 2 3 2133 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2135 ~ sub-TLV ~ 2136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2138 Figure 9.1: Request Address Allocation TLV 2140 Function: Request address allocation. 2141 TLV Type: 400 2142 TLV Length: variable 2144 TLV Fields: 2145 Name Type Description 2146 -------------- ------ ---------------------- 2147 Pool-Name Sub-TLV Address pool name. 2149 9.2 Address Assignment Response TLV 2151 0 1 2 3 2152 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2153 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2154 | Lease Time | 2155 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2156 | IPv4 Addr and Mask | 2157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2158 | IPv4 Addr and Mask continued | 2159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2160 | Result Code | Reserved | ~ 2161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ sub-TLVs | 2162 ~ ~ 2163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2165 Figure 9.2: Address Assignment Response TLV 2167 Function: The CGN sends a response to the address assignment 2168 request. 2169 TLV Type: 401 2170 TLV Length: variable 2171 TLV Fields: 2172 Name Type Description 2173 -------------- ------ ---------------------- 2174 Lease-Time 4 bytes Duration of address lease in seconds. 2175 Client-IP IPv4-Addr Start address and mask of the address 2176 segment. 2177 Result-Code 1 byte Processing Result, 0: Success, 1: Failure 2178 Pool-Name Sub-TLV Address segment address pool name. 2180 9.3 Address Renewal Request TLV 2182 0 1 2 3 2183 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2185 | IPv4 Address and Mask | 2186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2187 | IPv4 Address and Mask continued | 2188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2189 ~ sub-TLVs ~ 2190 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2192 Figure 9.3: Request Address Renewal TLV 2194 Function: Request address renewal. 2195 TLV Type: 402 2196 TLV Length: variable 2198 TLV fields: 2199 Name Type Description 2200 -------------- ------ ---------------------- 2201 Client-IP IPv4-Addr Start address and mask of the address 2202 segment. 2203 Pool-Name Sub-TLV Address segment address pool name. 2205 9.4 Address Renewal Response TLV 2207 0 1 2 3 2208 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2210 | IPv4 Address and Mask | 2211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2212 | IPv4 Address and Mask continued | 2213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2214 | Result-Code | Reserved | ~ 2215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ sub-TLVs | 2216 ~ ~ 2217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2219 Figure 9.4: Address Renewal Response TLV 2221 Function: Request address renewal. 2222 TLV Type: 403 2223 TLV Length: variable 2225 TLV fields: 2226 Name Type Description 2227 -------------- ------ ---------------------- 2228 Client-IP IPv4-Addr Start address and mask of the address 2229 segment. 2230 Result-Code 1 bytes Processing Result, 0: Success, 1: Failure 2231 Pool-Name Sub-TLV Address segment address pool name. 2233 9.5 Address Release Request TLV 2235 0 1 2 3 2236 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2238 | IPv4 Address and Mask | 2239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2240 | IPv4 Address and Mask continued | 2241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2242 ~ sub-TLVs ~ 2243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2245 Figure 9.5: Request Address Renewal TLV 2247 Function: The CGN request the release of IP addresses. 2248 TLV Type: 404 2249 TLV Length: variable 2250 TLV fields: 2251 Name Type Description 2252 -------------- ------ ---------------------- 2253 Client-IP IPv4-Addr Start address and mask of the address 2254 segment. 2255 Pool-Name Sub-TLV Address segment address pool name. 2257 9.6 Address Release Response TLV 2259 0 1 2 3 2260 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2262 | IPv4 Address and Mask | 2263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2264 | IPv4 Address and Mask continued | 2265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2266 | Result-Code | Reserved | ~ 2267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ sub-TLVs | 2268 ~ ~ 2269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 2271 Figure 9.6: Address Renewal Response TLV 2273 Function: Request address renewal. 2274 TLV Type: 405 2275 TLV Length: variable 2277 TLV fields: 2278 Name Type Description 2279 -------------- ------ ---------------------- 2280 Client-IP IPv4-Addr Start address and mask of the address 2281 segment. 2282 Result-Code 4 bytes Processing Result, 0: Success, 1: Failure 2283 Pool-Name Sub-TLV Address segment address pool name. 2285 10. Implementation Status 2287 This section is NOT intended to appear in any resulting RFC. 2289 This section discusses the status of implementations that have 2290 provided information and the testing of this protocol at the time of 2291 posting of this Internet-Draft, and is based on the proposal in 2292 [RFC7942] ("Improving Awareness of Running Code: The Implementation 2293 Status Section"). The description of implementations in this section 2294 is intended to assist the IETF in its decision processes in 2295 progressing drafts to RFCs. Please note that the listing of any 2296 individual implementation or test results here does not imply 2297 endorsement by the IETF. Furthermore, no effort has been spent to 2298 verify the information presented here that was supplied by IETF 2299 contributors. This is not intended as, and must not be construed to 2300 be, a catalog of available implementations or their testing or 2301 features. Readers are advised to note that other implementations may 2302 exist. 2304 According to [RFC7942], "this will allow reviewers ... to assign due 2305 consideration to documents that have the benefit of running code, 2306 which may serve as evidence of valuable experimentation and feedback 2307 that have made the implemented protocols more mature.". 2309 10.1 Implementations 2311 Information on three S-CUSP implementations appears below. 2313 10.1.1 Huawei Technologies 2315 Name: Cloud-based BNG. 2317 Maturity: Production. 2319 Coverage: According to S-CUSP protocol. 2321 Contact information: 2322 Zhouyi Yu: yuzhouyi@huawei.com 2324 Date: 2018-11-01 2326 10.1.2 ZTE 2328 Name: ZXR10 V6000 vBRAS 2330 Maturity: Production 2332 Coverage: According to S-CUSP protocol. 2334 Contact information: 2335 Yong Chen: 10056167@zte.com.cn 2336 Huaibin Wang: 10008729@zte.com.cn 2338 Date: 2018-12-01 2340 10.1.3 H3C 2342 Name: CUSP protocol for BRAS Control Plane and User Plan 2343 Separation 2345 Maturity: Research 2347 Coverage: According to S-CUSP protocol 2349 Contact information: mengdan@h3c.com; liuhanlei@h3c.com 2351 Date: 2019-1-30 2353 10.2 Hackathon 2355 Successful use of the protocol at the IETF-102 Hackathon, Montreal, 2356 Quebec, in 2018. 2358 Hackathon Project: Control Plane and User Plane Separation BNG 2359 control channel Protocol (CUSP) 2361 Champions: Zhenqiang Li, Michael Wang 2363 Report: See 2364 github.com/IETF-Hackathon/ietf102-project-presentations/blob/ 2365 master/IETF102-hackathon-presentation-CUSP.pptx 2367 10.3 EANTC Testing 2369 EANTC (European Advanced Networking Test Center (www.eantc.de)) 2370 tested the Huawei implementation. Their summary was as follows: 2371 "EANTC tested advanced aspects of the Cloud-based Broadband Network 2372 Gateway (vBNG) with a focus on performance, scalability and high 2373 availability with up to 20 Million emulated subscribers. The solution 2374 performed very well across all test scenarios." 2376 See report at 2377 www.eantc.de/fileadmin/eantc/downloads/News/2018/EANTC-vBRAS- 2378 phase2.pdf 2380 11. Security Considerations 2382 The S-CUSP messages do not provide security. Thus, if these messages 2383 are exchanged in an environment where security is a concern, that 2384 security must be provided by another protocol such as TLS 1.3 2385 [RFC8446]. 2387 12. IANA Considerations 2389 IANA is requested to perform the actions below in this section. 2391 12.1 Service Name and Port Number 2393 IANA is requested to assign a service name and port for BNG S-CUSP as 2394 follows: 2396 Service Port Transport 2397 Name Number Protocol Description Reference 2398 ------- ------ --------- ------------- --------------- 2399 s-cusp tbd1 tcp Control-plane and [this document] 2400 User-plane 2401 Separation Protocol 2403 12.2 S-CUSP Parameters 2405 IANA is requested to create an "S-CUSP Parameters" web page and 2406 include thereon the registries set up in the Sub-Sections below. 2408 12.2.1 Message Types 2410 IANA is requested to create an S-CUSP Message Types registry on the 2411 S-CUSP Parameters Web Page as follows: 2413 Registry Name: S-CUSP Message Types 2414 Registration Procedure: Expert Review 2415 Reference: [this document] 2417 Type Name Reference 2418 ------ ----------- --------------- 2419 0 - Reserved 2420 1 Hello [this document] 2421 2 Keepalive [this document] 2422 3 Sync_Request [this document] 2423 4 Sync_Begin [this document] 2424 5 Sync_Data [this document] 2425 6 Sync_End [this document] 2426 7 Update_Request [this document] 2427 8 Update_Response [this document] 2428 9 Report [this document] 2429 10 Event [this document] 2430 11 Vendor [this document] 2432 12-199 - Unassigned 2433 200 Addr_Allocation_Req [this document] 2434 201 Addr_Allocation_Ack [this document] 2435 202 Addr_Renew_Req [this document] 2436 203 Addr_Renew_Ack [this document] 2437 204 Addr_Release_Req [this document] 2438 205 Addr_Release_Ack [this document] 2439 206-254 - Unassigned 2440 255 - Reserved 2442 12.2.2 TLV Types 2444 IANA is requested to create an S-CUSP TLV Types registry on the S- 2445 CUSP Parameters Web Page as follows: 2447 Registry Name: S-CUSP TLV Types 2448 Registration Procedure: Expert Review 2449 Reference: [this document] 2451 Type Name Usage Description 2452 ------ ------------ -------------------------- 2453 1 Access-IfSrv Service information about the user access 2454 interface on the BNG. 2455 2 User-Basic Basic information about a BNG user. 2456 3 User-PPP PPP information about a BNG user. 2457 4 User-IPv4 IPv4 address of a BNG user. 2458 5 User-IPv6 IPv6 address of a BNG user. 2459 6 User-Auth QoS authorization information of a BNG 2460 user. 2461 7 RouteV4-Info BNG IPv4 routing information. 2462 8 RouteV6-Info BNG IPv6 routing information. 2463 9 Static-IPv4-User Static user information on a BNG. Used to 2464 proactively detect and go online. 2465 10 Static-IPv6-User Static user information on a BNG. Used to 2466 proactively detect and go online. 2467 11 User-L2TP-LAC L2TP LAC user information. 2468 12 User-L2TP-LNS L2TP LNS user information. 2469 13 User-L2TP-LAC-Tnl L2TP LAC tunnel information. 2470 14 User-L2TP-LNS-Tnl L2TP LNS tunnel information. 2471 15 User-NAT Public network segment information for a 2472 NAT user. 2473 16-99 unassigned 2474 100 Hello-Info The CP and UP advertise versions to each 2475 other 2476 101 Error-Info The Ack of the control message carries the 2477 processing result, success, or error. 2478 102-199 unassigned - 2479 200 Interface-Info Interfaces reported by the UP including 2480 physical interfaces, sub-interfaces, trunk 2481 interfaces, and tunnel interfaces. 2482 201 Board-Info Board information reported by the UP 2483 including the board type and in-position 2484 status. 2485 202-299 unassigned - 2486 300 Traffic-Info User traffic statistics. 2487 301 Detect-Info User detection information. 2488 302 User-TBL-Result Processing result of user forwarding table 2489 delivery. 2490 303-299 unassigned - 2491 400 Addr-Alloc-Req Request address allocation. 2492 401 Addr-Alloc-Ack Address allocation response. 2493 402 Addr-Renew-Req Request for address lease renewal. 2494 403 Addr-Renew-Ack Response to a request for extending an IP 2495 address lease. 2496 404 Addr-Release-Req Request to release the address. 2497 405 Addr-Release-Ack Ack of a message releasing an IP address. 2498 406-1023 unassigned - 2499 1024 Vendor-Defined As implemented by vendor. 2500 1025-65535 unassigned - 2502 12.2.3 TLV Operation Codes 2504 IANA is requested to create an S-CUSP TLV Operation Codes registry on 2505 the S-CUSP Parameters Web Page as follows: 2507 Registry Name: S-CUSP TLV Operation Codes 2508 Registration Procedure: Expert Review 2509 Reference: [this document] 2511 Code Operation Reference 2512 ---- ---------- --------- 2513 0 - reserved 2514 1 Update [this document] 2515 2 Delete [this document] 2516 3-15 - unassigned 2518 12.2.4 Sub-TLV Types 2520 IANA is requested to create an S-CUSP Sub-TLV Types registry on the 2521 S-CUSP Parameters Web Page as follows: 2523 Registry Name: S-CUSP Sub-TLV Types 2524 Registration Procedure: Expert Review 2525 Reference: [this document] 2526 Code Operation Reference 2527 ----- ------------------ --------------- 2528 0 - reserved 2529 1 VRF Name [this document] 2530 2 Ingress-QoS-Profile [this document] 2531 3 Egress-QoS-Profile [this document] 2532 4 User-ACL-Policy [this document] 2533 5 Multicast-ProfileV4 [this document] 2534 6 Multicast-ProfileV6 [this document] 2535 7 Ingress-CAR [this document] 2536 8 Egress-CAR [this document] 2537 9 NAT-Instance [this document] 2538 10 Pool-Name [this document] 2539 11 If-Desc [this document] 2540 12-64534 - unassigned 2541 65535 -reserved 2543 12.2.5 ERRID Codes 2545 IANA is requested to create an S-CUSP ERRID Codes registry on the S- 2546 CUSP Parameters Web Page as follows: 2548 Registry Name: S-CUSP ERRID Codes 2549 Registration Procedure: Expert Review 2550 Reference: [this document] 2552 Value Name Remarks 2553 ------ ------- -------- 2554 0 Success Success 2555 1 Fail Failure. The reason is not classified. 2556 2 TLV-Unknown The TVL type cannot be identified. 2557 3 TLV-Length The TLV length is abnormal. 2558 4 TLV-Value The TLV value is abnormal 2559 5-999 - unassigned Unassigned basic error codes. 2560 1000 - reserved 2561 1001 Version-Mismatch The version negotiation fails. Terminate. 2562 The subsequent service processes 2563 corresponding to the UP are suspended. 2564 1002-1999 - unassigned Unassigned version negotiation error codes. 2565 2000 - reserved 2566 2001 Synch-NoReady The data to be smoothed is not ready. 2567 2002 Synch-Unsupport The request for smooth data is not 2568 supported. 2569 2003-2999 - unassigned Unassigned data synchronization error 2570 codes. 2571 3000 - reserved 2572 3001 Pool-Mismatch The corresponding address pool cannot be 2573 found. 2575 3002 Pool-Full The address pool is fully allocated and no 2576 address segment is available. 2577 3003 Subnet-Mismatch The address pool subnet cannot be found. 2578 3004 Subnet-Conflict Subnets in the address pool have been 2579 classified into other clients. 2580 3005-3999 - unassigned Unassigned address allocation error codes, 2581 used in NAT address allocation. 2582 4000 - reserved 2583 4001 Update-Fail-No-Res The forwarding table fails to be 2584 delivered because the forwarding resources 2585 are insufficient. 2586 4002 QoS-Update-Success The QoS policy takes effect. 2587 4003 QoS-Update-Sq-Fail Failed to process the queue in the QoS 2588 policy. 2589 4004 QoS-Update-CAR-Fail Processing of the CAR in the QoS policy 2590 fails. 2591 4005 Statistic-Fail-No-Res Statistics processing failed due to 2592 insufficient statistics resources. 2593 4006-4999 - unassigned forwarding table delivery error codes. 2594 5000-4294967295 - reserved 2596 Contributors 2598 Zitao Wang 2599 Huawei Technologies 2600 101 Software Avenue, Yuhua District 2601 Nanjing, Jiangsu 210012 2602 China 2604 Email: wangzitao@huawei.com 2606 Normative References 2608 [RFC793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, 2609 DOI 10.17487/RFC0793, September 1981, . 2612 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2613 Requirement Levels", BCP 14, RFC 2119, DOI 2614 10.17487/RFC2119, March 1997, . 2617 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 2618 and A. Bierman, Ed., "Network Configuration Protocol 2619 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 2620 . 2622 [RFC2661] Townsley, W., Valencia, A., Rubens, A., Pall, G., Zorn, G., 2623 and B. Palter, "Layer Two Tunneling Protocol "L2TP"", RFC 2624 2661, DOI 10.17487/RFC2661, August 1999, . 2627 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 2628 "Remote Authentication Dial In User Service (RADIUS)", RFC 2629 2865, DOI 10.17487/RFC2865, June 2000, . 2632 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 2633 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2634 2017, . 2636 Informative References 2638 [SCUSP-architecture] Hu, S., Qin, G. Li, Z., Chua, T., Lopez, V., 2639 Eastlake, D., Wang, Z., and J. Song, "Architecture for 2640 Control Plane and User Plane Separated BNG", 2641 draft-cuspdt-rtgwg-cu-separation-bng-architecture-04 (work 2642 in progress), March 2019. 2644 [SCUSP-YANG] Huang, G., Hu, F., Hu, S., and F. Fangwei, "YANG Data 2645 Model for Configuration Interface of Control-Plane and 2646 User-Plane separation BNG", 2647 draft-cuspdt-rtgwg-cu-separation-yang-model (work in 2648 progress), January 2019. 2650 [RFC1661] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", STD 2651 51, RFC 1661, DOI 10.17487/RFC1661, July 1994, 2652 . 2654 [RFC3022] Srisuresh, P. and K. Egevang, "Traditional IP Network 2655 Address Translator (Traditional NAT)", RFC 3022, DOI 2656 10.17487/RFC3022, January 2001, 2659 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2660 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 2662 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 2663 Code: The Implementation Status Section", BCP 205, RFC 2664 7942, DOI 10.17487/RFC7942, July 2016, . 2667 [RFC8446] Rescorla, E., "The Transport Layer Security (TLS) Protocol 2668 Version 1.3", RFC 8446, DOI 10.17487/RFC8446, August 2018, 2669 . 2671 [TR-384] Broadband Forum, "Cloud Central Office Reference 2672 Architectural Framework", BBF TR-384, 2018. 2674 Authors' Addresses 2676 Shujun Hu 2677 China Mobile 2678 32 Xuanwumen West Ave, Xicheng District 2679 Beijing, Beijing 100053 2680 China 2682 Email: hushujun@chinamobile.com 2684 Donald Eastlake, 3rd 2685 Huawei Technologies 2686 1424 Pro Shop Court 2687 Davenport, FL 33896 2688 USA 2690 Phone: +1-508-333-2270 2691 Email: d3e3e3@gmail.com 2693 Mach Chen 2694 Huawei Technologies 2695 Huawei Bldg., No. 156 Beiqing Road 2696 Beijing 100095 China 2698 Email: mach.chen@huawei.com 2700 Fengwei Qin 2701 China Mobile 2702 32 Xuanwumen West Ave, Xicheng District 2703 Beijing, Beijing 100053 2704 China 2706 Email: qinfengwei@chinamobile.com 2708 Zhenqiang Li 2709 China Mobile 2710 32 Xuanwumen West Ave, Xicheng District 2711 Beijing, Beijing 100053 2712 China 2714 Email: lizhenqiang@chinamobile.com 2715 Jun Song 2716 Huawei Technologies 2717 101 Software Avenue, Yuhua District 2718 Nanjing, Jiangsu 210012 2719 China 2721 Email: song.jun@huawei.com 2723 Tee Mong Chua 2724 Singapore Telecommunications Limited 2725 31 Exeter Road, #05-04 Comcentre Podium Block 2726 Singapore City 239732 2727 Singapore 2729 Email: teemong@singtel.com 2731 Copyright, Disclaimer, and Additional IPR Provisions 2733 Copyright (c) 2019 IETF Trust and the persons identified as the 2734 document authors. All rights reserved. 2736 This document is subject to BCP 78 and the IETF Trust's Legal 2737 Provisions Relating to IETF Documents 2738 (http://trustee.ietf.org/license-info) in effect on the date of 2739 publication of this document. Please review these documents 2740 carefully, as they describe your rights and restrictions with respect 2741 to this document. Code Components extracted from this document must 2742 include Simplified BSD License text as described in Section 4.e of 2743 the Trust Legal Provisions and are provided without warranty as 2744 described in the Simplified BSD License.