Status of This Memo

This is an Internet Standards Track document.¶

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.¶

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained athttps://www.rfc-editor.org/info/rfc9650.¶

Copyright Notice

Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) 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.¶

Table of Contents

1.Introduction

[RFC5029] defines the "IS-IS Neighbor Link-Attribute Bit Values"registry and specifies a registration procedure of "StandardsAction". In practice, this registration procedure is unnecessarilyrestrictive, as it prevents allocation of bits to experimentalprotocols, which in turn increases the risk of conflicts introduced byuse of unregistered code points (so-called "code point squatting").¶

Accordingly, this document changes the registration procedure for theregistry, as described inSection 2.¶

2.IANA Considerations

IANA has changed the registration procedure for the "IS-IS Neighbor Link-Attribute Bit Values" registry to "Expert Review"[RFC8126] and has listed this document as a reference for the registry. General guidancefor the designated experts is defined in[RFC7370], and more specificguidance can be found in[RFC5029].¶

3.Security Considerations

This document does not affect the security issues discussed in[RFC5029].¶

Acknowledgements

The author would like to thankJohn Scudder for his contributions.¶

Author's Address