idnits 2.17.1 draft-zch-lsr-isis-network-slicing-02.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-teas-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 (November 4, 2019) is 1635 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 292, but no explicit reference was found in the text ** Obsolete normative reference: RFC 5316 (Obsoleted by RFC 9346) == Outdated reference: A later version (-04) exists of draft-peng-teas-network-slicing-00 Summary: 3 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: May 7, 2020 Shaofu. Peng 6 ZTE Corporation 7 Fengwei. Qin 8 China Mobile 9 November 4, 2019 11 IS-IS Extensions to Support Packet Network Slicing using Segment Routing 12 draft-zch-lsr-isis-network-slicing-02 14 Abstract 16 [I-D.peng-teas-network-slicing] defines a unified administrative 17 instance identifier to distinguish different virtual network 18 resources for both intra-domain and inter-domain network slicing 19 scenarios. This draft describes the IS-IS extensions required to 20 support Packet Network Slicing using Segment Routing. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on May 7, 2020. 39 Copyright Notice 41 Copyright (c) 2019 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Conventions used in this document . . . . . . . . . . . . . . 2 58 3. Advertising AII information as a new TE parameter of a link . 2 59 4. Advertising prefix-SID per AII information . . . . . . . . . 4 60 5. Advertising Adjacency-SID per AII information . . . . . . . . 5 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 62 6.1. AII list sub-TLV . . . . . . . . . . . . . . . . . . . . 6 63 6.2. Prefix-SID for AII sub-TLV . . . . . . . . . . . . . . . 6 64 6.3. Adjacency -SID for AII sub-TLV . . . . . . . . . . . . . 6 65 7. Security Considerations . . . . . . . . . . . . . . . . . . . 6 66 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 67 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 68 9.1. Normative references . . . . . . . . . . . . . . . . . . 6 69 9.2. Informative references . . . . . . . . . . . . . . . . . 7 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 72 1. Introduction 74 For a packet network, network slicing requires the underlying network 75 to support partitioning of the network resources to provide the 76 client with dedicated (private) networking, computing, and storage 77 resources drawn from a shared pool. The slices may be seen as 78 virtual networks. [I-D.peng-teas-network-slicing] specifies a 79 detailed mechanism to signal association of shared resources required 80 to create and manage an NSI called "Administrative Instance 81 Identifier" (AII). 83 This draft describes the IS-IS extensions required to distribute AII 84 information in an AS. 86 2. Conventions used in this document 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 90 document are to be interpreted as described in RFC2119. 92 3. Advertising AII information as a new TE parameter of a link 94 [RFC5305] describes extensions to the Intermediate System to 95 Intermediate System (IS-IS) protocol to support Traffic Engineering 96 (TE). 98 AII can be used to color links to partition underlay resource. This 99 document defines a new extension of the existing IGP-TE 100 mechanisms[RFC5305] to distribute AII information in an AS as a new 101 TE parameter of a link. 103 The AII list sub-TLV has the following format: 105 0 1 2 3 106 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 107 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 108 | Type=TBD1 | Length | Reserved | Number | 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 | AII for virtual networks 1 | 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 | ...... | 113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 | AII for virtual networks N | 115 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 Figure 1 119 Type: 43 (Suggested value to be assigned by IANA) 121 Length: variable. 123 Number:Number of virtual networks. 125 AII for VN: allocate different AII for different virtual networks. 126 AII is used to distinguish different virtual network resources. 128 This sub-TLV MAY be present in any of the following TLVs: 130 TLV-22 (Extended IS reachability) [RFC5305]. 132 TLV-222 (Multitopology IS)[RFC5120]. 134 TLV-23 (IS Neighbor Attribute)[RFC5311]. 136 TLV-223 (Multitopology IS Neighbor Attribute)[RFC5311]. 138 TLV-141 (inter-AS reachability information)[RFC5316]. 140 This sub-TLV SHOULD appear once at most in each TLV. Indicates that 141 a link MAY belong to multiple virtual networks. 143 Note that AII 0 does not require notification, and all links are 144 always in AII 0 at the same time. 146 4. Advertising prefix-SID per AII information 148 [I-D.ietf-isis-segment-routing-extensions] defines a new IS-IS sub- 149 TLV: the Prefix Segment Identifier sub-TLV (Prefix-SID sub-TLV). The 150 Prefix-SID sub-TLV carries the Segment Routing IGP-Prefix-SID as 151 defined in [RFC8402], and is associated to a prefix advertised by a 152 node. 154 To distinguish forwarding behavior of different virtual networks, 155 Prefix-SID need to be allocated per AII and advertised in the IGP 156 domain. This document defines a new extension of the existing 157 Prefix-SID sub-TLV. 159 The Prefix-SID for AII sub-TLV has the following format: 161 0 1 2 3 162 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 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | Type=TBD2 | Length | Flag | Algorithm | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 | AII | 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 168 | SID/Index/Label(Variable) | 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 Figure 2 173 where: 175 Type:33 (Suggested value to be assigned by IANA) 177 Length: Variable. Depending on the size of the SID. 179 The "Flags" and "SID/Index/Label" fields are the same as the Prefix- 180 SID sub-TLV [I-D.ietf-isis-segment-routing-extensions]. 182 AII: Identifies the AII information corresponding to the Prefix-SID. 184 This sub-TLV MAY be present in any of the following TLVs: 186 TLV-135 (Extended IPv4 reachability) defined in [RFC5305]. 188 TLV-235 (Multitopology IPv4 Reachability) defined in [RFC5120]. 190 TLV-236 (IPv6 IP Reachability) defined in [RFC5308]. 192 TLV-237 (Multitopology IPv6 IP Reachability) defined in [RFC5120]. 194 This sub-TLV MAY appear multiple times in each TLV. 196 5. Advertising Adjacency-SID per AII information 198 [I-D.ietf-isis-segment-routing-extensions]defines a new IS-IS sub- 199 TLV: the Adjacency Segment Identifier sub-TLV (Adj-SID sub-TLV).The 200 Adj-SID sub-TLV is an optional sub-TLV carrying the Segment Routing 201 IGP-Adjacency-SID as defined in [RFC8402]. 203 To distinguish forwarding behavior of different virtual networks, 204 Adjacency -SID need to be allocated per AII and advertised in the IGP 205 domain. This document defines a new extension of the existing 206 Adjacency-SID sub-TLV. 208 The Adjacency-SID for AII sub-TLV has the following format: 210 0 1 2 3 211 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 212 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 | Type=TBD3 | Length | Flag | Algorithm | 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | AII | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 217 | SID/Index/Label(Variable) | 218 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 Figure 3 222 where: 224 Type:44 (Suggested value to be assigned by IANA) 226 Length: Variable. Depending on the size of the SID. 228 The "Flags" and "SID/Index/Label" fields are the same as the 229 Adjacency-SID sub-TLV [I-D.ietf-isis-segment-routing-extensions]. 231 AII: Identifies the AII information corresponding to the Adjacency- 232 SID. 234 This sub-TLV MAY be present in any of the following TLVs: 236 TLV-22 (Extended IS reachability) [RFC5305]. 238 TLV-222 (Multitopology IS)[RFC5120]. 240 TLV-23 (IS Neighbor Attribute)[RFC5311]. 242 TLV-223 (Multitopology IS Neighbor Attribute)[RFC5311]. 244 TLV-141 (inter-AS reachability information)[RFC5316]. 246 Multiple Adj-SID sub-TLVs MAY be associated with a single IS- 247 neighbor. This sub-TLV MAY appear multiple times in each TLV. 249 6. IANA Considerations 251 This document requests allocation for the following Sub-TLVs. 253 6.1. AII list sub-TLV 255 This TLV shares sub-TLV space with existing "Sub-TLVs for TLVs 22, 256 222, 23,223 and 141 registry". 258 Type:43(suggested - to be assigned by IANA). 260 6.2. Prefix-SID for AII sub-TLV 262 This TLV shares sub-TLV space with existing "Sub-TLVs for TLVs 263 135,235,226 and 237 registry". 265 Type:33(suggested - to be assigned by IANA). 267 6.3. Adjacency -SID for AII sub-TLV 269 This TLV shares sub-TLV space with existing "Sub-TLVs for TLVs 22, 270 222, 23,223 and 141 registry". 272 Type:44(suggested - to be assigned by IANA). 274 7. Security Considerations 276 TBD. 278 8. Acknowledgements 280 TBD. 282 9. References 284 9.1. Normative references 286 [I-D.ietf-isis-segment-routing-extensions] 287 Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., 288 Gredler, H., and B. Decraene, "IS-IS Extensions for 289 Segment Routing", draft-ietf-isis-segment-routing- 290 extensions-25 (work in progress), May 2019. 292 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 293 Requirement Levels", BCP 14, RFC 2119, 294 DOI 10.17487/RFC2119, March 1997, 295 . 297 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 298 Topology (MT) Routing in Intermediate System to 299 Intermediate Systems (IS-ISs)", RFC 5120, 300 DOI 10.17487/RFC5120, February 2008, 301 . 303 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 304 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 305 2008, . 307 [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, 308 DOI 10.17487/RFC5308, October 2008, 309 . 311 [RFC5311] McPherson, D., Ed., Ginsberg, L., Previdi, S., and M. 312 Shand, "Simplified Extension of Link State PDU (LSP) Space 313 for IS-IS", RFC 5311, DOI 10.17487/RFC5311, February 2009, 314 . 316 [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in 317 Support of Inter-Autonomous System (AS) MPLS and GMPLS 318 Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, 319 December 2008, . 321 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 322 Decraene, B., Litkowski, S., and R. Shakir, "Segment 323 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 324 July 2018, . 326 9.2. Informative references 328 [I-D.peng-teas-network-slicing] 329 Peng, S., Chen, R., and G. Mirsky, "Packet Network Slicing 330 using Segment Routing", draft-peng-teas-network-slicing-00 331 (work in progress), August 2019. 333 Authors' Addresses 335 Yongqing Zhu 336 China Telecom 338 Email: zhuyq.gd@chinatelecom.cn 340 Ran Chen 341 ZTE Corporation 343 Email: chen.ran@zte.com.cn 345 Shaofu Peng 346 ZTE Corporation 348 Email: peng.shaofu@zte.com.cn 350 Fengwei Qin 351 China Mobile 353 Email: qinfengwei@chinamobile.com