<?xmlversion='1.0' encoding='utf-8'?> <!-- This template is for creating an Internet Draft using xml2rfc, which is available here: http://xml.resource.org. -->version="1.0" encoding="UTF-8"?> <!DOCTYPE rfcSYSTEM "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" number="9184" ipr="trust200902" obsoletes=""updates="7153updates="7153, 8955" submissionType="IETF" category="std" consensus="true" 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 ***** --><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="BGPExt. Com.Extended Community Registries Update" >BGP Extended Community Registries Update</title> <seriesInfoname="Internet-Draft" value="draft-ietf-idr-bgp-ext-com-registry-05"/>name="RFC" value="9184"/> <author fullname="Christoph Loibl" surname="Loibl"> <organization>next layer Telekom GmbH</organization> <address> <postal> <street>Mariahilfer Guertel 37/7</street> <city>Vienna</city> <region></region> <code>1150</code><country>AT</country><country>Austria</country> </postal> <phone>+43 664 1176414</phone> <email>cl@tix.at</email> </address> </author> <dateyear="2021"/> <!-- If the month and year are both specified and are the current ones, xml2rfc will fill in the current day for you. If only the current year is specified, xml2rfc 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 specified for the purpose of calculating the expiry date). With drafts it is normally sufficient to specify just the year. --> <!-- Meta-data Declarations -->year="2022" month="January" /> <area>Routing Area</area> <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 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> <t> This document updates several BGP Extended Community registries in order to replace the "Experimental Use" registration procedure in some entries, since their use is clearly not experimental and is thus misleading. </t> <t> This document updatesRFC7153RFCs 7153 andRFC8955.8955. </t> </abstract> </front> <middle> <section> <name>Introduction</name> <t><xref target="RFC7153" /> reorganizes theThe IANA registries for the type values and sub-type values of the BGP Extended Communitiesattribute.attribute were reorganized by <xref target="RFC7153"/>. As aresult theresult, IANAmaintainedmaintains a registry entitled "BGP Transitive Extended CommunityTypes"Types", which includes a range ofType Valuestype values (0x80-0x8F) reserved for ExperimentalUse.Use <xref target="RFC8126" />. Out of this experimentalrange therange, types 0x80, 0x81, and 0x82 have been used in <xref target="RFC5575" /> and <xref target="RFC7674" /> (both documents were renderedObsoleteobsolete by <xref target="RFC8955" />). The primary use for those types and the sub-type registries isnon experimental.non-experimental. </t> <t> <xref target="IANA" />of this document requestsdescribes updates to the registrycleanupto reflect the actual use of thosecode-points (removing "Experimental Use" from the sub-type registry names) and changescode points by changing the registration procedureof the types 0x80, 0x81, 0x82from "Experimental Use" touse the First"First Come FirstServed policyServed" <xreftarget="RFC8126" /> and thus updatestarget="RFC8126"/> for the types 0x80-0x82 (and removing "Experimental Use" from the sub-type registry names), thereby updating <xref target="RFC7153" /> and <xref target="RFC8955" />. </t> </section> <section anchor="IANA" numbered="true" toc="default"> <name>IANA Considerations</name> <section> <name>Registry: BGP Transitive Extended Community Types</name> <t>IANA maintains a registry entitled "BGP Transitive Extended Community Types". IANAis requested to add [this document]has added RFC 9184 to theReferencereference of thisregistry, updateregistry. They have also updated theNamename of theType Valuestype values according to <xref target="iana_ext_comm_types" /> andappendadded RFC 9184 as a referenceto [this document] tofor the existingreferences.entries. </t> <table anchor="iana_ext_comm_types"> <name>Registry: BGP Transitive Extended Community Types</name> <thead> <tr> <th>Type Value</th> <th>Name</th> <th>Reference</th> </tr> </thead> <tbody> <tr> <td> 0x80 </td> <td> Generic Transitive Extended Community (Sub-Types are defined in the "Generic Transitive Extended Community Sub-Types" registry) </td> <td>[add this document]RFC 9184 </td> </tr> <tr> <td>0x81</td> <td> Generic Transitive Extended Community Part 2 (Sub-Types are defined in the "Generic Transitive Extended Community Part 2 Sub-Types" registry) </td><td>[add this document]</td><td>RFC 9184</td> </tr> <tr> <td>0x82</td> <td> Generic Transitive Extended Community Part 3 (Sub-Types are defined in the "Generic Transitive Extended Community Part 3 Sub-Types" registry) </td><td>[add this document]</td><td>RFC 9184</td> </tr> </tbody> </table><t>Furthermore<t>Furthermore, IANAis requested to changehas changed the registration procedures of this registryof Type Valuesfor type values 0x80thruthrough 0x82 to First Come First Served <xref target="RFC8126" />. The resultingRegistration Proceduresregistration procedures should read as in <xref target="iana_ext_comm_types_regproc"/>. </t> <table anchor="iana_ext_comm_types_regproc" > <name>Registration Procedures: BGP Transitive Extended Community Types</name> <thead> <tr> <th align="left">Range</th> <th align="left">Registration Procedures</th> </tr> </thead> <tbody> <tr> <td>0x00-0x3f</td> <td> First Come First Served </td> </tr> <tr> <td>0x80-0x82</td> <td> First Come First Served (see[this document])RFC 9184) </td> </tr> <tr> <td>0x83-0x8f</td> <td> Reserved for Experimental Use (see[RFC3692])<xref target="RFC3692"/>) </td> </tr> <tr> <td>0x90-0xbf</td> <td> Standards Action </td> </tr> </tbody> </table> </section> <section> <name>Registry: Generic Transitive Experimental Use Extended Community Sub-Types</name> <t>IANA maintains a registry entitled "Generic Transitive Experimental Use Extended Community Sub-Types". IANAis requested to add [this document]has added RFC 9184 to theReferencereference of this registry andupdateupdated the registry title to: </t> <ul empty="true" spacing="normal"> <li>"Generic Transitive Extended Community Sub-Types"</li> </ul> </section> <section> <name>Registry: Generic Transitive Experimental Use Extended Community Part 2 Sub-Types</name> <t>IANA maintains a registry entitled "Generic Transitive Experimental Use Extended Community Part 2 Sub-Types". IANAis requested to add [this document]has added RFC 9184 to theReferencereference of this registry andupdateupdated the registry title to: </t> <ul empty="true" spacing="normal"> <li>"Generic Transitive Extended Community Part 2 Sub-Types"</li> </ul> </section> <section> <name>Registry: Generic Transitive Experimental Use Extended Community Part 3 Sub-Types</name> <t>IANA maintains a registry entitled "Generic Transitive Experimental Use Extended Community Part 3 Sub-Types". IANAis requested to add [this document]has added RFC 9184 to theReferencereference of this registry andupdateupdated the registry title to: </t> <ul empty="true" spacing="normal"> <li>"Generic Transitive Extended Community Part 3 Sub-Types"</li> </ul> </section> </section> <section anchor="Security" numbered="true" toc="default"> <name>Security Considerations</name> <t> There are no direct security considerations arising from this document. </t> </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><!-- *****BACK MATTER ***** --><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.xml") 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 files in the same directory as the including file. You can also define the XML_LIBRARY environment 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> <name>References</name> <references> <name>Normative References</name> <?rfcinclude="http://xml.resource.org/public/rfc/bibxml/reference.RFC.7153.xml"include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7153.xml" ?> <?rfcinclude="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8126.xml"include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml" ?> </references> <references> <name>Informative References</name><!-- Here we use entities that we defined at the beginning. --><?rfcinclude="http://xml.resource.org/public/rfc/bibxml/reference.RFC.3692.xml"include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3692.xml" ?> <?rfcinclude="http://xml.resource.org/public/rfc/bibxml/reference.RFC.5575.xml"include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5575.xml" ?> <?rfcinclude="http://xml.resource.org/public/rfc/bibxml/reference.RFC.7674.xml"include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7674.xml" ?> <?rfcinclude="http://xml.resource.org/public/rfc/bibxml/reference.RFC.8955.xml"include="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8955.xml" ?> </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 pointed out that the IANA registry contains misleading entries in this context. </t> </section> </back> </rfc>