idnits 2.17.1 draft-zch-lsr-isis-network-slicing-01.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 is 1 instance of too long lines in the document, the longest one being 4 characters in excess of 72. ** The abstract seems to contain references ([I-D.peng-lsr-network-slicing]), 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 (July 6, 2019) is 1749 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: 'RFC2119' is defined on line 297, but no explicit reference was found in the text == Outdated reference: A later version (-17) exists of draft-ietf-teas-enhanced-vpn-01 ** Downref: Normative reference to an Informational draft: draft-ietf-teas-enhanced-vpn (ref. 'I-D.ietf-teas-enhanced-vpn') ** Obsolete normative reference: RFC 5316 (Obsoleted by RFC 9346) Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Networking Working Group Yongqing. Zhu 3 Internet-Draft China Telecom 4 Intended status: Standards Track Ran. Chen 5 Expires: January 7, 2020 Shaofu. Peng 6 ZTE Corporation 7 July 6, 2019 9 IS-IS Extensions to Support Packet Network Slicing using Segment Routing 10 draft-zch-lsr-isis-network-slicing-01 12 Abstract 14 [I-D.peng-lsr-network-slicing] defines a unified administrative 15 instance identifier to distinguish different virtual network 16 resources for both intra-domain and inter-domain network slicing 17 scenarios. This draft describes the IS-IS extensions required to 18 support Packet Network Slicing using Segment Routing. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on January 7, 2020. 37 Copyright Notice 39 Copyright (c) 2019 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Conventions used in this document . . . . . . . . . . . . . . 2 56 3. Advertising AII information as a new TE parameter of a link . 2 57 4. Advertising prefix-SID per AII information . . . . . . . . . 4 58 5. Advertising Adjacency-SID per AII information . . . . . . . . 5 59 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 60 6.1. AII list sub-TLV . . . . . . . . . . . . . . . . . . . . 6 61 6.2. Prefix-SID for AII sub-TLV . . . . . . . . . . . . . . . 6 62 6.3. Adjacency -SID for AII sub-TLV . . . . . . . . . . . . . 6 63 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 64 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 65 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 66 9.1. Normative references . . . . . . . . . . . . . . . . . . 6 67 9.2. Informative references . . . . . . . . . . . . . . . . . 8 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 70 1. Introduction 72 For a packet network, network slicing requires the underlying network 73 to support partitioning of the network resources to provide the 74 client with dedicated (private) networking, computing, and storage 75 resources drawn from a shared pool. The slices may be seen as 76 virtual networks. [I-D.ietf-teas-enhanced-vpn] described a framework 77 to create virtual networks in a packet network. 78 [I-D.peng-lsr-network-slicing] specifies a detailed mechanism to 79 signal association of shared resources required to create and manage 80 an NSI called "Administrative Instance Identifier" (AII). 82 This draft describes the IS-IS extensions required to distribute AII 83 information in an AS. 85 2. Conventions used in this document 87 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 88 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 89 document are to be interpreted as described in RFC2119. 91 3. Advertising AII information as a new TE parameter of a link 93 [RFC5305] describes extensions to the Intermediate System to 94 Intermediate System (IS-IS) protocol to support Traffic Engineering 95 (TE). 97 AII can be used to color links to partition underlay resource. This 98 document defines a new extension of the existing IGP-TE 99 mechanisms[RFC5305] to distribute AII information in an AS as a new 100 TE parameter of a link. 102 The AII list sub-TLV has the following format: 104 0 1 2 3 105 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 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 | Type=TBD1 | Length | Reserved | Number | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | AII for virtual networks 1 | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 | ...... | 112 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 113 | AII for virtual networks N | 114 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 116 Figure 1 118 Type: 43 (Suggested value to be assigned by IANA) 120 Length: variable. 122 Number:Number of virtual networks. 124 AII for VN: allocate different AII for different virtual networks. 125 AII is used to distinguish different virtual network resources. 127 This sub-TLV MAY be present in any of the following TLVs: 129 TLV-22 (Extended IS reachability) [RFC5305]. 131 TLV-222 (Multitopology IS)[RFC5120]. 133 TLV-23 (IS Neighbor Attribute)[RFC5311]. 135 TLV-223 (Multitopology IS Neighbor Attribute)[RFC5311]. 137 TLV-141 (inter-AS reachability information)[RFC5316]. 139 This sub-TLV SHOULD appear once at most in each TLV. Indicates that 140 a link MAY belong to multiple virtual networks. 142 Note that AII 0 does not require notification, and all links are 143 always in AII 0 at the same time. 145 4. Advertising prefix-SID per AII information 147 [I-D.ietf-isis-segment-routing-extensions] defines a new IS-IS sub- 148 TLV: the Prefix Segment Identifier sub-TLV (Prefix-SID sub-TLV). The 149 Prefix-SID sub-TLV carries the Segment Routing IGP-Prefix-SID as 150 defined in [RFC8402], and is associated to a prefix advertised by a 151 node. 153 To distinguish forwarding behavior of different virtual networks, 154 Prefix-SID need to be allocated per AII and advertised in the IGP 155 domain. This document defines a new extension of the existing 156 Prefix-SID sub-TLV. 158 The Prefix-SID for AII sub-TLV has the following format: 160 0 1 2 3 161 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 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | Type=TBD2 | Length | Flag | Algorithm | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | AII | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | SID/Index/Label(Variable) | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 170 Figure 2 172 where: 174 Type:33 (Suggested value to be assigned by IANA) 176 Length: Variable. Depending on the size of the SID. 178 The "Flags" and "SID/Index/Label" fields are the same as the Prefix- 179 SID sub-TLV [I-D.ietf-isis-segment-routing-extensions]. 181 AII: Identifies the AII information corresponding to the Prefix-SID. 183 This sub-TLV MAY be present in any of the following TLVs: 185 TLV-135 (Extended IPv4 reachability) defined in [RFC5305]. 187 TLV-235 (Multitopology IPv4 Reachability) defined in [RFC5120]. 189 TLV-236 (IPv6 IP Reachability) defined in [RFC5308]. 191 TLV-237 (Multitopology IPv6 IP Reachability) defined in [RFC5120]. 193 This sub-TLV MAY appear multiple times in each TLV. 195 5. Advertising Adjacency-SID per AII information 197 [I-D.ietf-isis-segment-routing-extensions]defines a new IS-IS sub- 198 TLV: the Adjacency Segment Identifier sub-TLV (Adj-SID sub-TLV).The 199 Adj-SID sub-TLV is an optional sub-TLV carrying the Segment Routing 200 IGP-Adjacency-SID as defined in [RFC8402]. 202 To distinguish forwarding behavior of different virtual networks, 203 Adjacency -SID need to be allocated per AII and advertised in the IGP 204 domain. This document defines a new extension of the existing 205 Adjacency-SID sub-TLV. 207 The Adjacency-SID for AII sub-TLV has the following format: 209 0 1 2 3 210 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 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 | Type=TBD3 | Length | Flag | Algorithm | 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 | AII | 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 | SID/Index/Label(Variable) | 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 219 Figure 3 221 where: 223 Type:44 (Suggested value to be assigned by IANA) 225 Length: Variable. Depending on the size of the SID. 227 The "Flags" and "SID/Index/Label" fields are the same as the 228 Adjacency-SID sub-TLV [I-D.ietf-isis-segment-routing-extensions]. 230 AII: Identifies the AII information corresponding to the Adjacency- 231 SID. 233 This sub-TLV MAY be present in any of the following TLVs: 235 TLV-22 (Extended IS reachability) [RFC5305]. 237 TLV-222 (Multitopology IS)[RFC5120]. 239 TLV-23 (IS Neighbor Attribute)[RFC5311]. 241 TLV-223 (Multitopology IS Neighbor Attribute)[RFC5311]. 243 TLV-141 (inter-AS reachability information)[RFC5316]. 245 Multiple Adj-SID sub-TLVs MAY be associated with a single IS- 246 neighbor. This sub-TLV MAY appear multiple times in each TLV. 248 6. IANA Considerations 250 This document requests allocation for the following Sub-TLVs. 252 6.1. AII list sub-TLV 254 This TLV shares sub-TLV space with existing "Sub-TLVs for TLVs 22, 255 222, 23,223 and 141 registry". 257 Type:43(suggested - to be assigned by IANA). 259 6.2. Prefix-SID for AII sub-TLV 261 This TLV shares sub-TLV space with existing "Sub-TLVs for TLVs 262 135,235,226 and 237 registry". 264 Type:33(suggested - to be assigned by IANA). 266 6.3. Adjacency -SID for AII sub-TLV 268 This TLV shares sub-TLV space with existing "Sub-TLVs for TLVs 22, 269 222, 23,223 and 141 registry". 271 Type:44(suggested - to be assigned by IANA). 273 7. Security Considerations 275 TBD. 277 8. Acknowledgements 279 TBD. 281 9. References 283 9.1. Normative references 285 [I-D.ietf-isis-segment-routing-extensions] 286 Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., 287 Gredler, H., and B. Decraene, "IS-IS Extensions for 288 Segment Routing", draft-ietf-isis-segment-routing- 289 extensions-25 (work in progress), May 2019. 291 [I-D.ietf-teas-enhanced-vpn] 292 Dong, J., Bryant, S., Li, Z., Miyasaka, T., and Y. Lee, "A 293 Framework for Enhanced Virtual Private Networks (VPN+) 294 Service", draft-ietf-teas-enhanced-vpn-01 (work in 295 progress), February 2019. 297 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 298 Requirement Levels", BCP 14, RFC 2119, 299 DOI 10.17487/RFC2119, March 1997, 300 . 302 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 303 Topology (MT) Routing in Intermediate System to 304 Intermediate Systems (IS-ISs)", RFC 5120, 305 DOI 10.17487/RFC5120, February 2008, 306 . 308 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 309 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 310 2008, . 312 [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, 313 DOI 10.17487/RFC5308, October 2008, 314 . 316 [RFC5311] McPherson, D., Ed., Ginsberg, L., Previdi, S., and M. 317 Shand, "Simplified Extension of Link State PDU (LSP) Space 318 for IS-IS", RFC 5311, DOI 10.17487/RFC5311, February 2009, 319 . 321 [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in 322 Support of Inter-Autonomous System (AS) MPLS and GMPLS 323 Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, 324 December 2008, . 326 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 327 Decraene, B., Litkowski, S., and R. Shakir, "Segment 328 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 329 July 2018, . 331 9.2. Informative references 333 [I-D.peng-lsr-network-slicing] 334 Peng, S., Chen, R., and G. Mirsky, "Packet Network Slicing 335 using Segment Routing", draft-peng-lsr-network-slicing-00 336 (work in progress), February 2019. 338 Authors' Addresses 340 Yongqing Zhu 341 China Telecom 343 Email: zhuyq.gd@chinatelecom.cn 345 Ran Chen 346 ZTE Corporation 348 Email: chen.ran@zte.com.cn 350 Shaofu Peng 351 ZTE Corporation 353 Email: peng.shaofu@zte.com.cn