<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">

<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
     docName="draft-ietf-idr-capabilities-registry-change-09" number="8810"
     ipr="trust200902" updates="5492" obsoletes="" submissionType="IETF"
     category="std" consensus="true" xml:lang="en" tocInclude="true"
     tocDepth="4" symRefs="true" sortRefs="true" version="3"> 

  <!-- xml2rfc v2v3 conversion 2.44.0 -->

  <front>
    <title abbrev="Capability Codes Registration Procedures">
    Revision to Capability Codes Registration Procedures</title>
    <seriesInfo name="RFC" value="8810"/>

    <author fullname="John Scudder" initials="J." surname="Scudder">
      <organization>Juniper Networks</organization>
      <address>
        <postal>
          <street>1194 N. Mathilda Ave</street>
          <city>Sunnyvale</city>
          <region>CA</region>
          <code>94089</code>
          <country>United States of America</country>
        </postal>
        <email>jgs@juniper.net</email>
      </address>
    </author>
    <date year="2020" month="August" />

    <area>RTG</area>
    <workgroup>IDR</workgroup>
    <keyword>IDR</keyword>
    <abstract>


      <t>
	This document updates RFC 5492 by making a change to the
	registration procedures for BGP Capability Codes. Specifically, the
	range formerly designated "Private Use" is divided into
	three new ranges: "First Come First Served",
	"Experimental Use", and "Reserved".
</t>
    </abstract>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" toc="default">
      <name>Introduction</name>
      <t>
	The Border Gateway Protocol uses a mechanism called "Capability
	Advertisement" <xref target="RFC5492" format="default"/> to enable BGP peers to 
	tell one another about their optional protocol extensions. These
	so-called "Capabilities" are signaled using code points called
	"Capability Codes".
</t>
      <t>
	<xref target="RFC5492" format="default"/> designates the range of Capability Codes
	128-255 as "Private Use". Subsequent experience has
	shown this to be not only useless, but actively confusing to
	implementors.</t>
      <t>
	Accordingly, this document revises the registration procedures for
	the range 128-255, as follows, using the terminology defined in <xref
	target="RFC8126" format="default"/>:</t> 
      <dl newline="false" spacing="compact" indent="10">
        <dt>128-238:</dt>
	<dd>First Come First Served</dd>
        <dt>239-254:</dt>
	<dd>Experimental Use</dd>
        <dt>255:</dt>
	<dd>Reserved</dd>
      </dl>
      <t>
	The procedures for the ranges 1-63 and 64-127 are unchanged,
	remaining "IETF Review" and "First Come First Served",
      respectively. The full range for “First Come First Served” is now 64-238.</t>
    </section>
    <section anchor="discussion" numbered="true" toc="default">
      <name>Discussion</name>
      <t>
	The reason for providing an "Experimental Use" range is to preserve a
	range for use during early development. Although there are few
	practical differences between "Experimental Use" and "Private Use", the
	change both makes it clear that code points from this space should
	not be used long term or in shipping products and reduces the
	consumption of the scarce Capability Codes space expended for this
	purpose. Once classified as "Experimental Use", it should be considered
	difficult to reclassify the space for some other purpose in the
	future.
</t>
      <t>
	The reason for reserving the maximum value is that it may be useful
	in the future if extension of the number space is needed.
</t>

      <t>
    Since the range 128-255 was formerly designated "Private Use",
    implementors may have chosen to use code points within that range prior to
    publication of this document. For this reason, a survey was conducted
    beginning August 14, 2015 (version 01 of the individual draft <xref
    target="I-D.scudder-idr-capabilities-registry-change"/>) to find any such
    uses. A number were contributed and were used to seed <xref
    target="new_allocations" format="default"/>. Of course, there can be no
    guarantee that all uses were discovered; however, the likelihood seems
    high that remaining uses, if any, genuinely do fall under the intended use
    of "Private Use" and are restricted to some special deployment and are not
    in wide use. Furthermore, any remaining uses would be no worse than any
    other code point collision, such as occasionally occurs with code point
    "squatting", and could be dealt with in the same manner.
</t>
    </section>
    <section anchor="IANA" numbered="true" toc="default">
      <name>IANA Considerations</name>


      <t>
	IANA has revised the "Capability Codes" registry as follows.
</t>
      <t>
	Reference: <xref target="RFC5492" format="default"/> and this document.
</t>

<t>Note: The IETF will be the Change Controller for all future registrations.
</t>
      <t>
	Registration procedures:
</t>
      <table anchor="registration_procedures" align="center">
        <thead>
          <tr>
            <th align="center">Range</th>
            <th align="left">Registration Procedures</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="center">1-63</td>
            <td align="left">IETF Review</td>
          </tr>
          <tr>
            <td align="center">64-238</td>
            <td align="left">First Come First Served</td>
          </tr>
          <tr>
            <td align="center">239-254</td>
            <td align="left">Experimental Use</td>
          </tr>
        </tbody>
      </table>
      <t>
	IANA has made the following new allocations within the
	"Capability Codes" registry:
</t>
      <table anchor="new_allocations" align="center">
        <thead>
          <tr>
            <th align="center">Value</th>
            <th align="left">Description</th>
            <th align="left">Reference</th>
            <th align="left">Change Controller</th>
          </tr>
        </thead>
        <tbody>
          <tr>
            <td align="center">128</td>
            <td align="left">Prestandard Route Refresh (deprecated)</td>
            <td align="left">RFC 8810</td>
            <td align="left">IETF</td>
          </tr>
          <tr>
            <td align="center">129</td>
            <td align="left">Prestandard Outbound Route Filtering (deprecated),
       prestandard Routing Policy Distribution (deprecated)</td>
            <td align="left">RFC 8810</td>
            <td align="left">IETF</td>
          </tr>
          <tr>
            <td align="center">130</td>
            <td align="left">Prestandard Outbound Route Filtering (deprecated)</td>
            <td align="left">RFC 8810</td>
            <td align="left">IETF</td>
          </tr>
          <tr>
            <td align="center">131</td>
            <td align="left">Prestandard Multisession (deprecated)</td>
            <td align="left">RFC 8810</td>
            <td align="left">IETF</td>
          </tr>
          <tr>
            <td align="center">184</td>
            <td align="left">Prestandard FQDN (deprecated)</td>
            <td align="left">RFC 8810</td>
            <td align="left">IETF</td>
          </tr>
          <tr>
            <td align="center">185</td>
            <td align="left">Prestandard OPERATIONAL message (deprecated)</td>
            <td align="left">RFC 8810</td>
            <td align="left">IETF</td>
          </tr>
          <tr>
            <td align="center">255</td>
            <td align="left">Reserved</td>
            <td align="left">RFC 8810</td>
            <td align="left">IETF</td>
          </tr>
        </tbody>
      </table>
    </section>
    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This revision to registration procedures does not change the
      underlying security issues inherent in the existing <xref
      target="RFC5492" format="default"/> and <xref target="RFC4271"
      format="default"/>.</t> 
    </section>
  </middle>

  <back>
<displayreference target="I-D.scudder-idr-capabilities-registry-change" to="SCUDDER"/>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
	<xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.5492.xml"/>
        <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml"/>
      </references>
      <references>
        <name>Informative References</name>
        <xi:include
	    href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.4271.xml"/>

<reference anchor='I-D.scudder-idr-capabilities-registry-change'>
<front>
<title>Revision to Capability Codes Registration Procedures</title>

<author initials='J' surname='Scudder' fullname='John Scudder'>
    <organization />
</author>

<date month='August' day='14' year='2015' />

<abstract><t>This document updates RFC 5492 by making a change to the registration procedures for BGP Capability Codes.  Specifically, the range formerly designated "Reserved for Private Use" is divided into three new ranges, respectively designated as "First Come First Served", "Experimental" and "Reserved".</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-scudder-idr-capabilities-registry-change-01' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-scudder-idr-capabilities-registry-change-01.txt' />
</reference>

      </references>
    </references>
    <section anchor="Acknowledgements" numbered="false" toc="default">
      <name>Acknowledgements</name>
      <t>
	Thanks to <contact fullname="Alia Atlas"/>, <contact fullname="Bruno
	Decraene"/>, <contact fullname="Martin Djernaes"/>, <contact fullname="Jie Dong"/>,
	<contact fullname="Jeff Haas"/>, <contact fullname="Sue Hares"/>,
	<contact fullname="Acee Lindem"/>, <contact fullname="Thomas
	Mangin"/>, and <contact fullname="Tom Petch"/> for their
	reviews and comments.</t>
    </section>
  </back>
</rfc>
