Skip to main content

The BGP Monitoring Protocol (BMP) Peer Up Message Namespace
RFC 9736

Revision differences

Document history

Date By Action
2025-03-13
(System) IANA registries were updated to include RFC9736
2025-03-13
(System)
Received changes through RFC Editor sync (created document RFC 9736, created became rfc relationship between draft-ietf-grow-bmp-peer-up and RFC 9736, set title to 'The …
Received changes through RFC Editor sync (created document RFC 9736, created became rfc relationship between draft-ietf-grow-bmp-peer-up and RFC 9736, set title to 'The BGP Monitoring Protocol (BMP) Peer Up Message Namespace', set abstract to '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.', set pages to 6, set standardization level to Proposed Standard, added RFC published event at 2025-03-13, created updates relation between RFC 9736 and RFC 7854, created updates relation between RFC 9736 and RFC 8671, created updates relation between RFC 9736 and RFC 9069)
2025-03-13
(System) RFC published