idnits 2.17.1 draft-li-mpls-e2e-ietf-network-slicing-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 244 has weird spacing: '... Option this ...' -- The document date (April 14, 2021) is 1080 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) == Outdated reference: A later version (-17) exists of draft-ietf-teas-enhanced-vpn-06 ** Downref: Normative reference to an Informational draft: draft-ietf-teas-enhanced-vpn (ref. 'I-D.ietf-teas-enhanced-vpn') == Outdated reference: A later version (-01) exists of draft-ietf-teas-ietf-network-slice-definition-00 ** Downref: Normative reference to an Informational draft: draft-ietf-teas-ietf-network-slice-definition (ref. 'I-D.ietf-teas-ietf-network-slice-definition') ** Downref: Normative reference to an Informational draft: draft-ietf-teas-ietf-network-slice-framework (ref. 'I-D.ietf-teas-ietf-network-slice-framework') == Outdated reference: A later version (-03) exists of draft-li-mpls-enhanced-vpn-vtn-id-01 == Outdated reference: A later version (-04) exists of draft-dong-teas-enhanced-vpn-vtn-scalability-01 Summary: 3 errors (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Z. Li 3 Internet-Draft J. Dong 4 Intended status: Standards Track Huawei Technologies 5 Expires: October 16, 2021 April 14, 2021 7 Encapsulation of End-to-End IETF Network Slice Information in MPLS 8 draft-li-mpls-e2e-ietf-network-slicing-00 10 Abstract 12 Network slicing can be used to meet the connectivity and performance 13 requirement of different services or customers in a shared network. 14 An IETF network slice may span multiple network domains. And in the 15 context of 5G, the 5G end-to-end network slices consist of three 16 major types of network segments: Radio Access Network (RAN), 17 Transport Network (TN) and Core Network (CN). 19 In order to facilitate the mapping between network slices in 20 different network segments and network domains, it is beneficial to 21 carry the identifiers of the 5G end-to-end network slice, the multi- 22 domain IETF network slice together with the intra-domain network 23 slice identifier in the data packet. 25 This document defines the mechanism of encapsulating the end-to-end 26 network slice related identifiers in MPLS data plane. 28 Requirements Language 30 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 31 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 32 document are to be interpreted as described in RFC 2119 [RFC2119]. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at https://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on October 16, 2021. 50 Copyright Notice 52 Copyright (c) 2021 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (https://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 68 2. Extensions to MPLS VTN Extension Header . . . . . . . . . . . 3 69 2.1. Global VTN-ID Option . . . . . . . . . . . . . . . . . . 4 70 2.2. 5G Network Slice ID Option . . . . . . . . . . . . . . . 5 71 3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 5 72 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 73 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 74 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 75 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 76 7.1. Normative References . . . . . . . . . . . . . . . . . . 6 77 7.2. Informative References . . . . . . . . . . . . . . . . . 7 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 80 1. Introduction 82 The definition and the characteristics of IETF are introduced in 83 [I-D.ietf-teas-ietf-network-slice-definition], and 84 [I-D.ietf-teas-ietf-network-slice-framework] describes a general 85 framework of IETF network slice. 87 [I-D.ietf-teas-enhanced-vpn] describes the framework and the 88 candidate component technologies for providing enhanced VPN services. 89 VPN+ can be built from a VPN overlay and an underlying Virtual 90 Transport Network (VTN), which has a customized network topology and 91 a set of dedicated or shared resources in the underlay network. 92 Enhanced VPN (VPN+) can be used for the realization of IETF network 93 slices. 95 [I-D.dong-teas-enhanced-vpn-vtn-scalability] describes the 96 scalability considerations in the control plane and data plane to 97 enable VPN+ services, and provide several suggestions to improve the 98 scalability of VTN. In the control plane, It proposes the approach 99 of decoupling the topology and resource attributes of VTN, so that 100 multiple VTNs may share the same topology and the result of topology 101 based path computation. In the data plane, it proposes to carry a 102 VTN-ID in the data packet to determine the set of resources reserved 103 for the corresponding VTN. 105 An IETF network slice may span multiple network domains. Further in 106 the context of 5G, there can be end-to-end network slices which 107 consists of three major types of network segments: Radio Access 108 Network (RAN), Transport Network (TN) and Core Network (CN). In 109 order to facilitate the mapping between network slices in different 110 network segments and network domains, it may be beneficial to carry 111 the identifiers of the 5G end-to-end network slice and the multi- 112 domain IETF network slice together with the intra-domain network 113 slice identifier in the data packet. 115 [I-D.li-teas-e2e-ietf-network-slicing] describes the framework of 116 carrying end-to-end network slice related identifiers in the data 117 plane, each of the identifiers may span a different network scope. 119 With MPLS data plane, [I-D.li-mpls-enhanced-vpn-vtn-id] specifies the 120 extensions and mechanisms to carry the VTN-ID of a single network 121 domain in an MPLS extension header, so as to improve the scalability 122 of VTN [I-D.dong-teas-enhanced-vpn-vtn-scalability]. This document 123 further specifies the extensions and mechanisms of encapsulating the 124 identifiers of the 5G end-to-end network slice and the multi-domain 125 IETF network slice in MPLS data plane to support the end-to-end 126 network slicing. 128 2. Extensions to MPLS VTN Extension Header 130 This section describes the approach of encapsulating the end-to-end 131 network slice identifiers in MPLS data plane. Two new options are 132 defined in the MPLS VTN extension header as defined in 133 [I-D.li-mpls-enhanced-vpn-vtn-id]. 135 The format of the VTN extension header is shown as below: 137 0 1 2 3 138 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 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 |Nibble | Length| Flags | Reserved | 141 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 142 ~ Options ~ 143 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 144 Figure 1. The format of VTN extension header 146 The Global VTN-ID and the 5G network slice identifier (i.e. S-NSSAI) 147 are defined as two new options of the VTN extension header. 148 Depending on whether a IETF network slice spans multiple domains and 149 whether it is used as part of the 5G end-to-end network slice, the 150 Global VTN-ID and the 5G network slice ID are optional in the data 151 packet. 153 2.1. Global VTN-ID Option 155 The format of the Global VTN-ID option is shown as below: 157 Option Option Option 158 Type Data Len Data 159 +--------+--------+--------+--------+--------+--------+ 160 |BBCTTTTT|00000100| Global VTN-ID | 161 +--------+--------+--------+--------+--------+--------+ 162 Figure 2. The format of Global VTN-ID Option 164 Option Type: 8-bit identifier of the type of option. The type of 165 Global VTN-ID option is to be assigned by IANA. The highest-order 166 bits of the type field are defined as below: 168 o BB 00 The highest-order 2 bits are set to 00 to indicate that a 169 node which does not recognize this type will skip over it and 170 continue processing the header. 172 o C 0 The third highest-order bit are set to 0 to indicate this 173 option does not change en route. 175 Opt Data Len: 8-bit unsigned integer indicates the length of the 176 option Data field of this option, in octets. The value of Opt Data 177 Len of the Global VTN-ID option SHOULD be set to 4. 179 Option Data: 4-octet identifier which uniquely identifies a global 180 VTN which spans multiple network domains. 182 2.2. 5G Network Slice ID Option 184 The format of the 5G network slice ID option is shown as below: 186 Option Option Option 187 Type Data Len Data 188 +--------+--------+--------+--------+--------+--------+ 189 |BBCTTTTT|00000100| S-NSSAI | 190 +--------+--------+--------+--------+--------+--------+ 191 Figure 3. The format of 5G network slice ID Option 193 Option Type: 8-bit identifier of the type of option. The type of 5G 194 network slice ID option is to be assigned by IANA. The highest-order 195 bits of the type field are defined as below: 197 o BB 00 The highest-order 2 bits are set to 00 to indicate that a 198 node which does not recognize this type will skip over it and 199 continue processing the header. 201 o C 0 The third highest-order bit are set to 0 to indicate this 202 option does not change en route. 204 Opt Data Len: 8-bit unsigned integer indicates the length of the 205 option Data field of this option, in octets. The value of Opt Data 206 Len of the 5G network slice ID option SHOULD be set to 4. This 207 aligns with the length of the S-NSSAI defined in 3GPP. 209 Option Data: 4-octet identifier which uniquely identifies a 5G end- 210 to-end network slice. 212 3. Procedures 214 The ingress node of a multi-domain IETF network slice SHOULD 215 encapsulate the received packet with an MPLS label stack and the VTN 216 extension header, the Global VTN-ID the packet is mapped to MAY be 217 carried in the Global VTN-ID option of the VTN extension header. 219 The edge nodes of each domain MAY parse the Global VTN-ID in the VTN 220 extension header and maps it to a local VTN. When the mechanism as 221 defined in [I-D.li-mpls-enhanced-vpn-vtn-id] is used in the local 222 domain, the Local VTN-ID is obtained from the mapping relationship 223 between the Global VTN-ID and Local VTN-ID maintained on the edge 224 node, and the Local VTN-ID SHOULD be encapsulated in the VTN 225 extension header. The Local VTN-ID is used to identify the local 226 network resources reserved for the VTN in the local domain. The 227 local VTN-ID in the packet MAY be updated on the edge nodes of each 228 domain. 230 When the multi-domain IETF network slice is part of a 5G end-to-end 231 network slice, the 5G Network Slice ID option MAY be carried in the 232 VTN extension header. The S-NSSAI MAY be used for the collection and 233 report of the performance information of the 5G end-to-end network 234 slice in the transport network. 236 4. IANA Considerations 238 IANA is requested to assign two option types of the VTN extension 239 header. 241 Value Description Reference 242 ------------------------------------------------- 243 TBD1 Global VTN-ID Option this document 244 TBD2 5G Network Slice ID Option this document 246 5. Security Considerations 248 TBD 250 6. Acknowledgements 252 TBD 254 7. References 256 7.1. Normative References 258 [I-D.ietf-teas-enhanced-vpn] 259 Dong, J., Bryant, S., Li, Z., Miyasaka, T., and Y. Lee, "A 260 Framework for Enhanced Virtual Private Networks (VPN+) 261 Service", draft-ietf-teas-enhanced-vpn-06 (work in 262 progress), July 2020. 264 [I-D.ietf-teas-ietf-network-slice-definition] 265 Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J. 266 Tantsura, "Definition of IETF Network Slices", draft-ietf- 267 teas-ietf-network-slice-definition-00 (work in progress), 268 January 2021. 270 [I-D.ietf-teas-ietf-network-slice-framework] 271 Gray, E. and J. Drake, "Framework for IETF Network 272 Slices", March 2021, . 275 [I-D.li-mpls-enhanced-vpn-vtn-id] 276 Li, Z. and J. Dong, "Carrying Virtual Transport Network 277 Identifier in MPLS Packet", draft-li-mpls-enhanced-vpn- 278 vtn-id-01 (work in progress), April 2021. 280 [I-D.li-teas-e2e-ietf-network-slicing] 281 Li, Z. and J. Dong, "Framework for End-to-End IETF Network 282 Slicing", April 2021, . 285 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 286 Requirement Levels", BCP 14, RFC 2119, 287 DOI 10.17487/RFC2119, March 1997, 288 . 290 7.2. Informative References 292 [I-D.dong-teas-enhanced-vpn-vtn-scalability] 293 Dong, J., Li, Z., Qin, F., and G. Yang, "Scalability 294 Considerations for Enhanced VPN (VPN+)", draft-dong-teas- 295 enhanced-vpn-vtn-scalability-01 (work in progress), 296 November 2020. 298 Authors' Addresses 300 Zhenbin Li 301 Huawei Technologies 302 Huawei Campus, No. 156 Beiqing Road 303 Beijing 100095 304 China 306 Email: lizhenbin@huawei.com 308 Jie Dong 309 Huawei Technologies 310 Huawei Campus, No. 156 Beiqing Road 311 Beijing 100095 312 China 314 Email: jie.dong@huawei.com