RFC 9515 on Revision to Registration Procedures for Multiple BMP Registries
rfc-editor@rfc-editor.org Fri, 08 December 2023 21:17 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E022C48EDE3; Fri, 8 Dec 2023 13:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f7HX01exOS3Q; Fri, 8 Dec 2023 13:17:53 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25E25C4B62B8; Fri, 8 Dec 2023 13:17:53 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id ED2081996100; Fri, 8 Dec 2023 13:17:52 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9515 on Revision to Registration Procedures for Multiple BMP Registries
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, grow@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231208211752.ED2081996100@rfcpa.amsl.com>
Date: Fri, 08 Dec 2023 13:17:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/WYjACv_uOb260LfVW4Vm9rDoigg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Dec 2023 21:17:57 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9515
Title: Revision to Registration Procedures for
Multiple BMP Registries
Author: J. Scudder
Status: Standards Track
Stream: IETF
Date: December 2023
Mailbox: jgs@juniper.net
Pages: 3
Updates: RFC 7854
I-D Tag: draft-ietf-grow-bmp-registries-change-04.txt
URL: https://www.rfc-editor.org/info/rfc9515
DOI: 10.17487/RFC9515
This document updates RFC 7854, "BGP Monitoring Protocol (BMP)", by
changing the registration procedures for several registries.
Specifically, any BMP registry with a range of 32768-65530 designated
"Specification Required" has that range redesignated as "First Come
First Served".
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
Association Management Solutions, LLC