rfc9184.original   rfc9184.txt 
IDR Working Group C. Loibl Internet Engineering Task Force (IETF) C. Loibl
Internet-Draft next layer Telekom GmbH Request for Comments: 9184 next layer Telekom GmbH
Updates: 7153 8955 (if approved) 16 December 2021 Updates: 7153, 8955 January 2022
Intended status: Standards Track Category: Standards Track
Expires: 19 June 2022 ISSN: 2070-1721
BGP Extended Community Registries Update BGP Extended Community Registries Update
draft-ietf-idr-bgp-ext-com-registry-05
Abstract Abstract
This document updates several BGP Extended Community registries in This document updates several BGP Extended Community registries in
order to replace the "Experimental Use" registration procedure in order to replace the "Experimental Use" registration procedure in
some entries, since their use is clearly not experimental and thus some entries, since their use is clearly not experimental and is thus
misleading. misleading.
This document updates RFC7153 and RFC8955. This document updates RFCs 7153 and 8955.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on 19 June 2022. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9184.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 2. IANA Considerations
2.1. Registry: BGP Transitive Extended Community Types . . . . 3 2.1. Registry: BGP Transitive Extended Community Types
2.2. Registry: Generic Transitive Experimental Use Extended 2.2. Registry: Generic Transitive Experimental Use Extended
Community Sub-Types . . . . . . . . . . . . . . . . . . . 4 Community Sub-Types
2.3. Registry: Generic Transitive Experimental Use Extended 2.3. Registry: Generic Transitive Experimental Use Extended
Community Part 2 Sub-Types . . . . . . . . . . . . . . . 4 Community Part 2 Sub-Types
2.4. Registry: Generic Transitive Experimental Use Extended 2.4. Registry: Generic Transitive Experimental Use Extended
Community Part 3 Sub-Types . . . . . . . . . . . . . . . 4 Community Part 3 Sub-Types
3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 3. Security Considerations
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 4. References
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Normative References
5.1. Normative References . . . . . . . . . . . . . . . . . . 4 4.2. Informative References
5.2. Informative References . . . . . . . . . . . . . . . . . 5 Acknowledgements
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address
1. Introduction 1. Introduction
[RFC7153] reorganizes the IANA registries for the type values and The IANA registries for the type values and sub-type values of the
sub-type values of the BGP Extended Communities attribute. As a BGP Extended Communities attribute were reorganized by [RFC7153]. As
result the IANA maintained registry entitled "BGP Transitive Extended a result, IANA maintains a registry entitled "BGP Transitive Extended
Community Types" includes a range of Type Values (0x80-0x8F) reserved Community Types", which includes a range of type values (0x80-0x8F)
for Experimental Use. Out of this experimental range the types 0x80, reserved for Experimental Use [RFC8126]. Out of this experimental
0x81, 0x82 have been used in [RFC5575] and [RFC7674] (both documents range, types 0x80, 0x81, and 0x82 have been used in [RFC5575] and
rendered Obsolete by [RFC8955]). The primary use for those types and [RFC7674] (both documents were rendered obsolete by [RFC8955]). The
sub-type registries is non experimental. primary use for those types and the sub-type registries is non-
experimental.
Section 2 of this document requests the registry cleanup to reflect Section 2 describes updates to the registry to reflect the actual use
the actual use of those code-points (removing "Experimental Use" from of those code points by changing the registration procedure from
the sub-type registry names) and changes the registration procedure "Experimental Use" to "First Come First Served" [RFC8126] for the
of the types 0x80, 0x81, 0x82 to use the First Come First Served types 0x80-0x82 (and removing "Experimental Use" from the sub-type
policy [RFC8126] and thus updates [RFC7153] and [RFC8955]. registry names), thereby updating [RFC7153] and [RFC8955].
2. IANA Considerations 2. IANA Considerations
2.1. Registry: BGP Transitive Extended Community Types 2.1. Registry: BGP Transitive Extended Community Types
IANA maintains a registry entitled "BGP Transitive Extended Community IANA maintains a registry entitled "BGP Transitive Extended Community
Types". IANA is requested to add [this document] to the Reference of Types". IANA has added RFC 9184 to the reference of this registry.
this registry, update the Name of the Type Values according to They have also updated the name of the type values according to
Table 1 and append a reference to [this document] to the existing Table 1 and added RFC 9184 as a reference for the existing entries.
references.
+=======+==============================================+===========+ +=======+==============================================+===========+
| Type | Name | Reference | | Type | Name | Reference |
| Value | | | | Value | | |
+=======+==============================================+===========+ +=======+==============================================+===========+
| 0x80 | Generic Transitive Extended Community (Sub- | [add this | | 0x80 | Generic Transitive Extended Community (Sub- | RFC 9184 |
| | Types are defined in the "Generic Transitive | document] | | | Types are defined in the "Generic Transitive | |
| | Extended Community Sub-Types" registry) | | | | Extended Community Sub-Types" registry) | |
+-------+----------------------------------------------+-----------+ +-------+----------------------------------------------+-----------+
| 0x81 | Generic Transitive Extended Community Part 2 | [add this | | 0x81 | Generic Transitive Extended Community Part 2 | RFC 9184 |
| | (Sub-Types are defined in the "Generic | document] | | | (Sub-Types are defined in the "Generic | |
| | Transitive Extended Community Part 2 Sub- | | | | Transitive Extended Community Part 2 Sub- | |
| | Types" registry) | | | | Types" registry) | |
+-------+----------------------------------------------+-----------+ +-------+----------------------------------------------+-----------+
| 0x82 | Generic Transitive Extended Community Part 3 | [add this | | 0x82 | Generic Transitive Extended Community Part 3 | RFC 9184 |
| | (Sub-Types are defined in the "Generic | document] | | | (Sub-Types are defined in the "Generic | |
| | Transitive Extended Community Part 3 Sub- | | | | Transitive Extended Community Part 3 Sub- | |
| | Types" registry) | | | | Types" registry) | |
+-------+----------------------------------------------+-----------+ +-------+----------------------------------------------+-----------+
Table 1: Registry: BGP Transitive Extended Community Types Table 1: Registry: BGP Transitive Extended Community Types
Furthermore IANA is requested to change the registration procedures Furthermore, IANA has changed the registration procedures of this
of this registry of Type Values 0x80 thru 0x82 to First Come First registry for type values 0x80 through 0x82 to First Come First Served
Served [RFC8126]. The resulting Registration Procedures should read [RFC8126]. The resulting registration procedures should read as in
as in Table 2. Table 2.
+===========+===============================================+ +===========+===============================================+
| Range | Registration Procedures | | Range | Registration Procedures |
+===========+===============================================+ +===========+===============================================+
| 0x00-0x3f | First Come First Served | | 0x00-0x3f | First Come First Served |
+-----------+-----------------------------------------------+ +-----------+-----------------------------------------------+
| 0x80-0x82 | First Come First Served (see [this document]) | | 0x80-0x82 | First Come First Served (see RFC 9184) |
+-----------+-----------------------------------------------+ +-----------+-----------------------------------------------+
| 0x83-0x8f | Reserved for Experimental Use (see [RFC3692]) | | 0x83-0x8f | Reserved for Experimental Use (see [RFC3692]) |
+-----------+-----------------------------------------------+ +-----------+-----------------------------------------------+
| 0x90-0xbf | Standards Action | | 0x90-0xbf | Standards Action |
+-----------+-----------------------------------------------+ +-----------+-----------------------------------------------+
Table 2: Registration Procedures: BGP Transitive Extended Table 2: Registration Procedures: BGP Transitive Extended
Community Types Community Types
2.2. Registry: Generic Transitive Experimental Use Extended Community 2.2. Registry: Generic Transitive Experimental Use Extended Community
Sub-Types Sub-Types
IANA maintains a registry entitled "Generic Transitive Experimental IANA maintains a registry entitled "Generic Transitive Experimental
Use Extended Community Sub-Types". IANA is requested to add [this Use Extended Community Sub-Types". IANA has added RFC 9184 to the
document] to the Reference of this registry and update the registry reference of this registry and updated the registry title to:
title to:
"Generic Transitive Extended Community Sub-Types" "Generic Transitive Extended Community Sub-Types"
2.3. Registry: Generic Transitive Experimental Use Extended Community 2.3. Registry: Generic Transitive Experimental Use Extended Community
Part 2 Sub-Types Part 2 Sub-Types
IANA maintains a registry entitled "Generic Transitive Experimental IANA maintains a registry entitled "Generic Transitive Experimental
Use Extended Community Part 2 Sub-Types". IANA is requested to add Use Extended Community Part 2 Sub-Types". IANA has added RFC 9184 to
[this document] to the Reference of this registry and update the the reference of this registry and updated the registry title to:
registry title to:
"Generic Transitive Extended Community Part 2 Sub-Types" "Generic Transitive Extended Community Part 2 Sub-Types"
2.4. Registry: Generic Transitive Experimental Use Extended Community 2.4. Registry: Generic Transitive Experimental Use Extended Community
Part 3 Sub-Types Part 3 Sub-Types
IANA maintains a registry entitled "Generic Transitive Experimental IANA maintains a registry entitled "Generic Transitive Experimental
Use Extended Community Part 3 Sub-Types". IANA is requested to add Use Extended Community Part 3 Sub-Types". IANA has added RFC 9184 to
[this document] to the Reference of this registry and update the the reference of this registry and updated the registry title to:
registry title to:
"Generic Transitive Extended Community Part 3 Sub-Types" "Generic Transitive Extended Community Part 3 Sub-Types"
3. Security Considerations 3. Security Considerations
There are no direct security considerations arising from this There are no direct security considerations arising from this
document. document.
4. Acknowledgements 4. References
The author wants to thank Alvaro Retana who pointed out, that the
IANA registry contains misleading entries in this context.
5. References
5.1. Normative References 4.1. Normative References
[RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP [RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP
Extended Communities", RFC 7153, DOI 10.17487/RFC7153, Extended Communities", RFC 7153, DOI 10.17487/RFC7153,
March 2014, <https://www.rfc-editor.org/info/rfc7153>. March 2014, <https://www.rfc-editor.org/info/rfc7153>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>. <https://www.rfc-editor.org/info/rfc8126>.
5.2. Informative References 4.2. Informative References
[RFC3692] Narten, T., "Assigning Experimental and Testing Numbers [RFC3692] Narten, T., "Assigning Experimental and Testing Numbers
Considered Useful", BCP 82, RFC 3692, Considered Useful", BCP 82, RFC 3692,
DOI 10.17487/RFC3692, January 2004, DOI 10.17487/RFC3692, January 2004,
<https://www.rfc-editor.org/info/rfc3692>. <https://www.rfc-editor.org/info/rfc3692>.
[RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., [RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J.,
and D. McPherson, "Dissemination of Flow Specification and D. McPherson, "Dissemination of Flow Specification
Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009, Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009,
<https://www.rfc-editor.org/info/rfc5575>. <https://www.rfc-editor.org/info/rfc5575>.
[RFC7674] Haas, J., Ed., "Clarification of the Flowspec Redirect [RFC7674] Haas, J., Ed., "Clarification of the Flowspec Redirect
Extended Community", RFC 7674, DOI 10.17487/RFC7674, Extended Community", RFC 7674, DOI 10.17487/RFC7674,
October 2015, <https://www.rfc-editor.org/info/rfc7674>. October 2015, <https://www.rfc-editor.org/info/rfc7674>.
[RFC8955] Loibl, C., Hares, S., Raszuk, R., McPherson, D., and M. [RFC8955] Loibl, C., Hares, S., Raszuk, R., McPherson, D., and M.
Bacher, "Dissemination of Flow Specification Rules", Bacher, "Dissemination of Flow Specification Rules",
RFC 8955, DOI 10.17487/RFC8955, December 2020, RFC 8955, DOI 10.17487/RFC8955, December 2020,
<https://www.rfc-editor.org/info/rfc8955>. <https://www.rfc-editor.org/info/rfc8955>.
Acknowledgements
The author wants to thank Alvaro Retana, who pointed out that the
IANA registry contains misleading entries in this context.
Author's Address Author's Address
Christoph Loibl Christoph Loibl
next layer Telekom GmbH next layer Telekom GmbH
Mariahilfer Guertel 37/7 Mariahilfer Guertel 37/7
1150 Vienna 1150 Vienna
Austria Austria
Phone: +43 664 1176414 Phone: +43 664 1176414
Email: cl@tix.at Email: cl@tix.at
 End of changes. 29 change blocks. 
85 lines changed or deleted 80 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/