idnits 2.17.1 draft-padebettu-5g-wireline-transport-over-ppp-00.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC1661], [RFC2516]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 30, 2020) is 1334 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC1332' is defined on line 578, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group V. Padebettu 3 Internet-Draft Juniper Networks Inc. 4 Intended status: Informational August 30, 2020 5 Expires: March 3, 2021 7 5G Wireline Transport over PPP 8 draft-padebettu-5g-wireline-transport-over-ppp-00 10 Abstract 12 To support connecting 5G residential gateways(5G-RG) to 5G Core (5GC) 13 over wireline access, the control packets and data packets of the 5G- 14 RG should be transported over the wireline access network (W-AN) to 15 Access Gateway Function(W-AGF). 17 The Point-to-Point Protocol (PPP) [RFC1661] provides a standard 18 method for transporting multi-protocol datagrams over point-to-point 19 links. PPP defines an extensible Link Control Protocol, and proposes 20 a family of Network Control Protocols for establishing and 21 configuring different network-layer protocols. 23 This document defines the 5G Wireline Control Protocol(5WCP) for 24 establishing and configuring the 5G Wireline Data protocol(5W Data) 25 over PPP for Wireline Access for 5G Networks. The method inherits 26 multiplexing of traffic for multiple 5G-RGs per VLAN from PPPoE 27 [RFC2516] and defines multiplexing multiple PDU Sessions per 5G-RG. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at https://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on March 3, 2021. 46 Copyright Notice 48 Copyright (c) 2020 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (https://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 65 3. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 4. 5G Wireline Transport over PPP . . . . . . . . . . . . . . . 4 67 4.1. 5G Wireline Conrol Protocol for 5G AS/NAS . . . . . . . . 4 68 4.2. Sending 5G Wireline Datagrams . . . . . . . . . . . . . . 6 69 4.3. 5G Wireline Control Protocol Procedures . . . . . . . . . 7 70 4.3.1. 5WCP Registration Procedure . . . . . . . . . . . . . 7 71 4.3.2. 5WCP De-registration Procedure . . . . . . . . . . . 8 72 4.3.3. 5WCP Authentication Procedure . . . . . . . . . . . . 8 73 4.3.4. 5WCP Identity Procedure . . . . . . . . . . . . . . . 9 74 4.3.5. 5WCP Configuration Update Procedure . . . . . . . . . 9 75 4.3.6. 5WCP Service Request Procedure . . . . . . . . . . . 9 76 4.3.7. 5WCP Notification Procedure . . . . . . . . . . . . . 9 77 4.3.8. 5WCP Security Mode Procedure . . . . . . . . . . . . 10 78 4.3.9. 5WCP UL/DL Procedure . . . . . . . . . . . . . . . . 10 79 4.3.10. 5WCP 5GMM Status Procedure . . . . . . . . . . . . . 10 80 4.3.11. 5WCP PDU Session Establishment Procedure . . . . . . 11 81 4.3.12. 5WCP PDU Session Modification Procedure . . . . . . . 11 82 4.3.13. 5WCP PDU Session Release Procedure . . . . . . . . . 12 83 4.3.14. 5WCP 5GSM Status Procedure . . . . . . . . . . . . . 12 84 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 85 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 86 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13 87 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 88 8.1. Normative References . . . . . . . . . . . . . . . . . . 13 89 8.2. Informative References . . . . . . . . . . . . . . . . . 14 90 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14 92 1. Introduction 94 Wireless Wireline convergence with 5G ("fifth generation") mobile 95 network introduces 5G Access Gateway Function (W-AGF is defined in 96 [TS.23.316-3GPP]) as Wireline Access Network (W-AN). W-AGF 97 transports the Control Packets from the 5G capable Residential 98 Gateway(5G-RG) to the 5G Control Plane(5GCP) and transports the Data 99 Packets from the 5G-RG to the 5G User Plane Function(UPF). 5G-RG is 100 connected to the W-AGF over the wireline access based on TR-101 101 [BBF.TR.101]. 103 The wireline transport defined for the 5G-RG is based on existing 104 wireline technologies for faster implementation and adaptation. 5G 105 defines end-to-end QoS which requires the wireline transport to carry 106 the 5G QoS information inline with the data. 108 5G NAS [TS.24.501-3GPP] is the control channel which registers, 109 authenticates and authorizes the end-point, providing the information 110 (IP Address, Gateway, DNS, etc. )for transporting the data from the 111 5G-RG over the link. 113 PPP has three main components: 115 1. A method for encapsulating multi-protocol datagrams. 117 2. A Link Control Protocol (LCP) for establishing, configuring, 118 and testing the data-link connection. 120 3. A family of Network Control Protocols for establishing and 121 configuring different network-layer protocols. 123 In order to establish communications over a point-to-point link, each 124 end of the PPP link must first send LCP packets to configure and test 125 the data link. After the link has been established from negotiating 126 optional facilities as needed by the LCP, PPP must send 5G NAS 127 control packets to choose and configure the 5G NAS network-layer 128 protocol. Once 5G NAS has reached the Opened state, 5G datagrams can 129 be sent over the link. 131 The link will remain configured for communications until explicit LCP 132 or 5G NAS packets close the link down, or until some external event 133 occurs (an inactivity timer expires or network administrator 134 intervention). 136 2. Requirements Language 138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 140 "OPTIONAL" in this document are to be interpreted as described in BCP 141 14 [RFC2119] [RFC8174] when, and only when, they appear in all 142 capitals, as shown here. 144 3. Acronyms 146 This document uses the following acronyms: 148 3GPP 3rd Generation Partnership Project 149 5GC 5th Generation Core (network) 150 5GCP 5G Control Plane 151 W-AGF Wireline Access Gateway Function 152 NAS Non-Access Stratum 153 PDU Protocol Data Unit 154 QFI QoS Flow Identifier 155 QoS Quality of Service 156 RG Residential Gateway 157 5G-RG 5G capable Residential Gateway 158 RQI Reflective QoS Indicator 159 WWC Wireless Wireline Convergence 161 4. 5G Wireline Transport over PPP 163 The 5G Wireline Control Protocol (5WCP) is responsible for 164 configuring, enabling, and disabling the 5G Wireline protocol modules 165 on both ends of the point-to-point link. 5WCP uses the same packet 166 exchange mechanism as the Link Control Protocol (LCP) [RFC1661]. 167 5WCP packets may not be exchanged until PPP has reached the Network- 168 Layer Protocol phase. 5WCP packets received before this phase is 169 reached MUST be silently discarded. 171 4.1. 5G Wireline Conrol Protocol for 5G AS/NAS 173 5WCP is exactly same as the LCP [RFC1661] with the following 174 exceptions: 176 Data Link Layer Protocol Field 178 Exactly one 5WCP packet is encapsulated in the Information 179 field of PPP Data Link Layer frames where the Protocol field 180 indicates type hex 80##/8037 (5G Wireline Control Protocol). 182 Code field 183 Only Codes 1 through 7 (Configure-Request, Configure-Ack, 184 Configure-Nak, Configure-Reject, Terminate-Request, Terminate- 185 Ack and Code-Reject) are used. Other Codes should be treated 186 as unrecognized and should result in Code-Rejects. 188 Configuration Option Types 190 5WCP has no Configuration Options. 192 The format of 5WCP packets is defined here. 194 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 195 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 196 | CODE | IDENTIFIER | LENGTH | 197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 | DATA ~ 199 +-+-+-+-++-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 Figure 1: 5G Wireline Control Protocol Packet Format. 203 The description of each field is as follows: 205 CODE is one octet, and valid values are only 1 through 7 207 IDENTIFIER is one octet, and aids in matching requests and 208 replies. 210 LENGTH is two octets, and is the length of the packet, including 211 the Code, Identifier, Length and Data fields. Length MUST NOT 212 exceed the MRU of the link. 214 DATA is the 5WCP Payload 216 The format of 5WCP Payload is defined here. 218 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 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | VER | FLAGS | MSG TYPE | ATLV COUNT | 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | ATTRIBUTE TLV(s) | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | PAYLOAD (NAS PDU) ~ 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 Figure 2: 5G Wireline Control Payload Format. 229 The description of each field is as follows: 231 VER is the version. It MUST be set to 1. 233 FLAGS is for future extensibility. It MUST be set to 0. 235 MSG TYPE as defined in Section 9.7 of [TS.24.501-3GPP] 237 ATLV COUNT is the total number of ATTRIBUTE TLV(s) in the header 239 ATTRIBUTE TLV 241 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 242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 243 | TYPE | LENGTH | VALUE ~ 244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 246 Figure 3: Attribute TLV Format. 248 PAYLOAD is the NAS PDU as defined in [TS.24.501-3GPP] 250 4.2. Sending 5G Wireline Datagrams 252 Before any 5G Wireline Data packets may be communicated, PPP must 253 reach the Network-Layer Protocol phase, and the 5G Wireline Control 254 Protocol must reach the Opened state. 256 Exactly one 5G Wireline Data packet is encapsulated in the PPP Data 257 Link Layer frames where the Protocol field indicates type hex 00## / 258 0037 (5G Wireline Data). 260 The maximum length of an IP packet transmitted over a PPP link is 261 same as the maximum length of the Information field of a PPP data 262 link layer frame. 264 The format of 5G Wireline Data is defined here. 266 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 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 268 | VER |U|R| FLAGS | PROTOCOL ID | 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 | PDU SESSION ID| QFI | LENGTH | 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 272 | PAYLOAD ~ 273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 275 Figure 4: 5G Wireline Data Packet Format. 277 The description of each field is as follows: 279 VER is the version. It MUST be set to 1. 281 U is set to 1 for PDU Session of type UNSTRUCTURED as defined in 282 Section 9.11.4.1 of [TS.24.501-3GPP] 284 R is set to 1 if Reflective QoS is enabled for the PDU Session 286 FLAGS is set to 0. 288 PROTOCOL ID is the 16 bit identifier of the data payload type 289 encoded using values from the IANA PPP DLL protocol numbers 290 registry. (https://www.iana.org/assignments/ppp-numbers/ppp- 291 numbers.xhtml#ppp-numbers-2) 293 The following values are examples for PROTOCOL ID: 295 0x0021: Internet Protocol, Version 4 (IPv4) 297 0x0057: Internet Protocol, Version 6 (IPv6) 299 QFI is set to the QoS Flow Indicator. 301 LENGTH includes all header fields and Payload length in BYTES. 303 PAYLOAD is encoded as per the protocol ID. 305 4.3. 5G Wireline Control Protocol Procedures 307 The following sections describe the detailed 5WCP procedures that map 308 to 5G NAS Procedures as described in [TS.24.501-3GPP] 310 4.3.1. 5WCP Registration Procedure 312 The 5WCP Registration Procedure is described below: 314 5G-RG W-AGF 315 +----------------------------------------------------------+ 317 +----Configure-Request (Registration Request)----> 319 <----Configure-Ack (Registration Accept)---------+ 321 <----Configure-Nack (Registration Reject)--------+ 323 +----Configure-Ack(Registration Complete)---------> 325 4.3.2. 5WCP De-registration Procedure 327 The 5WCP De-registration Procedure is described below: 329 4.3.2.1. 5GCP initiated De-registration Procedure 331 5G-RG W-AGF 332 +---------------------------------------------------------+ 334 <--Terminate-Request (De-registration Request)--+ 336 +---Terminate-Ack (De-registration Accept)------> 338 4.3.2.2. 5G-RG initiated De-registration Procedure 340 5G-RG W-AGF 341 +---------------------------------------------------------+ 343 +--Terminate-Request (De-registration Request)--> 345 <------Terminate-Ack (De-registration Accept)---+ 347 4.3.3. 5WCP Authentication Procedure 349 The 5WCP Authentication Procedure is described below: 351 5G-RG W-AGF 352 +----------------------------------------------------------+ 354 <---Configure-Request (Authentication Request)---+ 356 +-----Configure-Ack (Authentication Response)----> 358 <-----Configure-Ack (Authentication Result)------+ 360 +-----Configure-Nack (Authentication Failure)----> 362 <-----Configure-Nack (Authentication Reject)-----+ 364 4.3.4. 5WCP Identity Procedure 366 The 5WCP Identity Procedure is described below: 368 5G-RG W-AGF 369 +--------------------------------------------------------+ 371 <----Configure-Request (Identity Request)------+ 373 +----Configure-Ack (Identity Response)---------> 375 4.3.5. 5WCP Configuration Update Procedure 377 The 5WCP Configuration Update Procedure is described below: 379 5G-RG W-AGF 380 +-----------------------------------------------------------+ 382 <--Configure-Request (Configuration Update Command)--+ 384 +--Configure-Ack (Configuration Update Complete)-----> 386 4.3.6. 5WCP Service Request Procedure 388 The 5WCP Service Request Procedure is described below: 390 5G-RG W-AGF 391 +----------------------------------------------------------+ 393 +------Configure-Request (Service Request)------> 395 <-------Configure-Ack (Service Accept)----------+ 397 <------Configure-Nack (Service Reject)----------+ 399 4.3.7. 5WCP Notification Procedure 401 The 5WCP Notification Procedure is described below: 403 5G-RG W-AGF 404 +----------------------------------------------------------+ 406 <-------Configure-Request (Notification)---------+ 408 +----Configure-Ack (Notification Response)--------> 410 4.3.8. 5WCP Security Mode Procedure 412 The 5WCP Security Mode Procedure is described below: 414 5G-RG W-AGF 415 +----------------------------------------------------------+ 417 <---Configure-Request (Security Mode Command)---+ 419 +---Configure-Ack (Security Mode Complete)------> 421 +---Configure-Nack (Security Mode Reject)-------> 423 4.3.9. 5WCP UL/DL Procedure 425 The 5WCP UL/DL Procedure is described below: 427 5G-RG W-AGF 428 +----------------------------------------------------------+ 430 <-----Configure-Request (DL NAS Transport)-----+ 432 +----------------Configure-Ack ----------------> 434 +-----Configure-Request (UL NAS Transport)-----> 436 <----------------Configure-Ack ----------------+ 438 4.3.10. 5WCP 5GMM Status Procedure 440 The 5WCP 5GMM Status Procedure is described below: 442 5G-RG W-AGF 443 +----------------------------------------------------------+ 445 <-------Configure-Request (5GMM Status)-------+ 447 +----------------Configure-Ack ----------------> 449 +-------Configure-Request (5GMM Status)--------> 451 <----------------Configure-Ack ----------------+ 453 4.3.11. 5WCP PDU Session Establishment Procedure 455 The 5WCP PDU Session Establishment Procedure is described below: 457 5G-RG W-AGF 458 +------------------------------------------------------------+ 460 +-Configure-Request(PDU Session Establishment Request)-> 462 <---Configure-Ack(PDU Session Establishment Accept)----+ 464 <---Configure-Nack(PDU Session Establishment Reject)---+ 466 4.3.12. 5WCP PDU Session Modification Procedure 468 The 5WCP PDU Session Modification Procedure is described below: 470 5G-RG W-AGF 471 +------------------------------------------------------------+ 473 +-Configure-Request(PDU Session Modification Request)-> 475 <---Configure-Nack(PDU Session Modification Reject)---+ 477 <-Configure-Request(PDU Session Modification Command)-+ 479 +---Configure-Ack(PDU Session Modification Complete)--> 481 +-Configure-Nack(PDU Session Modification Cmd Reject)-> 483 4.3.13. 5WCP PDU Session Release Procedure 485 The 5WCP PDU Session Release Procedure is described below: 487 5G-RG W-AGF 488 +------------------------------------------------------------+ 490 +---Configure-Request(PDU Session Release Request)---> 492 <-----Configure-Nack(PDU Session Release Reject)-----+ 494 <---Configure-Request(PDU Session Release Command)---+ 496 +-----Configure-Ack(PDU Session Release Complete)----> 498 4.3.14. 5WCP 5GSM Status Procedure 500 The 5WCP 5GSM Status Procedure is described below: 502 5G-RG W-AGF 503 +----------------------------------------------------------+ 505 <-------Configure-Request (5GSM Status)-------+ 507 +----------------Configure-Ack ----------------> 509 +-------Configure-Request (5GSM Status)--------> 511 <----------------Configure-Ack ----------------+ 513 5. Security Considerations 515 5G NAS procedures used for session life cycle maintenance employ 516 ciphering and integrity protection as defined in [TS.33.501-3GPP]. 518 There is no impact on the security of a fixed access network and it 519 will be equivalent to current practice. 521 6. IANA Considerations 523 IANA is requested to create a registry on the Point-to-Point (PPP) 524 Protocol Field Assignments IANA Web page as follows: 526 Registry Name: PPP DLL Protocol Numbers 528 Registration Procedure: 529 0xxx-3xxx IETF Review Network Layer Protocols 530 8xxx-bxxx IETF Review Network Control Protocols 532 Code-Points 533 ---------------------------------------------------------- 534 Value (in hex) Protocol Name Reference 535 ---------------------------------------------------------- 536 0037 5G Wireline Data [This Document] 537 8037 5G Wireline Control [This Document] 538 ----------------------------------------------------------- 540 7. Acknowledgments 542 Some of the text in this document is taken from previous documents 543 produced by the Point-to-Point Protocol Working Group of the Internet 544 Engineering Task Force (IETF). 546 The author would also like to thank Ron Bonica for all his help and 547 John Gibbons for reviewing the document. 549 8. References 551 8.1. Normative References 553 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 554 Requirement Levels", BCP 14, RFC 2119, 555 DOI 10.17487/RFC2119, March 1997, 556 . 558 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 559 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 560 May 2017, . 562 [RFC1661] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", 563 STD 51, RFC 1661, DOI 10.17487/RFC1661, July 1994, 564 . 566 [TS.24.501-3GPP] 567 3rd Generation Partnership Project (3GPP), "Non-Access- 568 Stratum (NAS) protocol for 5G System (5GS); Stage 3, 3GPP 569 TS 24.501 v16.5.1", July 2020. 571 [TS.24.007-3GPP] 572 3rd Generation Partnership Project (3GPP), "Wireless and 573 wireline convergence access support for the 5G System 574 (5GS) v16.3.0", July 2020. 576 8.2. Informative References 578 [RFC1332] McGregor, G., "The PPP Internet Protocol Control Protocol 579 (IPCP)", RFC 1332, DOI 10.17487/RFC1332, May 1992, 580 . 582 [RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D., 583 and R. Wheeler, "A Method for Transmitting PPP Over 584 Ethernet (PPPoE)", RFC 2516, DOI 10.17487/RFC2516, 585 February 1999, . 587 [TS.23.501-3GPP] 588 3rd Generation Partnership Project (3GPP), "System 589 Architecture for 5G System; Stage 2, 3GPP TS 23.501 590 v16.5.1", August 2020. 592 [TS.23.502-3GPP] 593 3rd Generation Partnership Project (3GPP), "Procedures for 594 the 5G System (5GS); 3GPP TS 23.502 v16.5.1", August 2020. 596 [TS.23.316-3GPP] 597 3rd Generation Partnership Project (3GPP), "Wireless and 598 wireline convergence access support for the 5G System 599 (5GS) v16.4.0", July 2020. 601 [TS.33.501-3GPP] 602 3rd Generation Partnership Project (3GPP), "Security 603 architecture and procedures for 5G System, 3GPP TS 33.501 604 v16.3.0", July 2020. 606 [BBF.TR.101] 607 Broadband Forum (BBF), "Migration to Ethernet-Based 608 Broadband Aggregation, BBF TR 101 issue:2", July 2011. 610 Author's Address 612 Venkatesh Padebettu 613 Juniper Networks Inc. 614 Exora Business Park 615 Bangalore, KA 560103 616 India 618 Email: vpadebettu@juniper.net