<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" ipr="trust200902" docName="draft-ietf-lsr-labv-registration-03" number="9650" category="std" consensus="true" submissionType="IETF" updates="5029" obsoletes="" xml:lang="en" tocInclude="true" sortRefs="true" symRefs="true" prepTime="2024-08-26T22:57:52" indexInclude="true" scripts="Common,Latin" tocDepth="3">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-lsr-labv-registration-03" rel="prev"/>
  <link href="https://dx.doi.org/10.17487/rfc9650" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <front>
    <title abbrev="Link-Attribute Bit Values Registration">Revision to Registration Procedures for IS-IS Neighbor Link-Attribute Bit Values</title>
    <seriesInfo name="RFC" value="9650" stream="IETF"/>
    <author initials="T." surname="Li" fullname="Tony Li">
      <organization showOnFrontPage="true">Juniper Networks</organization>
      <address>
        <email>tony.li@tony.li</email>
      </address>
    </author>
    <date month="08" year="2024"/>
    <area>RTG</area>
    <workgroup>lsr</workgroup>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">RFC 5029, "Definition of an IS-IS Link Attribute Sub-TLV", defines an IANA
      registry called "IS-IS Neighbor Link-Attribute Bit Values". This
document changes the registration procedure for that registry from
"Standards Action" to "Expert Review". This document updates RFC 5029.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="https://www.rfc-editor.org/info/rfc9650" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2024 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
              <li pn="section-toc.1-1.4.2.1">
                <t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.4.2.2">
                <t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgements">Acknowledgements</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-address">Author's Address</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section anchor="introduction" numbered="true" removeInRFC="false" toc="include" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1"><xref target="RFC5029" format="default" sectionFormat="of" derivedContent="RFC5029"/> defines the "IS-IS Neighbor Link-Attribute Bit Values"
registry and specifies a registration procedure of "Standards
Action". In practice, this registration procedure is unnecessarily
restrictive, as it prevents allocation of bits to experimental
protocols, which in turn increases the risk of conflicts introduced by
use of unregistered code points (so-called "code point squatting").</t>
      <t indent="0" pn="section-1-2">Accordingly, this document changes the registration procedure for the
registry, as described in <xref target="IANA" format="default" sectionFormat="of" derivedContent="Section 2"/>.</t>
    </section>
    <section anchor="IANA" numbered="true" removeInRFC="false" toc="include" pn="section-2">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-2-1">IANA has changed the registration procedure for the "IS-IS Neighbor Link-Attribute Bit Values" registry to "Expert Review" <xref target="RFC8126" format="default" sectionFormat="of" derivedContent="RFC8126"/> and has listed this document as a reference for the registry.  General guidance
for the designated experts is defined in <xref target="RFC7370" format="default" sectionFormat="of" derivedContent="RFC7370"/>, and more specific
guidance can be found in <xref target="RFC5029" format="default" sectionFormat="of" derivedContent="RFC5029"/>.</t>
    </section>
    <section anchor="security-considerations" numbered="true" removeInRFC="false" toc="include" pn="section-3">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-3-1">This document does not affect the security issues discussed in <xref target="RFC5029" format="default" sectionFormat="of" derivedContent="RFC5029"/>.</t>
    </section>
  </middle>
  <back>
    <references pn="section-4">
      <name slugifiedName="name-references">References</name>
      <references pn="section-4.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC5029" target="https://www.rfc-editor.org/info/rfc5029" quoteTitle="true" derivedAnchor="RFC5029">
          <front>
            <title>Definition of an IS-IS Link Attribute Sub-TLV</title>
            <author fullname="JP. Vasseur" initials="JP." surname="Vasseur"/>
            <author fullname="S. Previdi" initials="S." surname="Previdi"/>
            <date month="September" year="2007"/>
            <abstract>
              <t indent="0">This document defines a sub-TLV called "Link-attributes" carried within the TLV 22 and used to flood some link characteristics. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5029"/>
          <seriesInfo name="DOI" value="10.17487/RFC5029"/>
        </reference>
      </references>
      <references pn="section-4.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="RFC7370" target="https://www.rfc-editor.org/info/rfc7370" quoteTitle="true" derivedAnchor="RFC7370">
          <front>
            <title>Updates to the IS-IS TLV Codepoints Registry</title>
            <author fullname="L. Ginsberg" initials="L." surname="Ginsberg"/>
            <date month="September" year="2014"/>
            <abstract>
              <t indent="0">This document recommends some editorial changes to the IANA "IS-IS TLV Codepoints" registry to more accurately document the state of the protocol. It also sets out new guidelines for Designated Experts to apply when reviewing allocations from the registry.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="7370"/>
          <seriesInfo name="DOI" value="10.17487/RFC7370"/>
        </reference>
        <reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8126" quoteTitle="true" derivedAnchor="RFC8126">
          <front>
            <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
            <author fullname="M. Cotton" initials="M." surname="Cotton"/>
            <author fullname="B. Leiba" initials="B." surname="Leiba"/>
            <author fullname="T. Narten" initials="T." surname="Narten"/>
            <date month="June" year="2017"/>
            <abstract>
              <t indent="0">Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
              <t indent="0">To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
              <t indent="0">This is the third edition of this document; it obsoletes RFC 5226.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="26"/>
          <seriesInfo name="RFC" value="8126"/>
          <seriesInfo name="DOI" value="10.17487/RFC8126"/>
        </reference>
      </references>
    </references>
    <section anchor="acknowledgements" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgements">Acknowledgements</name>
      <t indent="0" pn="section-appendix.a-1">The author would like to thank <contact fullname="John Scudder"/> for his contributions.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-address">Author's Address</name>
      <author initials="T." surname="Li" fullname="Tony Li">
        <organization showOnFrontPage="true">Juniper Networks</organization>
        <address>
          <email>tony.li@tony.li</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
