RFC 8810

Revision to Capability Codes Registration Procedures

📅 published August 2020, from ietf

Revision to Capability Codes Registration Procedures 🎀

okay bestie, this is RFC 8810, and it's giving standards-track drama in the best way ✨

  • Author: John Scudder, Juniper Networks 💖
  • Category: Standards Track 🧚
  • Date: August 2020 🌸
  • Updates: RFC 5492 🔥
  • Obsoletes: nothing, it's not replacing anyone 💅
  • ISSN: 2070-1721 🦋

Basically, this one tweaks how the BGP Capability Codes registry gets managed. Read on, it's iconic 👑

Abstract ✨

okay so this doc updates RFC 5492 by changing the registration procedures for BGP Capability Codes 💖 The range that used to be called "Private Use" gets split into three new ranges: "First Come First Served", "Experimental Use", and "Reserved" 🎀

Status of This Memo 🌸

This is an Internet Standards Track document 🧚

This doc is a product of the Internet Engineering Task Force (IETF) 💅 It represents the consensus of the IETF community, received public review, and got approved for publication by the Internet Engineering Steering Group (IESG) 👑 For more on Internet Standards, check Section 2 of RFC 7841 🦋

Info about the current status, any errata, and how to give feedback lives at https://www.rfc-editor.org/info/rfc8810 🫶

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) as in effect on the date of publication 🍓 Please review these carefully, because they describe your rights and restrictions for this doc 🙈 Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they come without warranty as described in the Simplified BSD License 💅

Table of Contents 🦋

  • 1. Introduction ✨
  • 2. Discussion 💖
  • 3. IANA Considerations 🎀
  • 4. Security Considerations 💀
  • 5. References 🌸
    • 5.1. Normative References 🧚
    • 5.2. Informative References 🌈
  • Acknowledgements 🫶
  • Author's Address 💜

1. Introduction 🧚

okay so BGP uses a mechanism called "Capability Advertisement" [RFC5492] so BGP peers can tell each other about their optional protocol extensions 🌸 These so-called "Capabilities" get signaled using code points called "Capability Codes" 💖

[RFC5492] designates the range of Capability Codes 128-255 as "Private Use" 🙈 Subsequent experience showed this was not only useless but actively confusing to implementors 💀

So this document revises the registration procedures for the range 128-255, using the terminology defined in [RFC8126] 🎀

128-238: First Come First Served 239-254: Experimental Use 255: Reserved

The procedures for the ranges 1-63 and 64-127 are unchanged, and they're still "IETF Review" and "First Come First Served", respectively 💅 The full range for "First Come First Served" is now 64-238 👑

2. Discussion 🦋

The reason for the "Experimental Use" range is to preserve a range for use during early development ✨ There are few practical differences between "Experimental Use" and "Private Use", but this change makes it clear that code points from this space should not be used long term or in shipping products 💖 It also reduces the consumption of the scarce Capability Codes space spent on this purpose 🎀 Once something is classified as "Experimental Use", it should be considered difficult to reclassify that space for some other purpose later 🌸

The reason for reserving the maximum value is that it may be useful in the future if the number space needs extending 🧚

Since 128-255 used to be "Private Use", implementors may have picked code points in that range before this document was published 😭 So a survey started August 14, 2015 (version 01 of the individual draft [SCUDDER]) to find any such uses 🫶 A number were contributed and used to seed Table 2 🌈 Of course, there's no guarantee every use was found 💀 But the likelihood seems high that any remaining uses really do fall under the intended "Private Use" purpose, are restricted to some special deployment, and aren't in wide use 💜 And even if some remain, they'd be no worse than any other code point collision, like occasional "squatting", and could be handled the same way 🍓

3. IANA Considerations 👑

IANA has revised the "Capability Codes" registry as follows 🎀

Reference: [RFC5492] and this document 🦋

Note: The IETF will be the Change Controller for all future registrations 💅

Registration procedures 🌸

+=========+=========================+
|  Range  | Registration Procedures |
+=========+=========================+
|   1-63  | IETF Review             |
+---------+-------------------------+
|  64-238 | First Come First Served |
+---------+-------------------------+
| 239-254 | Experimental Use        |
+---------+-------------------------+

                  Table 1

IANA has made the following new allocations within the "Capability Codes" registry 🧚

+=======+============================+===========+============+
| Value | Description                | Reference | Change     |
|       |                            |           | Controller |
+=======+============================+===========+============+
|  128  | Prestandard Route Refresh  | RFC 8810  | IETF       |
|       | (deprecated)               |           |            |
+-------+----------------------------+-----------+------------+
|  129  | Prestandard Outbound Route | RFC 8810  | IETF       |
|       | Filtering (deprecated),    |           |            |
|       | prestandard Routing Policy |           |            |
|       | Distribution (deprecated)  |           |            |
+-------+----------------------------+-----------+------------+
|  130  | Prestandard Outbound Route | RFC 8810  | IETF       |
|       | Filtering (deprecated)     |           |            |
+-------+----------------------------+-----------+------------+
|  131  | Prestandard Multisession   | RFC 8810  | IETF       |
|       | (deprecated)               |           |            |
+-------+----------------------------+-----------+------------+
|  184  | Prestandard FQDN           | RFC 8810  | IETF       |
|       | (deprecated)               |           |            |
+-------+----------------------------+-----------+------------+
|  185  | Prestandard OPERATIONAL    | RFC 8810  | IETF       |
|       | message (deprecated)       |           |            |
+-------+----------------------------+-----------+------------+
|  255  | Reserved                   | RFC 8810  | IETF       |
+-------+----------------------------+-----------+------------+

                  Table 2

4. Security Considerations 💀

This revision to the registration procedures does not change the underlying security issues inherent in the existing [RFC5492] and [RFC4271] 😭🫶

5. References 🌈

5.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 🎀

5.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 🦋

[SCUDDER] Scudder, J., "Revision to Capability Codes Registration Procedures", Work in Progress, Internet-Draft, draft-scudder-idr-capabilities-registry-change-01, 14 August 2015, https://tools.ietf.org/html/draft-scudder-idr-capabilities-registry-change-01 👑

Acknowledgements 🫶

Thanks to Alia Atlas, Bruno Decraene, Martin Djernaes, Jie Dong, Jeff Haas, Sue Hares, Acee Lindem, Thomas Mangin, and Tom Petch for their reviews and comments 💜

Author's Address 🧚

John Scudder Juniper Networks 1194 N. Mathilda Ave Sunnyvale, CA 94089 United States of America

Email: jgs@juniper.net 💅

📦 where this page comes from