Last Call: <draft-ietf-grow-bmp-peer-up-04.txt> (BMP Peer Up Message Namespace) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 03 September 2024 18:36 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-grow-bmp-peer-up-04.txt> (BMP Peer Up Message Namespace) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <172538857583.1440197.6128196574236311628@dt-datatracker-68b7b78cf9-q8rsp>
Date: Tue, 03 Sep 2024 11:36:15 -0700
Message-ID-Hash: XPV6OGJITPARL3TXN2Z4K3HTZHYU5BCA
CC: draft-ietf-grow-bmp-peer-up@ietf.org, grow-chairs@ietf.org, grow@ietf.org
Reply-To: last-call@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/GTOjzn4shn2KwRrfm6mOHl1zb5g>

The IESG has received a request from the Global Routing Operations WG (grow)
to consider the following document: - 'BMP Peer Up Message Namespace'
  <draft-ietf-grow-bmp-peer-up-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-09-17. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   RFC 7854, BMP, uses different message types for different purposes.
   Most of these are Type, Length, Value (TLV) structured.  One message
   type, the Peer Up message, lacks a set of TLVs defined for its use,
   instead sharing a namespace with the Initiation message.  Subsequent
   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 RFC 8671 and RFC 9069 by
   moving the defined codepoints in the newly introduced registry.  The
   changes in this document are formal only, compliant implementations
   of RFC 7854, RFC 8671 and RFC 9069 also comply with this
   specification.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-grow-bmp-peer-up/



No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-grow-bmp-peer-up-04.txt> (… The IESG