rfc9356xml2.original.xml   rfc9356.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?> <!DOCTYPE rfc [
<?rfc tocompact="yes"?> <!ENTITY nbsp "&#160;">
<?rfc tocdepth="3"?> <!ENTITY zwsp "&#8203;">
<?rfc tocindent="yes"?> <!ENTITY nbhy "&#8209;">
<?rfc symrefs="yes"?> <!ENTITY wj "&#8288;">
<?rfc sortrefs="yes"?> ]>
<?rfc comments="yes"?>
<?rfc inline="yes"?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" category="
<?rfc compact="yes"?> std" consensus="true" docName="draft-ietf-lsr-ospf-l2bundles-10" number="9356" i
<?rfc subcompact="no"?> pr="trust200902" updates="9085" obsoletes="" xml:lang="en" tocInclude="true" toc
<rfc category="std" docName="draft-ietf-lsr-ospf-l2bundles-10" Depth="3" symRefs="true" sortRefs="true" version="3">
ipr="trust200902" updates="9085">
<!-- xml2rfc v2v3 conversion 3.15.0 -->
<front> <front>
<title abbrev="OSPF L2 Bundle Member Link Attributes">Advertising Layer 2 <title abbrev="OSPF L2 Bundle Member Link Attributes">Advertising Layer 2
Bundle Member Link Attributes in OSPF</title> Bundle Member Link Attributes in OSPF</title>
<seriesInfo name="RFC" value="9356"/>
<author fullname="Ketan Talaulikar" initials="K." role="editor" <author fullname="Ketan Talaulikar" initials="K." role="editor" surname="Tal
surname="Talaulikar"> aulikar">
<organization>Cisco Systems</organization> <organization>Cisco Systems</organization>
<address> <address>
<postal> <postal>
<street/> <street/>
<city/> <city/>
<code/> <code/>
<region/> <region/>
<country>India</country> <country>India</country>
</postal> </postal>
<email>ketant.ietf@gmail.com</email> <email>ketant.ietf@gmail.com</email>
</address> </address>
</author> </author>
<author fullname="Peter Psenak" initials="P." surname="Psenak"> <author fullname="Peter Psenak" initials="P." surname="Psenak">
<organization>Cisco Systems</organization> <organization>Cisco Systems</organization>
<address> <address>
<postal> <postal>
<street>Apollo Business Center</street> <extaddr>Apollo Business Center</extaddr>
<street>Mlynske nivy 43</street> <street>Mlynske nivy 43</street>
<city>Bratislava</city> <city>Bratislava</city>
<code>821 09</code> <code>821 09</code>
<country>Slovakia</country> <country>Slovakia</country>
</postal> </postal>
<email>ppsenak@cisco.com</email> <email>ppsenak@cisco.com</email>
</address> </address>
</author> </author>
<date year="2023" month="January" />
<date year=""/> <area>rtg</area>
<workgroup>lsr</workgroup>
<area>Routing</area>
<workgroup>Link State Routing</workgroup>
<keyword>OSPF</keyword> <keyword>OSPF</keyword>
<abstract> <abstract>
<t>There are deployments where the Layer 3 (L3) interface on which OSPF <t>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 3 advertisements only support advertising link attributes of the L3
interface. If entities external to OSPF wish to control traffic flows on interface. If entities external to OSPF wish to control traffic flows on
the individual physical links which comprise the Layer 2 interface the individual physical links that comprise the L2 interface
bundle, link attribute information for the bundle members is bundle, link attribute information for the bundle members is
required.</t> required.</t>
<t>This document defines the protocol extensions for OSPF to advertise <t>This document defines the protocol extensions for OSPF to advertise
the link attributes of L2 bundle members. The document also specifies the link attributes of L2 bundle members. The document also specifies
the advertisment of these OSPF extensions via BGP Link State protocol the advertisement of these OSPF extensions via the Border Gateway Protocol
and thereby updates RFC9085.</t> - Link State (BGP-LS)
and thereby updates RFC 9085.</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section title="Introduction"> <section numbered="true" toc="default">
<t>There are deployments where the Layer 3 interface on which an OSPF <name>Introduction</name>
adjacency is established is a Layer 2 interface bundle, for instance a <t>There are deployments where the L3 interface on which an
Link Aggregation Group (LAG) <xref target="IEEE802.1AX"/>. This reduces OSPF adjacency is established is a L2 interface bundle, for
the number of adjacencies that need to be maintained by the OSPF instance, a Link Aggregation Group (LAG) <xref target="IEEE802.1AX"
protocol in cases where there are parallel links between the neighbors. format="default"/>. This reduces the number of adjacencies that need to
Entities external to OSPF such as Path Computation Elements (PCE) <xref be maintained by the OSPF protocol in cases where there are parallel
target="RFC4655"/> may wish to control traffic flows on individual Layer links between the neighbors. Entities external to OSPF such as Path
2 member links of the underlying bundle (e.g., LAG) interface. To do so, Computation Elements (PCEs) <xref target="RFC4655" format="default"/> may
link attribute information for individual bundle members is required. wish to control traffic flows on individual L2 member links of the
The protocol extensions defined in this document provide the means to underlying bundle interface (e.g., LAG). To do so, link attribute
advertise this information.</t> information for individual bundle members is required. The protocol
extensions defined in this document provide the means to advertise this
information.</t>
<t>This document defines sub-TLVs to advertise link attribute <t>This document defines sub-TLVs to advertise link attribute
information for each of the L2 bundle members which comprise the Layer 3 information for each of the L2 bundle members that comprise the L3
interface on which OSPF operates. Similar capabilities were introduced interface on which OSPF operates. Similar capabilities were introduced
in IS-IS via <xref target="RFC8668"/>.</t> for IS-IS in <xref target="RFC8668" format="default"/>.</t>
<t><xref target="RFC8665"/> and <xref target="RFC8666"/> introduced the
adjacency segment identifier (Adj-SID) link attribute for OSPFv2 and
OSPFv3 respectively which can be used as an instruction to forwarding to
send traffic over a specific link <xref target="RFC8402"/>. This
document enables the advertisement of the Adj-SIDs using the same
Adjacency SID Sub-TLV at the granularity level of each L2 bundle member
link so that traffic may be steered over that specific member link.</t>
<t>Note that the advertisements at the L2 bundle member link-level
defined in this document are intended to be provided to external (to
OSPF) entities and do not alter or change the OSPF route computation.
The following items are intentionally not defined and are outside the
scope of this document:</t>
<t><list style="symbols">
<t>What link attributes will be advertised. This is determined by
the needs of the external entities.</t>
<t>A minimum or default set of link attributes.</t>
<t>How these attributes are configured.</t>
<t>How the advertisements are used.</t>
<t>What impact the use of these advertisements may have on traffic
flow in the network.</t>
<t>How the advertisements are passed to external entities.</t> <t><xref target="RFC8665" format="default"/> and <xref target="RFC8666"
</list></t> format="default"/> introduced the Adjacency Segment Identifier (Adj-SID)
link attribute for OSPFv2 and OSPFv3, respectively, which can be used as
an instruction to forward traffic over a specific link <xref
target="RFC8402" format="default"/>. This document enables the
advertisement of the Adj-SIDs using the same Adj-SID sub-TLV at
the granularity level of each L2 bundle member link so that traffic may
be steered over that specific member link.</t>
<t>The BGP Link State (BGP-LS) <xref target="RFC7752"/> was extended for <t>Note that the advertisements at the L2 bundle member link level
the advertisement of Layer 2 bundle members and their attributes by defined in this document are intended to be provided to entities external
<xref target="RFC9085"/> which covered only IS-IS. This document updates to OSPF
<xref target="RFC9085"/> by specifying the advertisement from OSPF and do not alter or change the OSPF route computation. The
(refer <xref target="BGPLS"/>).</t> following items are intentionally not defined in and are outside the scope
of this document:</t>
<ul spacing="normal">
<li>What link attributes will be advertised. This is determined by
the needs of the external entities.</li>
<li>A minimum or default set of link attributes.</li>
<li>How these attributes are configured.</li>
<li>How the advertisements are used.</li>
<li>What impact the use of these advertisements may have on traffic
flow in the network.</li>
<li>How the advertisements are passed to external entities.</li>
</ul>
<section title="Requirements Language"> <t>BGP Link State (BGP-LS) <xref target="RFC7752" format="default"/>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", was extended for the advertisement of L2 bundle members and their
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and attributes in <xref target="RFC9085" format="default"/>, which covered
"OPTIONAL" in this document are to be interpreted as described in BCP only IS-IS. This document updates <xref target="RFC9085"
14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only format="default"/> by specifying the advertisement from OSPF (refer to
when, they appear in all capitals, as shown here.</t> <xref target="BGPLS" format="default"/>).</t>
<section numbered="true" toc="default">
<name>Requirements Language</name>
<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
"<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>",
"<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document
are to be interpreted as described in BCP&nbsp;14 <xref
target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.
</t>
</section> </section>
</section> </section>
<section numbered="true" toc="default">
<section title="L2 Bundle Member Attributes"> <name>L2 Bundle Member Attributes</name> <t>A new L2 Bundle Member
<t>A new L2 Bundle Member Attributes Sub-TLV is introduced to advertise Attributes sub-TLV is introduced to advertise L2 bundle member
L2 bundle member attributes in both OSPFv2 and OSPFv3. In the case of attributes in both OSPFv2 and OSPFv3. In the case of OSPFv2, this
OSPFv2, this sub-TLV is an optional sub-TLV of the OSPFv2 Extended Link sub-TLV is an optional sub-TLV of the OSPFv2 Extended Link TLV that is
TLV that is used to describe link attributes via the OSPFv2 Extended used to describe link attributes via the OSPFv2 Extended Link Opaque LSA
Link Opaque LSA <xref target="RFC7684"/>. In the case of OSPFv3, this (Link State Advertisement) <xref target="RFC7684" format="default"/>. In
sub-TLV is an optional sub-TLV of the Router Link TLV of the OSPFv3 the case of OSPFv3, this sub-TLV is an optional sub-TLV of the Router-Link
E-Router-LSA <xref target="RFC8362"/>.</t> TLV of the OSPFv3 E-Router-LSA <xref target="RFC8362"
format="default"/>.</t>
<t>When the OSPF adjacency is associated with an L2 bundle interface, <t>When the OSPF adjacency is associated with an L2 bundle interface,
this sub-TLV is used to advertise the underlying L2 bundle member links this sub-TLV is used to advertise the underlying L2 bundle member links
along with their respective link attributes. The inclusion of this along with their respective link attributes. The inclusion of this
information implies that the identified link is a member of the L2 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 bundle associated with an OSPF L3 link and that the member link is
operationally up. Therefore, advertisements of member links MUST NOT be operationally up. Therefore, advertisements of member links <bcp14>MUST NO
done when the member link becomes operationally down or it is no longer T</bcp14> be
done when the member link becomes operationally down or is no longer
a member of the identified L2 bundle.</t> a member of the identified L2 bundle.</t>
<t>The advertisement of the L2 Bundle Member Attributes sub-TLV may be
<t>The advertisement of the L2 Bundle Member Attributes Sub-TLV may be asymmetric for an OSPF link, depending on the underlying L2
asymmetric for an OSPF link depending on the underlying layer 2 connectivity, i.e., advertised by the router on only one end.</t>
connectivity i.e., advertised by the router on only one end.</t> <t>The L2 Bundle Member Attributes sub-TLV has the following format:
</t>
<t>The L2 Bundle Member Attributes Sub-TLV has the following format: <figure anchor="L2BTLVFIG">
<figure anchor="L2BTLVFIG" <name>L2 Bundle Member Attributes Sub-TLV Format</name>
title="L2 Bundle Member Attributes sub-TLV Format"> <artwork name="" type="" align="left" alt=""><![CDATA[
<artwork><![CDATA[ 0 1 2 0 1 2 3
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) // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure></t> -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</figure>
<t>Where:<list style="hanging"> <t>Where:</t>
<t>Type: 24 for OSPFv2 and 29 for OSPFv3</t> <dl newline="false" spacing="normal">
<dt>Type:</dt>
<t>Length: The total length (in octets) of the value portion of the <dd>24 for OSPFv2 and 29 for OSPFv3</dd>
TLV including nested Sub-TLVs.</t> <dt>Length:</dt>
<dd>The total length (in octets) of the value portion of the
<t>L2 Bundle Member Descriptor: A 4 octet Link Local Identifier as TLV including nested sub-TLVs.</dd>
described in <xref target="RFC4202"/> and used in <xref <dt>L2 Bundle Member Descriptor:</dt>
target="RFC8510"/> for the member link.</t>
</list></t>
<dd>A 4-octet link-local identifier for the member link. This identifier
is described as "link local identifier" in <xref
target="RFC4202" format="default"/> and used as "Local Interface ID" in
<xref target="RFC8510"
format="default"/>.</dd>
</dl>
<t>Link attributes for L2 bundle member links are advertised as sub-TLVs <t>Link attributes for L2 bundle member links are advertised as sub-TLVs
of the L2 Bundle Member Attribute Sub-TLV.</t> of the L2 Bundle Member Attributes sub-TLV.</t>
<t>In the case of OSPFv2, the L2 Bundle Member Attributes sub-TLV shares
<t>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 <bcp14>MAY</bcp14> be used to describe the attributes
Extended Link TLV MAY be used to describe the attributes of the member of the member link. <xref target="OSPFV2L2EXCL" format="default"/>
link. <xref target="OSPFV2L2EXCL"/> below lists sub-TLVs and their lists sub-TLVs and their applicability for L2 bundle member links. The
applicability for L2 bundle member links. The sub-TLVs that are not sub-TLVs that are not applicable <bcp14>MUST NOT</bcp14> be used as
applicable MUST NOT be used as sub-TLVs for the L2 Bundle Member sub-TLVs for the L2 Bundle Member Attributes sub-TLV. Specifications
Attributes Sub-TLV. Specifications that introduce new sub-TLVs of the that introduce new sub-TLVs of the Extended Link TLV <bcp14>MUST</bcp14>
Extended Link TLV MUST indicate their applicability for the L2 Bundle indicate their applicability to the L2 Bundle Member Attributes
Member Attributes Sub-TLV. Typically, attributes that have Layer 3 sub-TLV. Typically, attributes that have L3
semantics would not be applicable while Layer 2 attributes would apply. semantics would not be applicable, but L2 attributes would apply.
An implementation MUST ignore any sub-TLVs received that are not An implementation <bcp14>MUST</bcp14> ignore any sub-TLVs received that ar
applicable in the context of the L2 Bundle Member Attribute Sub-TLV.</t> e not
applicable in the context of the L2 Bundle Member Attributes sub-TLV.</t>
<t><figure anchor="OSPFV2L2EXCL" <table anchor="OSPFV2L2EXCL" align="left">
title="Applicability of OSPFv2 Link Attribute Sub-TLVs for L2 Bundle M <name>Applicability of OSPFv2 Link Attribute Sub-TLVs for L2 Bundle Members</n
embers"> ame>
<artwork><![CDATA[ Y - applicable <thead>
N - not-applicable <tr>
<th>Value</th>
<th>Description</th>
<th>Applicability</th>
</tr>
</thead>
<tbody>
<tr>
<td>1</td>
<td>SID/Label</td>
<td align="center">N</td>
</tr>
<tr>
<td>2</td>
<td>Adj-SID</td>
<td align="center">Y</td>
</tr>
<tr>
<td>3</td>
<td>LAN Adj-SID/Label</td>
<td align="center">Y</td>
</tr>
<tr>
<td>4</td>
<td>Network-to-Router Metric</td>
<td align="center">N</td>
</tr>
<tr>
<td>5</td>
<td>RTM Capability</td>
<td align="center">N</td>
</tr>
<tr>
<td>6</td>
<td>OSPFv2 Link MSD</td>
<td align="center">N</td>
</tr>
<tr>
<td>7</td>
<td>Graceful-Link-Shutdown</td>
<td align="center">N</td>
</tr>
<tr>
<td>8</td>
<td>Remote IPv4 Address</td>
<td align="center">N</td>
</tr>
<tr>
<td>9</td>
<td>Local/Remote Interface ID</td>
<td align="center">N</td>
</tr>
<tr>
<td>10</td>
<td>Application-Specific Link Attributes</td>
<td align="center">Y</td>
</tr>
<tr>
<td>11</td>
<td>Shared Risk Link Group</td>
<td align="center">Y</td>
</tr>
<tr>
<td>12</td>
<td>Unidirectional Link Delay</td>
<td align="center">Y</td>
</tr>
<tr>
<td>13</td>
<td>Min/Max Unidirectional Link Delay</td>
<td align="center">Y</td>
</tr>
<tr>
<td>14</td>
<td>Unidirectional Delay Variation</td>
<td align="center">Y</td>
</tr>
<tr>
<td>15</td>
<td>Unidirectional Link Loss</td>
<td align="center">Y</td>
</tr>
<tr>
<td>16</td>
<td>Unidirectional Residual Bandwidth</td>
<td align="center">Y</td>
</tr>
<tr>
<td>17</td>
<td>Unidirectional Available Bandwidth</td>
<td align="center">Y</td>
</tr>
<tr>
<td>18</td>
<td>Unidirectional Utilized Bandwidth</td>
<td align="center">Y</td>
</tr>
<tr>
<td>19</td>
<td>Administrative Group</td>
<td align="center">Y</td>
</tr>
<tr>
<td>20</td>
<td>Extended Administrative Group</td>
<td align="center">Y</td>
</tr>
<tr>
<td>22</td>
<td>TE Metric</td>
<td align="center">Y</td>
</tr>
<tr>
<td>23</td>
<td>Maximum Link Bandwidth</td>
<td align="center">Y</td>
</tr>
<tr>
<td>24</td>
<td>L2 Bundle Member Attributes</td>
<td align="center">N</td>
</tr>
</tbody>
</table>
1 SID/Label (N) <t>Applicability:</t>
2 Adj-SID (Y) <dl newline="false" spacing="normal" indent="5">
3 LAN Adj-SID/Label (Y) <dt>Y:</dt><dd>This sub-TLV <bcp14>MAY</bcp14> appear in the L2 Bundle Member At
4 Network-to-Router Metric (N) tributes sub-TLV.</dd>
5 RTM Capability (N) <dt>N:</dt><dd>This sub-TLV <bcp14>MUST NOT</bcp14> appear in the L2 Bundle Memb
6 OSPFv2 Link MSD (N) er Attributes sub-TLV.</dd>
7 Graceful-Link-Shutdown (N) </dl>
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)
]]></artwork> <t>In the case of OSPFv3, the L2 Bundle Member Attributes sub-TLV shares
</figure></t> the sub-TLV space of the Router-Link TLV, and the sub-TLVs of the
Router-Link TLV <bcp14>MAY</bcp14> be used to describe the attributes of
the member link. <xref target="OSPFV3L2EXCL" format="default"/> 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 <bcp14>MUST NOT</bcp14> be used as sub-TLVs for the L2 Bundle
Member Attributes sub-TLV. Specifications that introduce new sub-TLVs of
the Router-Link TLV <bcp14>MUST</bcp14> indicate their applicability to
the L2 Bundle Member Attributes sub-TLV. An implementation
<bcp14>MUST</bcp14> ignore any sub-TLVs received that are not applicable
in the context of the L2 Bundle Member Attributes sub-TLV.</t>
<t>In the case of OSPFv3, the L2 Bundle Member Attributes Sub-TLV shares <table anchor="OSPFV3L2EXCL" align="left">
the sub-TLV space of the Router Link TLV and the sub-TLVs of the Router <name>Applicability of OSPFv3 Link Attribute Sub-TLVs for L2 Bundle Members</n
Link TLV MAY be used to describe the attributes of the member link. ame>
<xref target="OSPFV3L2EXCL"/> below lists sub-TLVs that are applicable <thead>
to the Router Link TLV and their applicability for L2 bundle member <tr>
links. The sub-TLVs that are not applicable MUST NOT be used as sub-TLVs <th>Value</th>
for the L2 Bundle Member Attributes Sub-TLV. Specifications that <th>Description</th>
introduce new sub-TLVs of the Router Link TLV MUST indicate their <th>Applicability</th>
applicability for the L2 Bundle Member Attributes Sub-TLV. An </tr>
implementation MUST ignore any sub-TLVs received that are not applicable </thead>
in the context of the L2 Bundle Member Attribute Sub-TLV.</t> <tbody>
<tr>
<td>1</td>
<td>IPv6-Forwarding-Address</td>
<td align="center">X</td>
</tr>
<tr>
<td>2</td>
<td>IPv4-Forwarding-Address</td>
<td align="center">X</td>
</tr>
<tr>
<td>3</td>
<td>Route-Tag</td>
<td align="center">X</td>
</tr>
<tr>
<td>4</td>
<td>Prefix SID</td>
<td align="center">X</td>
</tr>
<tr>
<td>5</td>
<td>Adj-SID</td>
<td align="center">Y</td>
</tr>
<tr>
<td>6</td>
<td>LAN Adj-SID</td>
<td align="center">Y</td>
</tr>
<tr>
<td>7</td>
<td>SID/Label</td>
<td align="center">N</td>
</tr>
<tr>
<td>8</td>
<td>Graceful-Link-Shutdown</td>
<td align="center">N</td>
</tr>
<tr>
<td>9</td>
<td>OSPFv3 Link MSD</td>
<td align="center">N</td>
</tr>
<tr>
<td>11</td>
<td>Application-Specific Link Attributes</td>
<td align="center">Y</td>
</tr>
<tr>
<td>12</td>
<td>Shared Risk Link Group</td>
<td align="center">Y</td>
</tr>
<tr>
<td>13</td>
<td>Unidirectional Link Delay</td>
<td align="center">Y</td>
</tr>
<tr>
<td>14</td>
<td>Min/Max Unidirectional Link Delay</td>
<td align="center">Y</td>
</tr>
<tr>
<td>15</td>
<td>Unidirectional Delay Variation</td>
<td align="center">Y</td>
</tr>
<tr>
<td>16</td>
<td>Unidirectional Link Loss</td>
<td align="center">Y</td>
</tr>
<tr>
<td>17</td>
<td>Unidirectional Residual Bandwidth</td>
<td align="center">Y</td>
</tr>
<tr>
<td>18</td>
<td>Unidirectional Available Bandwidth</td>
<td align="center">Y</td>
</tr>
<tr>
<td>19</td>
<td>Unidirectional Utilized Bandwidth</td>
<td align="center">Y</td>
</tr>
<tr>
<td>20</td>
<td>Administrative Group</td>
<td align="center">Y</td>
</tr>
<tr>
<td>21</td>
<td>Extended Administrative Group</td>
<td align="center">Y</td>
</tr>
<tr>
<td>22</td>
<td>TE Metric</td>
<td align="center">Y</td>
</tr>
<tr>
<td>23</td>
<td>Maximum Link Bandwidth</td>
<td align="center">Y</td>
</tr>
<tr>
<td>24</td>
<td>Local Interface IPv6 Address</td>
<td align="center">N</td>
</tr>
<tr>
<td>25</td>
<td>Remote Interface IPv6 Address</td>
<td align="center">N</td>
</tr>
<tr>
<td>26</td>
<td>Flexible Algorithm Prefix Metric (FAPM)</td>
<td align="center">X</td>
</tr>
<tr>
<td>27</td>
<td>Prefix Source OSPF Router-ID</td>
<td align="center">X</td>
</tr>
<tr>
<td>28</td>
<td>Prefix Source Router Address</td>
<td align="center">X</td>
</tr>
<tr>
<td>29</td>
<td>L2 Bundle Member Attributes</td>
<td align="center">N</td>
</tr>
<tr>
<td>33</td>
<td>OSPF Flexible Algorithm ASBR Metric</td>
<td align="center">X</td>
</tr>
</tbody>
</table>
<t><figure anchor="OSPFV3L2EXCL" <t>Applicability:</t>
title="Applicability of OSPFv3 Link Attribute Sub-TLVs for L2 Bundle M
embers">
<artwork><![CDATA[ Y - applicable
N - not-applicable
X - not Router Link Sub-TLV
1 IPv6-Forwarding-Address (X) <dl newline="false" spacing="normal" indent="5">
2 IPv4-Forwarding-Address (X) <dt>Y:</dt><dd>This sub-TLV <bcp14>MAY</bcp14> appear in the L2 Bundle Member At
3 Route-Tag (X) tributes sub-TLV.</dd>
4 Prefix SID (X) <dt>N:</dt><dd>This sub-TLV <bcp14>MUST NOT</bcp14> appear in the L2 Bundle Memb
5 Adj-SID (Y) er Attributes sub-TLV.</dd>
6 LAN Adj-SID (Y) <dt>X:</dt><dd>This is not a sub-TLV of the Router-Link TLV; it <bcp14>MUST NOT<
7 SID/Label (N) /bcp14> appear in the L2 Bundle Member Attributes sub-TLV.</dd>
8 Graceful-Link-Shutdown (N) </dl>
9 OSPFv3 Link MSD (N)
10 OSPFv3 Link Attribute Bits (N)
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 Traffic Engineering Metric (Y)
23 Maximum Link Bandwidth (Y)
24 Local Interface IPv6 Address (N)
25 Remote Interface IPv6 Address (N)
26 Flex-Algorithm Prefix Metric (X)
27 Prefix Source OSPF Router-ID (X)
28 Prefix Source Router Address (X)
29 L2 Bundle Member Attributes (N)
30 SRv6 SID Structure (Y)
31 SRv6 End.X SID Structure (Y)
32 SRv6 End.X SID Structure (Y)
]]></artwork>
</figure></t>
</section> </section>
<section anchor="BGPLS" numbered="true" toc="default">
<section anchor="BGPLS" title="BGP-LS Advertisement"> <name>BGP-LS Advertisement</name>
<t>The BGP-LS extensions for the advertisment of Layer 2 bundle members <t>The BGP-LS extensions for the advertisement of L2 bundle members
and their attributes was specified in <xref target="RFC9085"/>. Using and their attributes were specified in <xref target="RFC9085"
the OSPF L2 Bundle Member Attributes sub-TLV defined in this document, format="default"/>. Using the OSPF L2 Bundle Member Attributes sub-TLV
the L2 bundle member information can now be advertised from OSPF into defined in this document, the L2 bundle member information can now be
BGP-LS on the same lines as discussed for IS-IS in section 2.2.3 of advertised from OSPF into BGP-LS on the same lines as discussed for
<xref target="RFC9085"/>.</t> IS-IS in <xref target="RFC9085" sectionFormat="of"
section="2.2.3"/>.</t>
</section> </section>
<section anchor="IANA" title="IANA Considerations"> <section anchor="IANA" numbered="true" toc="default">
<t>IANA has allocated the following code point via early allocation in
the "OSPFv2 Extended Link TLV Sub-TLVs" registry under the "OSPFv2
Parameters" registry that needs to be made permanent:</t>
<t>Value: 24</t>
<t>Name: L2 Bundle Member Attributes</t>
<t>IANA has allocated the following code point via early allocation in
the "OSPFv3 Extended LSA Sub-TLVs" registry under the "OSPFv3
Parameters" registry that needs to be made permanent:</t>
<t>Value: 29</t>
<t>Name: L2 Bundle Member Attributes</t>
<t>IANA is requested to introduce a column "Applicability to L2 Bundle
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 <xref target="OSPFV2L2EXCL"/>.
An explanatory note is also to be added to this registry as follows:</t>
<t><figure align="left">
<artwork align="left"><![CDATA[ The column for the Applicability t
o L2 Bundle Member sub-TLV (L2BM)
may be marked as follows:
Y - sub-TLV MAY appear in L2 Bundle Member sub-TLV
N - sub-TLV MUST NOT appear in L2 Bundle Member sub-TLV
]]></artwork>
</figure></t>
<t>Similarly, IANA is requested to introduce a column "Applicability to
L2 Bundle Member sub-TLV" (abbreviated as L2BM) in the registry tables
for the "OSPFv3 Extended LSA Sub-TLVs" registry with the initial updates
(Y/N/X) against allocations as indicated in <xref
target="OSPFV3L2EXCL"/>.</t>
<t><figure align="left">
<artwork align="left"><![CDATA[ The column for the Applicability t
o L2 Bundle Member sub-TLV (L2BM)
may be marked as follows:
Y - sub-TLV MAY appear in L2 Bundle Member sub-TLV
N - sub-TLV MUST NOT appear in L2 Bundle Member sub-TLV
X - sub-TLV is not a Router Link sub-TLV; it MUST NOT appear
in L2 Bundle Member sub-TLV
]]></artwork>
</figure></t>
<t>Further allocations from these two registries are required to <name>IANA Considerations</name>
indicate the applicability of the introduced sub-TLV to the L2 Bundle <t>IANA has allocated the following code point in
Member sub-TLV that would get updated in these registries.</t> the "OSPFv2 Extended Link TLV Sub-TLVs" subregistry under the "Open Shorte
st Path First v2 (OSPFv2)
Parameters" registry:</t>
<dl newline="false" spacing="normal">
<dt>Value:</dt>
<dd>24</dd>
<dt>Designation:</dt>
<dd>L2 Bundle Member Attributes</dd>
</dl>
<t>IANA has allocated the following code point in
the "OSPFv3 Extended-LSA Sub-TLVs" subregistry under the "Open Shortest Pa
th First v3 (OSPFv3)
Parameters" registry:</t>
<dl newline="false" spacing="normal">
<dt>Value:</dt>
<dd>29</dd>
<dt>Description:</dt>
<dd>L2 Bundle Member Attributes</dd>
</dl>
<t>IANA has also introduced a column titled "L2BM" in the "OSPFv2
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 <xref
target="OSPFV2L2EXCL" format="default"/>. The following explanatory
note has been added to the registry:</t>
<blockquote>
<t>The "L2BM" column indicates applicability to the L2 Bundle Attributes
Member sub-TLV. The options for the "L2BM" column are:
</t>
<dl newline="false" spacing="normal" indent="5">
<dt>Y -</dt><dd>This sub-TLV <bcp14>MAY</bcp14> appear in the L2 Bundle Member A
ttributes sub-TLV.</dd>
<dt>N -</dt><dd>This sub-TLV <bcp14>MUST NOT</bcp14> appear in the L2 Bundle Mem
ber Attributes sub-TLV.</dd>
</dl>
</blockquote>
<t>Similarly, IANA has introduced a column titled "L2BM" in the "OSPFv3
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 <xref
target="OSPFV3L2EXCL" format="default"/>. The following explanatory note
has been added to the registry:</t>
<blockquote>
<t>The "L2BM" column indicates applicability to the L2 Bundle Attributes
Member sub-TLV. The options for the "L2BM" column are:
</t>
<dl newline="false" spacing="normal" indent="5">
<dt>Y -</dt><dd>This sub-TLV <bcp14>MAY</bcp14> appear in the L2 Bundle Member A
ttributes sub-TLV.</dd>
<dt>N -</dt><dd>This sub-TLV <bcp14>MUST NOT</bcp14> appear in the L2 Bundle Mem
ber Attributes sub-TLV.</dd>
<dt>X -</dt><dd>This is not a sub-TLV of the Router-Link TLV; it <bcp14>MUST NOT
</bcp14> appear in the L2 Bundle Member Attributes sub-TLV.</dd>
</dl>
</blockquote>
<t>Future allocations in these two registries are required to indicate
the applicability of the introduced sub-TLV to the L2 Bundle Member
Attributes sub-TLV. IANA has added this document as a reference for
both registries.</t>
</section> </section>
<section anchor="OPER" numbered="true" toc="default">
<section anchor="OPER" title="Operational Considerations"> <name>Operational Considerations</name>
<t>Implementations MUST NOT enable the advertisement of Layer 2 bundle <t>Implementations <bcp14>MUST NOT</bcp14> enable the advertisement of L2
member links and their attributes in OSPF LSAs by default and MUST bundle
member links and their attributes in OSPF LSAs by default and <bcp14>MUST<
/bcp14>
provide a configuration option to enable their advertisement on specific provide a configuration option to enable their advertisement on specific
links.</t> links.</t>
<t><xref target="RFC9129" format="default"/> specifies the base YANG data
<t><xref target="I-D.ietf-ospf-yang"/> specifies the base OSPF YANG model for OSPF. The required configuration and operational elements for th
model. The required configuration and operational elements for this is
feature are expected to be introduce as augmentation to this base OSPF feature are expected to be introduced as augmentation to this base YANG da
YANG model.</t> ta model for OSPF.</t>
</section> </section>
<section anchor="Security" numbered="true" toc="default">
<section anchor="Security" title="Security Considerations"> <name>Security Considerations</name>
<t>The OSPF protocol has supported the advertisement of link attribute <t>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 <xref target="RFC3630"/>, <xref advertisements defined in <xref target="RFC3630" format="default"/>,
target="RFC4203"/>, <xref target="RFC5329"/>, <xref target="RFC7471"/>, <xref target="RFC4203" format="default"/>, <xref target="RFC5329"
<xref target="RFC8665"/>, and <xref target="RFC8666"/> - but are format="default"/>, <xref target="RFC7471" format="default"/>, <xref
associated with L2 links which are part of a bundle interface on which target="RFC8665" format="default"/>, and <xref target="RFC8666"
the OSPF protocol operates. Therefore, the security considerations of format="default"/>, but they are associated with L2 links that are part of
these documents are applicable and there are no new security issues a bundle interface on which the OSPF protocol operates. Therefore, the
introduced by the extensions in this document.</t> security considerations of these documents are applicable, and there are
no new security issues introduced by the extensions in this
document.</t>
<t>As always, if the protocol is used in an environment where <t>As always, if the protocol is used in an environment where
unauthorized access to the physical links on which OSPF packets are sent unauthorized access to the physical links on which OSPF packets are sent
occurs then attacks are possible. The use of authentication as defined occurs, then attacks are possible. The use of authentication as defined
in <xref target="RFC5709"/>, <xref target="RFC7474"/>, <xref in <xref target="RFC5709" format="default"/>, <xref target="RFC7474" forma
target="RFC4552"/>, and <xref target="RFC7166"/> is recommended for t="default"/>, <xref target="RFC4552" format="default"/>, and <xref target="RFC7
166" format="default"/> is recommended for
preventing such attacks.</t> preventing such attacks.</t>
</section> </section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>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 <xref target="RFC8668"/>.</t>
<t>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.</t>
</section>
</middle> </middle>
<back> <back>
<references title="Normative References"> <references>
<reference anchor="IEEE802.1AX"> <name>References</name>
<front> <references>
<title>IEEE Standard for Local and Metropolitan Area Networks - Link <name>Normative References</name>
Aggregation IEEE Std 802.1AX-2020 (Revision of IEEE Std
802.1AX-2014)</title>
<author>
<organization abbrev="IEEE">Institute of Electrical and
Electronics Engineers</organization>
</author>
<date day="30" month="January" year="2020"/>
</front>
</reference>
<?rfc include='reference.RFC.2119'?>
<?rfc include='reference.RFC.8174'?>
<?rfc include='reference.RFC.4202'?>
<?rfc include='reference.RFC.7684'?>
<?rfc include='reference.RFC.8362'?> <reference anchor="IEEE802.1AX">
<front>
<title>IEEE Standard for Local and Metropolitan Area Networks--Link
Aggregation</title>
<author>
<organization>IEEE</organization>
</author>
<date month="May" year="2020"/>
</front>
<seriesInfo name="IEEE Std" value="802.1AX"/>
<seriesInfo name="DOI" value="10.1109/IEEESTD.2020.9105034"/>
</reference>
<?rfc include='reference.RFC.8665'?> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2
119.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
174.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4
202.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
684.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
362.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
665.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
666.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
085.xml"/>
</references>
<references>
<name>Informative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3
630.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4
203.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4
655.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
329.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
471.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
752.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
402.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
510.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5
709.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
474.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4
552.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7
166.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8
668.xml"/>
<?rfc include='reference.RFC.8666'?> <!-- [I-D.ietf-ospf-yang] Published as RFC 9129 -->
<?rfc include='reference.RFC.9085'?> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9
129.xml"/>
</references>
</references> </references>
<references title="Informational References"> <section anchor="Acknowledgements" numbered="false" toc="default">
<?rfc include='reference.RFC.3630'?> <name>Acknowledgements</name>
<t>This document leverages similar work done for IS-IS, and the
<?rfc include='reference.RFC.4203'?> authors of this document would like to acknowledge the contributions of
the authors of <xref target="RFC8668" format="default"/>.</t>
<?rfc include='reference.RFC.4655'?> <t>The authors would like to thank <contact fullname="Anoop Ghanwani"/>,
<contact fullname="Paul Kyzivat"/>, <contact fullname="Dan Romascanu"/>,
<?rfc include='reference.RFC.5329'?> and <contact fullname="Russ Mundy"/> for their review and feedback on
this document. The authors would also like to thank <contact
<?rfc include='reference.RFC.7471'?> fullname="Acee Lindem"/> for his detailed shepherd review of this
document. The authors would also like to thank <contact fullname="John
<?rfc include='reference.RFC.7752'?> Scudder"/> for his AD review and the discussion related to the
applicability of TLVs/sub-TLVs to the L2 Bundle Member Attributes sub-TLV.
<?rfc include='reference.RFC.8402'?> </t>
</section>
<?rfc include='reference.RFC.8510'?>
<?rfc include='reference.RFC.5709'?>
<?rfc include='reference.RFC.7474'?>
<?rfc include='reference.RFC.4552'?>
<?rfc include='reference.RFC.7166'?>
<?rfc include='reference.RFC.8668'?>
<?rfc include='reference.I-D.ietf-ospf-yang.xml'?>
</references>
</back> </back>
</rfc> </rfc>
 End of changes. 57 change blocks. 
393 lines changed or deleted 637 lines changed or added

This html diff was produced by rfcdiff 1.48.