The BGP Monitoring Protocol Peer Up Message Namespace
RFC 9736, “The BGP Monitoring Protocol Peer Up Message Namespace”, is a Proposed Standard document published in March 2025 by J. Scudder, P. Lucente. It updates RFC 7854, RFC 8671, RFC 9069. The canonical text is published by the RFC Editor.
Abstract
RFC 7854, the BGP Monitoring Protocol (BMP), uses different message types for different purposes. Most of these are structured as Type, Length, Value (TLV). One message type, the Peer Up message, lacks a set of TLVs defined for its use, instead sharing a namespace with the Initiation message. Experience has shown that this namespace sharing was a mistake, as it hampers the extension of the protocol.
This document updates RFC 7854 by creating an independent namespace for the Peer Up message. It also updates RFCs 8671 and 9069 by moving defined codepoints into the newly introduced registry. Compliant implementations of RFCs 7854, 8671, and 9069 also comply with this specification.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 9736 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 9735 Locator/ID Separation Protocol Distinguished Name Encoding
- RFC 9737 Reporting Errors in NFSv4.2 via LAYOUTRETURN
- RFC 9734 X.509 Certificate Extended Key Usage for Instant Messaging URIs
- RFC 9738 IMAP MESSAGELIMIT Extension
- RFC 9733 BRSKI with Alternative Enrollment
- RFC 9739 Protocol Independent Multicast Light
- RFC 9732 A Framework for NRP-Based Enhanced Virtual Private Networks
- RFC 9740 New IPFIX Information Elements for TCP Options and IPv6 Extension Headers