idnits 2.17.1 draft-li-lsr-isis-te-metric-lan-extensions-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 document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? RFC 2119 keyword, line 381: '... Implementations MUST make it possible...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (5 March 2022) is 782 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC2119' is mentioned on line 27, but not defined == Missing Reference: 'RFC8174' is mentioned on line 27, but not defined == Missing Reference: 'ISO10589' is mentioned on line 357, but not defined == Unused Reference: 'RFC5305' is defined on line 419, but no explicit reference was found in the text Summary: 2 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group C. Li 3 Internet-Draft G. Xu 4 Intended status: Informational Z. Hu 5 Expires: 6 September 2022 Huawei 6 5 March 2022 8 IS-IS Traffic Engineering (TE) Metric LAN Extensions 9 draft-li-lsr-isis-te-metric-lan-extensions-00 11 Abstract 13 In certain networks, network-performance criteria (e.g., latency) are 14 becoming as critical to data-path selection as other metrics. This 15 document describes extensions to IS-IS Traffic Engineering (TE) 16 Metric Extensions (RFC 8570) for LAN subnetworks. These extensions 17 provide a way to distribute and collect network-performance 18 information in LAN subnetworks. 20 Requirements Language 22 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 23 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 24 document are to be interpreted as described in BCP 14 [RFC2119] 25 [RFC8174] when, and only when, they appear in all capitals, as shown 26 here. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at https://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on 6 September 2022. 45 Copyright Notice 47 Copyright (c) 2022 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 52 license-info) in effect on the date of publication of this document. 53 Please review these documents carefully, as they describe your rights 54 and restrictions with respect to this document. Code Components 55 extracted from this document must include Revised BSD License text as 56 described in Section 4.e of the Trust Legal Provisions and are 57 provided without warranty as described in the Revised BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 62 2. Sub-TLV Details . . . . . . . . . . . . . . . . . . . . . . . 3 63 2.1. Unidirectional Link Delay LAN Sub-TLV . . . . . . . . . . 3 64 2.2. Min/Max Unidirectional Link Delay LAN Sub-TLV . . . . . . 4 65 2.3. Unidirectional Delay Variation LAN Sub-TLV . . . . . . . 5 66 2.4. Unidirectional Link Loss LAN Sub-TLV . . . . . . . . . . 5 67 2.5. Unidirectional Residual Bandwidth LAN Sub-TLV . . . . . . 6 68 2.6. Unidirectional Available Bandwidth LAN Sub-TLV . . . . . 7 69 2.7. Unidirectional Utilized Bandwidth LAN Sub-TLV . . . . . . 8 70 3. Announcement Thresholds and Filters . . . . . . . . . . . . . 8 71 4. Announcement Suppression . . . . . . . . . . . . . . . . . . 8 72 5. Network Stability and Announcement Periodicity . . . . . . . 9 73 6. Enabling and Disabling Sub-TLVs . . . . . . . . . . . . . . . 9 74 7. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 9 75 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 76 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 77 10. Security Considerations . . . . . . . . . . . . . . . . . . . 9 78 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 81 1. Introduction 83 In certain networks, network-performance criteria (e.g., latency) are 84 becoming as critical to data-path selection as other metrics. This 85 document describes extensions to IS-IS Traffic Engineering (TE) 86 Metric Extensions (RFC 8570) for LAN subnetworks. These extensions 87 provide a way to distribute and collect network-performance 88 information in LAN subnetworks. 90 In LAN subnetworks, the Designated Intermediate System (DIS) is 91 elected and originates the Pseudonode LSP (PN LSP) including all 92 neighbors of the DIS. Since, on LANs, each router only advertises 93 one adjacency to the DIS (and doesn't advertise any other adjacency), 94 each router should advertise the TE metric for each of its neighbors. 96 2. Sub-TLV Details 98 This document registers new IS-IS TE sub-TLVs in the "Sub-TLVs for 99 TLVs 22, 23, 141, 222, and 223" registry. These new sub-TLVs 100 provides ways to distribute network-performance information in LAN 101 subnetworks. 103 This document registers new sub-TLVs: 105 Type Description 106 ---------------------------------------------------- 107 TBD Unidirectional Link Delay LAN Sub-TLV 108 TBD Min/Max Unidirectional Link Delay LAN Sub-TLV 109 TBD Unidirectional Delay Variation LAN Sub-TLV 110 TBD Unidirectional Link Loss LAN Sub-TLV 111 TBD Unidirectional Residual Bandwidth LAN Sub-TLV 112 TBD Unidirectional Available Bandwidth LAN Sub-TLV 113 TBD Unidirectional Utilized Bandwidth LAN Sub-TLV 115 Figure 1: Figure 1 117 2.1. Unidirectional Link Delay LAN Sub-TLV 119 This sub-TLV advertises the average link delay between two real 120 connected IS-IS neighbors in LAN. Each router advertises the average 121 link delay for each of its neighbors inside a newly defined sub-TLV 122 that is a part of the TLV advertising the adjacency to the DIS (e.g., 123 TLV-22). The format of this sub-TLV is shown in the following 124 diagram: 126 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 127 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 | Type | Length | 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 130 | Neighbor System-ID (ID length octets) | 131 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 132 | | 133 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 135 |A| RESERVED | Delay | 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 138 Figure 2: Figure 2: Unidirectional Link Delay LAN Sub-TLV 140 Type: TBD (suggested value 41) is to be assigned by IANA. 142 Length: 4 + System-ID length. 144 Neighbor System-ID: IS-IS System-ID of length "ID Length" as defined 145 in [ISO10589]. 147 The other fields are the same as defined in [RFC8570] for 148 Unidirectional Link Delay Sub-TLV. 150 This sub-TLV is optional. 152 2.2. Min/Max Unidirectional Link Delay LAN Sub-TLV 154 This sub-TLV advertises the minimum and maximum delay values between 155 two real connected IS-IS neighbors in LAN. Each router advertises 156 the minimum and maximum delay for each of its neighbors inside a 157 newly defined sub-TLV that is a part of the TLV advertising the 158 adjacency to the DIS (e.g., TLV-22). The format of this sub-TLV is 159 shown in the following diagram: 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 | Length | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | Neighbor System-ID (ID length octets) | 166 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 170 |A| RESERVED | Min Delay | 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 172 | RESERVED | Max Delay | 173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 175 Figure 3: Figure 3: Min/Max Unidirectional Link Delay LAN Sub-TLV 177 Type: TBD (suggested value 42) is to be assigned by IANA. 179 Length: 8 + System-ID length. 181 Neighbor System-ID: IS-IS System-ID of length "ID Length" as defined 182 in [ISO10589]. 184 The other fields are the same as defined in [RFC8570] for Min/Max 185 Unidirectional Link Delay Sub-TLV. 187 This sub-TLV is optional. 189 2.3. Unidirectional Delay Variation LAN Sub-TLV 191 This sub-TLV advertises the average link delay variation between two 192 real connected IS-IS neighbors in LAN. Each router advertises 193 average link delay variation for each of its neighbors inside a newly 194 defined sub-TLV that is a part of the TLV advertising the adjacency 195 to the DIS (e.g., TLV-22). The format of this sub-TLV is shown in 196 the following diagram: 198 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 199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 | Type | Length | 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 | Neighbor System-ID (ID length octets) | 203 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | | 205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 207 |A| RESERVED | Delay Variation | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 210 Figure 4: Figure 4: Unidirectional Delay Variation LAN Sub-TLV 212 Type: TBD (suggested value 43) is to be assigned by IANA. 214 Length: 4 + System-ID length. 216 Neighbor System-ID: IS-IS System-ID of length "ID Length" as defined 217 in [ISO10589]. 219 The other fields are the same as defined in [RFC8570] for 220 Unidirectional Delay Variation Sub-TLV. 222 This sub-TLV is optional. 224 2.4. Unidirectional Link Loss LAN Sub-TLV 226 This sub-TLV advertises the loss (as a packet percentage) between two 227 real connected IS-IS neighbors in LAN. Each router advertises the 228 link loss for each of its neighbors inside a newly defined sub-TLV 229 that is a part of the TLV advertising the adjacency to the DIS (e.g., 230 TLV-22). The format of this sub-TLV is shown in the following 231 diagram: 233 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 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 | Type | Length | 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | Neighbor System-ID (ID length octets) | 238 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 | | 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 242 |A| RESERVED | Link Loss | 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 245 Figure 5: Figure 5: Unidirectional Link Loss LAN Sub-TLV 247 Type: TBD (suggested value 44) is to be assigned by IANA. 249 Length: 4 + System-ID length. 251 Neighbor System-ID: IS-IS System-ID of length "ID Length" as defined 252 in [ISO10589]. 254 The other fields are the same as defined in [RFC8570] for 255 Unidirectional Link Loss Sub-TLV. 257 This sub-TLV is optional. 259 2.5. Unidirectional Residual Bandwidth LAN Sub-TLV 261 This sub-TLV advertises the residual bandwidth between two real 262 connected IS-IS neighbors in LAN. Each router advertises the 263 residual bandwidth for each of its neighbors inside a newly defined 264 sub-TLV that is a part of the TLV advertising the adjacency to the 265 DIS (e.g., TLV-22). The format of this sub-TLV is shown in the 266 following diagram: 268 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 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 | Type | Length | 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 272 | Neighbor System-ID (ID length octets) | 273 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 | | 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 277 | Residual Bandwidth | 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 280 Figure 6: Figure 6: Unidirectional Residual Bandwidth LAN Sub-TLV 282 Type: TBD (suggested value 45) is to be assigned by IANA. 284 Length: 4 + System-ID length. 286 Neighbor System-ID: IS-IS System-ID of length "ID Length" as defined 287 in [ISO10589]. 289 The other fields are the same as defined in [RFC8570] for 290 Unidirectional Residual Bandwidth Sub-TLV. 292 This sub-TLV is optional. 294 2.6. Unidirectional Available Bandwidth LAN Sub-TLV 296 This sub-TLV advertises the available bandwidth between two real 297 connected IS-IS neighbors in LAN. Each router advertises the 298 available bandwidth for each of its neighbors inside a newly defined 299 sub-TLV that is a part of the TLV advertising the adjacency to the 300 DIS (e.g., TLV-22). The format of this sub-TLV is shown in the 301 following diagram: 303 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 304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 305 | Type | Length | 306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 307 | Neighbor System-ID (ID length octets) | 308 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 309 | | 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 312 | Available Bandwidth | 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 315 Figure 7: Figure 7: Unidirectional Available Bandwidth LAN Sub-TLV 317 Type: TBD (suggested value 46) is to be assigned by IANA. 319 Length: 4 + System-ID length. 321 Neighbor System-ID: IS-IS System-ID of length "ID Length" as defined 322 in [ISO10589]. 324 The other fields are the same as defined in [RFC8570] for 325 Unidirectional Available Bandwidth Sub-TLV. 327 This sub-TLV is optional. 329 2.7. Unidirectional Utilized Bandwidth LAN Sub-TLV 331 This sub-TLV advertises the bandwidth utilization between two real 332 connected IS-IS neighbors in LAN. Each router advertises the 333 bandwidth utilization (for each of its neighbors) inside a newly 334 defined sub-TLV that is a part of the TLV advertising the adjacency 335 to the DIS (e.g., TLV-22). The format of this sub-TLV is shown in 336 the following diagram: 338 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 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 | Type | Length | 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 | Neighbor System-ID (ID length octets) | 343 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 | | 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 347 | Utilized Bandwidth | 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+--+-+-+-+-+-+-+--+ 350 Figure 8: Figure 8: Unidirectional Utilized Bandwidth LAN Sub-TLV 352 Type: TBD (suggested value 47) is to be assigned by IANA. 354 Length: 4 + System-ID length. 356 Neighbor System-ID: IS-IS System-ID of length "ID Length" as defined 357 in [ISO10589]. 359 The other fields are the same as defined in [RFC8570] for 360 Unidirectional Utilized Bandwidth Sub-TLV. 362 This sub-TLV is optional. 364 3. Announcement Thresholds and Filters 366 This document uses the same principle for announcement thresholds and 367 filters as described in RFC 8570. 369 4. Announcement Suppression 371 This document uses the same principle for announcement suppression as 372 described in RFC 8570. 374 5. Network Stability and Announcement Periodicity 376 This document uses the same principle for network stability and 377 announcement periodicity as described in RFC 8570. 379 6. Enabling and Disabling Sub-TLVs 381 Implementations MUST make it possible to enable or disable each sub- 382 TLV based on configuration. 384 7. Compatibility 386 Unrecognized sub-TLVs should be silently ignored. 388 8. Acknowledgements 390 TBD. 392 9. IANA Considerations 394 This document requests that IANA allocates new sub-TLV types from the 395 "Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223 (Extended IS 396 reachability, IS Neighbor Attribute, L2 Bundle Member Attributes, 397 inter-AS reachability information, MT-ISN, and MT IS Neighbor 398 Attribute TLVs)" registry as specified. 400 Value Description 401 --------------------------------------------------------------- 402 TBD Unidirectional Link Delay LAN Sub-TLV 403 TBD Min/Max Unidirectional Link Delay LAN Sub-TLV 404 TBD Unidirectional Delay Variation LAN Sub-TLV 405 TBD Unidirectional Link Loss LAN Sub-TLV 406 TBD Unidirectional Residual Bandwidth LAN Sub-TLV 407 TBD Unidirectional Available Bandwidth LAN Sub-TLV 408 TBD Unidirectional Utilized Bandwidth LAN Sub-TLV 410 Figure 9: Figure 9 412 10. Security Considerations 414 These extensions to IS-IS do not add any new security issues to the 415 existing IGP. 417 11. References 419 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 420 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 421 2008, . 423 [RFC8570] Ginsberg, L., Ed., Previdi, S., Ed., Giacalone, S., Ward, 424 D., Drake, J., and Q. Wu, "IS-IS Traffic Engineering (TE) 425 Metric Extensions", RFC 8570, DOI 10.17487/RFC8570, March 426 2019, . 428 Authors' Addresses 430 Chenxi Li 431 Huawei 432 Huawei Bld., No.156 Beiqing Rd. 433 Beijing 434 100095 435 China 436 Email: lichenxi1@huawei.com 438 Guoqi Xu 439 Huawei 440 Huawei Bld., No. 156 Beiqing Rd. 441 Beijing 442 100095 443 China 444 Email: xuguoqi@huawei.com 446 Zhibo Hu 447 Huawei 448 Huawei Bld., No.156 Beiqing Rd. 449 Beijing 450 100095 451 China 452 Email: huzhibo@huawei.com