idnits 2.17.1 draft-ietf-ospf-te-link-attr-reuse-05.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 seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 17, 2018) is 2011 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: 'I-D.ietf-idr-ls-distribution' is defined on line 761, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ospf-segment-routing-extensions' is defined on line 777, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 5714 == Outdated reference: A later version (-19) exists of draft-ietf-isis-te-app-05 == Outdated reference: A later version (-26) exists of draft-ietf-lsr-flex-algo-00 == Outdated reference: A later version (-27) exists of draft-ietf-ospf-segment-routing-extensions-25 Summary: 1 error (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 LSR Working Group P. Psenak, Ed. 3 Internet-Draft Cisco Systems, Inc. 4 Intended status: Standards Track A. Lindem 5 Expires: April 20, 2019 L. Ginsberg 6 Cisco Systems 7 W. Henderickx 8 Nokia 9 J. Tantsura 10 Nuage Networks 11 H. Gredler 12 RtBrick Inc. 13 J. Drake 14 Juniper Networks 15 October 17, 2018 17 OSPF Link Traffic Engineering (TE) Attribute Reuse 18 draft-ietf-ospf-te-link-attr-reuse-05.txt 20 Abstract 22 Various link attributes have been defined in OSPF in the context of 23 the MPLS Traffic Engineering (TE) and GMPLS. Many of these link 24 attributes can be used for applications other than MPLS Traffic 25 Engineering or GMPLS. This document defines how to distribute such 26 attributes in OSPFv2 and OSPFv3 for applications other than MPLS 27 Traffic Engineering or GMPLS. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at https://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on April 20, 2019. 46 Copyright Notice 48 Copyright (c) 2018 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (https://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 This document may contain material from IETF Documents or IETF 62 Contributions published or made publicly available before November 63 10, 2008. The person(s) controlling the copyright in some of this 64 material may not have granted the IETF Trust the right to allow 65 modifications of such material outside the IETF Standards Process. 66 Without obtaining an adequate license from the person(s) controlling 67 the copyright in such materials, this document may not be modified 68 outside the IETF Standards Process, and derivative works of it may 69 not be created outside the IETF Standards Process, except to format 70 it for publication as an RFC or to translate it into languages other 71 than English. 73 Table of Contents 75 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 76 1.1. Requirements notation . . . . . . . . . . . . . . . . . . 4 77 2. Link attributes examples . . . . . . . . . . . . . . . . . . 4 78 3. Advertising Link Attributes . . . . . . . . . . . . . . . . . 4 79 3.1. OSPFv2 TE Opaque LSA and OSPFv3 Intra-Area-TE-LSA . . . . 4 80 3.2. OSPFv2 Extended Link Opaque LSA and OSPFv3 E-Router-LSA . 5 81 3.3. Selected Approach . . . . . . . . . . . . . . . . . . . . 6 82 4. Reused TE link attributes . . . . . . . . . . . . . . . . . . 6 83 4.1. Shared Risk Link Group (SRLG) . . . . . . . . . . . . . . 6 84 4.2. Extended Metrics . . . . . . . . . . . . . . . . . . . . 7 85 4.3. Traffic Engineering Metric . . . . . . . . . . . . . . . 8 86 4.4. Administrative Group . . . . . . . . . . . . . . . . . . 8 87 5. Advertisement of Application Specific Values . . . . . . . . 8 88 6. Maximum Link Bandwidth . . . . . . . . . . . . . . . . . . . 11 89 7. Local Interface IPv6 Address Sub-TLV . . . . . . . . . . . . 12 90 8. Remote Interface IPv6 Address Sub-TLV . . . . . . . . . . . . 12 91 9. Deployment Considerations . . . . . . . . . . . . . . . . . . 12 92 10. Attribute Advertisements and Enablement . . . . . . . . . . . 12 93 11. Backward Compatibility . . . . . . . . . . . . . . . . . . . 13 94 12. Security Considerations . . . . . . . . . . . . . . . . . . . 14 95 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 96 13.1. OSPFv2 . . . . . . . . . . . . . . . . . . . . . . . . . 14 97 13.2. OSPFv3 . . . . . . . . . . . . . . . . . . . . . . . . . 15 98 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 99 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 100 15.1. Normative References . . . . . . . . . . . . . . . . . . 16 101 15.2. Informative References . . . . . . . . . . . . . . . . . 17 102 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 104 1. Introduction 106 Various link attributes have been defined in OSPFv2 [RFC2328] and 107 OSPFv3 [RFC5340] in the context of the MPLS traffic engineering and 108 GMPLS. All these attributes are distributed by OSPFv2 as sub-TLVs of 109 the Link-TLV advertised in the OSPFv2 TE Opaque LSA [RFC3630]. In 110 OSPFv3, they are distributed as sub-TLVs of the Link-TLV advertised 111 in the OSPFv3 Intra-Area-TE-LSA as defined in [RFC5329]. 113 Many of these link attributes are useful outside of traditional MPLS 114 Traffic Engineering or GMPLS. This brings its own set of problems, 115 in particular how to distribute these link attributes in OSPFv2 and 116 OSPFv3 when MPLS TE and GMPLS are not deployed or are deployed in 117 parallel with other applications that use these link attributes. 119 [RFC7855] discusses use cases/requirements for SR. Included among 120 these use cases is SRTE. If both RSVP-TE and SRTE are deployed in a 121 network, link attribute advertisements can be used by one or both of 122 these applications. As there is no requirement for the link 123 attributes advertised on a given link used by SRTE to be identical to 124 the link attributes advertised on that same link used by RSVP-TE, 125 there is a clear requirement to indicate independently which link 126 attribute advertisements are to be used by each application. 128 As the number of applications which may wish to utilize link 129 attributes may grow in the future, an additional requirement is that 130 the extensions defined allow the association of additional 131 applications to link attributes without altering the format of the 132 advertisements or introducing new backwards compatibility issues. 134 Finally, there may still be many cases where a single attribute value 135 can be shared among multiple applications, so the solution should 136 minimize advertising duplicate link/attribute when possible. 138 1.1. Requirements notation 140 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 141 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 142 document are to be interpreted as described in [RFC2119]. 144 2. Link attributes examples 146 This section lists some of the link attributes originally defined for 147 MPLS Traffic Engineering that can be used for other applications in 148 OSPFv2 and OSPFv3. The list doesn't necessarily contain all the 149 required attributes. 151 1. Remote Interface IP address [RFC3630] - OSPFv2 currently cannot 152 distinguish between parallel links between two OSPFv2 routers. 153 As a result, the two-way connectivity check performed during SPF 154 may succeed when the two routers disagree on which of the links 155 to use for data traffic. 157 2. Link Local/Remote Identifiers - [RFC4203] - Used for the two-way 158 connectivity check for parallel unnumbered links. Also used for 159 identifying adjacencies for unnumbered links in Segment Routing 160 traffic engineering. 162 3. Shared Risk Link Group (SRLG) [RFC4203] - In IPFRR, the SRLG is 163 used to compute diverse backup paths [RFC5714]. 165 4. Unidirectional Link Delay/Loss Metrics [RFC7471] - Could be used 166 for the shortest path first (SPF) computation using alternate 167 metrics within an OSPF area. 169 3. Advertising Link Attributes 171 This section outlines possible approaches for advertising link 172 attributes originally defined for MPLS Traffic Engineering or GMPLS 173 when they are used for other applications. 175 3.1. OSPFv2 TE Opaque LSA and OSPFv3 Intra-Area-TE-LSA 177 One approach for advertising link attributes is to continue to use 178 the OSPFv2 TE Opaque LSA [RFC3630] or the OSPFv3 Intra-Area-TE-LSA 179 [RFC5329]. There are several problems with this approach: 181 1. Whenever the link is advertised in an OSPFv2 TE Opaque LSA or in 182 an OSPFv3 Intra-Area-TE-LSA, the link becomes a part of the TE 183 topology, which may not match IP routed topology. By making the 184 link part of the TE topology, remote nodes may mistakenly believe 185 that the link is available for MPLS TE or GMPLS, when, in fact, 186 MPLS is not enabled on the link. 188 2. The OSPFv2 TE Opaque LSA and OSPFv3 Intra-Area-TE-LSA advertise 189 link attributes that are not used or required by MPLS TE or 190 GMPLS. There is no mechanism in these TE LSAs to indicate which 191 of the link attributes are passed to the MPLS TE application and 192 which are used by other applications including OSPF itself. 194 3. Link attributes used for non-TE applications are partitioned 195 across multiple LSAs - the TE Opaque LSA and the Extended Link 196 Opaque LSA in OSPFv2 and the OSPFv3 Intra-Area-TE-LSA and OSPFv3 197 Extended LSA Router-Link TLV [RFC8362] in OSPFv3. This 198 partitioning will require implementations to lookup multiple LSAs 199 to extract link attributes for a single link, bringing needless 200 complexity to OSPF implementations. 202 The advantage of this approach is that there is no additional 203 standardization requirement to advertise the TE/GMPL attributes for 204 other applications. Additionally, link attributes are only 205 advertised once when both OSPF TE and other applications are deployed 206 on the same link. This is not expected to be a common deployment 207 scenario. 209 3.2. OSPFv2 Extended Link Opaque LSA and OSPFv3 E-Router-LSA 211 An alternative approach for advertising link attributes is to use 212 Extended Link Opaque LSAs as defined in [RFC7684] for OSPFv2 and 213 Extended Router-LSAs [RFC8362] for OSPFv3. These LSAs were defined 214 as a generic containers for distribution of the extended link 215 attributes. There are several advantages in using them: 217 1. Advertisement of the link attributes does not make the link part 218 of the TE topology. It avoids any conflicts and is fully 219 compatible with the [RFC3630] and [RFC5329]. 221 2. The OSPFv2 TE Opaque LSA and OSPFv3 Intra-Area-TE-LSA remains 222 truly opaque to OSPFv2 and OSPFv3 as originally defined in 223 [RFC3630] and [RFC5329] respectively. Their contents are not 224 inspected by OSPF, that act as a pure transport. 226 3. There is clear distinction between link attributes used by TE and 227 link attributes used by other OSPFv2 or OSPFv3 applications. 229 4. All link attributes that are used by other applications are 230 advertised in a single LSA, the Extended Link Opaque LSA in 231 OSPFv2 or the OSPFv3 E-Router-LSA [RFC8362] in OSPFv3. 233 The disadvantage of this approach is that in rare cases, the same 234 link attribute is advertised in both the TE Opaque and Extended Link 235 Attribute LSAs in OSPFv2 or the Intra-Area-TE-LSA and E-Router-LSA in 236 OSPFv3. Additionally, there will be additional standardization 237 effort. However, this could also be viewed as an advantage as the 238 non-TE use cases for the TE link attributes are documented and 239 validated by the LSR working group. 241 3.3. Selected Approach 243 It is RECOMMENDED to use the Extended Link Opaque LSA [RFC7684] and 244 E-Router-LSA [RFC8362] to advertise any link attributes used for non- 245 TE applications in OSPFv2 or OSPFv3 respectively, including those 246 that have been originally defined for TE applications. 248 It is also RECOMMENDED that TE link attributes used for RSVP-TE/GMPLS 249 continue to use OSPFv2 TE Opaque LSA [RFC3630] and OSPFv3 Intra-Area- 250 TE-LSA [RFC5329]. 252 It is also RECOMMENDED to keep the format of the link attribute TLVs 253 that have been defined for TE applications unchanged even when they 254 are used for non-TE applications. 256 Finally, it is RECOMMENDED to allocate unique code points for these 257 TE link attribute TLVs in the OSPFv2 Extended Link TLV Sub-TLV 258 Registry [RFC7684] and in the OSPFv3 Extended LSA Sub-TLV Registry 259 [RFC8362]. For each reused TLV, the code point will be defined in an 260 IETF document along with the expected use-case(s). 262 4. Reused TE link attributes 264 This section defines the use case and code points for the OSPFv2 265 Extended Link TLV Sub-TLV Registry and OSPFv3 Extended LSA Sub-TLV 266 Registry for some of the link attributes that have been originally 267 defined for TE or GMPLS. 269 Remote interface IP address and Link Local/Remote Identifiers have 270 been added as sub-TLVs of OSPFv2 Extended Link TLV by [RFC8379]. 271 Link Local/Remote Identifiers are already included in the OSPFv3 272 Router-Link TLV [RFC8362]. 274 4.1. Shared Risk Link Group (SRLG) 276 The SRLG of a link can be used in IPFRR to compute a backup path that 277 does not share any SRLG group with the protected link. 279 To advertise the SRLG of the link in the OSPFv2 Extended Link TLV, 280 the same format for the sub-TLV defined in section 1.3 of [RFC4203] 281 is used and TLV type TBD1 is used. Similarly, for OSPFv3 to 282 advertise the SRLG in the OSPFv3 Router-Link TLV, TLV type TBD2 is 283 used. 285 4.2. Extended Metrics 287 [RFC3630] defines several link bandwidth types. [RFC7471] defines 288 extended link metrics that are based on link bandwidth, delay and 289 loss characteristics. All these can be used to compute best paths 290 within an OSPF area to satisfy requirements for bandwidth, delay 291 (nominal or worst case) or loss. 293 To advertise extended link metrics in the OSPFv2 Extended Link TLV, 294 the same format for the sub-TLVs defined in [RFC7471] is used with 295 the following TLV types: 297 TBD3 - Unidirectional Link Delay 299 TBD4 - Min/Max Unidirectional Link Delay 301 TBD5 - Unidirectional Delay Variation 303 TBD6 - Unidirectional Link Loss 305 TBD7 - Unidirectional Residual Bandwidth 307 TBD8 - Unidirectional Available Bandwidth 309 TBD9 - Unidirectional Utilized Bandwidth 311 To advertise extended link metrics in the OSPFv3 Extended LSA Router- 312 Link TLV, the same format for the sub-TLVs defined in [RFC7471] is 313 used with the following TLV types: 315 TBD10 - Unidirectional Link Delay 317 TBD11 - Min/Max Unidirectional Link Delay 319 TBD12 - Unidirectional Delay Variation 321 TBD13 - Unidirectional Link Loss 323 TBD14 - Unidirectional Residual Bandwidth 325 TBD15 - Unidirectional Available Bandwidth 327 TBD16 - Unidirectional Utilized Bandwidth 329 4.3. Traffic Engineering Metric 331 [RFC3630] defines Traffic Engineering Metric. 333 To advertise the Traffic Engineering Metric in the OSPFv2 Extended 334 Link TLV, the same format for the sub-TLV defined in section 2.5.5 of 335 [RFC3630] is used and TLV type TBD27 is used. Similarly, for OSPFv3 336 to advertise the Traffic Engineering Metric in the OSPFv3 Router-Link 337 TLV, TLV type TBD28 is used. 339 4.4. Administrative Group 341 [RFC3630] and [RFC7308] define the Administrative Group and Extended 342 Administrative Group sub-TLVs respectively. 344 One use case where advertisement of the Extended Administrative 345 Group(s) for a link is required is described in 346 [I-D.ietf-lsr-flex-algo]. 348 To advertise the Administrative Group and Extended Administrative 349 Group in the OSPFv2 Extended Link TLV, the same format for the sub- 350 TLVs defined in [RFC3630] and [RFC7308] is used with the following 351 TLV types: 353 TBD17 - Administrative Group 355 TBD18 - Extended Administrative Group 357 To advertise Administrative Group and Extended Administrative Group 358 in the OSPFv3 Router-Link TLV, the same format for the sub-TLVs 359 defined in [RFC3630] and [RFC7308] is used with the following TLV 360 types: 362 TBD19 - Administrative Group 364 TBD20 - Extended Administrative Group 366 5. Advertisement of Application Specific Values 368 Multiple applications can utilize link attributes that are advertised 369 by OSPF. Some examples of applications using the link attributes are 370 Segment Routing Traffic Engineering and LFA [RFC5286]. 372 In some cases the link attribute MAY have different values for 373 different applications. An example could be SRLG [Section 4.1], 374 where values used by LFA could be different then the values used by 375 Segment Routing Traffic Engineering. 377 To allow advertisement of the application specific values of the link 378 attribute, a new Application Specific Link Attributes (ASLA) sub-TLV 379 is defined. The ASLA sub-TLV is a sub-TLV of the OSPFv2 Extended 380 Link TLV [RFC7471] and OSPFv3 Router-Link TLV [RFC8362]. The ASLA 381 sub-TLV is an optional sub-TLV and can appear multiple times in the 382 OSPFv2 Extended Link TLV and OSPFv3 Router-Link TLV. It has the 383 following format: 385 0 1 2 3 386 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 387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 388 | Type | Length | 389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 390 | SABML | UDABML | Reserved | 391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 392 | Standard Application Bit-Mask | 393 +- -+ 394 | ... | 395 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 396 | User Defined Application Bit-Mask | 397 +- -+ 398 | ... | 399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 400 | Link Attribute sub-sub-TLVs | 401 +- -+ 402 | ... | 404 where: 406 Type: TBD21 (OSPFv2), TBD22 (OSPFv3) 408 Length: variable 410 SABML: Standard Application Bit-Mask Length. If the Standard 411 Application Bit-Mask is not present, the Standard Application Bit- 412 Mask Length MUST be set to 0. 414 UDABML: User Defined Application Bit-Mask Length. If the User 415 Defined Application Bit-Mask is not present, the User Defined 416 Application Bit-Mask Length MUST be set to 0. 418 Standard Application Bit-Mask: Optional set of bits, where each 419 bit represents a single standard application. Bits are defined in 420 [I-D.ietf-isis-te-app], which also request a new IANA "Link 421 Attribute Applications" registry under "Interior Gateway Protocol 422 (IGP) Parameters" for them. The bits are repeated here for 423 informational purpose: 425 Bit-0: RSVP Traffic Engineering 427 Bit-1: Segment Routing Traffic Engineering 429 Bit-2: Loop Free Alternate (LFA). Includes all LFA types 431 Bit-3: Flexible Algorithm 433 User Defined Application Bit-Mask: Optional set of bits, where 434 each bit represents a single user defined application. 436 Standard Application Bits are defined/sent starting with Bit 0. 437 Additional bit definitions that are defined in the future SHOULD be 438 assigned in ascending bit order so as to minimize the number of 439 octets that will need to be transmitted. 441 User Defined Application bits have no relationship to Standard 442 Application bits and are NOT managed by IANA or any other standards 443 body. It is recommended that bits are used starting with Bit 0 so as 444 to minimize the number of octets required to advertise all of them. 446 Undefined bits in both Bit-Masks MUST be transmitted as 0 and MUST be 447 ignored on receipt. Bits that are NOT transmitted MUST be treated as 448 if they are set to 0 on receipt. 450 If the link attribute advertisement is limited to be used by a 451 specific set of applications, corresponding Bit-Masks MUST be present 452 and application specific bit(s) MUST be set for all applications that 453 use the link attributes advertised in the ASLA sub-TLV. 455 Application Bit-Masks apply to all link attributes that support 456 application specific values and are advertised in the ASLA sub-TLV. 458 The advantage of not making the Application Bit-Masks part of the 459 attribute advertisement itself is that we can keep the format of the 460 link attributes that have been defined previously and reuse the same 461 format when advertising them in the ASLA sub-TLV. 463 When neither the Standard Application Bits nor the User Defined 464 Application bits are set (i.e., both SABML and UDABML are 0) in the 465 ASLA sub-TLV, then the link attributes included in it MUST be 466 considered as being applicable to all applications. 468 If, however, another advertisement of the same link attribute 469 includes any Application Bit-Mask in the ASLA sub-TLV, applications 470 that are listed in the Application Bit-Masks of such ASLA sub-TLV 471 SHOULD use the attribute advertisement which has the application 472 specific bit set in the Application Bit-Masks. 474 If the same application is listed in the Application Bit-Masks of 475 more then one ASLA sub-TLV, the application SHOULD use the first 476 advertisement and ignore any subsequent advertisements of the same 477 attribute. This situation SHOULD be logged as an error. 479 This document defines the initial set of link attributes that MUST 480 use ASLA sub-TLV if advertised in the OSPFv2 Extended Link TLV or in 481 the OSPFv3 Router-Link TLV. If the ASLA sub-TLV includes any link 482 attribute(s) NOT listed below, they MUST be ignored. Documents which 483 define new link attributes MUST state whether the new attributes 484 support application specific values and as such MUST be advertised in 485 an ASLA sub-TLV. The link attributes that MUST be advertised in ASLA 486 sub-TLVs are: 488 - Shared Risk Link Group 490 - Unidirectional Link Delay 492 - Min/Max Unidirectional Link Delay 494 - Unidirectional Delay Variation 496 - Unidirectional Link Loss 498 - Unidirectional Residual Bandwidth 500 - Unidirectional Available Bandwidth 502 - Unidirectional Utilized Bandwidth 504 - Administrative Group 506 - Extended Administrative Group 508 - Traffic Engineering Metric 510 6. Maximum Link Bandwidth 512 Maximum link bandwidth is an application independent attribute of the 513 link that is defined in [RFC3630]. Because it is an application 514 independent attribute, it MUST NOT be advertised in ASLA sub-TLV. 515 Instead, it MAY be advertised as a sub-TLV of the Extended Link 516 Opaque LSA Extended Link TLV in OSPFv2 [RFC7684] or sub-TLV of OSPFv3 517 E-Router-LSA Router-Link TLV in OSPFv3 [RFC8362]. 519 To advertise the Maximum link bandwidth in the OSPFv2 Extended Link 520 TLV, the same format for sub-TLV defined in [RFC3630] is used with 521 TLV type TBD23. 523 To advertise the Maximum link bandwidth in the OSPFv3 Router-Link 524 TLV, the same format for sub-TLV defined in [RFC3630] is used with 525 TLV type TBD24. 527 7. Local Interface IPv6 Address Sub-TLV 529 The Local Interface IPv6 Address Sub-TLV is an application 530 independent attribute of the link that is defined in [RFC5329]. 531 Because it is an application independent attribute, it MUST NOT be 532 advertised in the ASLA sub-TLV. Instead, it MAY be advertised as a 533 sub-TLV of the OSPFv3 E-Router-LSA Router-Link TLV [RFC8362]. 535 To advertise the Local Interface IPv6 Address Sub-TLV in the OSPFv3 536 Router-Link TLV, the same format for sub-TLV defined in [RFC5329] is 537 used with TLV type TBD25. 539 8. Remote Interface IPv6 Address Sub-TLV 541 The Remote Interface IPv6 Address Sub-TLV is an application 542 independent attribute of the link that is defined in [RFC5329]. 543 Because it is an application independent attribute, it MUST NOT be 544 advertised in the ASLA sub-TLV. Instead, it MAY be advertised as a 545 sub-TLV of the OSPFv3 E-Router-LSA Router-Link TLV [RFC8362]. 547 To advertise the Remote Interface IPv6 Address Sub-TLV in the OSPFv3 548 Router-Link TLV, the same format for sub-TLV defined in [RFC5329] is 549 used with TLV type TBD26. 551 9. Deployment Considerations 553 If link attributes are advertised associated with zero length 554 application bit masks for both standard applications and user defined 555 applications, then that set of link attributes MAY be used by any 556 application. If support for a new application is introduced on any 557 node in a network in the presence of such advertisements, these 558 advertisements MAY be used by the new application. If this is not 559 what is intended, then existing advertisements MUST be readvertised 560 with an explicit set of applications specified before a new 561 application is introduced. 563 10. Attribute Advertisements and Enablement 565 This document defines extensions to support the advertisement of 566 application specific link attributes. 568 Whether the presence of link attribute advertisements for a given 569 application indicates that the application is enabled on that link 570 depends upon the application. Similarly, whether the absence of link 571 attribute advertisements indicates that the application is not 572 enabled depends upon the application. 574 In the case of RSVP-TE, the advertisement of application specific 575 link attributes implies that RSVP is enabled on that link. 577 In the case of SRTE, advertisement of application specific link 578 attributes does NOT indicate enablement of SRTE. The advertisements 579 are only used to support constraints which may be applied when 580 specifying an explicit path. SRTE is implicitly enabled on all links 581 which are part of the Segment Routing enabled topology independent of 582 the existence of link attribute advertisements. 584 In the case of LFA, advertisement of application specific link 585 attributes does NOT indicate enablement of LFA on that link. 586 Enablement is controlled by local configuration. 588 In the case of Flexible Algorithm, advertisement of application 589 specific link attributes does NOT indicate enablement of Flexible 590 Algorithm on that link. Rather the attributes are used to determine 591 what links are included/excluded in the algorithm specific 592 constrained SPF. This is fully specified in 593 [I-D.ietf-lsr-flex-algo]. 595 If, in the future, additional standard applications are defined to 596 use this mechanism, the specification defining this use MUST define 597 the relationship between application specific link attribute 598 advertisements and enablement for that application. 600 This document allows the advertisement of application specific link 601 attributes with no application identifiers i.e., both the Standard 602 Application Bit Mask and the User Defined Application Bit Mask are 603 not present Section 5. This supports the use of the link attribute 604 by any application. In the presence of an application where the 605 advertisement of link attribute advertisements is used to infer the 606 enablement of an application on that link (e.g., RSVP-TE), the 607 absence of the application identifier leaves ambiguous whether that 608 application is enabled on such a link. This needs to be considered 609 when making use of the "any application" encoding. 611 11. Backward Compatibility 613 Link attributes may be concurrently advertised in both the TE Opaque 614 LSA and the Extended Link Opaque LSA in OSPFv2 and the OSPFv3 Intra- 615 Area-TE-LSA and OSPFv3 Extended LSA Router-Link TLV in OSPFv3. 617 In fact, there is at least one OSPF implementation that utilizes the 618 link attributes advertised in TE Opaque LSAs [RFC3630] for Non-RSVP 619 TE applications. For example, this implementation of LFA and remote 620 LFA utilizes links attributes such as Shared Risk Link Groups (SRLG) 621 [RFC4203] and Admin Group [[RFC3630] advertised in TE Opaque LSAs. 622 These applications are described in [RFC5286], [RFC7490], [RFC7916] 623 and [RFC8102]. 625 When an OSPF routing domain includes routers using link attributes 626 from the OSPFv2 TE Opaque LSAs or the OSPFv3 Intra-Area-TE-LSA for 627 Non-RSVP TE applications such as LFA, OSPF routers in that domain 628 SHOULD continue to advertise such OSPFv2 TE Opaque LSAs or the OSPFv3 629 Intra-Area-TE-LSA. If there are also OSPF routers using the link 630 attributes described herein for any other application, OSPF routers 631 in the routing domain will also need to advertise these attributes in 632 OSPFv2 Extended Link Attributes LSAs or OSPFv3 E-Router-LSA. In such 633 a deployment, the advertised attributes SHOULD be the same and Non- 634 RSVP application access to link attributes is a matter of local 635 policy. 637 12. Security Considerations 639 Implementations must assure that malformed TLV and Sub-TLV 640 permutations do not result in errors that cause hard OSPF failures. 642 13. IANA Considerations 644 13.1. OSPFv2 646 OSPFv2 Extended Link TLV Sub-TLVs registry [RFC7684] defines sub-TLVs 647 at any level of nesting for OSPFv2 Extended Link TLVs. This 648 specification updates OSPFv2 Extended Link TLV sub-TLVs registry with 649 the following TLV types: 651 TBD21 (10 Recommended) - Application Specific Link Attributes 653 TBD1 (11 Recommended) - Shared Risk Link Group 655 TBD3 (12 Recommended) - Unidirectional Link Delay 657 TBD4 (13 Recommended) - Min/Max Unidirectional Link Delay 659 TBD5 (14 Recommended) - Unidirectional Delay Variation 661 TBD6 (15 Recommended) - Unidirectional Link Loss 663 TBD7 (16 Recommended) - Unidirectional Residual Bandwidth 665 TBD8 (17 Recommended) - Unidirectional Available Bandwidth 666 TBD9 (18 Recommended) - Unidirectional Utilized Bandwidth 668 TBD9 (19 Recommended) - Administrative Group 670 TBD17 (20 Recommended) - Extended Administrative Group 672 TBD23 (21 Recommended) - Maximum Link Bandwidth 674 TBD27 (22 Recommended) - Traffic Engineering Metric 676 13.2. OSPFv3 678 OSPFv3 Extended LSA Sub-TLV Registry [RFC8362] defines sub-TLVs at 679 any level of nesting for OSPFv3 Extended LSAs. This specification 680 updates OSPFv3 Extended LSA Sub-TLV Registry with the following TLV 681 types: 683 TBD22 (9 Recommended) - Application Specific Link Attributes 685 TBD2 (10 Recommended) - Shared Risk Link Group 687 TBD10 (11 Recommended) - Unidirectional Link Delay 689 TBD11 (12 Recommended) - Min/Max Unidirectional Link Delay 691 TBD12 (13 Recommended) - Unidirectional Delay Variation 693 TBD13 (14 Recommended) - Unidirectional Link Loss 695 TBD14 (15 Recommended) - Unidirectional Residual Bandwidth 697 TBD15 (16 Recommended) - Unidirectional Available Bandwidth 699 TBD16 (17 Recommended) - Unidirectional Utilized Bandwidth 701 TBD19 (18 Recommended) - Administrative Group 703 TBD20 (19 Recommended) - Extended Administrative Group 705 TBD24 (20 Recommended) - Maximum Link Bandwidth 707 TBD25 (21 Recommended) - Local Interface IPv6 Address Sub-TLV 709 TBD26 (22 Recommended) - Local Interface IPv6 Address Sub-TLV 711 TBD28 (23 Recommended) - Traffic Engineering Metric 713 14. Acknowledgments 715 Thanks to Chris Bowers for his review and comments. 717 15. References 719 15.1. Normative References 721 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 722 Requirement Levels", BCP 14, RFC 2119, 723 DOI 10.17487/RFC2119, March 1997, 724 . 726 [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering 727 (TE) Extensions to OSPF Version 2", RFC 3630, 728 DOI 10.17487/RFC3630, September 2003, 729 . 731 [RFC5329] Ishiguro, K., Manral, V., Davey, A., and A. Lindem, Ed., 732 "Traffic Engineering Extensions to OSPF Version 3", 733 RFC 5329, DOI 10.17487/RFC5329, September 2008, 734 . 736 [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 737 for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, 738 . 740 [RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework", 741 RFC 5714, DOI 10.17487/RFC5714, January 2010, 742 . 744 [RFC7308] Osborne, E., "Extended Administrative Groups in MPLS 745 Traffic Engineering (MPLS-TE)", RFC 7308, 746 DOI 10.17487/RFC7308, July 2014, 747 . 749 [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., 750 Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute 751 Advertisement", RFC 7684, DOI 10.17487/RFC7684, November 752 2015, . 754 [RFC8362] Lindem, A., Roy, A., Goethals, D., Reddy Vallem, V., and 755 F. Baker, "OSPFv3 Link State Advertisement (LSA) 756 Extensibility", RFC 8362, DOI 10.17487/RFC8362, April 757 2018, . 759 15.2. Informative References 761 [I-D.ietf-idr-ls-distribution] 762 Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. 763 Ray, "North-Bound Distribution of Link-State and TE 764 Information using BGP", draft-ietf-idr-ls-distribution-13 765 (work in progress), October 2015. 767 [I-D.ietf-isis-te-app] 768 Ginsberg, L., Psenak, P., Previdi, S., Henderickx, W., and 769 J. Drake, "IS-IS TE Attributes per application", draft- 770 ietf-isis-te-app-05 (work in progress), October 2018. 772 [I-D.ietf-lsr-flex-algo] 773 Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and 774 A. Gulko, "IGP Flexible Algorithm", draft-ietf-lsr-flex- 775 algo-00 (work in progress), May 2018. 777 [I-D.ietf-ospf-segment-routing-extensions] 778 Psenak, P., Previdi, S., Filsfils, C., Gredler, H., 779 Shakir, R., Henderickx, W., and J. Tantsura, "OSPF 780 Extensions for Segment Routing", draft-ietf-ospf-segment- 781 routing-extensions-25 (work in progress), April 2018. 783 [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, 784 DOI 10.17487/RFC2328, April 1998, 785 . 787 [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in 788 Support of Generalized Multi-Protocol Label Switching 789 (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, 790 . 792 [RFC5286] Atlas, A., Ed. and A. Zinin, Ed., "Basic Specification for 793 IP Fast Reroute: Loop-Free Alternates", RFC 5286, 794 DOI 10.17487/RFC5286, September 2008, 795 . 797 [RFC7471] Giacalone, S., Ward, D., Drake, J., Atlas, A., and S. 798 Previdi, "OSPF Traffic Engineering (TE) Metric 799 Extensions", RFC 7471, DOI 10.17487/RFC7471, March 2015, 800 . 802 [RFC7490] Bryant, S., Filsfils, C., Previdi, S., Shand, M., and N. 803 So, "Remote Loop-Free Alternate (LFA) Fast Reroute (FRR)", 804 RFC 7490, DOI 10.17487/RFC7490, April 2015, 805 . 807 [RFC7855] Previdi, S., Ed., Filsfils, C., Ed., Decraene, B., 808 Litkowski, S., Horneffer, M., and R. Shakir, "Source 809 Packet Routing in Networking (SPRING) Problem Statement 810 and Requirements", RFC 7855, DOI 10.17487/RFC7855, May 811 2016, . 813 [RFC7916] Litkowski, S., Ed., Decraene, B., Filsfils, C., Raza, K., 814 Horneffer, M., and P. Sarkar, "Operational Management of 815 Loop-Free Alternates", RFC 7916, DOI 10.17487/RFC7916, 816 July 2016, . 818 [RFC8102] Sarkar, P., Ed., Hegde, S., Bowers, C., Gredler, H., and 819 S. Litkowski, "Remote-LFA Node Protection and 820 Manageability", RFC 8102, DOI 10.17487/RFC8102, March 821 2017, . 823 [RFC8379] Hegde, S., Sarkar, P., Gredler, H., Nanduri, M., and L. 824 Jalil, "OSPF Graceful Link Shutdown", RFC 8379, 825 DOI 10.17487/RFC8379, May 2018, 826 . 828 Authors' Addresses 830 Peter Psenak (editor) 831 Cisco Systems, Inc. 832 Eurovea Centre, Central 3 833 Pribinova Street 10 834 Bratislava 81109 835 Slovakia 837 Email: ppsenak@cisco.com 839 Acee Lindem 840 Cisco Systems 841 301 Midenhall Way 842 Cary, NC 27513 843 USA 845 Email: acee@cisco.com 846 Les Ginsberg 847 Cisco Systems 848 821 Alder Drive 849 MILPITAS, CA 95035 850 USA 852 Email: ginsberg@cisco.com 854 Wim Henderickx 855 Nokia 856 Copernicuslaan 50 857 Antwerp, 2018 94089 858 Belgium 860 Email: wim.henderickx@nokia.com 862 Jeff Tantsura 863 Nuage Networks 864 US 866 Email: jefftant.ietf@gmail.com 868 Hannes Gredler 869 RtBrick Inc. 871 Email: hannes@rtbrick.com 873 John Drake 874 Juniper Networks 876 Email: jdrake@juniper.net