Internet DRAFT - draft-ietf-idr-capabilities-registry-change
draft-ietf-idr-capabilities-registry-change
Network Working Group J. Scudder
Internet-Draft Juniper Networks
Updates: 5492 (if approved) May 8, 2020
Intended status: Standards Track
Expires: November 9, 2020
Revision to Capability Codes Registration Procedures
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
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
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 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
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Scudder Expires November 9, 2020 [Page 1]
Internet-Draft Capability Codes Registration Procedures May 2020
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
The Border Gateway Protocol uses a mechanism called "Capability
Advertisement" [RFC5492] to enable BGP peers to tell one another
about their optional protocol extensions. These so-called
"Capabilities" are signaled using code points called "Capability
Codes".
[RFC5492] designates the range of Capability Codes 128-255 as
"Reserved for Private Use". Subsequent experience has shown this to
be not only useless, but actively confusing to implementors.
Accordingly, this document revises the registration procedures for
the range 128-255, as follows, using the terminology defined in
[RFC8126]:
o 128-238: First Come First Served
o 239-254: Experimental Use
o 255: Reserved
The procedures for the ranges 1-63 and 64-127 are unchanged,
remaining "IETF Review" and "First Come First Served" respectively.
2. Discussion
The reason for providing an Experimental Use range is to preserve a
range for use during early development. Although there are few
practical differences between Experimental and Private Use, the
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
Scudder Expires November 9, 2020 [Page 2]
Internet-Draft Capability Codes Registration Procedures May 2020
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
IANA is requested to perform the following new allocations within the
"Capability Codes" registry:
Scudder Expires November 9, 2020 [Page 3]
Internet-Draft Capability Codes Registration Procedures May 2020
+-------+----------------------------------+-----------+------------+
| 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
Thanks to Alia Atlas, Bruno Decraene, Martin Djernaes, Jie Dong, Jeff
Haas, Sue Hares, Acee Lindem, Thomas Mangin, and Tom Petch for review
and comments.
6. References
Scudder Expires November 9, 2020 [Page 4]
Internet-Draft Capability Codes Registration Procedures May 2020
6.1. Normative References
[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February
2009, <https://www.rfc-editor.org/info/rfc5492>.
[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,
<https://www.rfc-editor.org/info/rfc8126>.
6.2. Informative References
[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,
<https://www.rfc-editor.org/info/rfc4271>.
Author's Address
John Scudder
Juniper Networks
1194 N. Mathilda Ave
Sunnyvale, CA 94089
USA
Email: jgs@juniper.net
Scudder Expires November 9, 2020 [Page 5]
