Revision to Capability Codes Registration Procedures
Juniper Networks
1194 N. Mathilda Ave
Sunnyvale
CA
94089
USA
jgs@juniper.net
General
Network Working Group
IDR
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" and "Reserved".
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. BGP Capability Codes do not meet the criteria for
"Private Use" described in
section 4.1. An example of a legitimate "private use" code point might be
a BGP community value assigned for use
within a given Autonomous System, but no analogous use of Capabilities
exists.
Accordingly, this document revises the registration procedures for
the range 128-255, as follows, using the terminology defined in
:
128-238: First Come First Served
239-254: Experimental Use
255: Reserved
The procedures for the ranges 1-63 and 64-127 are unchanged,
remaining "IETF Review" and "First Come First Served" respectively.
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
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.
The reason for designating "IESG" as the change controller for all
registrations is that while it should be easy to obtain a Capability
Code, once registered it's not a trivial matter to safely and
interoperably change the use of that code, and thus working group
consensus should be sought before changes are made to existing
registrations.
Finally, we invite implementors who have used values in the range
128-255 to contribute to this draft, so that the values can be
included in the registry. Values that have been reported, are
included.
IANA is requested to revise the "Capability Codes" registry in the
"Border Gateway Protocol (BGP) Parameters" group as follows.
Reference: and this document.
Registry Owner/Change Controller: IESG
Registration procedures:
Range
Registration Procedures
1-63
IETF Review
64-238
First Come First Served
239-254
Experimental
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
128
Prestandard Route Refresh (deprecated)
(this document)
129
Prestandard Outbound Route Filtering (deprecated),
prestandard draft-li-idr-flowspec-rpd-04 (deprecated)
(this document)
130
Prestandard Outbound Route Filtering (deprecated)
(this document)
255
Reserved
(this document)
This revision to registration procedures does not change the
underlying security issues inherent in the existing and .
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.