rfc8668xml2.original.xml   rfc8668.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" number="8668"
<?rfc tocdepth="3"?> docName="draft-ietf-isis-l2bundles-07" category="std"
<?rfc tocindent="yes"?> submissionType="IETF" consensus="true" ipr="trust200902"
<?rfc symrefs="yes"?> tocInclude="true" symRefs="true" sortRefs="true"
<?rfc sortrefs="yes"?> xml:lang="en" version="3">
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-ietf-isis-l2bundles-07.txt"
ipr="trust200902">
<front> <front>
<title abbrev="isis-l2bundles">Advertising L2 Bundle Member Link <title abbrev="Advertising L2 Bundle Attributes in IS-IS">Advertising Layer 2 Bundle Member Link
Attributes in IS-IS</title> Attributes in IS-IS</title>
<seriesInfo name="RFC" value="8668"/>
<author fullname="Les Ginsberg" initials="L" surname="Ginsberg"> <author fullname="Les Ginsberg" initials="L" surname="Ginsberg" role="editor
<organization>Cisco Systems</organization> ">
<organization>Cisco Systems, Inc.</organization>
<address> <address>
<postal> <postal>
<street>510 McCarthy Blvd.</street> <street></street>
<city>Milpitas</city> <city></city>
<code>95035</code> <code></code>
<region>CA</region> <region></region>
<country>USA</country> <country></country>
</postal> </postal>
<email>ginsberg@cisco.com</email> <email>ginsberg@cisco.com</email>
</address> </address>
</author> </author>
<author fullname="Ahmed Bashandy" initials="A" surname="Bashandy"> <author fullname="Ahmed Bashandy" initials="A" surname="Bashandy">
<organization>Cisco Systems</organization> <organization>Unaffiliated</organization>
<address> <address>
<postal> <postal>
<street>170 West Tasman Drive</street>
<city>San Jose</city>
<code>95134</code> <country>United States of America</country>
<region>Ca</region>
<country>US</country>
</postal> </postal>
<email>abashandy.ietf@gmail.com
</email>
</address> </address>
</author> </author>
<author fullname="Clarence Filsfils" initials="C" surname="Filsfils"> <author fullname="Clarence Filsfils" initials="C" surname="Filsfils">
<organization>Cisco Systems</organization> <organization>Cisco Systems, Inc.</organization>
<address> <address>
<postal> <postal>
<street/> <street/>
<city/> <city/>
<code/> <code/>
<region/> <region/>
<country/> <country/>
</postal> </postal>
<email>cf@cisco.com</email> <email>cf@cisco.com</email>
</address> </address>
</author> </author>
<author fullname="Mohan Nanduri" initials="M" surname="Nanduri"> <author fullname="Mohan Nanduri" initials="M" surname="Nanduri">
<organization>eBay</organization> <organization>Oracle</organization>
<address> <address>
<postal> <postal>
<street/> <street/>
<city/> <city/>
<code/> <code/>
<country/> <country/>
</postal> </postal>
<email>mnanduri@ebay.com</email> <email>mohan.nanduri@oracle.com</email>
</address> </address>
</author> </author>
<author fullname="Ebben Aries" initials="E" surname="Aries"> <author fullname="Ebben Aries" initials="E" surname="Aries">
<organization>Private Contributer</organization> <organization>Arrcus Inc.</organization>
<address> <address>
<postal> <postal>
<street/> <street>2077 Gateway Place, Suite #400</street>
<city>San Jose</city>
<city/> <code>95119
</code>
<code/> <region>CA</region>
<country>United States of America
<country/> </country>
</postal> </postal>
<email>exa@dscp.org</email> <email>exa@arrcus.com</email>
</address> </address>
</author> </author>
<date day="25" month="May" year="2017"/> <date month="December" year="2019"/>
<area>Routing Area</area>
<workgroup>Networking Working Group</workgroup>
<keyword>Sample</keyword>
<abstract> <abstract>
<t>There are deployments where the Layer 3 interface on which IS-IS <t>There are deployments where the Layer 3 interface on which IS-IS
operates is a Layer 2 interface bundle. Existing IS-IS advertisements operates is a Layer 2 interface bundle. Existing IS-IS advertisements
only support advertising link attributes of the Layer 3 interface. If only support advertising link attributes of the Layer 3 interface. If
entities external to IS-IS wish to control traffic flows on the entities external to IS-IS wish to control traffic flows on the
individual physical links which comprise the Layer 2 interface bundle individual physical links that comprise the Layer 2 interface bundle,
link attribute information about the bundle members is required.</t> link attribute information about the bundle members is required.</t>
<t>This document introduces the ability for IS-IS to advertise the link <t>This document introduces the ability for IS-IS to advertise the link
attributes of layer 2 (L2) bundle members.</t> attributes of Layer 2 (L2) Bundle Members.</t>
</abstract> </abstract>
<note title="Requirements Language">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].</t>
</note>
</front> </front>
<middle> <middle>
<section title="Introduction"> <section>
<name>Introduction</name>
<t>There are deployments where the Layer 3 interface on which an IS-IS <t>There are deployments where the Layer 3 interface on which an IS-IS
adjacency is established is a Layer 2 interface bundle, for instance a adjacency is established is a Layer 2 interface bundle, for instance, a
Link Aggregation Group (LAG) [IEEE802.1AX]. This reduces the number of Link Aggregation Group (LAG) <xref target="IEEE802.1AX"/>. This reduces th
adjacencies which need to be maintained by the routing protocol in cases e number of
adjacencies that need to be maintained by the routing protocol in cases
where there are parallel links between the neighbors. Entities external where there are parallel links between the neighbors. Entities external
to IS-IS such as Path Computation Elements (PCE) [RFC4655] may wish to to IS-IS such as Path Computation Elements (PCEs) <xref target="RFC4655"/> may wish to
control traffic flows on individual members of the underlying Layer 2 control traffic flows on individual members of the underlying Layer 2
bundle. In order to do so link attribute information about individual bundle. In order to do so, link attribute information about individual
bundle members is required. The protocol extensions defined in this bundle members is required. The protocol extensions defined in this
document provide the means to advertise this information.</t> document provide the means to advertise this information.</t>
<t>This document introduces a new TLV to advertise link attribute <t>This document introduces a new TLV 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 Layer 3
interface on which IS-IS operates.</t> interface on which IS-IS operates.</t>
<t>[SR-ISIS] introduces a new link attribute - adjacency segment <t><xref target="RFC8667"/> introduces a new link attribute, adjacency seg
identifier (Adj-SID) - which can be used as an instruction to forwarding ment
identifier (Adj-SID), which can be used as an instruction to forwarding
to send traffic over a specific link. This document introduces to send traffic over a specific link. This document introduces
additional sub-TLVs to advertise Adj-SIDs for L2 Bundle members.</t> additional sub-TLVs to advertise Adj-SIDs for L2 Bundle Members.</t>
<t>Note that the new advertisements defined in this document are <t>Note that the new advertisements defined in this document are
intended to be provided to external (to IS-IS) entities. The following intended to be provided to external (to IS-IS) entities. The following
items are intentionally not defined and/or are outside the scope of this items are intentionally not defined and/or are outside the scope of this
document:</t> document:</t>
<t><list style="symbols"> <ul>
<t>What link attributes will be advertised. This is determined by <li>What link attributes will be advertised. This is determined by
the needs of the external entities.</t> the needs of the external entities.</li>
<t>A minimum or default set of link attributes.</t> <li>A minimum or default set of link attributes.</li>
<t>How these attributes are configured</t> <li>How these attributes are configured.</li>
<t>How the advertisements are used</t> <li>How the advertisements are used.</li>
<t>What impact the use of these advertisements may have on traffic <li>What impact the use of these advertisements may have on traffic
flow in the network</t> flow in the network.</li>
<t>How the advertisements are passed to external entities</t> <li>How the advertisements are passed to external entities.</li>
</list></t> </ul>
</section> </section>
<section title="L2 Bundle Member Attributes TLV"> <section>
<t>A new TLV is introduced to advertise L2 Bundle member attributes. <name>Requirements Language</name>
<t>
The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
IRED</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 anchor="BUNDLE">
<name>L2 Bundle Member Attributes TLV</name>
<t>A new TLV is introduced to advertise L2 Bundle Member attributes.
Although much of the information is identical to and uses the same Although much of the information is identical to and uses the same
sub-TLVs included in Extended IS-Neighbor advertisements (TLVs 22 and sub-TLVs included in Extended IS Neighbor advertisements (TLVs 22 and
222), a new TLV is used so that changes to the advertisement of the L2 222), a new TLV is used so that changes to the advertisement of the L2
Bundle member link attributes does not trigger unnecessary action by the Bundle Member link attributes do not trigger unnecessary action by the
[ISO10589] Decision process.</t> <xref target="ISO10589"/> Decision Process.</t>
<t>Advertisement of this information implies that the identified link is <t>Advertisement of this information implies that the identified link is
a member of the L2 Bundle associated with the identified Parent L3 a member of the L2 Bundle associated with the identified Parent L3
Neighbor and that the member link is operationally up. Therefore Neighbor and that the member link is operationally up. Therefore,
advertisements MUST be withdrawn if the link becomes operationally down advertisements <bcp14>MUST</bcp14> be withdrawn if the link becomes operat
ionally down
or it is no longer a member of the identified L2 Bundle.</t> or it is no longer a member of the identified L2 Bundle.</t>
<t>This new TLV utilizes the sub-TLV space defined for TLVs 22, 23, 141, <t>This new TLV utilizes the sub-TLV space defined for TLVs 22, 23, 141,
222, and 223.</t> 222, and 223.</t>
<t>The following new TLV is introduced:</t> <t>The following new TLV is introduced:</t>
<t><figure> <ul empty="true" spacing="normal">
<artwork><![CDATA[ L2 Bundle Member Attributes <li>L2 Bundle Member Attributes
Type: 25 (suggested - to be assigned by IANA) </li>
Length: Number of octets to follow <li>Type: 25
</li>
<li>Length: Number of octets to follow
</li>
Parent L3 Neighbor Descriptor </ul>
L3 Neighbor System ID + pseudonode ID (7 octets)
Flags: 1 octet field of following flags:
0 1 2 3 4 5 6 7 <ul empty="true" spacing="normal">
+-+-+-+-+-+-+-+-+ <li>Parent L3 Neighbor Descriptor
|P| | </li>
+-+-+-+-+-+-+-+-+ <li>
<ul empty="true">
<li>L3 Neighbor System ID + pseudonode ID (7 octets)
</li>
</ul>
<ul empty="true">
<li>
<dl spacing="compact">
<dt>Flags:</dt><dd>1-octet field of the following flags:</dd>
</dl>
</li>
</ul>
where: <ul empty="true"><li>
P-flag: When set to 1 one of the sub-TLVs described <ul empty="true" spacing="compact">
in Section 2.1 immediately follows the flags field. <li>
If the P-flag is set to 0, then none of the sub-TLVs
described in Section 2.1 are present.
Other bits: MUST be zero when originated and ignored when <artwork name="" type="" align="left" alt=""><![CDATA[ 0 1 2 3 4 5 6 7
received. +-+-+-+-+-+-+-+-+
|P| |
+-+-+-+-+-+-+-+-+]]></artwork>
One or more of the following: </li>
L2 Bundle Attribute Descriptors </ul>
Length of L2 Bundle Attribute Descriptor (1 octet)
NOTE: This includes all fields described below.
Number of L2 Bundle Member Descriptors (1 octet) <ul empty="true" spacing="compact">
L2 Bundle Member Link Local Identifiers <li>where:
(4 * Number of L2 Bundle Member Descriptors octets) </li>
</ul>
NOTE: An L2 Bundle Member Descriptor is a Link Local <ul empty="true" spacing="compact">
Identifier as defined in [RFC4202]. <li>
<dl spacing="compact" indent="9" ><dt>P-Flag:</dt><dd> When set to 1, one of the
sub-TLVs
described in <xref target="L3-adj" format="default"/> immediately follows the fl
ags field. If the P-Flag
is set to 0, then none of the sub-TLVs described in <xref target="L3-adj" format
="default"/> are
present.</dd>
</dl>
</li>
</ul>
sub-TLV(s) <ul empty="true">
<li>
<dl indent="9">
<dt>Other bits:</dt><dd><bcp14>MUST</bcp14> be zero when originated and ignored
when received.</dd>
</dl>
</li>
</ul>
A sub-TLV may define an attribute common to all of </li></ul>
the bundle members listed or a sub-TLV may define an
attribute unique to each bundle member. Use of these
two classes of sub-TLVs is described in the following
sections.
]]></artwork> </li>
</figure>NOTE: Only one Parent L3 Neighbor Descriptor is present in a </ul>
given TLV. Multiple L2 Bundle Attribute Descriptors may be present in a
single TLV.</t>
<section title="Parallel L3 Adjacencies"> <ul empty="true" spacing="compact">
<t>When there exist multiple L3 adjacencies to the same neighbor <li>One or more L2 Bundle Attribute Descriptors (as defined below).
</li>
</ul>
<ul empty="true" spacing="normal">
<li>
<ul empty="true" spacing="normal">
<li>Length of L2 Bundle Attribute Descriptor (1 octet)
</li>
<li>
<ul empty="true" spacing="normal">
<li>NOTE: This includes all fields described below.
</li>
</ul>
</li>
</ul>
</li>
<li>
<ul empty="true" spacing="normal">
<li>Number of L2 Bundle Member Descriptors (1 octet)
</li>
</ul>
</li>
<li>
<ul empty="true" spacing="normal">
<li>
L2 Bundle Member Link Local Identifiers&br; (4 * Number of L2
Bundle Member Descriptors octets)
</li>
</ul>
</li>
<li>
<ul empty="true" spacing="normal">
<li>
<ul empty="true" spacing="compact">
<li>NOTE: An L2 Bundle Member Descriptor is a Link Local
Identifier as defined in <xref target="RFC4202"/>.
</li>
</ul>
</li>
</ul>
</li>
<li>
<ul empty="true" spacing="normal">
<li>
Sub-TLV(s)&br;A sub-TLV may define an attribute common to all of the bundle
members listed, or it may define an attribute unique to each bundle member.
Use of these two classes of sub-TLVs is described in the following sections.
</li>
</ul>
</li>
</ul>
<ul empty="true">
<li>
<t>NOTE: Only one Parent L3 Neighbor Descriptor is present in a given
TLV. Multiple L2 Bundle Attribute Descriptors may be present in a single
TLV.</t>
</li>
</ul>
<section anchor="L3-adj">
<name>Parallel L3 Adjacencies</name>
<t>When there exist multiple L3 adjacencies to the same neighbor,
additional information is required to uniquely identify the L3 additional information is required to uniquely identify the L3
Neighbor. One and only one of the following three sub-TLVs is used to Neighbor. One and only one of the following three sub-TLVs is used to
uniquely identify the L3 adjacency:</t> uniquely identify the L3 adjacency:</t>
<t><list style="symbols"> <ul>
<t>IPv4 Interface Address (sub-TLV 6 defined in [RFC5305])</t> <li>IPv4 Interface Address (sub-TLV 6 defined in <xref target="RFC53
05"/>)</li>
<t>IPv6 Interface Address (sub-TLV 12 defined in [RFC6119])</t> <li>IPv6 Interface Address (sub-TLV 12 defined in <xref target="RFC6 119"/>)</li>
<t>Link Local/Remote Identifiers (sub-TLV 4 defined in <li>Link Local/Remote Identifiers (sub-TLV 4 defined in
[RFC5307])</t> <xref target="RFC5307"/>)</li>
</list></t> </ul>
<t>When the P-bit is set in the flags field in the Parent L3 Neighbor <t>When the P-Flag is set in the flags field in the Parent L3 Neighbor
Descriptor one and only one of the above sub-TLVs MUST be present. The Descriptor, one and only one of the above sub-TLVs <bcp14>MUST</bcp14> b
chosen sub-TLV MUST immediately follow the flags field described in e present. The
Section 2.</t> chosen sub-TLV <bcp14>MUST</bcp14> immediately follow the flags field de
scribed in
<xref target="BUNDLE" />.</t>
<t>These sub-TLVs MAY be omitted if no parallel adjacencies to the <t>These sub-TLVs <bcp14>MAY</bcp14> be omitted if no parallel adjacenci es to the
neighbor exist.</t> neighbor exist.</t>
</section> </section>
<section title="Shared Attribute sub-TLVs"> <section>
<t>These sub-TLVs advertise a single copy of an attribute (e.g. link <name>Shared Attribute Sub-TLVs</name>
<t>These sub-TLVs advertise a single copy of an attribute (e.g., link
bandwidth). The attribute applies to all of the L2 Bundle Members in bandwidth). The attribute applies to all of the L2 Bundle Members in
the set advertised under the preceding &nbsp;L2 Bundle Member the set advertised under the preceding&nbsp;L2 Bundle Member
Attribute Descriptor. No more than one copy of a given sub-TLV in this Attribute Descriptor. No more than one copy of a given sub-TLV in this
category may appear in the set of sub-TLVs under the preceding L2 category may appear in the set of sub-TLVs under the preceding L2
Bundle Member Attribute Descriptor. If multiple copies of a given Bundle Member Attribute Descriptor. If multiple copies of a given
sub-TLV are present all copies MUST be ignored.</t> sub-TLV are present, all copies <bcp14>MUST</bcp14> be ignored.</t>
<t>The set of L2 Bundle Member Descriptors which may be advertised <t>The set of L2 Bundle Member Descriptors that may be advertised
under a single L2 Bundle Member Attribute Descriptor is therefore under a single L2 Bundle Member Attribute Descriptor is therefore
limited to bundle members which share the set of attributes advertised limited to bundle members that share the set of attributes advertised
in the shared attribute sub-TLVs.</t> in the shared attribute sub-TLVs.</t>
<t>All existing sub-TLVs defined in the IANA Sub-TLVs for TLVs 22, 23, <t>All existing sub-TLVs defined in the IANA registry for Sub-TLVs for T
141, 222, and 223 registry are in the category of shared attribute LVs 22, 23,
141, 222, and 223 are in the category of shared attribute
sub-TLVs unless otherwise specified in this document.</t> sub-TLVs unless otherwise specified in this document.</t>
</section> </section>
</section> </section>
<section title="Advertising L2 Bundle Member Adj-SIDs"> <section>
<t>[SR-ISIS] defines sub-TLVs to advertise Adj-SIDs for L3 adjacencies. <name>Advertising L2 Bundle Member Adj-SIDs</name>
However these sub-TLVs only support a advertisement of a single Adj-SID. <t><xref target="RFC8667"/> defines sub-TLVs to advertise Adj-SIDs for L3
As it is expected that each L2 Bundle member will have unique Adj-SIDs adjacencies.
in many deployments it is desirable to define a new sub-TLV which allows However, these sub-TLVs only support the advertisement of a single Adj-SID
.
As it is expected that each L2 Bundle Member will have unique Adj-SIDs
in many deployments, it is desirable to define a new sub-TLV that allows
more efficient encoding of a set of Adj-SIDs in a single sub-TLV. Two more efficient encoding of a set of Adj-SIDs in a single sub-TLV. Two
new sub-TLVs are therefore introduced to support advertising Adj-SIDs new sub-TLVs are therefore introduced to support advertising Adj-SIDs
for L2 Bundle members. The format of the new sub-TLVs is similar to that for L2 Bundle Members. The format of the new sub-TLVs is similar to that
used for L3 adjacencies, but is optimized to allow advertisement of a used for L3 adjacencies, but it is optimized to allow advertisement of a
set of Adj-SIDs (one per L2 Bundle Member) in a single sub-TLV.</t> set of Adj-SIDs (one per L2 Bundle Member) in a single sub-TLV.</t>
<t>The two new sub-TLVs defined in the following sections do not fall <t>The two new sub-TLVs defined in the following sections do not fall
into the category of shared attribute sub-TLVs.</t> into the category of shared attribute sub-TLVs.</t>
<section title="L2 Bundle Member Adjacency Segment Identifier sub-TLV"> <section>
<name>L2 Bundle Member Adjacency Segment Identifier Sub-TLV</name>
<t>This sub-TLV is used to advertise Adj-SIDs for L2 Bundle Members <t>This sub-TLV is used to advertise Adj-SIDs for L2 Bundle Members
associated with a parent L3 adjacency which is Point-to-Point. The associated with a parent L3 adjacency that is point-to-point. The
following format is defined for this sub-TLV:</t> following format is defined for this sub-TLV:</t>
<t><figure> <ul empty="true">
<artwork><![CDATA[ Type: 41 (suggested value to be assigned by I <li>
ANA) (1 octet) <dl>
Length: variable (1 octet) <dt>Type:</dt>
<dd>41 (1 octet)</dd>
<dt>Length:</dt>
<dd>variable (1 octet)</dd>
<dt>Flags:</dt>
<dd>1-octet field of the following flags:</dd>
</dl>
Flags: 1 octet field of following flags: <ul empty="true"><li>
<artwork name="" type="" align="left" alt=""><![CDATA[ 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|F|*|V|L|S|P| |
+-+-+-+-+-+-+-+-+]]></artwork>
</li>
0 1 2 3 4 5 6 7 <li><t>where:</t>
+-+-+-+-+-+-+-+-+ <dl indent="9">
|F|*|V|L|S|P| | <dt>F-Flag:</dt><dd>Address-Family Flag. If unset, then the Adj-SID refers to
+-+-+-+-+-+-+-+-+ an L2 Bundle Member with outgoing IPv4 encapsulation. If set, then the
Adj-SID refers to an L2 Bundle Member with outgoing IPv6 encapsulation.</dd>
<dt>V-Flag:</dt><dd>Value Flag. If set, then the Adj-SID carries a value. By
default, the flag is SET.</dd>
<dt>L-Flag:</dt><dd>Local Flag. If set, then the value/index carried by the
Adj-SID has local significance. By default, the flag is SET.</dd>
<dt>S-Flag:</dt><dd>Set Flag. When set, the S-Flag indicates that the Adj-SID
refers to a set of L2 Bundle Members (and therefore <bcp14>MAY</bcp14> be assign
ed to other
L2 Bundle Members as well).</dd>
<dt>P-Flag:</dt><dd>Persistent Flag. When set, the P-Flag indicates that the
Adj-SID is persistently allocated, i.e., the Adj-SID value remains consistent
across router restart and/or interface flap.</dd>
<dt>Other bits:</dt><dd><bcp14>MUST</bcp14> be zero when originated and ignored
when
received.</dd>
</dl>
</li>
where: <li>
<t>NOTE: The flags are deliberately kept congruent to the flags in
the L3 ADJ-SID defined in <xref target="RFC8667"></xref>. * indicates a flag us
ed in the L3
Adj-SID sub-TLV, but one that is NOT used in this sub-TLV. These bits <bcp14>SH
OULD</bcp14>
be sent as 0 and <bcp14>MUST</bcp14> be ignored on receipt.</t>
</li>
NOTE: The flags are deliberately kept congruent to the flags </ul>
in the L3 ADJ-SID defined in [SR-ISIS]. </li>
* indicates a flag used in the L3 Adj-SID sub-TLV but which is
NOT used in this sub-TLV. These bits SHOULD be sent as 0 and
MUST be ignored on receipt.
F-Flag: Address-Family flag. If unset, then the Adj-SID refers <li>
to an L2 Bundle Member with outgoing IPv4 encapsulation. If set <dl indent="9">
then the Adj-SID refers to an L2 Bundle Member with outgoing <dt>Weight:
IPv6 encapsulation. </dt>
<dd>1 octet. The value represents the weight of the Adj-SID for the purpose
of load balancing. The use of the weight is defined in <xref target="RFC8402"><
/xref>.
</dd>
</dl>
</li>
V-Flag: Value flag. If set, then the Adj-SID carries a value. <li>
By default the flag is SET. NOTE: Flags and weight are shared by all L2 Bundle Members listed in the L2
Bundle Attribute Descriptor.
</li>
L-Flag: Local Flag. If set, then the value/index carried by <li>
the Adj-SID has local significance. By default the flag is <dl newline="true" indent="3">
SET. <dt>L2 Bundle Member Adj-SID Descriptors:</dt>
<dd>There <bcp14>MUST</bcp14> be one descriptor for each of the L2 Bundle Member
s advertised
under the preceding L2 Bundle Member Attribute Descriptor. Each descriptor
consists of one of the following fields:</dd>
</dl>
</li>
S-Flag. Set Flag. When set, the S-Flag indicates that the <li>
Adj-SID refers to a set of L2 Bundle Members (and therefore <ul empty="true">
MAY be assigned to other L2 Bundle Members as well). <li>
<dl indent="0">
<dt>SID/Index/Label:</dt>
<dd>According to the V- and L-Flags, it contains either:</dd>
</dl>
</li>
<li>
<ul>
<li>A 3-octet local label where the 20 rightmost bits are used for encoding
the label value. In this case, the V- and L-Flags <bcp14>MUST</bcp14> be set.
</li>
<li> A 4-octet index defining the offset in the SID/Label space advertised by
this router. See <xref target="RFC8667"/>. In this case, V- and L-Flags <bcp14>M
UST</bcp14> be unset.
</li>
</ul>
</li>
</ul>
</li>
P-Flag. Persistent flag. When set, the P-Flag indicates that </ul>
the Adj-SID is persistently allocated, i.e., the Adj-SID value
remains consistent across router restart and/or interface flap.
Other bits: MUST be zero when originated and ignored when </section>
received.
Weight: 1 octet. The value represents the weight of the Adj-SID <section>
for the purpose of load balancing. The use of the weight is <name>L2 Bundle Member LAN Adjacency SID Sub-TLV</name>
defined in [SR-ARCH]. <t>This sub-TLV is used to advertise Adj-SIDs for L2 Bundle Members
associated with a parent L3 adjacency that is a LAN adjacency. In LAN
subnetworks, the Designated Intermediate System (DIS) is elected and
originates the Pseudonode-LSP (PN-LSP) including all neighbors of the
DIS. When Segment Routing is used, each router in the LAN <bcp14>MAY</bc
p14>
advertise the Adj-SID of each of its neighbors on the LAN. Similarly,
for each L2 Bundle Member, a router <bcp14>MAY</bcp14> advertise an Adj-
SID to each
neighbor on the LAN.</t>
NOTE: Flags and weight are shared by all L2 Bundle Members <t>The following format is defined for this sub-TLV:</t>
listed in the L2 Bundle Attribute Descriptor.
L2 Bundle Member Adj-SID Descriptors. There MUST be one descriptor <ul empty="true">
for each of the L2 Bundle Members advertised under the preceding <li>
L2 Bundle Member Attribute Descriptor. Each descriptor consists <dl indent="0">
of one of the following fields: <dt>Type:</dt>
<dd>42 (1 octet)</dd>
<dt>Length:</dt>
<dd>variable (1 octet)</dd>
<dt>Neighbor System ID:</dt>
<dd>6 octets</dd>
<dt>Flags:</dt>
<dd>1-octet field of the following flags:</dd>
</dl>
<ul empty="true"><li>
<artwork name="" type="" align="left" alt=""><![CDATA[ 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|F|*|V|L|S|P| |
+-+-+-+-+-+-+-+-+]]></artwork>
</li>
SID/Index/Label: according to the V and L flags, it contains <li><t>where:</t>
either: <dl indent="9">
<dt>F-Flag:</dt><dd>Address-Family Flag. If unset, then the Adj-SID refers to
an L2 Bundle Member with outgoing IPv4 encapsulation. If set, then the
Adj-SID refers to an L2 Bundle Member with outgoing IPv6 encapsulation.</dd>
<dt>V-Flag:</dt>
<dd>Value Flag. If set, then the Adj-SID carries a value. By default, the
flag is SET.</dd>
<dt>L-Flag:</dt>
<dd>Local Flag. If set, then the value/index carried by the Adj-SID has local
significance. By default, the flag is SET.</dd>
* A 3 octet local label where the 20 rightmost bits are used <dt>S-Flag:</dt>
for encoding the label value. In this case the V and L <dd>Set Flag. When set, the S-Flag indicates that the Adj-SID refers to a set
flags MUST be set. of L2 Bundle Members (and therefore <bcp14>MAY</bcp14> be assigned to other L2 B
undle Members
as well).</dd>
* A 4 octet index defining the offset in the SID/Label space <dt>P-Flag:</dt>
advertised by this router. See [SR-ISIS]. <dd>Persistent Flag. When set, the P-Flag indicates that the Adj-SID is
In this case V and L flags MUST be unset. persistently allocated, i.e., the Adj-SID value remains consistent across
router restart and/or interface flap.</dd>
<dt>Other bits:</dt><dd><bcp14>MUST</bcp14> be zero when originated and ignored
when
received.</dd>
</dl>
</li>
]]></artwork> <li><t>NOTE: The flags are deliberately kept congruent to the flags in the L3
</figure></t> LAN Adjacency SID defined in <xref target="RFC8667"/>. * indicates a flag used
</section> in the L3 Adj-SID
sub-TLV, but one that is NOT used in this sub-TLV. These bits <bcp14>SHOULD</bc
p14> be sent
as 0 and <bcp14>MUST</bcp14> be ignored on receipt.</t>
</li>
<section title="L2 Bundle Member LAN Adjacency Segment Identifier sub-TLV" </ul>
> </li>
<t>This sub-TLV is used to advertise Adj-SIDs for L2 Bundle Members
associated with a parent L3 adjacency which is a LAN adjacency. In LAN
subnetworks, the Designated Intermediate System (DIS) is elected and
originates the Pseudonode-LSP (PN-LSP) including all neighbors of the
DIS. When Segment Routing is used, each router in the LAN MAY
advertise the Adj-SID of each of its neighbors on the LAN. Similarly,
for each L2 Bundle Member a router MAY advertise an Adj-SID to each
neighbor on the LAN.</t>
<t>The following format is defined for this sub-TLV:</t> <li>
<dl indent="9">
<dt>Weight:</dt>
<dd>1 octet. The value represents the weight of the Adj-SID for the purpose
of load balancing. The use of the weight is defined in
<xref target="RFC8402"></xref>.</dd>
</dl>
</li>
<t><figure> <li>
<artwork><![CDATA[ Type: 42 (suggested value to be assigned by I NOTE: Flags and weight are shared by all L2 Bundle Members listed in the L2
ANA) (1 octet) Bundle Attribute Descriptor.
Length: variable (1 octet) </li>
Neighbor System ID: 6 octets
Flags: 1 octet field of following flags: <li>
<dl newline="true" indent="3">
<dt>L2 Bundle Member LAN Adjacency SID Descriptors:</dt>
<dd>There <bcp14>MUST</bcp14> be one descriptor for each of the L2 Bundle Member
s advertised
under the preceding L2 Bundle Member Attribute Descriptor. Each descriptor
consists of one of the following fields:</dd>
</dl>
</li>
0 1 2 3 4 5 6 7 <li>
+-+-+-+-+-+-+-+-+ <ul empty="true">
|F|*|V|L|S|P| | <li>
+-+-+-+-+-+-+-+-+ <dl indent="0">
<dt>SID/Index/Label:</dt>
<dd>According to the V- and L-Flags, it contains either:</dd>
</dl>
</li>
<li>
<ul>
<li>A 3-octet local label where the 20 rightmost bits are used for encoding
the label value. In this case, the V- and L-Flags <bcp14>MUST</bcp14> be set.</
li>
<li> A 4-octet index defining the offset in the SID/Label space advertised by
this router. See <xref target="RFC8667"/>. In this case, V- and L-Flags
<bcp14>MUST</bcp14> be unset. </li>
</ul>
</li>
</ul>
</li>
where: </ul>
NOTE: The flags are deliberately kept congruent to the flags </section>
in the L3 LAN_ADJ-SID defined in [SR-ISIS].
* indicates a flag used in the L3 Adj-SID sub-TLV but which is
NOT used in this sub-TLV. These bits SHOULD be sent as 0 and
MUST be ignored on receipt.
F-Flag: Address-Family flag. If unset, then the Adj-SID refers </section>
to an L2 Bundle Member with outgoing IPv4 encapsulation. If set
then the Adj-SID refers to an L2 Bundle Member with outgoing
IPv6 encapsulation.
V-Flag: Value flag. If set, then the Adj-SID carries a value. <section anchor="IANA">
By default the flag is SET. <name>IANA Considerations</name>
<t>This document adds the following new TLV to the IS-IS "TLV Codepoints
Registry".</t>
L-Flag: Local Flag. If set, then the value/index carried by <dl>
the Adj-SID has local significance. By default the flag is <dt>Value:</dt><dd>25</dd>
SET. <dt>Name:</dt><dd>L2 Bundle Member Attributes</dd>
</dl>
<t>The name of the IANA registry for Sub-TLVs for TLVs 22, 23, 141, 222, a
nd 223
has been changed to include sub-TLV 25. An additional column has been adde
d to the registry to
indicate which sub-TLVs may appear in the new L2 Bundle Member
Attributes TLV. The column for TLV 25 has one of the following three
values:</t>
S-Flag. Set Flag. When set, the S-Flag indicates that the <dl indent="6">
Adj-SID refers to a set of L2 Bundle Members (and therefore <dt>y</dt><dd>sub-TLV may appear in TLV 25 but <bcp14>MUST
MAY be assigned to other L2 Bundle Members as well). NOT</bcp14> be shared by multiple L2 Bundle Members</dd>
<dt>y(s)</dt><dd>sub-TLV may appear in TLV 25 and <bcp14>MAY</bcp14>
be shared by multiple L2 Bundle Members</dd>
<dt>n</dt><dd>sub-TLV <bcp14>MUST NOT</bcp14> appear in TLV 25</dd>
</dl>
P-Flag. Persistent flag. When set, the P-Flag indicates that <t>The following table indicates the appropriate settings for all
the Adj-SID is persistently allocated, i.e., the Adj-SID value currently defined sub-TLVs with regard to their use in the new L2 Bundle
remains consistent across router restart and/or interface flap. Member Attributes TLV.</t>
Other bits: MUST be zero when originated and ignored when <table anchor="table1">
received. <thead>
<tr>
<th align='left'>Value</th>
<th align='left'>Description</th>
<th align='left'>TLV 25</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">3</td>
<td align="left">Administrative group (color)</td>
<td align="left">y(s)</td>
</tr>
Weight: 1 octet. The value represents the weight of the Adj-SID <tr>
for the purpose of load balancing. The use of the weight is <td align="left">4</td>
defined in [SR-ARCH]. <td align="left">Link Local/Remote Identifiers</td>
<td align="left">y(s)</td>
</tr>
NOTE: Flags and weight are shared by all L2 Bundle Members <tr>
listed in the L2 Bundle Attribute Descriptor. <td align="left">6</td>
<td align="left">IPv4 interface address</td>
<td align="left">y(s)</td>
</tr>
L2 Bundle Member LAN Adj-SID Descriptors. There MUST be one <tr>
descriptor for each of the L2 Bundle Members advertised <td align="left">8</td>
under the preceding L2 Bundle Member Attribute Descriptor. <td align="left">IPv4 neighbor address</td>
Each descriptor consists of one of the following fields: <td align="left">y(s)</td>
</tr>
SID/Index/Label: according to the V and L flags, it contains <tr>
either: <td align="left">9</td>
<td align="left">Maximum link bandwidth</td>
<td align="left">y(s)</td>
</tr>
* A 3 octet local label where the 20 rightmost bits are used <tr>
for encoding the label value. In this case the V and L <td align="left">10</td>
flags MUST be set. <td align="left">Maximum reservable link bandwidth</td>
<td align="left">y(s)</td>
</tr>
* A 4 octet index defining the offset in the SID/Label space <tr>
advertised by this router. See [SR-ISIS]. <td align="left">11</td>
In this case V and L flags MUST be unset. <td align="left">Unreserved bandwidth</td>
<td align="left">y(s)</td>
</tr>
]]></artwork> <tr>
</figure></t> <td align="left">12</td>
</section> <td align="left">IPv6 Interface Address</td>
</section> <td align="left">y(s)</td>
</tr>
<section anchor="IANA" title="IANA Considerations"> <tr>
<t>This document adds the following new TLV to the IS-IS TLV Codepoints <td align="left">13</td>
registry.</t> <td align="left">IPv6 Neighbor Address</td>
<td align="left">y(s)</td>
</tr>
<t>Value: 25 (suggested - to be assigned by IANA)</t> <tr>
<td align="left">14</td>
<td align="left">Extended Administrative Group</td>
<td align="left">y(s)</td>
</tr>
<t>Name: L2 Bundle Member Attributes</t> <tr>
<td align="left">18</td>
<td align="left">TE Default metric</td>
<td align="left">y(s)</td>
</tr>
<t>The name of the Sub-TLVs for TLVs 22, 23, 141, 222, and 223 registry <tr>
needs to be changed to Sub-TLVs for TLVs 22, 23, 25, 141, 222, and 223 <td align="left">19</td>
registry. An additional column needs to be added to the registry to <td align="left">Link-attributes</td>
indicate which sub-TLVs may appear in the new L2 Bundle Member <td align="left">y(s)</td>
Attributes TLV. The column for TLV 25 has one of the following three </tr>
values:</t>
<t><figure> <tr>
<artwork><![CDATA[y - sub-TLV may appear in TLV 25 but MUST NOT be sha <td align="left">20</td>
red by multiple <td align="left">Link Protection Type</td>
L2 Bundle Members <td align="left">y(s)</td>
y(s) - sub-TLV may appear in TLV 25 and MAY be shared by multiple </tr>
L2 Bundle Members
n - sub-TLV MUST NOT appear in TLV 25]]></artwork>
</figure></t>
<t>The following table indicates the appropriate settings for all <tr>
currently defined sub-TLVs as regards their use in the new L2 Bundle <td align="left">21</td>
Member Attributes TLV.</t> <td align="left">Interface Switching Capability Descriptor</td>
<td align="left">y(s)</td>
</tr>
<t><figure> <tr>
<artwork><![CDATA[ 3 Administrative group (color) y(s) <td align="left">22</td>
4 Link Local/Remote Identifiers y(s) <td align="left">Bandwidth Constraints</td>
6 IPv4 interface address y(s) <td align="left">y(s)</td>
8 IPv4 neighbor address y(s) </tr>
9 Maximum link bandwidth y(s)
10 Maximum reservable link bandwidth y(s)
11 Unreserved bandwidth y(s)
12 IPv6 Interface Address y(s)
13 IPv6 Neighbor Address y(s)
14 Extended Administrative Group y(s)
18 TE Default metric y(s)
19 Link-attributes y(s)
20 Link Protection Type y(s)
21 Interface Switching Capability Descriptor y(s)
22 Bandwidth Constraints y(s)
23 Unconstrained TE LSP Count y(s)
24 Remote AS number n
25 IPv4 remote ASBR Identifier n
26 IPv6 remote ASBR Identifier n
27 Interface Adjustment Capability Descriptor (IACD) y(s)
28 MTU n
29 SPB-Metric y(s)
30 SPB-A-OALG y(s)
33 Unidirectional Link Delay y
34 Min/Max Unidirectional Link Delay y
35 Unidirectional Delay Variation y
36 Unidirectional Link Loss y
37 Unidirectional Residual Bandwidth y
38 Unidirectional Available Bandwidth y
39 Unidirectional Utilized Bandwidth y
40 RTM Capability n
]]></artwork> <tr>
</figure></t> <td align="left">23</td>
<td align="left">Unconstrained TE LSP Count (sub-)TLV</td>
<td align="left">y(s)</td>
</tr>
<t>This document adds the following new sub-TLVs to the sub-TLVs for <tr>
TLVs 22, 23, 25, 141, 222, and 223 registry.</t> <td align="left">24</td>
<td align="left">remote AS number</td>
<td align="left">n</td>
</tr>
<t>Value: 41 (suggested - to be assigned by IANA)</t> <tr>
<td align="left">25</td>
<td align="left">IPv4 remote ASBR Identifier</td>
<td align="left">n</td>
</tr>
<t>Name: L2 Bundle Member Adj-SID</t> <tr>
<td align="left">26</td>
<td align="left">IPv6 remote ASBR Identifier</td>
<td align="left">n</td>
</tr>
<t>This sub-TLV is allowed in the following TLVs:</t> <tr>
<td align="left">27</td>
<td align="left">Interface Adjustment Capability Descriptor (IACD)</td>
<td align="left">y(s)</td>
</tr>
<t><figure> <tr>
<artwork><![CDATA[ 22 23 25 141 222 223 <td align="left">28</td>
n n y n n n <td align="left">MTU</td>
]]></artwork> <td align="left">n</td>
</figure></t> </tr>
<t>Value: 42 (suggested to be assigned by IANA)</t> <tr>
<td align="left">29</td>
<td align="left">SPB-Metric</td>
<td align="left">y(s)</td>
</tr>
<t>Name: L2 Bundle Member LAN Adj-SID</t> <tr>
<td align="left">30</td>
<td align="left">SPB-A-OALG</td>
<td align="left">y(s)</td>
</tr>
<t>This sub-TLV is allowed in the following TLVs:</t> <tr>
<td align="left">33</td>
<td align="left">Unidirectional Link Delay</td>
<td align="left">y</td>
</tr>
<tr>
<td align="left">34</td>
<td align="left">Min/Max Unidirectional Link Delay</td>
<td align="left">y</td>
</tr>
<tr>
<td align="left">35</td>
<td align="left">Unidirectional Delay Variation</td>
<td align="left">y</td>
</tr>
<tr>
<td align="left">36</td>
<td align="left">Unidirectional Link Loss</td>
<td align="left">y</td>
</tr>
<tr>
<td align="left">37</td>
<td align="left">Unidirectional Residual Bandwidth</td>
<td align="left">y</td>
</tr>
<tr>
<td align="left">38</td>
<td align="left">Unidirectional Available Bandwidth</td>
<td align="left">y</td>
</tr>
<tr>
<td align="left">39</td>
<td align="left">Unidirectional Utilized Bandwidth</td>
<td align="left">y</td>
</tr>
<tr>
<td align="left">40</td>
<td align="left">RTM Capability</td>
<td align="left">n</td>
</tr>
</tbody>
</table>
<t>This document adds the following new sub-TLVs to the above registry.</t
>
<table anchor="iana-table" align="center">
<thead>
<tr>
<th align='center'>Type</th>
<th align='left'>Description</th>
<th align='center'>22</th>
<th align='center'>23</th>
<th align='center'>25</th>
<th align='center'>141</th>
<th align='center'>222</th>
<th align='center'>223</th>
</tr>
</thead>
<tbody>
<tr>
<td align='center'>41</td>
<td align='left'>L2 Bundle Member Adj-SID</td>
<td align="center">n</td>
<td align="center">n</td>
<td align="center">y</td>
<td align="center">n</td>
<td align="center">n</td>
<td align="center">n</td>
</tr>
<tr>
<td align='center'>42</td>
<td align='left'>L2 Bundle Member LAN Adj-SID</td>
<td align="center">n</td>
<td align="center">n</td>
<td align="center">y</td>
<td align="center">n</td>
<td align="center">n</td>
<td align="center">n</td>
</tr>
</tbody>
</table>
<t><figure>
<artwork><![CDATA[ 22 23 25 141 222 223
n n y n n n
]]></artwork>
</figure></t>
</section> </section>
<section anchor="Security" title="Security Considerations"> <section>
<name>Security Considerations</name>
<t>The IS-IS protocol has supported the advertisement of link attribute <t>The IS-IS 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 existing
advertisements defined in [RFC4202], [RFC5305], [RFC7810], and [SR-ISIS] advertisements defined in <xref target="RFC4202"/>, <xref
- but are associated with L2 links which are part of a bundle interface target="RFC5305"/>, <xref target="RFC8570"/>, and <xref
target="RFC8667"/>, but are associated with L2 links that are part of a bu
ndle interface
on which the IS-IS protocol operates. There are therefore no new on which the IS-IS protocol operates. There are therefore no new
security issues introduced by the extensions in this document.</t> 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 IS-IS PDUs are sent unauthorized access to the physical links on which IS-IS Protocol Data
occurs then attacks are possible. The use of authentication as defined Units (PDUs) are sent occurs, then attacks are possible. The use of
in [RFC5304] and [RFC5310] is recommended to prevent such attacks.</t> authentication as defined in <xref target="RFC5304"/> and <xref
</section> target="RFC5310"/> is recommended to prevent such attacks.</t>
<section title="Contributors">
<t>The following people gave a substantial contribution to the content
of this document and should be considered as co-authors:</t>
<t><figure>
<artwork><![CDATA[Stefano Previdi
Cisco Systems
Via Del Serafico 200
Rome 0144
Italy
Email: sprevidi@cisco.com]]></artwork>
</figure></t>
</section> </section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>The authors would like to thank Jon Mitchell for his careful
review.</t>
</section>
</middle> </middle>
<back> <back>
<references title="Normative References"> <references>
<name>References</name>
<references>
<name>Normative References</name>
<reference anchor="ISO10589"> <reference anchor="ISO10589">
<front> <front>
<title>Intermediate system to Intermediate system intra-domain <title>Information technology -- Telecommunications and information
routeing information exchange protocol for use in conjunction with exchange between systems -- Intermediate System to Intermediate
the protocol for providing the connectionless-mode Network Service System intra-domain routeing information exchange protocol for use
(ISO 8473)</title> in conjunction with the protocol for providing the
connectionless-mode network service (ISO 8473)</title>
<author> <author>
<organization abbrev="ISO">International Organization for <organization abbrev="ISO">International Organization for
Standardization</organization> Standardization</organization>
</author> </author>
<date month="November" year="2002"/>
<date month="Nov" year="2002"/>
</front> </front>
<seriesInfo name="ISO/IEC" value="10589:2002, Second Edition"/> <seriesInfo name="ISO/IEC" value="10589:2002, Second Edition"/>
</reference> </reference>
<reference anchor="IEEE802.1AX"> <reference anchor="IEEE802.1AX" target="https://ieeexplore.ieee.org/docume nt/7055197">
<front> <front>
<title>IEEE Standard for Local and Metropolitan Area Networks - Link <title>IEEE Standard for Local and metropolitan area networks -- Link
Aggregation.</title> Aggregation</title>
<author> <author>
<organization abbrev="IEEE">Institute of Electrical and <organization abbrev="IEEE">IEEE</organization>
Electronics Engineers</organization>
</author> </author>
<date month="Nov" year="2008"/>
</front>
</reference>
<reference anchor="SR-ISIS">
<front>
<title>IS-IS Extensions for Segment Routing,
draft-ietf-isis-segment-routing-extensions-12(work in
progress)</title>
<author fullname="Previdi S., et al,"/>
<date month="April" year="2017"/>
</front> </front>
<seriesInfo name="IEEE" value="802.1AX"/>
</reference> </reference>
<?rfc include="reference.RFC.2119"?> <!-- draft-ietf-isis-segment-routing-extensions-25: Companion document -->
<reference anchor='RFC8667' target='https://www.rfc-editor.org/info/rfc8667'>
<front>
<title>IS-IS Extensions for Segment Routing</title>
<author initials='S' surname='Previdi' fullname='Stefano Previdi' role='editor'>
<organization/></author>
<author initials='L' surname='Ginsburg' fullname='Les Ginsburg' role='editor'><o
rganization /></author>
<author initials='C' surname='Filsfils' fullname='Clarence Filsfils'><organizati
on /></author>
<author initials='A' surname='Bashandy' fullname='Ahmed Bashandy'><organization
/></author>
<author initials='H' surname='Gredler' fullname='Hannes Gredler'><organization /
></author>
<author initials='B' surname='Decraene' fullname='Bruno Decraene'><organization
/></author>
<date year='2019' month='December'/>
</front>
<seriesInfo name='RFC' value='8667'/>
<seriesInfo name='DOI' value='10.17487/RFC8667'/>
</reference>
<?rfc include='reference.RFC.4202'?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4202.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5304.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5305.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5307.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5310.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6119.
xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8570.
xml"/>
</references>
<?rfc include='reference.RFC.5304'?> <references>
<name>Informative References</name>
<?rfc include='reference.RFC.5305'?> <reference anchor='RFC4655' target='https://www.rfc-editor.org/info/rfc4655'>
<front>
<title>A Path Computation Element (PCE)-Based Architecture</title>
<author initials='A.' surname='Farrel' fullname='A. Farrel'><organization /></au
thor>
<author initials='JP.' surname='Vasseur' fullname='JP. Vasseur'><organization />
</author>
<author initials='J.' surname='Ash' fullname='J. Ash'><organization /></author>
<date year='2006' month='August' />
</front>
<seriesInfo name='RFC' value='4655'/>
<seriesInfo name='DOI' value='10.17487/RFC4655'/>
</reference>
<?rfc include='reference.RFC.5307'?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8402.
xml"/>
</references>
</references>
<?rfc include='reference.RFC.5310'?> <section>
<name>Example Encoding</name>
<?rfc include='reference.RFC.6119'?> <t>Below is an example encoding of L2 Bundle advertisements in a case
where we have two parallel adjacencies to the same neighbor whose
system-id is 1234.1234.1234.00. The two L2 bundles have the following
sets of attributes:</t>
<?rfc include='reference.RFC.7810'?> <t>L3 Adjacency #1</t>
</references> <t>L3 IPv4 local link address: 192.0.2.1</t>
<t>Four bundle members with the following attributes:</t>
<references title="Informational References"> <table anchor="Adj1">
<?rfc include='reference.RFC.4655'?> <thead>
<tr>
<th align='center'>Num</th>
<th align='center'>Link Local ID</th>
<th align='center'>Bandwidth</th>
<th align='center'>Adj-SID/Weight</th>
</tr>
</thead>
<reference anchor="SR-ARCH"> <tbody>
<front> <tr>
<title>Segment Routing Architecture, <td align="center">1</td>
draft-ietf-spring-segment-routing-11(work in progress)</title> <td align="center">0x11111111</td>
<td align="center">1G</td>
<td align="center">0x11111/1 </td>
</tr>
<author fullname="Filsfils C., et al,"/> <tr>
<td align="center">2</td>
<td align="center">0x11112222</td>
<td align="center">1G</td>
<td align="center">0x11112/1</td>
</tr>
<date month="February" year="2017"/> <tr>
</front> <td align="center">3</td>
</reference> <td align="center">0x11113333</td>
</references> <td align="center">10G</td>
<td align="center">0x11113/1</td>
</tr>
<section title="Example Encoding"> <tr>
<t/> <td align="center">4</td>
<td align="center">0x11114444</td>
<td align="center">10G</td>
<td align="center">0x11114/1</td>
</tr>
<t>Below is an example encoding of L2 Bundle advertisements in a case </tbody>
where we have two parallel adjacencies to the same neighbor whose </table>
system-id is 1234.1234.1234.00. The two L2 bundles have the following
sets of attributes:</t>
<t><figure> <t>L3 Adjacency #2</t>
<artwork><![CDATA[L3 Adjacency #1 <t>L3 IPv4 local link address: 192.0.2.2</t>
L3 IPv4 local link address: 192.0.2.1 <t>Three bundle members with the following attributes:</t>
Four bundle members with the following attributes:
Num | Link Local ID | Bandwidth | Adj-SID/Weight | <table anchor="adj2">
1 | 0x11111111 | 1G | 0x11111/1 | <thead>
2 | 0x11112222 | 1G | 0x11112/1 | <tr>
3 | 0x11113333 | 10G | 0x11113/1 | <th align='center'>Num</th>
4 | 0x11114444 | 10G | 0x11114/1 | <th align='center'>Link Local ID</th>
<th align='center'>Bandwidth</th>
<th align='center'>Adj-SID/Weight</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center">1</td>
<td align="center">0x22221111</td>
<td align="center">10G</td>
<td align="center">22221/1</td>
</tr>
L3 Adjacency #2 <tr>
L3 IPv4 local link address: 192.0.2.2 <td align="center">2</td>
Three bundle members with the following attributes: <td align="center">0x22222222</td>
<td align="center">10G</td>
<td align="center">22222/1</td>
</tr>
Num | Link Local ID | Bandwidth | Adj-SID/Weight | <tr>
1 | 0x22221111 | 10G | 22221/1 | <td align="center">3</td>
2 | 0x22222222 | 10G | 22222/1 | <td align="center">0x22223333</td>
3 | 0x22223333 | 10G | 22223/1 | <td align="center">10G</td>
]]></artwork> <td align="center">22223/1</td>
</figure>This requires two TLVs, one for each L3 adjacency.</t> </tr>
</tbody>
</table>
<t>TLV for Adjacency #1:</t> <t>This requires two TLVs, one for each L3 adjacency.</t>
<t><figure> <t>TLV for Adjacency #1:</t>
<artwork><![CDATA[
<artwork><![CDATA[
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type(25) |Len: 64 | | Type(25) | Length(64) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
Parent L3 Neighbor Descriptor <t>Parent L3 Neighbor Descriptor</t>
<artwork><![CDATA[
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor System-ID octets 1-4: 1234.1234 | | Neighbor System-ID octets 1-4: 1234.1234 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| System-ID octets 5-6: 1234 | P-node: 00 |1|0|0|0|0|0|0|0| | System-ID octets 5-6: 1234 | P-node: 00 |1|0|0|0|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
IPv4 Interface Address sub-TLV <t>IPv4 Interface Address Sub-TLV</t>
<artwork><![CDATA[
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type(6)) | Length(4) | | Type(6) | Length(4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address:192.0.2.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address: 192.0.2.1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
L2 Bundle Attribute Descriptors <t>L2 Bundle Attribute Descriptors</t>
<artwork><![CDATA[
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Len:9+6+10 = 25| # Desc: 2 | |Len:9+6+10 = 25| # Desc: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier Bundle Member #1: 0x11111111 | | Link Local Identifier Bundle Member #1: 0x11111111 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier Bundle Member #2: 0x11112222 | | Link Local Identifier Bundle Member #2: 0x11112222 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
Maximum Link Bandwidth sub-TLV <t>Maximum Link Bandwidth Sub-TLV</t>
<artwork><![CDATA[
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(9) | Length(4) | | Type(9) | Length(4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth Value: 1G/8 | | Bandwidth Value: 1G/8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
L2 Bundle Member Adjacency Segment Identifier sub-TLV <t>L2 Bundle Member Adj-SID Sub-TLV</t>
<artwork><![CDATA[
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(41) | Length(8) |0|0|1|1|0|0|0|0| Weight: 1 | | Type(41) | Length(8) |0|0|1|1|0|0|0|0| Weight: 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Label Bundle Member #1: 0x11111 | | Local Label Bundle Member #1: 0x11111 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Label Bundle Member #2: 0x11112 | | Local Label Bundle Member #2: 0x11112 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
L2 Bundle Attribute Descriptors <t>L2 Bundle Attribute Descriptors</t>
<artwork><![CDATA[
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Len:9+6+10 = 25| # Desc: 2 | |Len:9+6+10 = 25| # Desc: 2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier Bundle Member #3: 0x11113333 | | Link Local Identifier Bundle Member #3: 0x11113333 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier Bundle Member #4: 0x11114444 | | Link Local Identifier Bundle Member #4: 0x11114444 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork>
Maximum Link Bandwidth sub-TLV <t>Maximum Link Bandwidth Sub-TLV</t>
<artwork><![CDATA[
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(9) | Length(4) | | Type(9) | Length(4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth Value: 10G/8 | | Bandwidth Value: 10G/8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
L2 Bundle Member Adjacency Segment Identifier sub-TLV <t>L2 Bundle Member Adj-SID Sub-TLV</t>
<artwork><![CDATA[
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(41) | Length(8) |0|0|1|1|0|0|0|0| Weight: 1 | | Type(41) | Length(8) |0|0|1|1|0|0|0|0| Weight: 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Label Bundle Member #3: 0x11113 | | Local Label Bundle Member #3: 0x11113 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Label Bundle Member #4: 0x11114 | | Local Label Bundle Member #4: 0x11114 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
]]></artwork>
</figure></t>
<t>TLV for Adjacency #2</t> <t>TLV for Adjacency #2:</t>
<t><figure> <artwork><![CDATA[
<artwork><![CDATA[ 0 1
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type(25) | Len: 46 | | Type(25) | Length(46) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
Parent L3 Neighbor Descriptor <t>Parent L3 Neighbor Descriptor</t>
<artwork><![CDATA[
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor System-ID octets 1-4: 1234.1234 | | Neighbor System-ID octets 1-4: 1234.1234 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| System-ID octets 5-6: 1234 | P-node: 00 |1|0|0|0|0|0|0|0| | System-ID octets 5-6: 1234 | P-node: 00 |1|0|0|0|0|0|0|0|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
IPv4 Interface Address sub-TLV <t>IPv4 Interface Address Sub-TLV</t>
<artwork><![CDATA[
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type(6)) | Length(4) | | Type(6) | Length(4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address: 192.0.2.2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address: 192.0.2.2 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
L2 Bundle Attribute Descriptors <t>L2 Bundle Attribute Descriptors</t>
<artwork><![CDATA[
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Len:13+6+13=32 | # Desc: 3 | |Len:13+6+13=32 | # Desc: 3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier Bundle Member #1: 0x22221111 | | Link Local Identifier Bundle Member #1: 0x22221111 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier Bundle Member #2: 0x22222222 | | Link Local Identifier Bundle Member #2: 0x22222222 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Link Local Identifier Bundle Member #3: 0x22223333 | | Link Local Identifier Bundle Member #3: 0x22223333 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
Maximum Link Bandwidth sub-TLV <t>Maximum Link Bandwidth Sub-TLV</t>
<artwork><![CDATA[
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(9) | Length(4) | | Type(9) | Length(4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bandwidth Value: 10G/8 | | Bandwidth Value: 10G/8 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
L2 Bundle Member Adjacency Segment Identifier sub-TLV <t>L2 Bundle Member Adj-SID Sub-TLV</t>
<artwork><![CDATA[
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(41) | Length(11) |0|0|1|1|0|0|0|0| Weight: 1 | | Type(41) | Length(11) |0|0|1|1|0|0|0|0| Weight: 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Label Bundle Member #1: 0x22221 | | Local Label Bundle Member #1: 0x22221 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Label Bundle Member #2: 0x22222 | | Local Label Bundle Member #2: 0x22222 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Label Bundle Member #3: 0x22223 | | Local Label Bundle Member #3: 0x22223 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+]]></artwork>
]]></artwork>
</figure></t>
</section> </section>
<section numbered="false">
<name>Acknowledgements</name>
<t>The authors would like to thank Jon Mitchell for his careful
review.</t>
</section>
<section numbered="false">
<name>Contributors</name>
<t>The following people gave a substantial contribution to the content
of this document and should be considered coauthors:</t>
<artwork><![CDATA[Stefano Previdi
Huawei Technologies
Italy
Email: stefano@previdi.net]]></artwork>
</section>
</back> </back>
</rfc> </rfc>
 End of changes. 191 change blocks. 
488 lines changed or deleted 933 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/