idnits 2.17.00 (12 Aug 2021) /tmp/idnits12508/draft-ietf-idr-bgp-ext-com-registry-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (16 December 2021) is 149 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 5575 (Obsoleted by RFC 8955) -- Obsolete informational reference (is this intentional?): RFC 7674 (Obsoleted by RFC 8955) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR Working Group C. Loibl 3 Internet-Draft next layer Telekom GmbH 4 Updates: 7153 8955 (if approved) 16 December 2021 5 Intended status: Standards Track 6 Expires: 19 June 2022 8 BGP Extended Community Registries Update 9 draft-ietf-idr-bgp-ext-com-registry-05 11 Abstract 13 This document updates several BGP Extended Community registries in 14 order to replace the "Experimental Use" registration procedure in 15 some entries, since their use is clearly not experimental and thus 16 misleading. 18 This document updates RFC7153 and RFC8955. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on 19 June 2022. 37 Copyright Notice 39 Copyright (c) 2021 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 44 license-info) in effect on the date of publication of this document. 45 Please review these documents carefully, as they describe your rights 46 and restrictions with respect to this document. Code Components 47 extracted from this document must include Revised BSD License text as 48 described in Section 4.e of the Trust Legal Provisions and are 49 provided without warranty as described in the Revised BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 55 2.1. Registry: BGP Transitive Extended Community Types . . . . 3 56 2.2. Registry: Generic Transitive Experimental Use Extended 57 Community Sub-Types . . . . . . . . . . . . . . . . . . . 4 58 2.3. Registry: Generic Transitive Experimental Use Extended 59 Community Part 2 Sub-Types . . . . . . . . . . . . . . . 4 60 2.4. Registry: Generic Transitive Experimental Use Extended 61 Community Part 3 Sub-Types . . . . . . . . . . . . . . . 4 62 3. Security Considerations . . . . . . . . . . . . . . . . . . . 4 63 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 64 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 5.1. Normative References . . . . . . . . . . . . . . . . . . 4 66 5.2. Informative References . . . . . . . . . . . . . . . . . 5 67 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 69 1. Introduction 71 [RFC7153] reorganizes the IANA registries for the type values and 72 sub-type values of the BGP Extended Communities attribute. As a 73 result the IANA maintained registry entitled "BGP Transitive Extended 74 Community Types" includes a range of Type Values (0x80-0x8F) reserved 75 for Experimental Use. Out of this experimental range the types 0x80, 76 0x81, 0x82 have been used in [RFC5575] and [RFC7674] (both documents 77 rendered Obsolete by [RFC8955]). The primary use for those types and 78 sub-type registries is non experimental. 80 Section 2 of this document requests the registry cleanup to reflect 81 the actual use of those code-points (removing "Experimental Use" from 82 the sub-type registry names) and changes the registration procedure 83 of the types 0x80, 0x81, 0x82 to use the First Come First Served 84 policy [RFC8126] and thus updates [RFC7153] and [RFC8955]. 86 2. IANA Considerations 87 2.1. Registry: BGP Transitive Extended Community Types 89 IANA maintains a registry entitled "BGP Transitive Extended Community 90 Types". IANA is requested to add [this document] to the Reference of 91 this registry, update the Name of the Type Values according to 92 Table 1 and append a reference to [this document] to the existing 93 references. 95 +=======+==============================================+===========+ 96 | Type | Name | Reference | 97 | Value | | | 98 +=======+==============================================+===========+ 99 | 0x80 | Generic Transitive Extended Community (Sub- | [add this | 100 | | Types are defined in the "Generic Transitive | document] | 101 | | Extended Community Sub-Types" registry) | | 102 +-------+----------------------------------------------+-----------+ 103 | 0x81 | Generic Transitive Extended Community Part 2 | [add this | 104 | | (Sub-Types are defined in the "Generic | document] | 105 | | Transitive Extended Community Part 2 Sub- | | 106 | | Types" registry) | | 107 +-------+----------------------------------------------+-----------+ 108 | 0x82 | Generic Transitive Extended Community Part 3 | [add this | 109 | | (Sub-Types are defined in the "Generic | document] | 110 | | Transitive Extended Community Part 3 Sub- | | 111 | | Types" registry) | | 112 +-------+----------------------------------------------+-----------+ 114 Table 1: Registry: BGP Transitive Extended Community Types 116 Furthermore IANA is requested to change the registration procedures 117 of this registry of Type Values 0x80 thru 0x82 to First Come First 118 Served [RFC8126]. The resulting Registration Procedures should read 119 as in Table 2. 121 +===========+===============================================+ 122 | Range | Registration Procedures | 123 +===========+===============================================+ 124 | 0x00-0x3f | First Come First Served | 125 +-----------+-----------------------------------------------+ 126 | 0x80-0x82 | First Come First Served (see [this document]) | 127 +-----------+-----------------------------------------------+ 128 | 0x83-0x8f | Reserved for Experimental Use (see [RFC3692]) | 129 +-----------+-----------------------------------------------+ 130 | 0x90-0xbf | Standards Action | 131 +-----------+-----------------------------------------------+ 133 Table 2: Registration Procedures: BGP Transitive Extended 134 Community Types 136 2.2. Registry: Generic Transitive Experimental Use Extended Community 137 Sub-Types 139 IANA maintains a registry entitled "Generic Transitive Experimental 140 Use Extended Community Sub-Types". IANA is requested to add [this 141 document] to the Reference of this registry and update the registry 142 title to: 144 "Generic Transitive Extended Community Sub-Types" 146 2.3. Registry: Generic Transitive Experimental Use Extended Community 147 Part 2 Sub-Types 149 IANA maintains a registry entitled "Generic Transitive Experimental 150 Use Extended Community Part 2 Sub-Types". IANA is requested to add 151 [this document] to the Reference of this registry and update the 152 registry title to: 154 "Generic Transitive Extended Community Part 2 Sub-Types" 156 2.4. Registry: Generic Transitive Experimental Use Extended Community 157 Part 3 Sub-Types 159 IANA maintains a registry entitled "Generic Transitive Experimental 160 Use Extended Community Part 3 Sub-Types". IANA is requested to add 161 [this document] to the Reference of this registry and update the 162 registry title to: 164 "Generic Transitive Extended Community Part 3 Sub-Types" 166 3. Security Considerations 168 There are no direct security considerations arising from this 169 document. 171 4. Acknowledgements 173 The author wants to thank Alvaro Retana who pointed out, that the 174 IANA registry contains misleading entries in this context. 176 5. References 178 5.1. Normative References 180 [RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP 181 Extended Communities", RFC 7153, DOI 10.17487/RFC7153, 182 March 2014, . 184 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 185 Writing an IANA Considerations Section in RFCs", BCP 26, 186 RFC 8126, DOI 10.17487/RFC8126, June 2017, 187 . 189 5.2. Informative References 191 [RFC3692] Narten, T., "Assigning Experimental and Testing Numbers 192 Considered Useful", BCP 82, RFC 3692, 193 DOI 10.17487/RFC3692, January 2004, 194 . 196 [RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., 197 and D. McPherson, "Dissemination of Flow Specification 198 Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009, 199 . 201 [RFC7674] Haas, J., Ed., "Clarification of the Flowspec Redirect 202 Extended Community", RFC 7674, DOI 10.17487/RFC7674, 203 October 2015, . 205 [RFC8955] Loibl, C., Hares, S., Raszuk, R., McPherson, D., and M. 206 Bacher, "Dissemination of Flow Specification Rules", 207 RFC 8955, DOI 10.17487/RFC8955, December 2020, 208 . 210 Author's Address 212 Christoph Loibl 213 next layer Telekom GmbH 214 Mariahilfer Guertel 37/7 215 1150 Vienna 216 Austria 218 Phone: +43 664 1176414 219 Email: cl@tix.at