rfc9104xml2.original.xml   rfc9104.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com)
by Daniel M Kohn (private) -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.
RFC.2119.xml">
]>
<rfc category="std" docName="draft-ietf-idr-eag-distribution-19"
ipr="trust200902">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?rfc iprnotified="no" ?> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-idr-eag-dist ribution-19" number="9104" ipr="trust200902" obsoletes="" updates="" submissionT ype="IETF" category="std" consensus="true" xml:lang="en" tocInclude="true" symRe fs="true" sortRefs="true" version="3">
<?rfc strict="yes" ?> <!-- xml2rfc v2v3 conversion 3.8.0 -->
<front> <front>
<title abbrev="Extended Administrative Group">Distribution of Traffic Engine <title abbrev="Extended Administrative Groups">Distribution of Traffic Engin
ering Extended eering Extended
Administrative Groups using BGP-LS</title> Administrative Groups Using&nbsp;the Border Gateway Protocol - Link State (B
GP-LS)</title>
<author fullname="Jeff Tantsura" initials="J.T." surname="Tantsura">
<organization>Juniper Networks</organization>
<seriesInfo name="RFC" value="9104"/>
<author fullname="Jeff Tantsura" initials="J." surname="Tantsura">
<organization>Microsoft</organization>
<address> <address>
<email>jefftant.ietf@gmail.com</email> <email>jefftant.ietf@gmail.com</email>
</address> </address>
</author> </author>
<author fullname="Zitao Wang" initials="Z." surname="Wang"> <author fullname="Zitao Wang" initials="Z." surname="Wang">
<organization>Huawei</organization> <organization>Huawei</organization>
<address> <address>
<postal> <postal>
<street>101 Software Avenue, Yuhua District</street> <extaddr>Yuhua District</extaddr>
<street>101 Software Avenue</street>
<city>Nanjing</city> <city>Nanjing</city>
<region>Jiangsu</region> <region>Jiangsu</region>
<code>210012</code> <code>210012</code>
<country>China</country> <country>China</country>
</postal> </postal>
<email>wangzitao@huawei.com</email> <email>wangzitao@huawei.com</email>
</address> </address>
</author> </author>
<author fullname="Qin Wu" initials="Q." surname="Wu"> <author fullname="Qin Wu" initials="Q." surname="Wu">
<organization>Huawei</organization> <organization>Huawei</organization>
<address> <address>
<postal> <postal>
<street>101 Software Avenue, Yuhua District</street> <extaddr>Yuhua District</extaddr>
<street>101 Software Avenue</street>
<city>Nanjing</city> <city>Nanjing</city>
<region>Jiangsu</region> <region>Jiangsu</region>
<code>210012</code> <code>210012</code>
<country>China</country> <country>China</country>
</postal> </postal>
<email>bill.wu@huawei.com</email> <email>bill.wu@huawei.com</email>
</address> </address>
</author> </author>
<author fullname="Ketan Talaulikar" initials="K." surname="Talaulikar"> <author fullname="Ketan Talaulikar" initials="K." surname="Talaulikar">
<organization>Cisco Systems</organization> <organization>Cisco Systems</organization>
<address> <address>
<email>ketant@cisco.com</email> <email>ketant@cisco.com</email>
</address> </address>
</author> </author>
<date year="2021" month="August"/>
<date year=""/>
<area>Routing Area</area> <area>Routing Area</area>
<workgroup>IDR Working Group</workgroup> <workgroup>IDR Working Group</workgroup>
<keyword>RFC</keyword>
<keyword>Request for Comments</keyword>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
<keyword>Inter-Domain Routing</keyword> <keyword>Inter-Domain Routing</keyword>
<abstract> <abstract>
<t>Administrative groups are link attributes used for traffic <t>Administrative groups are link attributes used for traffic
engineering. This document defines an extension to BGP-LS for engineering. This document defines an extension to the Border Gateway Protoc
advertisement of extended administrative groups (EAGs).</t> ol -
</abstract> Link State (BGP-LS) for advertisement of extended administrative groups (EAGs
).</t>
</abstract>
</front> </front>
<middle> <middle>
<section anchor="intro" title="Introduction"> <section anchor="intro" numbered="true" toc="default">
<t>Administrative groups (commonly referred to as "colors" or "link colors") <name>Introduction</name>
are link attributes that are advertised by link state protocols like IS-IS <x <t>Administrative groups (commonly referred to as "colors" or "link colors
ref target="RFC1195"/>, OSPFv2 <xref target="RFC2328"/> and OSPFv3 <xref target= ")
"RFC5340"/>. are link attributes that are advertised by link-state protocols like IS-IS <x
The BGP-LS advertisement of the originally defined (non-extended) administrat ref target="RFC1195" format="default"/>, OSPFv2 <xref target="RFC2328" format="d
ive groups is encoded efault"/>, and OSPFv3 <xref target="RFC5340" format="default"/>.
using the Administrative Group (color) TLV 1088 as defined in <xref target="R The Border Gateway Protocol - Link State (BGP-LS) advertisement of the origin
FC7752"/>.</t> ally defined (non-extended) administrative groups is encoded
using the Administrative Group (color) TLV 1088 as defined in <xref target="R
FC7752" format="default"/>.</t>
<t>These administrative groups are defined as a fixed-length 32-bit <t>These administrative groups are defined as a fixed-length 32-bit
bitmask. As networks grew and more use-cases were introduced, the 32-bit bitmask. As networks grew and more use cases were introduced, the 32-bit
length was found to be constraining and hence extended administrative length was found to be constraining, and hence extended administrative
groups (EAG) were introduced in <xref target="RFC7308"/>.</t> groups (EAGs) were introduced in <xref target="RFC7308" format="default"/>
.</t>
<t>The EAG TLV (Section 2) is not a replacement for the Administrative <t>The EAG TLV (<xref target="advert"/>) is not a replacement for the Admi
Group (color) TLV; as explained in <xref target="RFC7308"/> both values can nistrative
coexist. Group (color) TLV; as explained in <xref target="RFC7308" format="default"/>
, both values can coexist.
It is out of scope for this document to specify the behavior of the It is out of scope for this document to specify the behavior of the
BGP-LS consumer <xref target="RFC7752"/>. </t> BGP-LS consumer <xref target="RFC7752" format="default"/>. </t>
<t>This document specifies an extension to BGP-LS for advertisement of the <t>This document specifies an extension to BGP-LS for advertisement of the
extended administrative groups.</t> extended administrative groups.</t>
<section numbered="true" toc="default">
<section title="Requirements Language"> <name>Requirements Language</name>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>",
"OPTIONAL" in this document are to be interpreted as described in BCP "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>",
14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only "<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> when, they appear in all capitals, as shown here.</t>
</section> </section>
</section> </section>
<section anchor="advert" numbered="true" toc="default">
<section title="Advertising Extended Administrative Group in BGP-LS"> <name>Advertising Extended Administrative Groups in BGP-LS</name>
<t>This document defines an extension that enables BGP-LS speakers to <t>This document defines an extension that enables BGP-LS speakers to
signal the EAG of links in a network to a BGP-LS consumer of network signal the EAG of links in a network to a BGP-LS consumer of network
topology such as a centralized controller. The centralized controller topology such as a centralized controller. The centralized controller
can leverage this information in traffic engineering computations and can leverage this information in traffic engineering computations and
other use-cases. When a BGP-LS speaker is originating the topology other use cases. When a BGP-LS speaker is originating the topology
learnt via link-state routing protocols like OSPF or IS-IS, the EAG learned via link-state routing protocols like OSPF or IS-IS, the EAG
information of the links is sourced from the underlying extensions as information of the links is sourced from the underlying extensions as
defined in <xref target="RFC7308"/>.</t> defined in <xref target="RFC7308" format="default"/>.</t>
<t>The EAG of a link is encoded in a new Link Attribute TLV <xref target="
<t>The EAG of a link is encoded in a new Link Attribute TLV <xref RFC7752" format="default"/> using the following format:</t>
target="RFC7752"/> using the following format:</t> <figure anchor="link-attribute_tlv">
<name>Extended Administrative Group TLV Format</name>
<figure anchor="link-attribute_tlv" <artwork name="" type="ascii-art" align="left" alt=""><![CDATA[
title="Extended Administrative Group TLV Format">
<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 | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Extended Administrative Group (variable) // | Extended Administrative Group (variable) //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
]]></artwork> ]]></artwork>
</figure> </figure>
<t>Where:</t>
<dl spacing="normal">
<t>Where:<list style="symbols"> <dt>Type:</dt><dd>1173</dd>
<t>Type: 1173</t> <dt>Length:</dt><dd>variable length that represents the total length of
the value field in octets.
<t>Length: variable length which represents the total length of the va The length value <bcp14>MUST</bcp14> be a multiple of 4. If the length
lue field in octets. is not a multiple of 4, the TLV <bcp14>MUST</bcp14> be considered malformed.</d
The length value MUST be a multiple of 4. If the length is not a multi d>
ple of 4, the TLV MUST be considered malformed.</t> <dt>Value:</dt><dd>one or more sets of 32-bit bitmasks that indicate the
<t>Value: one or more sets of 32-bit bitmasks that indicate the
administrative groups (colors) that are enabled on the link when administrative groups (colors) that are enabled on the link when
those specific bits are set.</t> those specific bits are set.</dd>
</list> </dl>
</t>
</section> </section>
<section anchor="iana-consider" numbered="true" toc="default">
<name>IANA Considerations</name>
<t>IANA has assigned a code point from the "BGP-LS Node Descriptor, Link D
escriptor, Prefix Descriptor, and Attribute TLVs" registry as described in the f
ollowing table.</t>
<section anchor="iana-consider" title="IANA Considerations"> <table anchor="tab-1">
<t>This document requests assigning a code-point from the registry "BGP-LS <name></name>
Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs" <thead>
based on table below. Early allocation for these code-points have been <tr>
done by IANA.</t> <th>Code Point</th>
<th>Description</th>
<figure> <th>IS-IS TLV/Sub-TLV</th>
<artwork align="center"><![CDATA[ </tr>
+------------+-------------------------------+-------------------+ </thead>
| Code Point | Description | IS-IS TLV/Sub-TLV | <tbody>
+------------+-------------------------------+-------------------+ <tr>
| 1173 | Extended Administrative Group | 22/14 | <td>1173</td>
+------------+-------------------------------+-------------------+ <td>Extended Administrative Group</td>
<td>22/14</td>
</tr>
</tbody>
</table>
]]></artwork>
</figure>
</section> </section>
<section anchor="Manageability" numbered="true" toc="default">
<section anchor="Manageability" title="Manageability Considerations"> <name>Manageability Considerations</name>
<t>The new protocol extensions introduced in this document augment the <t>The new protocol extensions introduced in this document augment the
existing IGP topology information that is distributed via <xref existing IGP topology information that is distributed via <xref target="RF
target="RFC7752"/>. Procedures and protocol extensions defined in this C7752" format="default"/>. Procedures and protocol extensions defined in this
document do not affect the BGP protocol operations and management other document do not affect the BGP protocol operations and management other
than as discussed in the Manageability Considerations section of <xref than as discussed in Section&nbsp;<xref target="RFC7752" section="6"
target="RFC7752"/>. Specifically, the malformed attribute tests for sectionFormat="bare">"Manageability Considerations"</xref> of <xref target="RFC7
syntactic checks in the Fault Management section of <xref 752"/>. Specifically, the tests for malformed attributes, to perform
target="RFC7752"/> now encompass the new BGP-LS Attribute TLV defined syntactic checks as described in Section&nbsp;<xref target="RFC7752" secti
on="6.2.2"
sectionFormat="bare">"Fault Management"</xref> of <xref target="RFC7752"/>, now
encompass the new BGP-LS Attribute TLV defined
in this document. The semantic or content checking for the TLV in this document. The semantic or content checking for the TLV
specified in this document and its association with the BGP-LS NLRI specified in this document and its association with the BGP-LS Network Lay
types or its BGP-LS Attribute is left to the consumer of the BGP-LS er Reachability Information (NLRI)
information (e.g. an application or a controller) and not the BGP types or its BGP-LS Attribute are left to the consumer of the BGP-LS
protocol.</t> information (e.g., an application or a controller) and not to BGP itself.<
/t>
<t>A consumer of the BGP-LS information retrieves this information over <t>A consumer of the BGP-LS information retrieves this information over
a BGP-LS session (refer Section 1 and 2 of <xref target="RFC7752"/>).</t> a BGP-LS session (refer to Sections&nbsp;<xref target="RFC7752" section="1
"
sectionFormat="bare"/> and <xref target="RFC7752" section="2"
sectionFormat="bare"/> of <xref target="RFC7752"/>).</t>
</section> </section>
<section title="Security Considerations"> <section numbered="true" toc="default">
<t>The procedures and protocol extensions defined in this document do not <name>Security Considerations</name>
<t>The procedures and protocol extensions defined in this document do not
affect the BGP security model. See the "Security Considerations" section of affect the BGP security model. See the "Security Considerations" section of
<xref target="RFC4271"/> for a discussion of BGP security. <xref target="RFC4271" format="default"/> for a discussion of BGP security
This document only introduces a new Attribute TLV and any syntactic .
error in it would result in the BGP-LS Attribute being discarded <xref tar This document only introduces a new Attribute TLV, and any syntactic
get="RFC7752"/>. error in it would result in the BGP-LS Attribute being discarded <xref tar
Also, refer to <xref target="RFC4272"/> and <xref target="RFC6952"/> for a get="RFC7752" format="default"/>.
nalyses of security issues for BGP. Also, refer to <xref target="RFC4272" format="default"/> and <xref target=
Security considerations for acquiring and distributing BGP-LS information "RFC6952" format="default"/> for analyses of security issues for BGP.
are discussed in <xref target="RFC7752"/>. Security considerations for acquiring and distributing BGP-LS information
are discussed in <xref target="RFC7752" format="default"/>.
The TLV introduced in this document is used to propagate the EAG The TLV introduced in this document is used to propagate the EAG
extensions defined in <xref target="RFC7308"/>. extensions defined in <xref target="RFC7308" format="default"/>.
It is assumed that the IGP instances originating this TLV will support any required security mechanisms for OSPF and IS-IS, in order to prevent any securi ty It is assumed that the IGP instances originating this TLV will support any required security mechanisms for OSPF and IS-IS, in order to prevent any securi ty
issues when propagating the Sub-TLVs into BGP-LS.</t> issues when propagating the Sub-TLVs into BGP-LS.</t>
<t>Security concerns for OSPF are addressed in <xref target="RFC7474"/>, <t>Security concerns for OSPF are addressed in <xref target="RFC7474" form
<xref target="RFC4552"/> and <xref target="RFC7166"/>. at="default"/>, <xref target="RFC4552" format="default"/>, and <xref target="RF
Further security analysis for OSPF protocol is done in <xref target="RFC6863 C7166" format="default"/>.
"/>.</t> Further security analysis for the OSPF protocol is done in <xref target="RFC
6863" format="default"/>.</t>
<t>Security considerations for IS-IS are specified by <xref target="RFC5304" <t>Security considerations for IS-IS are specified by <xref target="RFC530
/>.</t> 4" format="default"/>.</t>
<t>The advertisement of the link attribute information defined in this <t>The advertisement of the link attribute information defined in this
document presents no significant additional risk beyond that associated wi th the document presents no significant additional risk beyond that associated wi th the
existing link attribute information already supported in <xref target="RFC existing link attribute information already supported in <xref target="RFC
7752"/>.</t> 7752" format="default"/>.</t>
</section>
<section title="Acknowledgments">
<t>The authors would like to thank Eric Osborne, Les Ginsberg, Tim Chown,
Ben Niven-Jenkins and Alvaro Retana for their reviews and valuable comments.</t>
</section> </section>
</middle> </middle>
<back> <back>
<references title="Normative References"> <references>
<?rfc include="reference.RFC.2119"?> <name>References</name>
<references>
<?rfc include="reference.RFC.8174"?> <name>Normative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<?rfc include="reference.RFC.7308"?> FC.2119.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<?rfc include="reference.RFC.7752"?> FC.8174.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
</references> FC.7308.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<references title="Informative References"> FC.7752.xml"/>
<?rfc include="reference.RFC.1195"?> </references>
<references>
<?rfc include="reference.RFC.2328"?> <name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<?rfc include="reference.RFC.5340"?> FC.1195.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<?rfc include="reference.RFC.4271"?> FC.2328.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<?rfc include="reference.RFC.4272"?> FC.5340.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<?rfc include="reference.RFC.6952"?> FC.4271.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<?rfc include="reference.RFC.4552"?> FC.4272.xml"/>
<?rfc include="reference.RFC.7166"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<?rfc include="reference.RFC.6863"?> FC.6952.xml"/>
<?rfc include="reference.RFC.7474"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.4552.xml"/>
<?rfc include="reference.RFC.5304"?> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.7166.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.6863.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.7474.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.5304.xml"/>
</references>
</references> </references>
<section numbered="false" toc="default">
<name>Acknowledgments</name>
<t>The authors would like to thank <contact fullname="Eric Osborne"/>, <co
ntact fullname="Les Ginsberg"/>, <contact fullname="Tim Chown"/>, <contact fulln
ame="Ben Niven-Jenkins"/>, and <contact fullname="Alvaro Retana"/> for their rev
iews and valuable comments.</t>
</section>
</back> </back>
</rfc> </rfc>
 End of changes. 55 change blocks. 
199 lines changed or deleted 184 lines changed or added

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