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

rfc-editor@rfc-editor.org Thu, 13 March 2025 22:01 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8418CB04BD3; Thu, 13 Mar 2025 15:01:31 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 49317236E58; Thu, 13 Mar 2025 15:01:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9736 on The BGP Monitoring Protocol (BMP) Peer Up Message Namespace
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250313220131.49317236E58@rfcpa.rfc-editor.org>
Date: Thu, 13 Mar 2025 15:01:31 -0700
Message-ID-Hash: MRJGE6HFXYSOU4LORNML6MU5AL4Q6R5N
X-Message-ID-Hash: MRJGE6HFXYSOU4LORNML6MU5AL4Q6R5N
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, grow@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/30cncSsWOYnOZwYPao4UUOJRvos>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

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:    jgs@juniper.net,
                    paolo@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-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team