RFC 9650

Revision to Registration Procedures for IS-IS Neighbor Link-Attribute Bit Values 🎀

okay bestie, let's get into RFC 9650 🦋 It's a Standards Track doc from Tony Li at Juniper Networks, published August 2024 (ISSN 2070-1721). It updates RFC 5029 and doesn't obsolete anything. The whole point is changing one registry's rules so experimental protocols can grab bits too 💅

Abstract ✨

okay so RFC 5029 is the one that defines the "IS-IS Neighbor Link-Attribute Bit Values" registry from IANA, and it sets the registration procedure to "Standards Action". this doc flips that to "Expert Review" 🔥 and it updates RFC 5029 while it's at it.

Status of This Memo 📜

this is an Internet Standards Track document. 🌸

it's a product of the Internet Engineering Task Force (IETF), so it represents the consensus of the IETF community. it got public review and was approved for publication by the Internet Engineering Steering Group (IESG). if you want more on Internet Standards, check out Section 2 of RFC 7841.

info about the current status, any errata, and how to give feedback lives at https://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 doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) as they stand on the publication date. read them carefully, because they spell out your rights and restrictions for this doc 🙈

code components pulled out of this doc have to include Revised BSD License text, as described in Section 4.e of the Trust Legal Provisions. they come without warranty, same as the Revised BSD License says.

Table of Contents 🧚

• 1. Introduction
• 2. IANA Considerations
• 3. Security Considerations
• 4. References
  • 4.1. Normative References
  • 4.2. Informative References
• Acknowledgements
• Author's Address

1. Introduction 💅

[RFC5029] defines the "IS-IS Neighbor Link-Attribute Bit Values" registry and sets its registration procedure to "Standards Action". ngl, that's unnecessarily restrictive 😭 because it blocks bits from going to experimental protocols. and when nobody can officially register a code point, people just start using unregistered ones anyway ("code point squatting"), which makes conflicts more likely. not ideal, bestie 💀

so this doc changes the registration procedure for the registry, as Section 2 explains. 👑

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 guidance for the designated experts is in [RFC7370], and the more specific guidance is in [RFC5029].

3. Security Considerations 💀

okay the security part is short, but it's a big deal 🔥 this doc does not affect the security issues discussed in [RFC5029]. so nothing new to worry about on that front, the existing concerns from RFC 5029 are still the ones that matter 🫶

4. References 🌸

4.1. Normative References 💜

[RFC5029]  Vasseur, JP. and S. Previdi, "Definition of an IS-IS Link
           Attribute Sub-TLV", RFC 5029, DOI 10.17487/RFC5029,
           September 2007, <https://www.rfc-editor.org/info/rfc5029>.

4.2. Informative References 🧚

[RFC7370]  Ginsberg, L., "Updates to the IS-IS TLV Codepoints
           Registry", RFC 7370, DOI 10.17487/RFC7370, September 2014,
           <https://www.rfc-editor.org/info/rfc7370>.

[RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
           Writing an IANA Considerations Section in RFCs", BCP 26,
           RFC 8126, DOI 10.17487/RFC8126, June 2017,
           <https://www.rfc-editor.org/info/rfc8126>.

Acknowledgements 🫶

the author would like to thank John Scudder for his contributions 🎀

Author's Address 💖

Tony Li Juniper Networks Email: tony.li@tony.li

---

that's the whole RFC, bestie ✨🦋🌈