draft-ietf-idr-extcomm-iana-00.txt   draft-ietf-idr-extcomm-iana-01.txt 
IDR Working Group Eric C. Rosen IDR Working Group Eric C. Rosen
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Intended Status: Standards Track Intended Status: Standards Track
Updates: 4360,5701 Yakov Rekhter Updates: 4360,5701 Yakov Rekhter
Expires: February 22, 2014 Juniper Networks, Inc. Expires: March 30, 2014 Juniper Networks, Inc.
August 22, 2013 September 30, 2013
IANA Registries for BGP Extended Communities IANA Registries for BGP Extended Communities
draft-ietf-idr-extcomm-iana-00.txt draft-ietf-idr-extcomm-iana-01.txt
Abstract Abstract
This document reorganizes the IANA Registries for the type values and This document reorganizes the IANA Registries for the type values and
sub-type values of BGP Extended Communities attribute and the BGP sub-type values of BGP Extended Communities attribute and the BGP
IPv6-Address-Specific Extended Communities attribute. This is done IPv6-Address-Specific Extended Communities attribute. This is done
in order to remove inter-dependencies among the registries, thus in order to remove inter-dependencies among the registries, thus
making it easier for IANA to determine which codepoints are available making it easier for IANA to determine which codepoints are available
for assignment in which registries. This document also clarifies the for assignment in which registries. This document also clarifies the
information that must be provided to IANA when requesting an information that must be provided to IANA when requesting an
skipping to change at page 7, line 11 skipping to change at page 7, line 11
in an IPv6-Address-Specific Extended Community registry that is in an IPv6-Address-Specific Extended Community registry that is
allocated in some other registry, it is the responsibility of the allocated in some other registry, it is the responsibility of the
requester to explicitly ask this of IANA. requester to explicitly ask this of IANA.
5. IANA Considerations 5. IANA Considerations
IANA is to replace the pre-existing BGP Extended Communities IANA is to replace the pre-existing BGP Extended Communities
registries with the registries described in this section. registries with the registries described in this section.
Any Extended Community Type or Sub-type codepoints allocated by IANA Any Extended Community Type or Sub-type codepoints allocated by IANA
between the date of this document that the date at which the between the date of this document and the date at which the
registries are reorganized must also be incorporated into the new registries are reorganized must also be incorporated into the new
registry organization. The authors will work with IANA to ensure registry organization. The authors will work with IANA to ensure
that this is done correctly. that this is done correctly.
The registries reproduced below do not include the "references" or The registries reproduced below do not include the "references" or
"date" fields of the registries, because it is difficult to "date" fields of the registries, because it is difficult to
incorporate those within the 72-character line limitation of RFCs. incorporate those within the 72-character line limitation of RFCs.
The references and associated dates must be copied from the current The references and associated dates must be copied from the current
registries when the new registries are introduced; the authors will registries when the new registries are introduced; the authors will
work with IANA to ensure this this information is carried over work with IANA to ensure that this information is carried over
correctly to the new registry organization. correctly to the new registry organization.
5.1. Registries for the TYPE Field 5.1. Registries for the TYPE Field
5.1.1. Transitive Types 5.1.1. Transitive Types
This registry contains values of the high-order octet (the "Type This registry contains values of the high-order octet (the "Type
Field") of a Transitive Extended Community. Field") of a Transitive Extended Community.
Registry Name: BGP TRANSITIVE EXTENDED COMMUNITY TYPES Registry Name: BGP TRANSITIVE EXTENDED COMMUNITY TYPES
skipping to change at page 15, line 19 skipping to change at page 15, line 19
RANGE REGISTRATION PROCEDURE RANGE REGISTRATION PROCEDURE
0x00-0xBF First Come, First Served 0x00-0xBF First Come, First Served
0xC0-0xFF IETF Review 0xC0-0xFF IETF Review
SUB-TYPE VALUE NAME SUB-TYPE VALUE NAME
0x06 Flow spec traffic-rate 0x06 Flow spec traffic-rate
0x07 Flow spec traffic-action (Use of the Value Field 0x07 Flow spec traffic-action (Use of the Value Field
is defined in the "Traffic Actions Field" is defined in the "Traffic Action Field"
registry) registry)
0x08 Flow spec redirect 0x08 Flow spec redirect
0x09 Flow spec traffic-remarking 0x09 Flow spec traffic-remarking
0x0A Layer2 Info Extended Community 0x0A Layer2 Info Extended Community
Note: RFC 5575 contains narrative text that declares the "Flow spec Note: RFC 5575 contains narrative text that declares the "Flow spec
traffic-rate" to be non-transitive, but then assigns it a codepoint that traffic-rate" to be non-transitive, but then assigns it a codepoint that
indicates it to be transitive. Addressing this error in RFC 5575 is not indicates it to be transitive. Addressing this error in RFC 5575 is not
within the scope of the current document. within the scope of the current document.
 End of changes. 6 change blocks. 
6 lines changed or deleted 6 lines changed or added

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