--- 1/draft-ietf-ospf-te-link-attr-reuse-13.txt 2020-06-07 13:13:13.062229765 -0700 +++ 2/draft-ietf-ospf-te-link-attr-reuse-14.txt 2020-06-07 13:13:13.106230877 -0700 @@ -1,24 +1,24 @@ LSR Working Group P. Psenak, Ed. Internet-Draft L. Ginsberg Intended status: Standards Track Cisco Systems -Expires: December 7, 2020 W. Henderickx +Expires: December 9, 2020 W. Henderickx Nokia J. Tantsura Apstra J. Drake Juniper Networks - June 5, 2020 + June 7, 2020 OSPF Link Traffic Engineering Attribute Reuse - draft-ietf-ospf-te-link-attr-reuse-13.txt + draft-ietf-ospf-te-link-attr-reuse-14.txt Abstract Existing traffic engineering related link attribute advertisements have been defined and are used in RSVP-TE deployments. Since the original RSVP-TE use case was defined, additional applications (e.g., Segment Routing Traffic Engineering, Loop Free Alternate) have been defined which also make use of the link attribute advertisements. In cases where multiple applications wish to make use of these link attributes the current advertisements do not support application @@ -35,21 +35,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on December 7, 2020. + This Internet-Draft will expire on December 9, 2020. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -210,21 +210,21 @@ have been originally defined for RSVP-TE applications (See Section 6). TE link attributes used for RSVP-TE/GMPLS continue to use OSPFv2 TE Opaque LSA [RFC3630] and OSPFv3 Intra-Area-TE-LSA [RFC5329]. The format of the link attribute TLVs that have been defined for RSVP-TE applications will be kept unchanged even when they are used for non-RSVP-TE applications. Unique code points are allocated for these link attribute TLVs from the OSPFv2 Extended Link TLV Sub-TLV - Registry [RFC7684] and from the OSPFv3 Extended LSA Sub-TLV Registry + Registry [RFC7684] and from the OSPFv3 Extended-LSA Sub-TLV Registry [RFC8362], as specified in Section 14. 5. Advertisement of Application Specific Values To allow advertisement of the application specific values of the link attribute, a new Application Specific Link Attributes (ASLA) sub-TLV is defined. The ASLA sub-TLV is a sub-TLV of the OSPFv2 Extended Link TLV [RFC7684] and OSPFv3 Router-Link TLV [RFC8362]. On top of advertising the link attributes for standardized @@ -351,21 +351,21 @@ - Administrative Group [RFC3630] - Extended Administrative Group [RFC7308] - TE Metric [RFC3630] 6. Reused TE link attributes This section defines the use case and indicates the code points (Section 14) from the OSPFv2 Extended Link TLV Sub-TLV Registry and - OSPFv3 Extended LSA Sub-TLV Registry for some of the link attributes + OSPFv3 Extended-LSA Sub-TLV Registry for some of the link attributes that have been originally defined for RSVP-TE or GMPLS. 6.1. Shared Risk Link Group (SRLG) The SRLG of a link can be used in OSPF calculated IPFRR [RFC5714] to compute a backup path that does not share any SRLG group with the protected link. To advertise the SRLG of the link in the OSPFv2 Extended Link TLV, the same format for the sub-TLV defined in section 1.3 of [RFC4203] @@ -391,21 +391,21 @@ 14 - Unidirectional Delay Variation 15 - Unidirectional Link Loss 16 - Unidirectional Residual Bandwidth 17 - Unidirectional Available Bandwidth 18 - Unidirectional Utilized Bandwidth - To advertise extended link metrics in the OSPFv3 Extended LSA Router- + To advertise extended link metrics in the OSPFv3 Extended-LSA Router- Link TLV, the same format for the sub-TLVs defined in [RFC7471] is used with the following TLV types: 13 - Unidirectional Link Delay 14 - Min/Max Unidirectional Link Delay 15 - Unidirectional Delay Variation 16 - Unidirectional Link Loss @@ -723,21 +723,21 @@ with (for example) [RFC3630]. As the advertisements defined in this document limit the scope to specific applications, the impact of tampering is similarly limited in scope. 14. IANA Considerations This specifications updates two existing registries: - OSPFv2 Extended Link TLV Sub-TLVs Registry - - OSPFv3 Extended LSA Sub-TLV Registry + - OSPFv3 Extended-LSA Sub-TLV Registry New values are allocated using the IETF Review procedure as described in [RFC5226]. 14.1. OSPFv2 The OSPFv2 Extended Link TLV Sub-TLVs Registry [RFC7684] defines sub- TLVs at any level of nesting for OSPFv2 Extended Link TLVs. IANA has assigned the following Sub-TLV types from the OSPFv2 Extended Link TLV Sub-TLVs Registry: @@ -762,38 +762,38 @@ 19 - Administrative Group 20 - Extended Administrative Group 22 - TE Metric 23 - Maximum Link Bandwidth 14.2. OSPFv3 - The OSPFv3 Extended LSA Sub-TLV Registry [RFC8362] defines sub-TLVs + The OSPFv3 Extended-LSA Sub-TLV Registry [RFC8362] defines sub-TLVs at any level of nesting for OSPFv3 Extended LSAs. IANA has assigned - the following Sub-TLV types from the OSPFv3 Extended LSA Sub-TLV + the following Sub-TLV types from the OSPFv3 Extended-LSA Sub-TLV Registry: 11 - Application Specific Link Attributes 12 - Shared Risk Link Group 13 - Unidirectional Link Delay 14 - Min/Max Unidirectional Link Delay 15 - Unidirectional Delay Variation 16 - Unidirectional Link Loss - 16 - Unidirectional Residual Bandwidth + 17 - Unidirectional Residual Bandwidth 18 - Unidirectional Available Bandwidth 19 - Unidirectional Utilized Bandwidth 20 - Administrative Group 21 - Extended Administrative Group 22 - TE Metric