--- 1/draft-ietf-idr-capabilities-registry-change-08.txt 2020-05-08 10:13:33.046859273 -0700 +++ 2/draft-ietf-idr-capabilities-registry-change-09.txt 2020-05-08 10:13:33.058859434 -0700 @@ -1,19 +1,19 @@ Network Working Group J. Scudder Internet-Draft Juniper Networks -Updates: 5492 (if approved) April 30, 2020 +Updates: 5492 (if approved) May 8, 2020 Intended status: Standards Track -Expires: November 1, 2020 +Expires: November 9, 2020 Revision to Capability Codes Registration Procedures - draft-ietf-idr-capabilities-registry-change-08 + draft-ietf-idr-capabilities-registry-change-09 Abstract This document updates RFC 5492 by making a change to the registration procedures for BGP Capability Codes. Specifically, the range formerly designated "Reserved for Private Use" is divided into three new ranges, respectively designated as "First Come First Served", "Experimental Use" and "Reserved". Status of This Memo @@ -24,21 +24,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on November 1, 2020. + This Internet-Draft will expire on November 9, 2020. Copyright Notice Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -91,72 +91,82 @@ change both makes it clear that code points from this space should not be used long-term or in shipping products, and reduces the consumption of the scarce Capability Code space expended for this purpose. Once classified as Experimental, it should be considered difficult to reclassify the space for some other purpose in the future. The reason for reserving the maximum value is that it may be useful in the future if extension of the number space is needed. + Since the range 128-255 was formerly designated Private Use, + implementors may have chosen to use code points within that range + prior to publication of this document. For this reason, a survey was + conducted beginning August 14, 2015 (version 01 of the individual + draft) to find any such uses. A number were contributed and were + used to seed Table 2. Of course there can be no guarantee that all + uses were discovered, however the likelihood seems high that + remaining uses, if any, genuinely do fall under the intended use of + "Private Use" and are restricted to some special deployment, and are + not in wide use. Furthermore, any remaining uses would be no worse + than any other code point collision, such as occasionally occurs with + code point "squatting", and could be dealt with in the same manner. + 3. IANA Considerations IANA is requested to revise the "Capability Codes" registry in the "Border Gateway Protocol (BGP) Parameters" group as follows. Reference: [RFC5492] and this document. Registration procedures: +---------+-------------------------+ | Range | Registration Procedures | +---------+-------------------------+ | 1-63 | IETF Review | | 64-238 | First Come First Served | | 239-254 | Experimental | +---------+-------------------------+ Table 1 - Note: a separate "owner" column is not provided because the owner of - all registrations, once made, is "IESG". - IANA is requested to perform the following new allocations within the "Capability Codes" registry: - +-------+--------------------------------------------+--------------+ - | Value | Description | Reference / | - | | | Change | - | | | Controller | - +-------+--------------------------------------------+--------------+ - | 128 | Prestandard Route Refresh (deprecated) | (this | - | | | document) | - +-------+--------------------------------------------+--------------+ - | 129 | Prestandard Outbound Route Filtering | (this | - | | (deprecated), prestandard Routing | document) | - | | Policy Distribution (deprecated) | | - +-------+--------------------------------------------+--------------+ - | 130 | Prestandard Outbound Route Filtering | (this | - | | (deprecated) | document) | - +-------+--------------------------------------------+--------------+ - | 131 | Prestandard Multisession (deprecated) | (this | - | | | document) | - +-------+--------------------------------------------+--------------+ - | 184 | Prestandard FQDN (deprecated) | (this | - | | | document) | - +-------+--------------------------------------------+--------------+ - | 185 | Prestandard OPERATIONAL message | (this | - | | (deprecated) | document) | - +-------+--------------------------------------------+--------------+ - | 255 | Reserved | (this | - | | | document) | - +-------+--------------------------------------------+--------------+ + +-------+----------------------------------+-----------+------------+ + | Value | Description | Reference | Change | + | | | | Controller | + +-------+----------------------------------+-----------+------------+ + | 128 | Prestandard Route Refresh | (this | IETF | + | | (deprecated) | document) | | + +-------+----------------------------------+-----------+------------+ + | 129 | Prestandard Outbound Route | (this | IETF | + | | Filtering (deprecated), | document) | | + | | prestandard Routing Policy | | | + | | Distribution (deprecated) | | | + +-------+----------------------------------+-----------+------------+ + | 130 | Prestandard Outbound Route | (this | IETF | + | | Filtering (deprecated) | document) | | + +-------+----------------------------------+-----------+------------+ + | 131 | Prestandard Multisession | (this | IETF | + | | (deprecated) | document) | | + +-------+----------------------------------+-----------+------------+ + | 184 | Prestandard FQDN (deprecated) | (this | IETF | + | | | document) | | + +-------+----------------------------------+-----------+------------+ + | 185 | Prestandard OPERATIONAL message | (this | IETF | + | | (deprecated) | document) | | + +-------+----------------------------------+-----------+------------+ + | 255 | Reserved | (this | IETF | + | | | document) | | + +-------+----------------------------------+-----------+------------+ Table 2 4. Security Considerations This revision to registration procedures does not change the underlying security issues inherent in the existing [RFC5492] and [RFC4271]. 5. Acknowledgements @@ -172,24 +182,20 @@ with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February 2009, . [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, . 6.2. Informative References - [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities - Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, - . - [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006, . Author's Address John Scudder Juniper Networks 1194 N. Mathilda Ave