--- 1/draft-ietf-idr-extcomm-iana-01.txt 2013-12-04 10:14:29.868612076 -0800 +++ 2/draft-ietf-idr-extcomm-iana-02.txt 2013-12-04 10:14:29.900612930 -0800 @@ -1,37 +1,37 @@ IDR Working Group Eric C. Rosen Internet Draft Cisco Systems, Inc. Intended Status: Standards Track Updates: 4360,5701 Yakov Rekhter -Expires: March 30, 2014 Juniper Networks, Inc. +Expires: June 4, 2014 Juniper Networks, Inc. - September 30, 2013 + December 4, 2013 IANA Registries for BGP Extended Communities - draft-ietf-idr-extcomm-iana-01.txt + draft-ietf-idr-extcomm-iana-02.txt Abstract This document reorganizes the IANA Registries for the type values and sub-type values of BGP Extended Communities attribute and the BGP IPv6-Address-Specific Extended Communities attribute. This is done in order to remove inter-dependencies among the registries, thus making it easier for IANA to determine which codepoints are available for assignment in which registries. This document also clarifies the information that must be provided to IANA when requesting an allocation from one or more of these registries. These changes are compatible with the existing allocations, and thus do not affect protocol implementations. The changes will however impact the "IANA Considerations" sections of future protocol specifications. This - document updates RFCs 4360 and 5701. + document updates RFC 4360 and RFC 5701. Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -72,33 +72,33 @@ 5.1 Registries for the TYPE Field ......................... 7 5.1.1 Transitive Types ...................................... 7 5.1.2 Non-Transitive Types .................................. 9 5.2 Registries for the Sub-Type Field ..................... 10 5.2.1 EVPN Sub-Types ........................................ 10 5.2.2 Transitive Two-Octet AS-Specific Sub-Types ............ 10 5.2.3 Non-Transitive Two-Octet AS-Specific Sub-Types ........ 11 5.2.4 Transitive Four-Octet AS-Specific Sub-Types ........... 12 5.2.5 Non-Transitive Four-Octet AS-Specific Sub-Types ....... 12 5.2.6 Transitive IPv4-Address-Specific Sub-Types ............ 13 - 5.2.7 Non-Transitive IPv4-Address-Specific Sub-Types ........ 13 + 5.2.7 Non-Transitive IPv4-Address-Specific Sub-Types ........ 14 5.2.8 Transitive Opaque Extended Community Sub-Types ........ 14 - 5.2.9 Non-Transitive Opaque Extended Community Sub-Types .... 14 + 5.2.9 Non-Transitive Opaque Extended Community Sub-Types .... 15 5.2.10 Generic Transitive Experimental Use Sub-Types ......... 15 - 5.2.11 Registries for the Value Field ........................ 15 - 5.2.11.1 Traffic Action Field .................................. 15 - 5.3 Registries for IPv6-Address-Specific ECs .............. 15 - 5.3.1 Transitive Types ...................................... 15 - 5.3.2 Non-Transitive Types .................................. 16 - 6 Security Considerations ............................... 16 + 5.2.11 Registries for the Value Field ........................ 16 + 5.2.11.1 Traffic Action Field .................................. 16 + 5.3 Registries for IPv6-Address-Specific ECs .............. 16 + 5.3.1 Transitive Types ...................................... 16 + 5.3.2 Non-Transitive Types .................................. 17 + 6 Security Considerations ............................... 17 7 Acknowledgments ....................................... 17 8 Authors' Addresses .................................... 17 - 9 Normative References .................................. 17 + 9 Normative References .................................. 18 1. Introduction RFC 4360 [RFC4360] defines the BGP "Extended Communities" (EC) attribute. This attribute consists of a sequence of eight-octet "extended communities". The high-order octet is defined to be the "Type" field. Each Type has a range of values for "Transitive Extended Community Types" and a range of values for "Non-transitive Extended Community Types". Some of these ranges are further sub- divided into a sub-range of values to be assigned by IANA under the @@ -233,31 +233,39 @@ IANA is to replace the pre-existing BGP Extended Communities registries with the registries described in this section. Any Extended Community Type or Sub-type codepoints allocated by IANA between the date of this document and the date at which the registries are reorganized must also be incorporated into the new registry organization. The authors will work with IANA to ensure that this is done correctly. The registries reproduced below do not include the "references" or - "date" fields of the registries, because it is difficult to - incorporate those within the 72-character line limitation of RFCs. - The references and associated dates must be copied from the current - registries when the new registries are introduced; the authors will - work with IANA to ensure that this information is carried over - correctly to the new registry organization. + "date" fields for the individual codepoints in the registries, + because it is difficult to incorporate those within the 72-character + line limitation of RFCs. The references and associated dates must be + copied from the current registries when the new registries are + introduced; the authors will work with IANA to ensure that this + information is carried over correctly to the new registry + organization. As this document does not change the usage or + semantics of any of the codepoints, the references associated with + the individual codepoints do not change. + + On the other hand, the reference for each of the registries defined + in this section should be changed to this document. 5.1. Registries for the TYPE Field 5.1.1. Transitive Types + This registry shall contain the following note: + This registry contains values of the high-order octet (the "Type Field") of a Transitive Extended Community. Registry Name: BGP TRANSITIVE EXTENDED COMMUNITY TYPES RANGE REGISTRATION PROCEDURES 0x00-0x3F First Come, First Served 0x80-0x8F Experimental Use (see RFC 3692) 0x90-0xBF Standards Action (early allocation per RFC 4020) @@ -293,20 +301,22 @@ 0x08 Flow spec redirect/mirror to IP next-hop 0x80 Generic Transitive Experimental Extended Community (Sub-Types are defined in the "Generic Transitive Experimental Extended Community Sub-Types" Registry) 5.1.2. Non-Transitive Types + This registry shall contain the following note: + This registry contains values of the high-order octet (the "Type Field") of a Non-transitive Extended Community. Registry Name: BGP NON-TRANSITIVE EXTENDED COMMUNITY TYPES RANGE REGISTRATION PROCEDURES 0x40-0x7F First Come, First Served 0xC0-0xCF Experimental Use (see RFC 3692) 0xD0-0xFF Standards Action (early allocation per RFC 4020) @@ -331,42 +341,46 @@ 0x43 Non-Transitive Opaque Extended Community (Sub-Types are defined in the "Non-Transitive Opaque Extended Community Sub-Types" Registry) 0x44 QoS Marking 5.2. Registries for the Sub-Type Field 5.2.1. EVPN Sub-Types + This registry shall contain the following note: + This registry contains values of the second octet (the "Sub-Type - field") of an extended community, when the value of the first octet - (the "Type field") is 0x06. + field") of an extended community, when the value of the first + octet (the "Type field") is 0x06. Registry Name: EVPN EXTENDED COMMUNITY SUB-TYPES RANGE REGISTRATION PROCEDURE 0x00-0xBF First Come, First Served 0xC0-0xFF IETF Review SUB-TYPE VALUE NAME 0x00 MAC Mobility 0x01 ESI MPLS Label 0x02 ES Import 5.2.2. Transitive Two-Octet AS-Specific Sub-Types + This registry shall contain the following note: + This registry contains values of the second octet (the "Sub-Type - field") of an extended community, when the value of the first octet - (the "Type field") is 0x00. + field") of an extended community, when the value of the first + octet (the "Type field") is 0x00. Registry Name: TRANSITIVE TWO-OCTET AS-SPECIFIC EXTENDED COMMUNITY SUB-TYPES RANGE REGISTRATION PROCEDURE 0x00-0xBF First Come, First Served 0xC0-0xFF IETF Review SUB-TYPE VALUE NAME @@ -374,41 +388,45 @@ 0x02 Route Target 0x03 Route Origin 0x05 OSPF Domain Identifier 0x08 BGP Data Collection 0x09 Source AS 0x0A L2VPN Identifier 0x10 Cisco VPN-Distinguisher 5.2.3. Non-Transitive Two-Octet AS-Specific Sub-Types + This registry shall contain the following note: + This registry contains values of the second octet (the "Sub-Type - field") of an extended community, when the value of the first octet - (the "Type field") is 0x40. + field") of an extended community, when the value of the first + octet (the "Type field") is 0x40. Registry Name: NON-TRANSITIVE TWO-OCTET AS-SPECIFIC EXTENDED COMMUNITY SUB-TYPES RANGE REGISTRATION PROCEDURE 0x00-0xBF First Come, First Served 0xC0-0xFF IETF Review SUB-TYPE VALUE NAME 0x04 Link Bandwidth Extended Community 5.2.4. Transitive Four-Octet AS-Specific Sub-Types + This registry shall contain the following note: + This registry contains values of the second octet (the "Sub-Type - field") of an extended community, when the value of the first octet - (the "Type field") is 0x02. + field") of an extended community, when the value of the first + octet (the "Type field") is 0x02. Registry Name: TRANSITIVE FOUR-OCTET AS-SPECIFIC EXTENDED COMMUNITY SUB-TYPES RANGE REGISTRATION PROCEDURE 0x00-0xBF First Come, First Served 0xC0-0xFF IETF Review SUB-TYPE VALUE NAME @@ -416,41 +434,45 @@ 0x02 Route Target 0x03 Route Origin 0x04 Generic 0x05 OSPF Domain Identifier 0x08 BGP Data Collection 0x09 Source AS 0x10 Cisco VPN Identifier 5.2.5. Non-Transitive Four-Octet AS-Specific Sub-Types + This registry shall contain the following note: + This registry contains values of the second octet (the "Sub-Type - field") of an extended community, when the value of the first octet - (the "Type field") is 0x42. + field") of an extended community, when the value of the first + octet (the "Type field") is 0x42. Registry Name: NON-TRANSITIVE FOUR-OCTET AS-SPECIFIC EXTENDED COMMUNITY SUB-TYPES RANGE REGISTRATION PROCEDURE 0x00-0xBF First Come, First Served 0xC0-0xFF IETF Review SUB-TYPE VALUE NAME 0x04 Generic 5.2.6. Transitive IPv4-Address-Specific Sub-Types + This registry shall contain the following note: + This registry contains values of the second octet (the "Sub-Type - field") of an extended community, when the value of the first octet - (the "Type field") is 0x01. + field") of an extended community, when the value of the first + octet (the "Type field") is 0x01. Registry Name: TRANSITIVE IPV4-ADDRESS-SPECIFIC EXTENDED COMMUNITY SUB-TYPES RANGE REGISTRATION PROCEDURE 0x00-0xBF First Come, First Served 0xC0-0xFF IETF Review SUB-TYPE VALUE NAME @@ -458,60 +480,66 @@ 0x02 Route Target 0x03 Route Origin 0x05 OSPF Domain Identifier 0x07 OSPF Route ID 0x0A L2VPN Identifier 0x0B VRF Route Import 0x10 Cisco VPN-Distinguisher 5.2.7. Non-Transitive IPv4-Address-Specific Sub-Types + This registry shall contain the following note: + This registry contains values of the second octet (the "Sub-Type - field") of an extended community, when the value of the first octet - (the "Type field") is 0x41. + field") of an extended community, when the value of the first + octet (the "Type field") is 0x41. Registry Name: NON-TRANSITIVE IPV4-ADDRESS-SPECIFIC EXTENDED COMMUNITY SUB-TYPES RANGE REGISTRATION PROCEDURE 0x00-0xBF First Come, First Served 0xC0-0xFF IETF Review None Assigned 5.2.8. Transitive Opaque Extended Community Sub-Types + This registry shall contain the following note: + This registry contains values of the second octet (the "Sub-Type - field") of an extended community, when the value of the first octet - (the "Type field") is 0x03. + field") of an extended community, when the value of the first + octet (the "Type field") is 0x03. Registry Name: TRANSITIVE OPAQUE EXTENDED COMMUNITY SUB-TYPES RANGE REGISTRATION PROCEDURE 0x00-0xBF First Come, First Served 0xC0-0xFF IETF Review SUB-TYPE VALUE NAME 0x06 OSPF Route Type 0x0B Color Extended Community 0x0C Encapsulation Extended Community 0x0D Default Gateway 5.2.9. Non-Transitive Opaque Extended Community Sub-Types + This registry shall contain the following note: + This registry contains values of the second octet (the "Sub-Type - field") of an extended community, when the value of the first octet - (the "Type field") is 0x43. + field") of an extended community, when the value of the first + octet (the "Type field") is 0x43. Registry Name: NON-TRANSITIVE OPAQUE EXTENDED COMMUNITY SUB-TYPES RANGE REGISTRATION PROCEDURE 0x00-0xBF First Come, First Served 0xC0-0xFF IETF Review SUB-TYPE VALUE NAME @@ -549,20 +577,22 @@ containing codepoints for the Value Field of an Extended Community. 5.2.11.1. Traffic Action Field This registry does not need to be modified. 5.3. Registries for IPv6-Address-Specific ECs 5.3.1. Transitive Types + This registry shall contain the following note: + This registry contains values of the two high-order octets of an IPv6-Address-Specific Extended Communities attribute. Registry Name: TRANSITIVE IPV6 ADDRESS SPECIFIC EXTENDED COMMUNITY TYPES RANGE REGISTRATION PROCEDURE 0x0000-0x00FF First Come, First Served @@ -570,40 +600,42 @@ 0x0002 Route Target 0x0003 Route Origin 0x0004 OSPFv3 Route Attributes (deprecated) 0x000B VRF Route Import 0x0010 Cisco VPN-Distinguisher 0x0011 UUID-based Route Target 5.3.2. Non-Transitive Types + This registry shall contain the following note: + This registry contains values of the two high-order octets of an IPv6-Address-Specific Extended Communities attribute. Registry Name: NON-TRANSITIVE IPV6 ADDRESS SPECIFIC EXTENDED COMMUNITY TYPES RANGE REGISTRATION PROCEDURE 0x4000-0x40FF First Come, First Served None assigned 6. Security Considerations No security considerations are raised by this document. 7. Acknowledgments - The authors wish to thank Jon Mitchell and Hyojeong Kim for their - comments. + The authors wish to thank Jon Mitchell, Hyojeong Kim, and Pearl Liang + for their review and comments. The authors wish to thank Amanda Baber of IANA for educating us on some of the problems faced by IANA staff when responding to requests for BGP Extended Community Type and Sub-Type codepoint allocations. 8. Authors' Addresses Yakov Rekhter Juniper Networks 1194 North Mathilda Ave.