RFC 8810 on Revision to Capability Codes Registration Procedures

rfc-editor@rfc-editor.org Tue, 18 August 2020 00:12 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 83C5A3A14B3; Mon, 17 Aug 2020 17:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v1QYuNSS-XbG; Mon, 17 Aug 2020 17:12:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F29F93A148F; Mon, 17 Aug 2020 17:12:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 22E2BF40762; Mon, 17 Aug 2020 17:11:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8810 on Revision to Capability Codes Registration Procedures
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, idr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200818001149.22E2BF40762@rfc-editor.org>
Date: Mon, 17 Aug 2020 17:11:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/k3xGd9OarwKHbgVCxPbx-XcYgsY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 18 Aug 2020 00:12:06 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8810

        Title:      Revision to Capability Codes Registration 
                    Procedures 
        Author:     J. Scudder
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2020
        Mailbox:    jgs@juniper.net
        Pages:      5
        Updates:    RFC 5492

        I-D Tag:    draft-ietf-idr-capabilities-registry-change-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8810

        DOI:        10.17487/RFC8810

This document updates RFC 5492 by making a change to the registration
procedures for BGP Capability Codes. Specifically, the range formerly
designated "Private Use" is divided into three new ranges: "First
Come First Served", "Experimental Use", and "Reserved".

This document is a product of the Inter-Domain Routing 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