RFC 9515: Revision to Registration Procedures for Multiple BMP Registries
In plain English — editorial summary, not part of the RFC
This document updates RFC 7854, "BGP Monitoring Protocol (BMP)", by changing the registration procedures for several registries. Specifically, any BMP registry with a range of 32768-65530 designated "Specification Required" has that range redesignated as "First Come First Served".
Document record
- Document ID
- RFC9515
- Published
- December 2023
- Authors
- J. Scudder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 3
- Also known as
- —
- Updates:
- RFC 7854
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9736The BGP Monitoring Protocol (BMP) Peer Up Message NamespaceCurrent
March 2025
- RFC 9972Advanced BGP Monitoring Protocol (BMP) Statistics TypesCurrent
May 2026
- RFC 9815BGP Link State (BGP-LS) Shortest Path First (SPF) RoutingCurrent
July 2025
- RFC 9107BGP Optimal Route Reflection (BGP ORR)Current
August 2021
- RFC 9072Extended Optional Parameters Length for BGP OPEN MessageCurrent
July 2021
- RFC 8810Revision to Capability Codes Registration ProceduresCurrent
August 2020
- RFC 8538Notification Message Support for BGP Graceful RestartCurrent
March 2019
- RFC 7947Internet Exchange BGP Route ServerCurrent
September 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?