<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
    which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
]>

<?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. -->
<!-- Below are generally applicable Processing Instructions (PIs) that
    most I-Ds might want to use.
    (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
    (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" docName="draft-ietf-grow-bmp-registries-change-01.txt"
ipr="trust200902" updates="7854">
  <!-- category values: std, bcp, info, exp, and historic
    ipr values: full3667, noModification3667, noDerivatives3667
    you can add the attributes updates="NNNN" and obsoletes="NNNN"
    they will automatically be output with "(if approved)" -->

  <!-- ***** FRONT MATTER ***** -->

  <front>

    <title abbrev="BMP TLV Registration Procedures">
    Revision to Registration Procedures for Multiple BMP Registries</title>

    <!-- add 'role="editor"' below for the editors if appropriate -->

    <!-- Another author who claims to be an editor -->

    <author fullname="John Scudder" initials="J."
            surname="Scudder">
      <organization>Juniper Networks</organization>

      <address>
        <postal>
          <street>1194 N. Mathilda Ave</street>

          <!-- Reorder these if your country does things differently -->

          <city>Sunnyvale</city>

          <region>CA</region>

          <code>94089</code>

          <country>USA</country>
        </postal>

        <email>jgs@juniper.net</email>

        <!-- uri and facsimile elements may also be added -->
      </address>
    </author>

    <date/>

    <!-- Meta-data Declarations -->

    <area>General</area>

    <workgroup>Network Working Group</workgroup>

    <keyword>IDR</keyword>

<abstract>
<t>
	This document updates RFC 7854, BGP Monitoring Protocol (BMP) by making
	a change to the registration procedures for several registries.
	Specifically, any BMP registry with a range of 32768-65530 designated
	"Specification Required" has that range re-designated as "First Come
	First Served".
</t>
</abstract>

  </front>

  <middle>

<section anchor="introduction" title="Introduction">
<t>
	<xref target="RFC7854"/> creates a number of IANA registries that
	include a range of 32768-65530 designated "Specification Required".
	Each such registry also has a large range designated "Standards
	Action". Subsequent experience has shown two things. First, there is
	less difference between these two policies in practice than there is in
	theory (consider that <xref target="RFC8126"/> explains that for
	Specification Required, "Publication of an RFC is an ideal means of
	achieving this requirement"). Second, it's desirable to have a very low
	bar to registration, to avoid the risk of conflicts introduced by use
	of unregistered code points (so-called "code point squatting"). 
</t>
	
<t>
	Accordingly, this document revises the registration procedures, as given
	in <xref target="IANA"/>.
</t>
</section>

<section anchor="IANA" title="IANA Considerations">
<t>
	IANA is requested to revise the following registries within the BMP
	group:
</t>

<?rfc subcompact="yes" ?>

<t><list style="symbols">
	<t>BMP Statistics Types</t>
	<t>BMP Initiation Message TLVs</t>
	<t>BMP Termination Message TLVs</t>
	<t>BMP Termination Message Reason Codes</t>
	<t>BMP Peer Down Reason Codes</t>
	<t>BMP Route Mirroring TLVs</t>
	<t>BMP Route Mirroring Information Codes</t>
</list></t>
	
<?rfc subcompact="no" ?>

<t>
	For each of these registries, the ranges 32768-65530 whose registration
	procedures were "Specification Required" are revised to have the 
	registration procedures "First Come First Served".
</t>
</section>

<section anchor="Security" title="Security Considerations">
<t>
	This revision to registration procedures does not change the
	underlying security issues inherent in the existing <xref
	target="RFC7854"/>.
</t>
</section>

<section anchor="Acknowledgements" title="Acknowledgements">
<t>
	Thanks to Jeff Haas for review and encouragement.
</t>
</section>

  </middle>

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

  <back>
    <references title="Normative References">
      <!--?rfc include=
      "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
      
	  <?rfc include="reference.RFC.7854.xml"?>
	  <?rfc include="reference.RFC.8126.xml"?>
    </references>
    
  </back>
</rfc>
