rfc9356.original   rfc9356.txt 
Link State Routing K. Talaulikar, Ed. Internet Engineering Task Force (IETF) K. Talaulikar, Ed.
Internet-Draft P. Psenak Request for Comments: 9356 P. Psenak
Updates: 9085 (if approved) Cisco Systems Updates: 9085 Cisco Systems
Intended status: Standards Track 7 October 2022 Category: Standards Track January 2023
Expires: 10 April 2023 ISSN: 2070-1721
Advertising Layer 2 Bundle Member Link Attributes in OSPF Advertising Layer 2 Bundle Member Link Attributes in OSPF
draft-ietf-lsr-ospf-l2bundles-10
Abstract Abstract
There are deployments where the Layer 3 (L3) interface on which OSPF There are deployments where the Layer 3 (L3) interface on which OSPF
operates is a Layer 2 (L2) interface bundle. Existing OSPF operates is a Layer 2 (L2) interface bundle. Existing OSPF
advertisements only support advertising link attributes of the Layer advertisements only support advertising link attributes of the L3
3 interface. If entities external to OSPF wish to control traffic interface. If entities external to OSPF wish to control traffic
flows on the individual physical links which comprise the Layer 2 flows on the individual physical links that comprise the L2 interface
interface bundle, link attribute information for the bundle members bundle, link attribute information for the bundle members is
is required. required.
This document defines the protocol extensions for OSPF to advertise This document defines the protocol extensions for OSPF to advertise
the link attributes of L2 bundle members. The document also the link attributes of L2 bundle members. The document also
specifies the advertisment of these OSPF extensions via BGP Link specifies the advertisement of these OSPF extensions via the Border
State protocol and thereby updates RFC9085. Gateway Protocol - Link State (BGP-LS) and thereby updates RFC 9085.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on 10 April 2023. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9356.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2023 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language
2. L2 Bundle Member Attributes . . . . . . . . . . . . . . . . . 4 2. L2 Bundle Member Attributes
3. BGP-LS Advertisement . . . . . . . . . . . . . . . . . . . . 7 3. BGP-LS Advertisement
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 4. IANA Considerations
5. Operational Considerations . . . . . . . . . . . . . . . . . 8 5. Operational Considerations
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 7. References
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.1. Normative References
8.1. Normative References . . . . . . . . . . . . . . . . . . 9 7.2. Informative References
8.2. Informational References . . . . . . . . . . . . . . . . 10 Acknowledgements
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses
1. Introduction 1. Introduction
There are deployments where the Layer 3 interface on which an OSPF There are deployments where the L3 interface on which an OSPF
adjacency is established is a Layer 2 interface bundle, for instance adjacency is established is a L2 interface bundle, for instance, a
a Link Aggregation Group (LAG) [IEEE802.1AX]. This reduces the Link Aggregation Group (LAG) [IEEE802.1AX]. This reduces the number
number of adjacencies that need to be maintained by the OSPF protocol of adjacencies that need to be maintained by the OSPF protocol in
in cases where there are parallel links between the neighbors. cases where there are parallel links between the neighbors. Entities
Entities external to OSPF such as Path Computation Elements (PCE) external to OSPF such as Path Computation Elements (PCEs) [RFC4655]
[RFC4655] may wish to control traffic flows on individual Layer 2 may wish to control traffic flows on individual L2 member links of
member links of the underlying bundle (e.g., LAG) interface. To do the underlying bundle interface (e.g., LAG). To do so, link
so, link attribute information for individual bundle members is attribute information for individual bundle members is required. The
required. The protocol extensions defined in this document provide protocol extensions defined in this document provide the means to
the means to advertise this information. advertise this information.
This document defines sub-TLVs to advertise link attribute This document defines sub-TLVs to advertise link attribute
information for each of the L2 bundle members which comprise the information for each of the L2 bundle members that comprise the L3
Layer 3 interface on which OSPF operates. Similar capabilities were interface on which OSPF operates. Similar capabilities were
introduced in IS-IS via [RFC8668]. introduced for IS-IS in [RFC8668].
[RFC8665] and [RFC8666] introduced the adjacency segment identifier [RFC8665] and [RFC8666] introduced the Adjacency Segment Identifier
(Adj-SID) link attribute for OSPFv2 and OSPFv3 respectively which can (Adj-SID) link attribute for OSPFv2 and OSPFv3, respectively, which
be used as an instruction to forwarding to send traffic over a can be used as an instruction to forward traffic over a specific link
specific link [RFC8402]. This document enables the advertisement of [RFC8402]. This document enables the advertisement of the Adj-SIDs
the Adj-SIDs using the same Adjacency SID Sub-TLV at the granularity using the same Adj-SID sub-TLV at the granularity level of each L2
level of each L2 bundle member link so that traffic may be steered bundle member link so that traffic may be steered over that specific
over that specific member link. member link.
Note that the advertisements at the L2 bundle member link-level Note that the advertisements at the L2 bundle member link level
defined in this document are intended to be provided to external (to defined in this document are intended to be provided to entities
OSPF) entities and do not alter or change the OSPF route computation. external to OSPF and do not alter or change the OSPF route
The following items are intentionally not defined and are outside the computation. The following items are intentionally not defined in
scope of this document: and are outside the scope of this document:
* What link attributes will be advertised. This is determined by * What link attributes will be advertised. This is determined by
the needs of the external entities. the needs of the external entities.
* A minimum or default set of link attributes. * A minimum or default set of link attributes.
* How these attributes are configured. * How these attributes are configured.
* How the advertisements are used. * How the advertisements are used.
* What impact the use of these advertisements may have on traffic * What impact the use of these advertisements may have on traffic
flow in the network. flow in the network.
* How the advertisements are passed to external entities. * How the advertisements are passed to external entities.
The BGP Link State (BGP-LS) [RFC7752] was extended for the BGP Link State (BGP-LS) [RFC7752] was extended for the advertisement
advertisement of Layer 2 bundle members and their attributes by of L2 bundle members and their attributes in [RFC9085], which covered
[RFC9085] which covered only IS-IS. This document updates [RFC9085] only IS-IS. This document updates [RFC9085] by specifying the
by specifying the advertisement from OSPF (refer Section 3). advertisement from OSPF (refer to Section 3).
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. L2 Bundle Member Attributes 2. L2 Bundle Member Attributes
A new L2 Bundle Member Attributes Sub-TLV is introduced to advertise A new L2 Bundle Member Attributes sub-TLV is introduced to advertise
L2 bundle member attributes in both OSPFv2 and OSPFv3. In the case L2 bundle member attributes in both OSPFv2 and OSPFv3. In the case
of OSPFv2, this sub-TLV is an optional sub-TLV of the OSPFv2 Extended of OSPFv2, this sub-TLV is an optional sub-TLV of the OSPFv2 Extended
Link TLV that is used to describe link attributes via the OSPFv2 Link TLV that is used to describe link attributes via the OSPFv2
Extended Link Opaque LSA [RFC7684]. In the case of OSPFv3, this sub- Extended Link Opaque LSA (Link State Advertisement) [RFC7684]. In
TLV is an optional sub-TLV of the Router Link TLV of the OSPFv3 E- the case of OSPFv3, this sub-TLV is an optional sub-TLV of the
Router-LSA [RFC8362]. Router-Link TLV of the OSPFv3 E-Router-LSA [RFC8362].
When the OSPF adjacency is associated with an L2 bundle interface, When the OSPF adjacency is associated with an L2 bundle interface,
this sub-TLV is used to advertise the underlying L2 bundle member this sub-TLV is used to advertise the underlying L2 bundle member
links along with their respective link attributes. The inclusion of links along with their respective link attributes. The inclusion of
this information implies that the identified link is a member of the this information implies that the identified link is a member of the
L2 bundle associated with an OSPF L3 link and that the member link is L2 bundle associated with an OSPF L3 link and that the member link is
operationally up. Therefore, advertisements of member links MUST NOT operationally up. Therefore, advertisements of member links MUST NOT
be done when the member link becomes operationally down or it is no be done when the member link becomes operationally down or is no
longer a member of the identified L2 bundle. longer a member of the identified L2 bundle.
The advertisement of the L2 Bundle Member Attributes Sub-TLV may be The advertisement of the L2 Bundle Member Attributes sub-TLV may be
asymmetric for an OSPF link depending on the underlying layer 2 asymmetric for an OSPF link, depending on the underlying L2
connectivity i.e., advertised by the router on only one end. connectivity, i.e., advertised by the router on only one end.
The L2 Bundle Member Attributes Sub-TLV has the following format: The L2 Bundle Member Attributes sub-TLV has the following format:
0 1 2 3 0 1 2 3
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 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| L2 Bundle Member Descriptor | | L2 Bundle Member Descriptor |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Member Link Attribute sub-TLVs (variable) // | Member Link Attribute sub-TLVs (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: L2 Bundle Member Attributes sub-TLV Format Figure 1: L2 Bundle Member Attributes Sub-TLV Format
Where: Where:
Type: 24 for OSPFv2 and 29 for OSPFv3 Type: 24 for OSPFv2 and 29 for OSPFv3
Length: The total length (in octets) of the value portion of the Length: The total length (in octets) of the value portion of the TLV
TLV including nested Sub-TLVs. including nested sub-TLVs.
L2 Bundle Member Descriptor: A 4 octet Link Local Identifier as L2 Bundle Member Descriptor: A 4-octet link-local identifier for the
described in [RFC4202] and used in [RFC8510] for the member link. member link. This identifier is described as "link local
identifier" in [RFC4202] and used as "Local Interface ID" in
[RFC8510].
Link attributes for L2 bundle member links are advertised as sub-TLVs Link attributes for L2 bundle member links are advertised as sub-TLVs
of the L2 Bundle Member Attribute Sub-TLV. of the L2 Bundle Member Attributes sub-TLV.
In the case of OSPFv2, the L2 Bundle Member Attributes Sub-TLV shares In the case of OSPFv2, the L2 Bundle Member Attributes sub-TLV shares
the sub-TLV space of the Extended Link TLV and the sub-TLVs of the the sub-TLV space of the Extended Link TLV, and the sub-TLVs of the
Extended Link TLV MAY be used to describe the attributes of the Extended Link TLV MAY be used to describe the attributes of the
member link. Figure 2 below lists sub-TLVs and their applicability member link. Table 1 lists sub-TLVs and their applicability for L2
for L2 bundle member links. The sub-TLVs that are not applicable bundle member links. The sub-TLVs that are not applicable MUST NOT
MUST NOT be used as sub-TLVs for the L2 Bundle Member Attributes Sub- be used as sub-TLVs for the L2 Bundle Member Attributes sub-TLV.
TLV. Specifications that introduce new sub-TLVs of the Extended Link Specifications that introduce new sub-TLVs of the Extended Link TLV
TLV MUST indicate their applicability for the L2 Bundle Member MUST indicate their applicability to the L2 Bundle Member Attributes
Attributes Sub-TLV. Typically, attributes that have Layer 3 sub-TLV. Typically, attributes that have L3 semantics would not be
semantics would not be applicable while Layer 2 attributes would applicable, but L2 attributes would apply. An implementation MUST
apply. An implementation MUST ignore any sub-TLVs received that are ignore any sub-TLVs received that are not applicable in the context
not applicable in the context of the L2 Bundle Member Attribute Sub- of the L2 Bundle Member Attributes sub-TLV.
TLV.
Y - applicable +=======+======================================+===============+
N - not-applicable | Value | Description | Applicability |
+=======+======================================+===============+
| 1 | SID/Label | N |
+-------+--------------------------------------+---------------+
| 2 | Adj-SID | Y |
+-------+--------------------------------------+---------------+
| 3 | LAN Adj-SID/Label | Y |
+-------+--------------------------------------+---------------+
| 4 | Network-to-Router Metric | N |
+-------+--------------------------------------+---------------+
| 5 | RTM Capability | N |
+-------+--------------------------------------+---------------+
| 6 | OSPFv2 Link MSD | N |
+-------+--------------------------------------+---------------+
| 7 | Graceful-Link-Shutdown | N |
+-------+--------------------------------------+---------------+
| 8 | Remote IPv4 Address | N |
+-------+--------------------------------------+---------------+
| 9 | Local/Remote Interface ID | N |
+-------+--------------------------------------+---------------+
| 10 | Application-Specific Link Attributes | Y |
+-------+--------------------------------------+---------------+
| 11 | Shared Risk Link Group | Y |
+-------+--------------------------------------+---------------+
| 12 | Unidirectional Link Delay | Y |
+-------+--------------------------------------+---------------+
| 13 | Min/Max Unidirectional Link Delay | Y |
+-------+--------------------------------------+---------------+
| 14 | Unidirectional Delay Variation | Y |
+-------+--------------------------------------+---------------+
| 15 | Unidirectional Link Loss | Y |
+-------+--------------------------------------+---------------+
| 16 | Unidirectional Residual Bandwidth | Y |
+-------+--------------------------------------+---------------+
| 17 | Unidirectional Available Bandwidth | Y |
+-------+--------------------------------------+---------------+
| 18 | Unidirectional Utilized Bandwidth | Y |
+-------+--------------------------------------+---------------+
| 19 | Administrative Group | Y |
+-------+--------------------------------------+---------------+
| 20 | Extended Administrative Group | Y |
+-------+--------------------------------------+---------------+
| 22 | TE Metric | Y |
+-------+--------------------------------------+---------------+
| 23 | Maximum Link Bandwidth | Y |
+-------+--------------------------------------+---------------+
| 24 | L2 Bundle Member Attributes | N |
+-------+--------------------------------------+---------------+
1 SID/Label (N) Table 1: Applicability of OSPFv2 Link Attribute Sub-TLVs for
2 Adj-SID (Y) L2 Bundle Members
3 LAN Adj-SID/Label (Y)
4 Network-to-Router Metric (N)
5 RTM Capability (N)
6 OSPFv2 Link MSD (N)
7 Graceful-Link-Shutdown (N)
8 Remote IPv4 Address (N)
9 Local/Remote Interface ID (N)
10 Application Specific Link Attributes (Y)
11 Shared Risk Link Group (Y)
12 Unidirectional Link Delay (Y)
13 Min/Max Unidirectional Link Delay (Y)
14 Unidirectional Delay Variation (Y)
15 Unidirectional Link Loss (Y)
16 Unidirectional Residual Bandwidth (Y)
17 Unidirectional Available Bandwidth (Y)
18 Unidirectional Utilized Bandwidth (Y)
19 Administrative Group (Y)
20 Extended Administrative Group (Y)
21 OSPFv2 Link Attributes Bits (N)
22 TE Metric (Y)
23 Maximum Link Bandwidth (Y)
24 L2 Bundle Member Attributes (N)
Figure 2: Applicability of OSPFv2 Link Attribute Sub-TLVs for L2 Applicability:
Bundle Members
In the case of OSPFv3, the L2 Bundle Member Attributes Sub-TLV shares Y: This sub-TLV MAY appear in the L2 Bundle Member Attributes sub-
the sub-TLV space of the Router Link TLV and the sub-TLVs of the TLV.
Router Link TLV MAY be used to describe the attributes of the member
link. Figure 3 below lists sub-TLVs that are applicable to the
Router Link TLV and their applicability for L2 bundle member links.
The sub-TLVs that are not applicable MUST NOT be used as sub-TLVs for
the L2 Bundle Member Attributes Sub-TLV. Specifications that
introduce new sub-TLVs of the Router Link TLV MUST indicate their
applicability for the L2 Bundle Member Attributes Sub-TLV. An
implementation MUST ignore any sub-TLVs received that are not
applicable in the context of the L2 Bundle Member Attribute Sub-TLV.
Y - applicable N: This sub-TLV MUST NOT appear in the L2 Bundle Member Attributes
N - not-applicable sub-TLV.
X - not Router Link Sub-TLV
1 IPv6-Forwarding-Address (X) In the case of OSPFv3, the L2 Bundle Member Attributes sub-TLV shares
2 IPv4-Forwarding-Address (X) the sub-TLV space of the Router-Link TLV, and the sub-TLVs of the
3 Route-Tag (X) Router-Link TLV MAY be used to describe the attributes of the member
4 Prefix SID (X) link. Table 2 lists sub-TLVs that are applicable to the Router-Link
5 Adj-SID (Y) TLV and their applicability for L2 bundle member links. The sub-TLVs
6 LAN Adj-SID (Y) that are not applicable MUST NOT be used as sub-TLVs for the L2
7 SID/Label (N) Bundle Member Attributes sub-TLV. Specifications that introduce new
8 Graceful-Link-Shutdown (N) sub-TLVs of the Router-Link TLV MUST indicate their applicability to
9 OSPFv3 Link MSD (N) the L2 Bundle Member Attributes sub-TLV. An implementation MUST
10 OSPFv3 Link Attribute Bits (N) ignore any sub-TLVs received that are not applicable in the context
11 Application Specific Link Attributes (Y) of the L2 Bundle Member Attributes sub-TLV.
12 Shared Risk Link Group (Y)
13 Unidirectional Link Delay (Y) +=======+=========================================+===============+
14 Min/Max Unidirectional Link Delay (Y) | Value | Description | Applicability |
15 Unidirectional Delay Variation (Y) +=======+=========================================+===============+
16 Unidirectional Link Loss (Y) | 1 | IPv6-Forwarding-Address | X |
17 Unidirectional Residual Bandwidth (Y) +-------+-----------------------------------------+---------------+
18 Unidirectional Available Bandwidth (Y) | 2 | IPv4-Forwarding-Address | X |
19 Unidirectional Utilized Bandwidth (Y) +-------+-----------------------------------------+---------------+
20 Administrative Group (Y) | 3 | Route-Tag | X |
21 Extended Administrative Group (Y) +-------+-----------------------------------------+---------------+
22 Traffic Engineering Metric (Y) | 4 | Prefix SID | X |
23 Maximum Link Bandwidth (Y) +-------+-----------------------------------------+---------------+
24 Local Interface IPv6 Address (N) | 5 | Adj-SID | Y |
25 Remote Interface IPv6 Address (N) +-------+-----------------------------------------+---------------+
26 Flex-Algorithm Prefix Metric (X) | 6 | LAN Adj-SID | Y |
27 Prefix Source OSPF Router-ID (X) +-------+-----------------------------------------+---------------+
28 Prefix Source Router Address (X) | 7 | SID/Label | N |
29 L2 Bundle Member Attributes (N) +-------+-----------------------------------------+---------------+
30 SRv6 SID Structure (Y) | 8 | Graceful-Link-Shutdown | N |
31 SRv6 End.X SID Structure (Y) +-------+-----------------------------------------+---------------+
32 SRv6 End.X SID Structure (Y) | 9 | OSPFv3 Link MSD | N |
Figure 3: Applicability of OSPFv3 Link Attribute Sub-TLVs for L2 +-------+-----------------------------------------+---------------+
Bundle Members | 11 | Application-Specific Link Attributes | Y |
+-------+-----------------------------------------+---------------+
| 12 | Shared Risk Link Group | Y |
+-------+-----------------------------------------+---------------+
| 13 | Unidirectional Link Delay | Y |
+-------+-----------------------------------------+---------------+
| 14 | Min/Max Unidirectional Link Delay | Y |
+-------+-----------------------------------------+---------------+
| 15 | Unidirectional Delay Variation | Y |
+-------+-----------------------------------------+---------------+
| 16 | Unidirectional Link Loss | Y |
+-------+-----------------------------------------+---------------+
| 17 | Unidirectional Residual Bandwidth | Y |
+-------+-----------------------------------------+---------------+
| 18 | Unidirectional Available Bandwidth | Y |
+-------+-----------------------------------------+---------------+
| 19 | Unidirectional Utilized Bandwidth | Y |
+-------+-----------------------------------------+---------------+
| 20 | Administrative Group | Y |
+-------+-----------------------------------------+---------------+
| 21 | Extended Administrative Group | Y |
+-------+-----------------------------------------+---------------+
| 22 | TE Metric | Y |
+-------+-----------------------------------------+---------------+
| 23 | Maximum Link Bandwidth | Y |
+-------+-----------------------------------------+---------------+
| 24 | Local Interface IPv6 Address | N |
+-------+-----------------------------------------+---------------+
| 25 | Remote Interface IPv6 Address | N |
+-------+-----------------------------------------+---------------+
| 26 | Flexible Algorithm Prefix Metric (FAPM) | X |
+-------+-----------------------------------------+---------------+
| 27 | Prefix Source OSPF Router-ID | X |
+-------+-----------------------------------------+---------------+
| 28 | Prefix Source Router Address | X |
+-------+-----------------------------------------+---------------+
| 29 | L2 Bundle Member Attributes | N |
+-------+-----------------------------------------+---------------+
| 33 | OSPF Flexible Algorithm ASBR Metric | X |
+-------+-----------------------------------------+---------------+
Table 2: Applicability of OSPFv3 Link Attribute Sub-TLVs for L2
Bundle Members
Applicability:
Y: This sub-TLV MAY appear in the L2 Bundle Member Attributes sub-
TLV.
N: This sub-TLV MUST NOT appear in the L2 Bundle Member Attributes
sub-TLV.
X: This is not a sub-TLV of the Router-Link TLV; it MUST NOT appear
in the L2 Bundle Member Attributes sub-TLV.
3. BGP-LS Advertisement 3. BGP-LS Advertisement
The BGP-LS extensions for the advertisment of Layer 2 bundle members The BGP-LS extensions for the advertisement of L2 bundle members and
and their attributes was specified in [RFC9085]. Using the OSPF L2 their attributes were specified in [RFC9085]. Using the OSPF L2
Bundle Member Attributes sub-TLV defined in this document, the L2 Bundle Member Attributes sub-TLV defined in this document, the L2
bundle member information can now be advertised from OSPF into BGP-LS bundle member information can now be advertised from OSPF into BGP-LS
on the same lines as discussed for IS-IS in section 2.2.3 of on the same lines as discussed for IS-IS in Section 2.2.3 of
[RFC9085]. [RFC9085].
4. IANA Considerations 4. IANA Considerations
IANA has allocated the following code point via early allocation in IANA has allocated the following code point in the "OSPFv2 Extended
the "OSPFv2 Extended Link TLV Sub-TLVs" registry under the "OSPFv2 Link TLV Sub-TLVs" subregistry under the "Open Shortest Path First v2
Parameters" registry that needs to be made permanent: (OSPFv2) Parameters" registry:
Value: 24
Name: L2 Bundle Member Attributes
IANA has allocated the following code point via early allocation in Value: 24
the "OSPFv3 Extended LSA Sub-TLVs" registry under the "OSPFv3
Parameters" registry that needs to be made permanent:
Value: 29 Designation: L2 Bundle Member Attributes
Name: L2 Bundle Member Attributes IANA has allocated the following code point in the "OSPFv3 Extended-
LSA Sub-TLVs" subregistry under the "Open Shortest Path First v3
(OSPFv3) Parameters" registry:
IANA is requested to introduce a column "Applicability to L2 Bundle Value: 29
Member sub-TLV" (abbreviated as L2BM) in the registry tables for the
"OSPFv2 Extended Link TLV Sub-TLVs" registry with the initial updates
(Y/N) against allocations as indicated in Figure 2. An explanatory
note is also to be added to this registry as follows:
The column for the Applicability to L2 Bundle Member sub-TLV (L2BM) Description: L2 Bundle Member Attributes
may be marked as follows:
Y - sub-TLV MAY appear in L2 Bundle Member sub-TLV IANA has also introduced a column titled "L2BM" in the "OSPFv2
N - sub-TLV MUST NOT appear in L2 Bundle Member sub-TLV Extended Link TLV Sub-TLVs" registry. The "L2BM" column indicates
applicability to the L2 Bundle Attributes Member sub-TLV. The
initial allocations (Y/N) for this column are indicated in Table 1.
The following explanatory note has been added to the registry:
Similarly, IANA is requested to introduce a column "Applicability to | The "L2BM" column indicates applicability to the L2 Bundle
L2 Bundle Member sub-TLV" (abbreviated as L2BM) in the registry | Attributes Member sub-TLV. The options for the "L2BM" column are:
tables for the "OSPFv3 Extended LSA Sub-TLVs" registry with the | Y - This sub-TLV MAY appear in the L2 Bundle Member Attributes
initial updates (Y/N/X) against allocations as indicated in Figure 3. | sub-TLV.
|
| N - This sub-TLV MUST NOT appear in the L2 Bundle Member
| Attributes sub-TLV.
The column for the Applicability to L2 Bundle Member sub-TLV (L2BM) Similarly, IANA has introduced a column titled "L2BM" in the "OSPFv3
may be marked as follows: Extended-LSA Sub-TLVs" registry. The "L2BM" column indicates
applicability to the L2 Bundle Attributes Member sub-TLV. The
initial allocations (Y/N/X) for this column are indicated in Table 2.
The following explanatory note has been added to the registry:
Y - sub-TLV MAY appear in L2 Bundle Member sub-TLV | The "L2BM" column indicates applicability to the L2 Bundle
N - sub-TLV MUST NOT appear in L2 Bundle Member sub-TLV | Attributes Member sub-TLV. The options for the "L2BM" column are:
X - sub-TLV is not a Router Link sub-TLV; it MUST NOT appear | Y - This sub-TLV MAY appear in the L2 Bundle Member Attributes
in L2 Bundle Member sub-TLV | sub-TLV.
|
| N - This sub-TLV MUST NOT appear in the L2 Bundle Member
| Attributes sub-TLV.
|
| X - This is not a sub-TLV of the Router-Link TLV; it MUST NOT
| appear in the L2 Bundle Member Attributes sub-TLV.
Further allocations from these two registries are required to Future allocations in these two registries are required to indicate
indicate the applicability of the introduced sub-TLV to the L2 Bundle the applicability of the introduced sub-TLV to the L2 Bundle Member
Member sub-TLV that would get updated in these registries. Attributes sub-TLV. IANA has added this document as a reference for
both registries.
5. Operational Considerations 5. Operational Considerations
Implementations MUST NOT enable the advertisement of Layer 2 bundle Implementations MUST NOT enable the advertisement of L2 bundle member
member links and their attributes in OSPF LSAs by default and MUST links and their attributes in OSPF LSAs by default and MUST provide a
provide a configuration option to enable their advertisement on configuration option to enable their advertisement on specific links.
specific links.
[I-D.ietf-ospf-yang] specifies the base OSPF YANG model. The [RFC9129] specifies the base YANG data model for OSPF. The required
required configuration and operational elements for this feature are configuration and operational elements for this feature are expected
expected to be introduce as augmentation to this base OSPF YANG to be introduced as augmentation to this base YANG data model for
model. OSPF.
6. Security Considerations 6. Security Considerations
The OSPF protocol has supported the advertisement of link attribute The OSPF protocol has supported the advertisement of link attribute
information, including link identifiers, for many years. The information, including link identifiers, for many years. The
advertisements defined in this document are identical to existing advertisements defined in this document are identical to the existing
advertisements defined in [RFC3630], [RFC4203], [RFC5329], [RFC7471], advertisements defined in [RFC3630], [RFC4203], [RFC5329], [RFC7471],
[RFC8665], and [RFC8666] - but are associated with L2 links which are [RFC8665], and [RFC8666], but they are associated with L2 links that
part of a bundle interface on which the OSPF protocol operates. are part of a bundle interface on which the OSPF protocol operates.
Therefore, the security considerations of these documents are Therefore, the security considerations of these documents are
applicable and there are no new security issues introduced by the applicable, and there are no new security issues introduced by the
extensions in this document. extensions in this document.
As always, if the protocol is used in an environment where As always, if the protocol is used in an environment where
unauthorized access to the physical links on which OSPF packets are unauthorized access to the physical links on which OSPF packets are
sent occurs then attacks are possible. The use of authentication as sent occurs, then attacks are possible. The use of authentication as
defined in [RFC5709], [RFC7474], [RFC4552], and [RFC7166] is defined in [RFC5709], [RFC7474], [RFC4552], and [RFC7166] is
recommended for preventing such attacks. recommended for preventing such attacks.
7. Acknowledgements 7. References
This document leverages the similar work done for IS-IS and the
authors of this document would like to acknowledge the contributions
of the authors of [RFC8668].
The authors would like to thank Anoop Ghanwani, Paul Kyzivat, Dan
Romascanu, and Russ Mundy for their review and feedback on this
document. The authors would also like to thank Acee Lindem for his
detailed shepherd review of this document. The authors would also
like to thank John Scudder for his AD review and the discussion
related to the applicability of TLVs/sub-TLVs to the L2 Bundle Member
TLV.
8. References
8.1. Normative References 7.1. Normative References
[IEEE802.1AX] [IEEE802.1AX]
IEEE, "IEEE Standard for Local and Metropolitan Area IEEE, "IEEE Standard for Local and Metropolitan Area
Networks - Link Aggregation IEEE Std 802.1AX-2020 Networks--Link Aggregation", IEEE Std 802.1AX,
(Revision of IEEE Std 802.1AX-2014)", 30 January 2020. DOI 10.1109/IEEESTD.2020.9105034, May 2020,
<https://doi.org/10.1109/IEEESTD.2020.9105034>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005,
<https://www.rfc-editor.org/info/rfc4202>. <https://www.rfc-editor.org/info/rfc4202>.
skipping to change at page 10, line 15 skipping to change at line 485
[RFC8666] Psenak, P., Ed. and S. Previdi, Ed., "OSPFv3 Extensions [RFC8666] Psenak, P., Ed. and S. Previdi, Ed., "OSPFv3 Extensions
for Segment Routing", RFC 8666, DOI 10.17487/RFC8666, for Segment Routing", RFC 8666, DOI 10.17487/RFC8666,
December 2019, <https://www.rfc-editor.org/info/rfc8666>. December 2019, <https://www.rfc-editor.org/info/rfc8666>.
[RFC9085] Previdi, S., Talaulikar, K., Ed., Filsfils, C., Gredler, [RFC9085] Previdi, S., Talaulikar, K., Ed., Filsfils, C., Gredler,
H., and M. Chen, "Border Gateway Protocol - Link State H., and M. Chen, "Border Gateway Protocol - Link State
(BGP-LS) Extensions for Segment Routing", RFC 9085, (BGP-LS) Extensions for Segment Routing", RFC 9085,
DOI 10.17487/RFC9085, August 2021, DOI 10.17487/RFC9085, August 2021,
<https://www.rfc-editor.org/info/rfc9085>. <https://www.rfc-editor.org/info/rfc9085>.
8.2. Informational References 7.2. Informative References
[I-D.ietf-ospf-yang]
Yeung, D., Qu, Y., Zhang, J., Chen, I., and A. Lindem,
"YANG Data Model for OSPF Protocol", Work in Progress,
Internet-Draft, draft-ietf-ospf-yang-29, 17 October 2019,
<https://www.ietf.org/archive/id/draft-ietf-ospf-yang-
29.txt>.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
DOI 10.17487/RFC3630, September 2003, DOI 10.17487/RFC3630, September 2003,
<https://www.rfc-editor.org/info/rfc3630>. <https://www.rfc-editor.org/info/rfc3630>.
[RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in [RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions in
Support of Generalized Multi-Protocol Label Switching Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005,
<https://www.rfc-editor.org/info/rfc4203>. <https://www.rfc-editor.org/info/rfc4203>.
skipping to change at page 11, line 42 skipping to change at line 553
Pillay-Esnault, "OSPF Link-Local Signaling (LLS) Pillay-Esnault, "OSPF Link-Local Signaling (LLS)
Extensions for Local Interface ID Advertisement", Extensions for Local Interface ID Advertisement",
RFC 8510, DOI 10.17487/RFC8510, January 2019, RFC 8510, DOI 10.17487/RFC8510, January 2019,
<https://www.rfc-editor.org/info/rfc8510>. <https://www.rfc-editor.org/info/rfc8510>.
[RFC8668] Ginsberg, L., Ed., Bashandy, A., Filsfils, C., Nanduri, [RFC8668] Ginsberg, L., Ed., Bashandy, A., Filsfils, C., Nanduri,
M., and E. Aries, "Advertising Layer 2 Bundle Member Link M., and E. Aries, "Advertising Layer 2 Bundle Member Link
Attributes in IS-IS", RFC 8668, DOI 10.17487/RFC8668, Attributes in IS-IS", RFC 8668, DOI 10.17487/RFC8668,
December 2019, <https://www.rfc-editor.org/info/rfc8668>. December 2019, <https://www.rfc-editor.org/info/rfc8668>.
[RFC9129] Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
"YANG Data Model for the OSPF Protocol", RFC 9129,
DOI 10.17487/RFC9129, October 2022,
<https://www.rfc-editor.org/info/rfc9129>.
Acknowledgements
This document leverages similar work done for IS-IS, and the authors
of this document would like to acknowledge the contributions of the
authors of [RFC8668].
The authors would like to thank Anoop Ghanwani, Paul Kyzivat, Dan
Romascanu, and Russ Mundy for their review and feedback on this
document. The authors would also like to thank Acee Lindem for his
detailed shepherd review of this document. The authors would also
like to thank John Scudder for his AD review and the discussion
related to the applicability of TLVs/sub-TLVs to the L2 Bundle Member
Attributes sub-TLV.
Authors' Addresses Authors' Addresses
Ketan Talaulikar (editor) Ketan Talaulikar (editor)
Cisco Systems Cisco Systems
India India
Email: ketant.ietf@gmail.com Email: ketant.ietf@gmail.com
Peter Psenak Peter Psenak
Cisco Systems Cisco Systems
Apollo Business Center Apollo Business Center
 End of changes. 59 change blocks. 
266 lines changed or deleted 336 lines changed or added

This html diff was produced by rfcdiff 1.48.