Diff: rfc9184.original.xml

	rfc9184.original.xml	rfc9184.xml

	<?xml version='1.0' encoding='utf-8'?>	<?xml version="1.0" encoding="UTF-8"?>
	<!-- This template is for creating an Internet Draft using xml2rfc,
	which is available here: http://xml.resource.org. -->	<!DOCTYPE rfc [
	<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent"[	<!ENTITY nbsp " ">
		<!ENTITY zwsp "">
		<!ENTITY nbhy "‑">
		<!ENTITY wj "⁠">
	]>	]>

	<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
	<!-- used by XSLT processors -->
	<!-- For a complete list and description of processing instructions (PIs),
	please see http://xml.resource.org/authoring/README.html. -->
	<rfc
	xmlns:xi="http://www.w3.org/2001/XInclude"
	category="std"
	docName="draft-ietf-idr-bgp-ext-com-registry-05"
	ipr="trust200902"
	obsoletes=""
	updates="7153 8955"
	submissionType="IETF"
	xml:lang="en"
	tocInclude="true"
	tocDepth="4"
	symRefs="true"
	sortRefs="true"
	version="3">
	<!-- xml2rfc v2v3 conversion 2.38.1 -->
	<!-- category values: std, bcp, info, exp, and historic
	ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902
	,
	or pre5378Trust200902
	you can add the attributes updates="NNNN" and obsoletes="NNNN"
	they will automatically be output with "(if approved)" -->


	<!-- *** FRONT MATTER *** -->	<rfc xmlns:xi="http://www.w3.org/2001/XInclude" docName="draft-ietf-idr-bgp-ext-
		com-registry-05"
		number="9184" ipr="trust200902" obsoletes="" updates="7153, 8955" submissionType
		="IETF" category="std"
		consensus="true" xml:lang="en" tocInclude="true" tocDepth="4" symRefs="true" sor
		tRefs="true" version="3">

	<front>	<front>

	<!-- The abbreviated title is used in the page header - it is only necessary
	if the
	full title is longer than 39 characters -->


	<title abbrev="BGP Ext. Com. Registries Update" >BGP Extended Community Regis	<title abbrev="BGP Extended Community Registries Update" >BGP Extended Commun
	tries Update</title>	ity Registries Update</title>
	<seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp-ext-com-registry-	<seriesInfo name="RFC" value="9184"/>
	05"/>
	<author fullname="Christoph Loibl" surname="Loibl">	<author fullname="Christoph Loibl" surname="Loibl">
	<organization>next layer Telekom GmbH</organization>	<organization>next layer Telekom GmbH</organization>
	<address>	<address>
	<postal>	<postal>
	<street>Mariahilfer Guertel 37/7</street>	<street>Mariahilfer Guertel 37/7</street>
	<city>Vienna</city>	<city>Vienna</city>
	<region></region>	<region></region>
	<code>1150</code>	<code>1150</code>

	<country>AT</country>	<country>Austria</country>
	</postal>	</postal>
	<phone>+43 664 1176414</phone>	<phone>+43 664 1176414</phone>
	<email>cl@tix.at</email>	<email>cl@tix.at</email>
	</address>	</address>
	</author>	</author>


	<date year="2021"/>	<date year="2022" month="January" />
	<!-- If the month and year are both specified and are the current ones, xml2
	rfc will fill
	in the current day for you. If only the current year is specified, xml2r
	fc will fill
	in the current day and month for you. If the year is not the current one
	, it is
	necessary to specify at least a month (xml2rfc assumes day="1" if not sp
	ecified for the
	purpose of calculating the expiry date). With drafts it is normally suf
	ficient to
	specify just the year. -->

	<!-- Meta-data Declarations -->

	<area>Routing Area</area>	<area>Routing Area</area>
	<workgroup>IDR Working Group</workgroup>	<workgroup>IDR Working Group</workgroup>

	<!-- WG name at the upperleft corner of the doc,
	IETF is fine for individual submissions.
	If this element is not present, the default is "Network Working Group",
	which is used by the RFC Editor as a nod to the history of the IETF. -->
	<keyword>RFC</keyword>
	<keyword>Request for Comments</keyword>
	<keyword>I-D</keyword>
	<keyword>Internet-Draft</keyword>
	<keyword>IANA</keyword>


	<!-- Keywords will be incorporated into HTML output	<keyword>IANA</keyword>
	files in a meta tag but they have no effect on text or nroff
	output. If you submit your draft to the RFC Editor, the
	keywords will be used for the search engine. -->

	<abstract>	<abstract>
	<t>	<t>
	This document updates several BGP Extended Community registries in order to	This document updates several BGP Extended Community registries in order to
	replace the "Experimental Use" registration procedure in some entries, s ince	replace the "Experimental Use" registration procedure in some entries, s ince

	their use is clearly not experimental and thus misleading.	their use is clearly not experimental and is thus misleading.
	</t>	</t>
	<t>	<t>

	This document updates RFC7153 and RFC8955.	This document updates RFCs 7153 and 8955.
	</t>	</t>
	</abstract>	</abstract>
	</front>	</front>
	<middle>	<middle>
	<section>	<section>
	<name>Introduction</name>	<name>Introduction</name>
	<t>	<t>

	<xref target="RFC7153" /> reorganizes the IANA registries for the type valu	The IANA registries for the type values and sub-type values of the BGP Exte
	es and	nded Communities attribute were reorganized by <xref target="RFC7153"/>. As a re
	sub-type values of the BGP Extended Communities attribute. As a result the	sult, IANA maintains a
	IANA maintained	registry entitled "BGP Transitive Extended Community Types", which includes
	registry entitled "BGP Transitive Extended Community Types" includes a rang	a range of type values (0x80-0x8F)
	e of Type Values (0x80-0x8F)	reserved for Experimental Use <xref target="RFC8126" />. Out of this experi
	reserved for Experimental Use. Out of this experimental range the types 0x8	mental range, types 0x80, 0x81, and 0x82 have
	0, 0x81, 0x82 have	been used in <xref target="RFC5575" /> and <xref target="RFC7674" /> (both
	been used in <xref target="RFC5575" /> and <xref target="RFC7674" /> (both	documents were rendered
	documents rendered	obsolete by <xref target="RFC8955" />).
	Obsolete by <xref target="RFC8955" />). The primary use for those types and
	sub-type registries	The primary use for those types and the sub-type registries
	is non experimental.	is non-experimental.
	</t>	</t>
	<t>	<t>

	<xref target="IANA" /> of this document requests the registry cleanup to re
	flect the	<xref target="IANA" /> describes updates to the registry to reflect the
	actual use of those code-points (removing "Experimental Use" from the sub-t	actual use of those code points by changing the registration procedure from
	ype registry names)	"Experimental Use" to "First Come First Served" <xref target="RFC8126"/> for th
	and changes the registration procedure of the types 0x80, 0x81, 0x82 to use	e types 0x80-0x82 (and removing "Experimental Use" from the sub-type registry na
	the First Come First Served	mes), thereby updating <xref target="RFC7153" /> and <xref target="RFC8955" />.
	policy <xref target="RFC8126" /> and thus updates <xref target="RFC7153" />
	and <xref target="RFC8955" />.
	</t>	</t>
	</section>	</section>
	<section anchor="IANA" numbered="true" toc="default">	<section anchor="IANA" numbered="true" toc="default">
	<name>IANA Considerations</name>	<name>IANA Considerations</name>
	<section>	<section>
	<name>Registry: BGP Transitive Extended Community Types</name>	<name>Registry: BGP Transitive Extended Community Types</name>
	<t>IANA maintains a registry entitled "BGP Transitive Extended Community T ypes".	<t>IANA maintains a registry entitled "BGP Transitive Extended Community T ypes".

	IANA is requested to add [this document] to the Reference of this registry
	,	IANA has added RFC 9184 to the reference of this registry. They have also
	update the Name of the Type Values according to <xref target="iana_ext_com	updated the name of the type values according to <xref target="iana_ext_co
	m_types" /> and	mm_types" /> and
	append a reference to [this document] to the existing references.	added RFC 9184 as a reference for the existing entries.
	</t>	</t>

	<table anchor="iana_ext_comm_types">	<table anchor="iana_ext_comm_types">
	<name>Registry: BGP Transitive Extended Community Types</name>	<name>Registry: BGP Transitive Extended Community Types</name>
	<thead>	<thead>
	<tr>	<tr>
	<th>Type Value</th>	<th>Type Value</th>
	<th>Name</th>	<th>Name</th>
	<th>Reference</th>	<th>Reference</th>
	</tr>	</tr>

	skipping to change at line 141 ¶	skipping to change at line 101 ¶
	<tr>	<tr>
	<td>	<td>
	0x80	0x80
	</td>	</td>
	<td>	<td>
	Generic Transitive Extended Community	Generic Transitive Extended Community
	(Sub-Types are defined in the "Generic Transitive	(Sub-Types are defined in the "Generic Transitive
	Extended Community Sub-Types" registry)	Extended Community Sub-Types" registry)
	</td>	</td>
	<td>	<td>

	[add this document]	RFC 9184
	</td>	</td>
	</tr>	</tr>
	<tr>	<tr>
	<td>0x81</td>	<td>0x81</td>
	<td>	<td>
	Generic Transitive Extended Community Part 2	Generic Transitive Extended Community Part 2
	(Sub-Types are defined in the "Generic Transitive	(Sub-Types are defined in the "Generic Transitive
	Extended Community Part 2 Sub-Types" registry)	Extended Community Part 2 Sub-Types" registry)
	</td>	</td>

	<td>[add this document]</td>	<td>RFC 9184</td>
	</tr>	</tr>
	<tr>	<tr>
	<td>0x82</td>	<td>0x82</td>
	<td>	<td>
	Generic Transitive Extended Community Part 3	Generic Transitive Extended Community Part 3
	(Sub-Types are defined in the "Generic Transitive	(Sub-Types are defined in the "Generic Transitive
	Extended Community Part 3 Sub-Types" registry)	Extended Community Part 3 Sub-Types" registry)
	</td>	</td>

	<td>[add this document]</td>	<td>RFC 9184</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>


	<t>Furthermore IANA is requested to change the registration procedures of	<t>Furthermore, IANA has changed the registration procedures of this regis
	this registry of Type Values 0x80 thru 0x82	try for type values 0x80 through 0x82
	to First Come First Served <xref target="RFC8126" />. The resulting Reg	to First Come First Served <xref target="RFC8126" />. The resulting reg
	istration Procedures should read as in	istration procedures should read as in
	<xref target="iana_ext_comm_types_regproc"/>.	<xref target="iana_ext_comm_types_regproc"/>.
	</t>	</t>

	<table anchor="iana_ext_comm_types_regproc" >	<table anchor="iana_ext_comm_types_regproc" >
	<name>Registration Procedures: BGP Transitive Extended Community Typ es</name>	<name>Registration Procedures: BGP Transitive Extended Community Typ es</name>
	<thead>	<thead>
	<tr>	<tr>
	<th align="left">Range</th>	<th align="left">Range</th>
	<th align="left">Registration Procedures</th>	<th align="left">Registration Procedures</th>
	</tr>	</tr>

	skipping to change at line 188 ¶	skipping to change at line 148 ¶
	<tbody>	<tbody>
	<tr>	<tr>
	<td>0x00-0x3f</td>	<td>0x00-0x3f</td>
	<td>	<td>
	First Come First Served	First Come First Served
	</td>	</td>
	</tr>	</tr>
	<tr>	<tr>
	<td>0x80-0x82</td>	<td>0x80-0x82</td>
	<td>	<td>

	First Come First Served (see [this document])	First Come First Served (see RFC 9184)
	</td>	</td>
	</tr>	</tr>
	<tr>	<tr>
	<td>0x83-0x8f</td>	<td>0x83-0x8f</td>
	<td>	<td>

	Reserved for Experimental Use (see [RFC3692])	Reserved for Experimental Use (see <xref target="RFC3692"/>)
	</td>	</td>
	</tr>	</tr>
	<tr>	<tr>
	<td>0x90-0xbf</td>	<td>0x90-0xbf</td>
	<td>	<td>
	Standards Action	Standards Action
	</td>	</td>
	</tr>	</tr>
	</tbody>	</tbody>
	</table>	</table>
	</section>	</section>
	<section>	<section>
	<name>Registry: Generic Transitive Experimental Use Extended Community S ub-Types</name>	<name>Registry: Generic Transitive Experimental Use Extended Community S ub-Types</name>
	<t>IANA maintains a registry entitled "Generic Transitive Experimental U se Extended Community Sub-Types".	<t>IANA maintains a registry entitled "Generic Transitive Experimental U se Extended Community Sub-Types".

	IANA is requested to add [this document] to the Reference of this regist	IANA has added RFC 9184 to the reference of this registry and
	ry and	updated the registry title to:
	update the registry title to:
	</t>	</t>
	<ul empty="true" spacing="normal">	<ul empty="true" spacing="normal">
	<li>"Generic Transitive Extended Community Sub-Types"</li>	<li>"Generic Transitive Extended Community Sub-Types"</li>
	</ul>	</ul>
	</section>	</section>
	<section>	<section>
	<name>Registry: Generic Transitive Experimental Use Extended Community P art 2 Sub-Types</name>	<name>Registry: Generic Transitive Experimental Use Extended Community P art 2 Sub-Types</name>
	<t>IANA maintains a registry entitled "Generic Transitive Experimental U se Extended Community Part 2 Sub-Types".	<t>IANA maintains a registry entitled "Generic Transitive Experimental U se Extended Community Part 2 Sub-Types".

	IANA is requested to add [this document] to the Reference of this regist	IANA has added RFC 9184 to the reference of this registry and
	ry and	updated the registry title to:
	update the registry title to:
	</t>	</t>
	<ul empty="true" spacing="normal">	<ul empty="true" spacing="normal">
	<li>"Generic Transitive Extended Community Part 2 Sub-Types"</li>	<li>"Generic Transitive Extended Community Part 2 Sub-Types"</li>
	</ul>	</ul>
	</section>	</section>
	<section>	<section>
	<name>Registry: Generic Transitive Experimental Use Extended Community P art 3 Sub-Types</name>	<name>Registry: Generic Transitive Experimental Use Extended Community P art 3 Sub-Types</name>
	<t>IANA maintains a registry entitled "Generic Transitive Experimental U se Extended Community Part 3 Sub-Types".	<t>IANA maintains a registry entitled "Generic Transitive Experimental U se Extended Community Part 3 Sub-Types".

	IANA is requested to add [this document] to the Reference of this regist	IANA has added RFC 9184 to the reference of this registry and
	ry and	updated the registry title to:
	update the registry title to:
	</t>	</t>
	<ul empty="true" spacing="normal">	<ul empty="true" spacing="normal">
	<li>"Generic Transitive Extended Community Part 3 Sub-Types"</li>	<li>"Generic Transitive Extended Community Part 3 Sub-Types"</li>
	</ul>	</ul>
	</section>	</section>
	</section>	</section>
	<section anchor="Security" numbered="true" toc="default">	<section anchor="Security" numbered="true" toc="default">
	<name>Security Considerations</name>	<name>Security Considerations</name>
	<t> There are no direct security considerations arising from this document . </t>	<t> There are no direct security considerations arising from this document . </t>
	</section>	</section>

	<section anchor="Acknowledgements" numbered="true" toc="default">
	<name>Acknowledgements</name>
	<t>The author wants to thank Alvaro Retana who pointed out, that the IANA
	registry contains
	misleading entries in this context.
	</t>
	</section>

	</middle>	</middle>

	<!-- ***BACK MATTER *** -->

	<back>	<back>

	<!-- References split into informative and normative -->

	<!-- There are 2 ways to insert reference entries from the citation libraries
	:
	1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (
	as shown)
	2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml
	"?> here
	(for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.x
	ml")

	Both are cited textually in the same manner: by using xref elements.
	If you use the PI option, xml2rfc will, by default, try to find included fil
	es in the same
	directory as the including file. You can also define the XML_LIBRARY environ
	ment variable
	with a value containing a set of directories to search. These can be either
	in the local
	filing system or remote ones accessed by http (http://domain/dir/... ).-->

	<references>	<references>
	<name>References</name>	<name>References</name>
	<references>	<references>
	<name>Normative References</name>	<name>Normative References</name>

	<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.7	<?rfc include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
	153.xml" ?>	7153.xml" ?>
	<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8	<?rfc include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
	126.xml" ?>	8126.xml" ?>
	</references>	</references>
	<references>	<references>
	<name>Informative References</name>	<name>Informative References</name>

	<!-- Here we use entities that we defined at the beginning. -->	<?rfc include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
	<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.3	3692.xml" ?>
	692.xml" ?>	<?rfc include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
	<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5	5575.xml" ?>
	575.xml" ?>	<?rfc include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
	<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.7	7674.xml" ?>
	674.xml" ?>	<?rfc include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.
	<?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8	8955.xml" ?>
	955.xml" ?>
	</references>	</references>
	</references>	</references>

	<!-- A reference written by by an organization not a person. -->	<section anchor="Acknowledgements" numbered="false" toc="default">
		<name>Acknowledgements</name>
		<t>The author wants to thank <contact fullname="Alvaro Retana"/>, who poin
		ted out that the IANA registry contains
		misleading entries in this context.
		</t>
		</section>
	</back>	</back>
	</rfc>	</rfc>

End of changes. 29 change blocks.
	152 lines changed or deleted	79 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/