A new Request for Comments is now available in online RFC libraries.
RFC 9736
Title: The BGP Monitoring Protocol (BMP)
Peer Up Message Namespace
Author: J. Scudder,
P. Lucente
Status: Standards Track
Stream: IETF
Date: March 2025
Mailbox: j...@juniper.net,
pa...@ntt.net
Pages: 6
Updates: RFC 7854, RFC 8671, RFC 9069
I-D Tag: draft-ietf-grow-bmp-peer-up-05.txt
URL: https://www.rfc-editor.org/info/rfc9736
DOI: 10.17487/RFC9736
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.
This document is a product of the Global Routing Operations Working Group of
the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
GROW mailing list -- grow@ietf.org
To unsubscribe send an email to grow-le...@ietf.org
