RFC 9515

RFC 9515: Revision to Registration Procedures for Multiple BMP Registries 🦋

Okay bestie, let's talk about RFC 9515 ✨. It was written by John Scudder from Juniper Networks, dated December 2023, and it's a Standards Track doc. It's an IETF publication (ISSN 2070-1721) and it updates RFC 7854, the BGP Monitoring Protocol. The header doesn't list anything it obsoletes, so nothing gets replaced here. It's just giving RFC 7854 a glow-up 💅

---

Abstract

This doc updates RFC 7854 ("BGP Monitoring Protocol (BMP)") by changing how a bunch of its registries get registered 🌸. The main move: any BMP registry that has the range 32768-65530 marked "Specification Required" gets that range redesignated as "First Come First Served". Iconic 💖

Status of This Memo

This is an Internet Standards Track document 🎀

It's a product of the Internet Engineering Task Force (IETF), and 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 of this doc, any errata, and how to send feedback lives at https://www.rfc-editor.org/info/rfc9515. Bookmark it, bestie 🔖

Copyright Notice

Copyright (c) 2023 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. Please read these carefully, because they spell out your rights and restrictions for this doc 📜 Any Code Components pulled out of this document must include Revised BSD License text, as described in Section 4.e of the Trust Legal Provisions. They come without warranty, as described in the Revised BSD License.

Table of Contents

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

---

1. Introduction ✨

Okay so [RFC7854] creates a bunch of IANA registries, and each one has a range of 32768-65530 marked "Specification Required". Every one of those registries also has a big range marked "Standards Action" 👀

Here's the tea: after some experience, two things became clear. First, these two policies are basically the same in practice, even though they look different on paper. [RFC8126] even says that for Specification Required, "Publication of an RFC is an ideal means of achieving this requirement" 📚 Second, it's really desirable to have a super low bar to registration. That helps avoid conflicts from people using unregistered code points, which is the so-called "code point squatting" 🙅‍♀️

So this doc revises the registration procedures, as laid out in Section 2. No cap, it's a glow-up 💅

2. IANA Considerations 🍓

IANA has revised the following registries in the BMP group:

• BMP Statistics Types
• BMP Initiation and Peer Up Information TLVs
• BMP Termination Message TLVs
• BMP Termination Message Reason Codes
• BMP Route Mirroring TLVs
• BMP Route Mirroring Information Codes

For each of these registries, the 32768-65530 ranges that used to be "Specification Required" now have "First Come First Served" as their registration procedures 🎀 Lowkey the cleanest part of the whole doc 🫶

3. Security Considerations 💀

This revision to the registration procedures does not change the underlying security issues inherent in [RFC7854]. So yeah, the security stuff from RFC 7854 is still the same 🔒 Don't skip reading that one, periodt ⚠️

4. Normative References 📖

[RFC7854]  Scudder, J., Ed., Fernando, R., and S. Stuart, "BGP
           Monitoring Protocol (BMP)", RFC 7854,
           DOI 10.17487/RFC7854, June 2016,
           <https://www.rfc-editor.org/info/rfc7854>.

[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 🫶

Huge thanks to Jeff Haas for the review and encouragement, and to Tom Petch for the review too 💜

Author's Address 🧚

John Scudder
Juniper Networks
1194 N. Mathilda Ave
Sunnyvale, CA 94089
United States of America
Email: jgs@juniper.net