idnits 2.17.1 draft-bashandy-isis-srv6-extensions-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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 19, 2018) is 2220 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 (-07) exists of draft-filsfils-spring-srv6-network-programming-04 == Outdated reference: A later version (-26) exists of draft-ietf-6man-segment-routing-header-10 -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO10589' Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Networking Working Group L. Ginsberg 3 Internet-Draft A. Bashandy 4 Intended status: Standards Track C. Filsfils 5 Expires: September 20, 2018 Cisco Systems 6 B. Decraene 7 Orange 8 Z. Hu 9 Huawei Technologies 10 March 19, 2018 12 IS-IS Extensions to Support Routing over IPv6 Dataplane 13 draft-bashandy-isis-srv6-extensions-02.txt 15 Abstract 17 Segment Routing (SR) allows for a flexible definition of end-to-end 18 paths by encoding paths as sequences of topological sub-paths, called 19 "segments". Segment routing architecture can be implemented over an 20 MPLS data plane as well as an IPv6 data plane. This draft describes 21 the IS-IS extensions required to support Segment Routing over an IPv6 22 data plane. 24 Requirements Language 26 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 27 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 28 "OPTIONAL" in this document are to be interpreted as described in BCP 29 14 [RFC2119] [RFC8174] when, and only when, they appear in all 30 capitals, as shown here. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at https://datatracker.ietf.org/drafts/current/. 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 This Internet-Draft will expire on September 20, 2018. 49 Copyright Notice 51 Copyright (c) 2018 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (https://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 67 2. SRv6-Capabilities sub-TLV . . . . . . . . . . . . . . . . . . 3 68 2.1. Maximum SL sub-sub-TLV . . . . . . . . . . . . . . . . . 4 69 2.2. Maximum End Pop SRH sub-sub-TLV . . . . . . . . . . . . . 5 70 2.3. Maximum T.Insert SRH sub-sub-TLV . . . . . . . . . . . . 5 71 2.4. Maximum T.Encap SRH sub-sub-TLV . . . . . . . . . . . . . 6 72 2.5. Maximum End D SRH sub-sub-TLV . . . . . . . . . . . . . . 6 73 3. SRv6 Endpoint function Descriptor . . . . . . . . . . . . . . 7 74 4. SRv6 Node SID TLV . . . . . . . . . . . . . . . . . . . . . . 7 75 5. Endpoint function Code Points . . . . . . . . . . . . . . . . 9 76 6. Advertising SRv6 SIDs associated with a Neighbor . . . . . . 9 77 6.1. SRv6 Adjacency-SID sub-TLV . . . . . . . . . . . . . . . 10 78 6.2. SRv6 LAN Adjacency-SID sub-TLV . . . . . . . . . . . . . 10 79 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 80 7.1. SRv6 Node SID TLV . . . . . . . . . . . . . . . . . . . . 12 81 7.2. SRv6 Capabilities sub-TLV . . . . . . . . . . . . . . . . 12 82 7.3. SRv6 Adjacency-SID and SRv6 LAN Adjacecncy-SID sub-TLVs . 13 83 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 84 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 85 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 86 10.1. Normative References . . . . . . . . . . . . . . . . . . 15 87 10.2. Informative References . . . . . . . . . . . . . . . . . 16 88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 90 1. Introduction 92 With Segment Routing (SR) [I-D.ietf-spring-segment-routing], a node 93 steers a packet through an ordered list of instructions, called 94 segments. 96 Segments are identified through Segment Identifiers (SIDs). 98 Segment Routing can be directly instantiated on the IPv6 data plane 99 through the use of the Segment Routing Header defined in 100 [I-D.ietf-6man-segment-routing-header]. SRv6 refers to this SR 101 instantiation on the IPv6 dataplane. 103 The network programming paradigm 104 [I-D.filsfils-spring-srv6-network-programming] is central to SRv6. 105 It describes how any function can be bound to a SID and how any 106 network program can be expressed as a combination of SID's. 108 This document specifies IS-IS extensions that allow IS-IS protocol to 109 encode some of these functions. 111 Familiarity with the network programming paradigm 112 [I-D.filsfils-spring-srv6-network-programming] is necessary to 113 understand the extensions specified in this document. 115 This document defines one new top level IS-IS TLV and several new IS- 116 IS sub-TLVs. 118 The SRv6 Capabilities sub-TLV announces the ability to support SRv6 119 and some Endpoint functions listed in Section 5 as well as 120 advertising limitations when applying such Endpoint functions. 122 The SRv6 Node SID top level TLV, the SRv6 Adjacency-SID sub-TLV, and 123 the SRv6 LAN Adjacency-SID sub-TLV are used to advertise which SIDs 124 are instantiated at a node and what Endpoint function is bound to 125 each instantiated SID. 127 2. SRv6-Capabilities sub-TLV 129 A node indicates that it has support for SRv6 by advertising a new 130 SRv6- capabilities sub-TLV of the router capabilities TLV [RFC7981]. 131 The SRv6- capabilities sub-TLV may contain optional sub-sub-TLVs. 133 The SRv6 Capabilities sub-TLV has the following format: 135 0 1 2 3 136 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 137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 | Type | Length | Flags | 139 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 140 | optional sub-sub-TLVs... 142 Type: Suggested value 25, to be assigned by IANA 144 Length: 2 + length of sub-sub-TLVs 146 Flags: 2 octets The following flags are defined: 148 0 1 149 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 |E|O| | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 where: 155 E-flag: If set, then router is able to apply "T.Encap" 156 operation. Further limitations as regards T.encap are 157 indicated by the advertisement of the Maximum T.Insert 158 sub-sub-TLV described below. 160 O-flag: If set, the router supports use of the O-bit 161 in the Segment Routing Header(SRH) as defined in 162 [draft-ietf-6man-segment-routing-header]. 164 The following sections define the supported sub-sub-TLVs. 166 2.1. Maximum SL sub-sub-TLV 168 The Maximum Segments Left sub-sub-TLV specifies the maximum value of 169 the "SL" field [I-D.ietf-6man-segment-routing-header] in the SRH of a 170 received packet before applying the Endpoint function associated with 171 a SID. 173 0 1 2 174 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 176 | Type | Length | Max SL | 177 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 Type: 1 180 Length: 1 181 SL Value: 1 octet 182 An 8 bit unsigned integer. 184 If the sub-sub-TLV is NOT advertised the value is assumed to be 0. 186 2.2. Maximum End Pop SRH sub-sub-TLV 188 The Maximum End Pop SRH sub-sub-TLV specifies the maximum number of 189 SIDs in the top SRH in an SRH stack to which the router can apply 190 "PSP" or USP" [I-D.filsfils-spring-srv6-network-programming] flavors. 192 0 1 2 193 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Type | Length |Max-End-Pop-SRH| 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 Type: 2 199 Length: 1 200 Max-End-Pop-SRH Value: 1 octet 201 An 8 bit unsigned integer. 203 If the value is zero or the sub-sub-TLV is NOT advertised, 204 then it is assumed that the router cannot apply PSP or USP flavors. 206 2.3. Maximum T.Insert SRH sub-sub-TLV 208 The Maximum T.Insert SRH sub-sub-TLV specifies the maximum number of 209 SIDs that can be inserted as part of the "T.insert" behavior 210 [I-D.filsfils-spring-srv6-network-programming]. 212 0 1 2 213 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 214 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 215 | Type | Length | Max-T.Insert | 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 Type: 3 219 Length: 1 220 Max-T.Insert Value: 1 octet 221 An 8 bit unsigned integer. 223 If the value is zero or the sub-sub-TLV is omitted, 224 then the router is assumed not to support any variation 225 of the "T.insert" behavior. 227 2.4. Maximum T.Encap SRH sub-sub-TLV 229 The Maximum T.Encap SRH sub-sub-TLV specifies the maximum number of 230 SIDs that can be included as part of the "T.Encap" behavior 231 [I-D.filsfils-spring-srv6-network-programming]. 233 0 1 2 234 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 236 | Type | Length | Max-T.Encap | 237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 Type: 4 240 Length: 1 241 Max-T.Encap Value: 1 octet 242 An 8 bit unsigned integer. 244 If this value is zero or the sub-sub-TLV is omitted and 245 the "E" flag is set in the associated SRv6 Capabilities 246 sub-TLV, then it is assumed that the router can apply T.Encap 247 by encapsulating the incoming packet in another IPv6 header 248 without SRH the same way IPinIP encapsulation is performed. 249 If the "E" flag is clear, then this sub-sub-TLV SHOULD NOT 250 be transmitted and MUST be ignored on receipt. 252 2.5. Maximum End D SRH sub-sub-TLV 254 The Maximum End D SRH sub-sub-TLV specifies the maximum number of 255 SIDs in an SRH when applying "End.DX6" and "End.DT6" Endpoint 256 functions. 258 0 1 2 259 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 260 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 261 | Type | Length | Max End D | 262 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 264 Type: 5 265 Length: 1 266 Max End D Value: 1 octet 267 An 8 bit unsigned integer. 269 If this value is zero or the sub-sub-TLV is omitted, 270 then it is assumed that the router cannot apply 271 "End.DX6" or "End.DT6" Endpoint functions if the extension 272 header right underneath the outer IPv6 header is an SRH. 274 3. SRv6 Endpoint function Descriptor 276 The SRv6 SID TLV defined in Section 4, P2P SRv6 X-SID sub-TLV 277 specified in Section 6.1, and LAN SRv6 X-SID sub-TLV specified in 278 section 6.2 MUST have one (and only one) SRv6 Endpoint function 279 Descriptor. 281 The SRv6 Endpoint function Descriptor has the following format: 283 0 1 284 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 285 +-+-+-+-+-+-+-+-+ 286 | Flags | 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 288 | Endpoint function (2 octets) | 289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 No flags are currently defined. 293 The second two octets encode the Endpoint function. 295 4. SRv6 Node SID TLV 297 The SRv6 Node SID TLV is introduced to advertise SRv6 Segment 298 Identifiers (SID) and their attributes. 300 The new TLV is used to advertise SRv6 SIDs with Endpoint functions 301 which do not require a particular neighbor in order to be correctly 302 applied [I-D.filsfils-spring-srv6-network-programming]. SRv6 SIDs 303 associated with a neighbor are advertised using the sub-TLVs defined 304 in Section 6. 306 This new TLV shares the sub-TLV space defined for TLVs 135, 235, 236 307 and 237. The SRv6 Node SID TLV has the following format: 309 0 1 2 3 310 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 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 | Type | Length | 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 | Flags | Func-flags | Endpoint function Value | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | SID size | SID (variable) . . . 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | Sub-tlv-len | Sub-TLVs (variable) . . . | 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 Type: 27 (Suggested value to be assigned by IANA) 323 Length: variable. 325 One or more SID entries, each of which has the following format: 327 Flags: 1 octet. The following flags are defined 329 0 330 0 1 2 3 4 5 6 7 331 +-+-+-+-+-+-+-+-+ 332 |D| Reserved | 333 +-+-+-+-+-+-+-+-+ 335 where: 336 D bit: When the SID is leaked from level-2 to level-1, the D 337 bit MUST be set. Otherwise, this bit MUST be clear. SIDs with 338 the D bit set MUST NOT be leaked from level-1 to level-2. This 339 is to prevent looping. 341 The remaining bits are reserved for future use. They SHOULD be 342 set to zero on transmission and MUST be ignored on receipt. 344 Func-flags: 1 octet. As defined in Section 3 346 Endpoint function Value: 2 octets. As defined in Section 3 348 SID-Size: 1 octet. Number of bits in the SID field. 350 SID: 1-16 octets. This field encodes the advertised SRv6 SID. The 351 "SID-size" field can have the values 1-128 and indicates the 352 number of bits in the SID. The SRv6 SID is encoded in the 353 minimal number of octets for the given number of bits. 355 Sub-TLV-length: 1 octet. Number of octets used by sub-TLVs 357 5. Endpoint function Code Points 359 Endpoint function code points are defined in 360 [I-D.filsfils-spring-srv6-network-programming]. The numerical values 361 are defined in the "Endpoint Types" registry defined in 362 [I-D.filsfils-spring-srv6-network-programming]. This section lists 363 the Endpoint function types which may be advertised by IS-IS. 365 o End (no PSP, no USP) 367 o End with PSP 369 o End with USP 371 o End with PSP&USP 373 o End.X (no PSP, no USP) 375 o End.X with PSP 377 o End.X with USP 379 o End.X with PSP&USP 381 o End.DX6 Function 383 o End.DT6 Function 385 o End.OTP 387 6. Advertising SRv6 SIDs associated with a Neighbor 389 Certain SRv6 Endpoint functions 390 [I-D.filsfils-spring-srv6-network-programming] must be associated 391 with a particular neighbor, and in case of multiple layer 3 links to 392 the same neighbor, with a particular link in order to be correctly 393 applied. 395 This document specifies how to advertise the End.X and End.DX6 396 variants as described in Section 5. 398 This document defines two new sub-TLVs of TLV 22, 23, 222, 223, and 399 141 - namely "SRv6 Adjacency-SID" and "SRv6 LAN Adjacency-SID". 401 6.1. SRv6 Adjacency-SID sub-TLV 403 This sub-TLV is used to advertise one or more SRv6 SIDs associated 404 with a point to point adjacency. 406 The SRv6 Adjacency-SID sub-TLV has the following format: 408 0 1 2 3 409 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 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 | Type | Length | 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | Flags | Func-flags | Endpoint function Value | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 | SID size | SID (variable) . . . 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 |Sub-sub-tlv-len| Sub-sub-TLVs (variable) . . . | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 420 Type: 40 (Suggested value to be assigned by IANA) 422 Length: variable. 424 One or more SIDs each of which has the following format: 426 Flags: 1 octet. No flags defined in this document 428 Func-flags: 1 octet. As defined in Section 3 430 Endpoint function Value: 2 octets. As defined in Section 3. 431 Legal values are the End.X and End.DX6 variants. 433 SID-Size: 1 octet. Number of bits in the SID field. 435 SID: 1-16 octets. This field encodes the advertised SRv6 SID. The 436 "SID-size" field can have the values 1-128 and indicates the 437 number of bits in the SID. The SRv6 SID is encoded in the 438 minimal number of octets for the given number of bits. 440 Sub-sub-TLV-length: 1 octet. Number of octets used by sub-sub- 441 TLVs 443 6.2. SRv6 LAN Adjacency-SID sub-TLV 445 This sub-TLV is used to advertise one or more SRv6 SIDs associated 446 with a LAN adjacency. 448 The SRv6 LAN Adjacency-SID sub-TLV has the following format: 450 0 1 2 3 451 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 452 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 453 | Type | Length | System ID (6 octets) | 454 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 455 | | 456 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 457 | Flags | Func-flags | Endpoint function Value | 458 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 459 | SID-size | SID (variable) . . . | 460 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 461 |Sub-sub-tlv-len| sub-sub-TLVs (variable) . . . | 462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 Type: 41 (Suggested value to be assigned by IANA) 465 Length: variable. 467 System-ID: 6 octets of IS-IS System-ID of length "ID Length" as 468 defined in [ISO10589]. 470 One or more SIDs each of which has the following format: 472 Flags 1 Octet. No flags are defined in this document 474 Func-flags: 1 octet. As defined in Section 3 476 Endpoint function Value: 2 octets. As defined in Section 3. 477 Legal values are the End.X and End.DX6 variants. 479 SID-Size: 1 octet. Number of bits in the SID field. 481 SID: 1-16 octets. This field encodes the advertised SRv6 SID. The 482 "SID-size" field can have the values 1-128 and indicates the 483 number of bits in the SID. The SRv6 SID is encoded in the 484 minimal number of octets for the given number of bits. 486 Sub-sub-TLV-length: 1 octet. Number of octets used by sub-sub- 487 TLVs. 489 7. IANA Considerations 491 This documents request allocation for the following TLVs, sub- TLVs, 492 and sub-sub-TLVs as well updating the ISIS TLV registry and defining 493 a new registry. 495 7.1. SRv6 Node SID TLV 497 This document adds the following new TLV to the IS-IS TLV Codepoints 498 registry. 500 Value: 27 (suggested - to be assigned by IANA) 502 Name: SRv6 Node SID 504 The name of the "Sub-TLVs for TLVs 135, 235, 236 and 237 registry" 505 needs to be changed to "Sub-TLVs for TLVs 27, 135, 235, 236 and 237 506 registry". 508 The revised table of sub-TLVs in the registry should be: 510 Type 27 135 235 236 237 512 1 n y y y y 513 2 n y y y y 514 3 y y y y y 515 4 y y y y y 516 11 y y y y y 517 12 y y y y y 519 7.2. SRv6 Capabilities sub-TLV 521 This document adds the definition of a new sub-TLV in the "Sub- TLVs 522 for TLV 242 registry". 524 Type: 25 (Suggested - to be assigned by IANA) 526 Description: SRv6 Capabilities 528 Thuis document requests the creation of a new IANA managed registry 529 for sub-sub-TLVs of the SRv6 Capability sub-TLV. The registration 530 procedure is "Expert Review" as defined in [RFC7370]. Suggested 531 registry name is "sub-sub-TLVs for SRv6 Capability sub-TLV". The 532 following sub-TLVs are defined by this document: 534 0: Reserved 536 1: Max-SL 538 2: Max-End-Pop-SRH 540 3: Max-T-Ins-SRH 541 4: Max-T-Encap-SRH 543 5: Max-End-D-SR 545 7.3. SRv6 Adjacency-SID and SRv6 LAN Adjacecncy-SID sub-TLVs 547 This document adds the definition of two new sub-TLVs in the "sub- 548 TLVs for TLV 22, 23, 141, 222 and 223 registry". 550 Type: 40 (suggested - to be assigned by IANA) 552 Description: SRv6 Adjacency-SID 554 Type: 41 (suggested - to be assigned by IANA) 556 Description: SRv6 LAN Adjacency-SID 558 Type 22 23 141 222 223 560 40 y y y y y 561 41 y y y y y 563 8. Security Considerations 565 Security concerns for IS-IS are addressed in [ISO10589], [RFC5304], 566 and [RFC5310]. 568 9. Contributors 570 The following people gave a substantial contribution to the content 571 of this document and should be considered as co-authors: 573 Stefano Previdi 574 Email: stefano@previdi.net 576 Peter Psenak 577 Cisco Systems 578 Apollo Business Center Mlynske nivy 43 579 Bratislava 821 09 580 Slovakia 581 Email: ppsenak@cisco.com 583 Paul Wells 584 Cisco Systems 585 Saint Paul, 586 Minnesota 587 United States 588 Email: pauwells@cisco.com 590 Daniel Voyer 591 Email: daniel.voyer@bell.ca 593 Satoru Matsushima 594 Email: satoru.matsushima@g.softbank.co.jp 596 Bart Peirens 597 Email: bart.peirens@proximus.com 599 Hani Elmalky 600 Email: hani.elmalky@ericsson.com 602 Prem Jonnalagadda 603 Email: prem@barefootnetworks.com 605 Milad Sharif 606 Email: msharif@barefootnetworks.com> 608 Robert Hanzl 609 Cisco Systems 610 Millenium Plaza Building, V Celnici 10, Prague 1, 611 Prague, Czech Republic 612 Email rhanzl@cisco.com 614 10. References 615 10.1. Normative References 617 [I-D.filsfils-spring-srv6-network-programming] 618 Filsfils, C., Li, Z., Leddy, J., daniel.voyer@bell.ca, d., 619 daniel.bernier@bell.ca, d., Steinberg, D., Raszuk, R., 620 Matsushima, S., Lebrun, D., Decraene, B., Peirens, B., 621 Salsano, S., Naik, G., Elmalky, H., Jonnalagadda, P., and 622 M. Sharif, "SRv6 Network Programming", draft-filsfils- 623 spring-srv6-network-programming-04 (work in progress), 624 March 2018. 626 [I-D.ietf-6man-segment-routing-header] 627 Previdi, S., Filsfils, C., Leddy, J., Matsushima, S., and 628 d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header 629 (SRH)", draft-ietf-6man-segment-routing-header-10 (work in 630 progress), March 2018. 632 [ISO10589] 633 "Intermediate system to Intermediate system intra-domain 634 routeing information exchange protocol for use in 635 conjunction with the protocol for providing the 636 connectionless-mode Network Service (ISO 8473), ISO/IEC 637 10589:2002, Second Edition.", Nov 2002. 639 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 640 Requirement Levels", BCP 14, RFC 2119, 641 DOI 10.17487/RFC2119, March 1997, 642 . 644 [RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic 645 Authentication", RFC 5304, DOI 10.17487/RFC5304, October 646 2008, . 648 [RFC5310] Bhatia, M., Manral, V., Li, T., Atkinson, R., White, R., 649 and M. Fanto, "IS-IS Generic Cryptographic 650 Authentication", RFC 5310, DOI 10.17487/RFC5310, February 651 2009, . 653 [RFC7370] Ginsberg, L., "Updates to the IS-IS TLV Codepoints 654 Registry", RFC 7370, DOI 10.17487/RFC7370, September 2014, 655 . 657 [RFC7981] Ginsberg, L., Previdi, S., and M. Chen, "IS-IS Extensions 658 for Advertising Router Information", RFC 7981, 659 DOI 10.17487/RFC7981, October 2016, 660 . 662 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 663 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 664 May 2017, . 666 10.2. Informative References 668 [I-D.ietf-spring-segment-routing] 669 Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., 670 Litkowski, S., and R. Shakir, "Segment Routing 671 Architecture", draft-ietf-spring-segment-routing-15 (work 672 in progress), January 2018. 674 Authors' Addresses 676 Les Ginsberg 677 Cisco Systems 678 821 Alder Drive 679 Milpitas, CA 95035 680 USA 682 Email: ginsberg@cisco.com 684 Ahmed Bashandy 685 Cisco Systems 686 170 West Tasman Dr 687 San Jose, CA 95134 688 USA 690 Email: bashandy@cisco.com 692 Clarence Filsfils 693 Cisco Systems 694 Brussels 695 Belgium 697 Email: cfilsfil@cisco.com 699 Bruno Decraene 700 Orange 701 Issy-les-Moulineaux 702 France 704 Email: bruno.decraene@orange.com 705 Zhibo Hu 706 Huawei Technologies 708 Email: huzhibo@huawei.com