idnits 2.17.1 draft-cl-idr-bgp-ext-com-registry-update-00.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 (18 March 2020) is 1499 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) == Missing Reference: 'RFC3692' is mentioned on line 127, but not defined == Unused Reference: 'RFC8126' is defined on line 180, but no explicit reference was found in the text -- 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 (~~), 3 warnings (==), 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 Communications 4 Updates: 7153 (if approved) 18 March 2020 5 Intended status: Standards Track 6 Expires: 19 September 2020 8 BGP Extended Community Registries Update 9 draft-cl-idr-bgp-ext-com-registry-update-00 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. 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 September 2020. 37 Copyright Notice 39 Copyright (c) 2020 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 Simplified BSD License text 48 as described in Section 4.e of the Trust Legal Provisions and are 49 provided without warranty as described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 55 2.1. Registry: BGP Transitive Extended Community Types . . . . 2 56 2.2. Registry: Generic Transitive Experimental Use Extended 57 Community Sub-Types . . . . . . . . . . . . . . . . . . . 3 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 . . . . . . . . . . . . . . . . . 4 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) with 75 Experimental Use registration procedure. Out of this experimental 76 range the types 0x80, 0x81, 0x82 have been assigned via [RFC5575] and 77 [RFC7674]. The primary use for those types and sub-type registries 78 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 first come first serve. 85 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 update the Name of the Type Values 91 according to Table 1 and append a reference to this document to the 92 existing references. 94 +-------+----------------------------------------------+-----------+ 95 | Type | Name | Reference | 96 | Value | | | 97 +=======+==============================================+===========+ 98 | 0x80 | Generic Transitive Extended Community (Sub- | [add this | 99 | | Types are defined in the "Generic Transitive | document] | 100 | | Extended Community Sub-Types" Registry) | | 101 +-------+----------------------------------------------+-----------+ 102 | 0x81 | Generic Transitive Extended Community Part 2 | [add this | 103 | | (Sub-Types are defined in the "Generic | document] | 104 | | Transitive Extended Community Part 2 Sub- | | 105 | | Types" Registry) | | 106 +-------+----------------------------------------------+-----------+ 107 | 0x82 | Generic Transitive Extended Community Part 3 | [add this | 108 | | (Sub-Types are defined in the "Generic | document] | 109 | | Transitive Extended Community Part 3 Sub- | | 110 | | Types" Registry) | | 111 +-------+----------------------------------------------+-----------+ 113 Table 1: Registry: BGP Transitive Extended Community Types 115 Furthermore IANA is requested to change the registration procedures 116 of this registry of Type Values 0x80 thru 0x82 to First Come First 117 Serve. The resulting Registration Procedures should read as in 118 Table 2. 120 +-----------+-----------------------------------------------+ 121 | Range | Registration Procedures | 122 +===========+===============================================+ 123 | 0x00-0x3f | First Come First Served | 124 +-----------+-----------------------------------------------+ 125 | 0x80-0x82 | First Come First Served (see [this document]) | 126 +-----------+-----------------------------------------------+ 127 | 0x83-0x8f | Reserved for Experimental Use (see [RFC3692]) | 128 +-----------+-----------------------------------------------+ 129 | 0x90-0xbf | Standards Action | 130 +-----------+-----------------------------------------------+ 132 Table 2: Registration Procedures: BGP Transitive Extended 133 Community Types 135 2.2. Registry: Generic Transitive Experimental Use Extended Community 136 Sub-Types 138 IANA maintains a registry entitled "Generic Transitive Experimental 139 Use Extended Community Sub-Types". IANA is requested update the 140 registry title to: 142 "Generic Transitive Extended Community Sub-Types" 144 2.3. Registry: Generic Transitive Experimental Use Extended Community 145 Part 2 Sub-Types 147 IANA maintains a registry entitled "Generic Transitive Experimental 148 Use Extended Community Part 2 Sub-Types". IANA is requested update 149 the registry title to: 151 "Generic Transitive Extended Community Part 2 Sub-Types" 153 2.4. Registry: Generic Transitive Experimental Use Extended Community 154 Part 3 Sub-Types 156 IANA maintains a registry entitled "Generic Transitive Experimental 157 Use Extended Community Part 3 Sub-Types". IANA is requested update 158 the registry title to: 160 "Generic Transitive Extended Community Part 3 Sub-Types" 162 3. Security Considerations 164 There are no direct security considerations arising from this 165 document. 167 4. Acknowledgements 169 The author wants to thank Alvaro Retana, who pointed out, that the 170 IANA registry contains misleading entries in this context. 172 5. References 174 5.1. Normative References 176 [RFC7153] Rosen, E. and Y. Rekhter, "IANA Registries for BGP 177 Extended Communities", RFC 7153, DOI 10.17487/RFC7153, 178 March 2014, . 180 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 181 Writing an IANA Considerations Section in RFCs", BCP 26, 182 RFC 8126, DOI 10.17487/RFC8126, June 2017, 183 . 185 5.2. Informative References 187 [RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., 188 and D. McPherson, "Dissemination of Flow Specification 189 Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009, 190 . 192 [RFC7674] Haas, J., Ed., "Clarification of the Flowspec Redirect 193 Extended Community", RFC 7674, DOI 10.17487/RFC7674, 194 October 2015, . 196 Author's Address 198 Christoph Loibl 199 Next Layer Communications 200 Mariahilfer Guertel 37/7 201 1150 Vienna 202 Austria 204 Phone: +43 664 1176414 205 Email: cl@tix.at