File formats:

Also available: XML file for editing

 

Status:

PROPOSED STANDARD

Updates:

RFC 7854, RFC 8671, RFC 9069

Authors:

J. Scudder
P. Lucente

Stream:

IETF

Source:

grow (ops)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9736

Discuss this RFC: Send questions or comments to the mailing list grow@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9736

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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.