draft-ietf-idr-bgp-ext-communities-07.txt   draft-ietf-idr-bgp-ext-communities-08.txt 
Network Working Group Srihari R. Sangli (Procket Networks)
Network Working Group Srihari R. Sangli (Cisco Systems)
Internet Draft Daniel Tappan (Cisco Systems) Internet Draft Daniel Tappan (Cisco Systems)
Expiration Date: September 2004 Yakov Rekhter (Juniper Networks) Expiration Date: August 2005 Yakov Rekhter (Juniper Networks)
BGP Extended Communities Attribute BGP Extended Communities Attribute
draft-ietf-idr-bgp-ext-communities-07.txt draft-ietf-idr-bgp-ext-communities-08.txt
1. Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
2. Abstract IPR Disclosure Acknowledgement
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Copyright Notice
Copyright (C) The Internet Society (year). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Additional copyright notices are not permitted in IETF Documents
except in the case where such document is the product of a joint
development effort between the IETF and another standards development
organization or the document is a republication of the work of
another standards organization. Such exceptions must be approved on
an individual basis by the IAB.
Disclaimer
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Abstract
This document describes an extension to BGP-4 which may be used to This document describes an extension to BGP-4 which may be used to
provide flexible control over the distribution of routing provide flexible control over the distribution of routing
information. information.
3. Specification of Requirements Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
4. Introduction 1. Introduction
The Extended Community Attribute provides two important enhancements The Extended Community Attribute provides two important enhancements
over the existing BGP Community Attribute: over the existing BGP Community Attribute:
- It provides an extended range, ensuring that communities can be - It provides an extended range, ensuring that communities can be
assigned for a plethora of uses, without fear of overlap. assigned for a plethora of uses, without fear of overlap.
- The addition of a Type field provides structure for the - The addition of a Type field provides structure for the
community space. community space.
The addition of structure allows the usage of policy based on the The addition of structure allows the usage of policy based on the
application for which the community value will be used. For example, application for which the community value will be used. For example,
one can filter out all communities of a particular type, or allow one can filter out all communities of a particular type, or allow
only certain values for a particular type of community. It also only certain values for a particular type of community. It also
allows one to specify whether a particular community is transitive or allows one to specify whether a particular community is transitive or
non-transitive across Autonomous system boundary. Without structure, non-transitive across Autonomous system boundary. Without structure,
this can only be accomplished by explicitly enumerating all community this can only be accomplished by explicitly enumerating all community
values which will be denied or allowed and passed to BGP speakers in values which will be denied or allowed and passed to BGP speakers in
neighboring ASes based on the transitive property. neighboring ASes based on the transitive property.
5. BGP Extended Communities Attribute 2. BGP Extended Communities Attribute
The Extended Communities Attribute is a transitive optional BGP The Extended Communities Attribute is a transitive optional BGP
attribute, with the Type Code 16. The attribute consists of a set of attribute, with the Type Code 16. The attribute consists of a set of
"extended communities". All routes with the Extended Communities "extended communities". All routes with the Extended Communities
attribute belong to the communities listed in the attribute. attribute belong to the communities listed in the attribute.
Each Extended Community is encoded as an eight octet quantity, as Each Extended Community is encoded as an eight octet quantity, as
follows: follows:
- Type Field : 1 or 2 octets - Type Field : 1 or 2 octets
skipping to change at page 4, line 16 skipping to change at page 5, line 5
The encoding of the Value Field is dependent on the "type" of The encoding of the Value Field is dependent on the "type" of
the community as specified by the Type Field. the community as specified by the Type Field.
Two extended communities are declared equal only when all 8 octets of Two extended communities are declared equal only when all 8 octets of
their encoding are equal. their encoding are equal.
The two members in the tuple <Type, Value> should be enumerated to The two members in the tuple <Type, Value> should be enumerated to
specify any community value. Based on the value of the Type field, specify any community value. Based on the value of the Type field,
the remaining octets of the community should be interpreted. the remaining octets of the community should be interpreted.
6. Defined BGP Extended Community Types 3. Defined BGP Extended Community Types
This section introduces a few extended types and defines the format This section introduces a few extended types and defines the format
of the Value Field for those types. The types introduced here provide of the Value Field for those types. The types introduced here provide
"templates", where each template is identified by the high order "templates", where each template is identified by the high order
octet of the extended community Type field, and the lower order octet octet of the extended community Type field, and the lower order octet
(sub-type) is used to indicate a particular type of extended commu- (sub-type) is used to indicate a particular type of extended commu-
nity. nity.
6.1. Two-octet AS specific extended community 3.1. Two-octet AS specific extended community
This is an extended type with Type Field comprising of 2 octets and This is an extended type with Type Field comprising of 2 octets and
Value Field comprising of 6 octets. Value Field comprising of 6 octets.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x00 or 0x40 | Sub-Type | Global Administrator | | 0x00 or 0x40 | Sub-Type | Global Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Local Administrator | | Local Administrator |
skipping to change at page 5, line 13 skipping to change at page 6, line 5
IANA. IANA.
Local Administrator sub-field: 4 octets Local Administrator sub-field: 4 octets
The organization identified by Autonomous System number in the The organization identified by Autonomous System number in the
Global Administrator sub-field, can encode any information in Global Administrator sub-field, can encode any information in
this sub-field. The format and meaning of the value encoded in this sub-field. The format and meaning of the value encoded in
this sub-field should be defined by the sub-type of the commu- this sub-field should be defined by the sub-type of the commu-
nity. nity.
6.2. IPv4 address specific extended community 3.2. IPv4 address specific extended community
This is an extended type with Type Field comprising of 2 octets and This is an extended type with Type Field comprising of 2 octets and
Value Field comprising of 6 octets. Value Field comprising of 6 octets.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x01 or 0x41 | Sub-Type | Global Administrator | | 0x01 or 0x41 | Sub-Type | Global Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Administrator (cont.) | Local Administrator | | Global Administrator (cont.) | Local Administrator |
skipping to change at page 6, line 5 skipping to change at page 6, line 36
This sub-field contains an IPv4 address assigned by IANA. This sub-field contains an IPv4 address assigned by IANA.
Local Administrator sub-field: 2 octets Local Administrator sub-field: 2 octets
The organization which has been assigned the IPv4 address in The organization which has been assigned the IPv4 address in
the Global Administrator sub-field, can encode any information the Global Administrator sub-field, can encode any information
in this sub-field. The format and meaning of this value in this sub-field. The format and meaning of this value
encoded in this sub-field should be defined by the sub-type of encoded in this sub-field should be defined by the sub-type of
the community. the community.
6.3. Four-octet AS specific extended community 3.3. Four-octet AS specific extended community
This is an extended type with Type Field comprising of 2 octets and This is an extended type with Type Field comprising of 2 octets and
Value Field comprising of 6 octets. Value Field comprising of 6 octets.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x02 or 0x42 | Sub-Type | Global Administrator | | 0x02 or 0x42 | Sub-Type | Global Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Administrator (cont.) | Local Administrator | | Global Administrator (cont.) | Local Administrator |
skipping to change at page 6, line 37 skipping to change at page 7, line 23
assigned by IANA. assigned by IANA.
Local Administrator sub-field: 2 octets Local Administrator sub-field: 2 octets
The organization identified by Autonomous System number in the The organization identified by Autonomous System number in the
Global Administrator sub-field, can encode any information in Global Administrator sub-field, can encode any information in
this sub-field. The format and meaning of the value encoded in this sub-field. The format and meaning of the value encoded in
this sub-field should be defined by the sub-type of the commu- this sub-field should be defined by the sub-type of the commu-
nity. nity.
6.4. Opaque extended community 3.4. Opaque extended community
This is an extended type with Type Field comprising of 2 octets and This is an extended type with Type Field comprising of 2 octets and
Value Field comprising of 6 octets. Value Field comprising of 6 octets.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x03 or 0x43 | Sub-Type | Value | | 0x03 or 0x43 | Sub-Type | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont.) | | Value (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The value of the high-order octet of this extended type is either The value of the high-order octet of this extended type is either
0x03 or 0x43. The low-order octet of this extended type is used to 0x03 or 0x43. The low-order octet of this extended type is used to
indicate sub-types. indicate sub-types.
This is a generic community of extended type. The value of the sub- This is a generic community of extended type. The value of the sub-
type which should define the Value Field is to be assigned by IANA. type which should define the Value Field is to be assigned by IANA.
7. Route Target Community 4. Route Target Community
The Route Target Community identifies one or more routers that may The Route Target Community identifies one or more routers that may
receive a set of routes (that carry this Community) carried by BGP. receive a set of routes (that carry this Community) carried by BGP.
This is transitive across the Autonomous system boundary. This is transitive across the Autonomous system boundary.
The Route Target Community is of an extended type. The Route Target Community is of an extended type.
The value of the high-order octet of the Type field for the Route The value of the high-order octet of the Type field for the Route
Target Community can be 0x00, 0x01 or 0x02. The value of the low- Target Community can be 0x00, 0x01 or 0x02. The value of the low-
order octet of the Type field for this community is 0x02. order octet of the Type field for this community is 0x02.
skipping to change at page 8, line 5 skipping to change at page 8, line 29
bering space which is administered by the organization to which the bering space which is administered by the organization to which the
Autonomous System number carried in the Global Administrator subfield Autonomous System number carried in the Global Administrator subfield
has been assigned by an appropriate authority. has been assigned by an appropriate authority.
When the value of the high-order octet of the Type field is 0x01, the When the value of the high-order octet of the Type field is 0x01, the
Local Administrator sub-field contains a number from a numbering Local Administrator sub-field contains a number from a numbering
space which is administered by the organization to which the IP space which is administered by the organization to which the IP
address carried in the Global Administrator subfield has been address carried in the Global Administrator subfield has been
assigned by an appropriate authority. assigned by an appropriate authority.
8. Route Origin Community 5. Route Origin Community
The Route Origin Community identifies one or more routers that inject The Route Origin Community identifies one or more routers that inject
a set of routes (that carry this Community) into BGP. This is transi- a set of routes (that carry this Community) into BGP. This is transi-
tive across the Autonomous system boundary. tive across the Autonomous system boundary.
The Route Origin Community is of an extended type. The Route Origin Community is of an extended type.
The value of the high-order octet of the Type field for the Route The value of the high-order octet of the Type field for the Route
Origin Community can be 0x00, 0x01 or 0x02. The value of the low- Origin Community can be 0x00, 0x01 or 0x02. The value of the low-
order octet of the Type field for this community is 0x03. order octet of the Type field for this community is 0x03.
skipping to change at page 8, line 29 skipping to change at page 9, line 5
bering space which is administered by the organization to which the bering space which is administered by the organization to which the
Autonomous System number carried in the Global Administrator subfield Autonomous System number carried in the Global Administrator subfield
has been assigned by an appropriate authority. has been assigned by an appropriate authority.
When the value of the high-order octet of the Type field is 0x01, the When the value of the high-order octet of the Type field is 0x01, the
Local Administrator sub-field contains a number from a numbering Local Administrator sub-field contains a number from a numbering
space which is administered by the organization to which the IP space which is administered by the organization to which the IP
address carried in the Global Administrator subfield has been address carried in the Global Administrator subfield has been
assigned by an appropriate authority. assigned by an appropriate authority.
9. Link Bandwidth Community 6. Link Bandwidth Community
When a router receives a route from a directly connected external When a router receives a route from a directly connected external
neighbor (the external neighbor that is one IP hop away), and adver- neighbor (the external neighbor that is one IP hop away), and adver-
tises this route (via IBGP) to internal neighbors, as part of this tises this route (via IBGP) to internal neighbors, as part of this
advertisement the router may carry the bandwidth of the link that advertisement the router may carry the bandwidth of the link that
connects the router with the external neighbor. The bandwidth of such connects the router with the external neighbor. The bandwidth of such
a link is carried in the Link Bandwidth Community. a link is carried in the Link Bandwidth Community.
The Link Bandwidth Community is of an extended type. The Link Bandwidth Community is of an extended type.
skipping to change at page 9, line 5 skipping to change at page 9, line 28
0x04. 0x04.
The value of the Global Administrator sub-field in the Value Field The value of the Global Administrator sub-field in the Value Field
MUST represent the Autonomous System of the router that attaches the MUST represent the Autonomous System of the router that attaches the
Link Bandwidth Community. Link Bandwidth Community.
The bandwidth of the link is expressed as 4 octets in IEEE floating The bandwidth of the link is expressed as 4 octets in IEEE floating
point format, units being bytes per second. It is carried in the point format, units being bytes per second. It is carried in the
Local Administrator sub-field of the Value Field. Local Administrator sub-field of the Value Field.
10. Operations 7. Operations
A BGP speaker may use the Extended Communities attribute to control A BGP speaker may use the Extended Communities attribute to control
which routing information it accepts or distributes to its peers. which routing information it accepts or distributes to its peers.
The Extended Community attribute MUST NOT be used to modify the BGP The Extended Community attribute MUST NOT be used to modify the BGP
best path selection algorithm in a way that leads to forwarding best path selection algorithm in a way that leads to forwarding
loops. loops.
A BGP speaker receiving a route that doesn't have the Extended Commu- A BGP speaker receiving a route that doesn't have the Extended Commu-
nities attribute MAY append this attribute to the route when propa- nities attribute MAY append this attribute to the route when propa-
skipping to change at page 10, line 5 skipping to change at page 10, line 18
munity SHOULD be removed from the route. However, the community munity SHOULD be removed from the route. However, the community
SHOULD NOT be removed when advertising the route across the BGP Con- SHOULD NOT be removed when advertising the route across the BGP Con-
federation boundary. federation boundary.
A route may carry both the BGP Communities attribute as defined in A route may carry both the BGP Communities attribute as defined in
[RFC1997]), and the Extended BGP Communities attribute. In this case [RFC1997]), and the Extended BGP Communities attribute. In this case
the BGP Communities attribute is handled as specified in [RFC1997], the BGP Communities attribute is handled as specified in [RFC1997],
and the Extended BGP Communities attribute is handled as specified in and the Extended BGP Communities attribute is handled as specified in
this document. this document.
11. IANA Considerations 8. IANA Considerations
The value of the high-order octet of the Type Field determines if an All the BGP Extended Communities contain a Type field for which IANA
extended community is a regular type or an extended type. The value is to create and maintain a registry entitled BGP Extended Communi-
of the high-order octet of the Type Field defined as regular type (or ties Type.
extended type) for a extended community MUST NOT be reused as the
value of the high-order octet of the Type Field defined as extended
type (or regular type).
For the high-order octet of the Type Field, values 0x00 through 0x03 The Type could be either regular or extended. For a regular Type the
and 0x40 through 0x43 are assigned in this document and are defined IANA allocates an 8-bits value; for an extended Type the IANA allo-
as extended types. cates a 16-bits value.
For the combination of the high-order and low-order octets of the The value allocated for a regular Type MUST NOT be reused as the
Type Field values 0x0002-0x0004, 0x0102-0x0103, and 0x0202-0x0203 are value of the high-order octet when allocating an extended Type. The
assigned in this document. value of the high-order octet allocated for an extended Type MUST NOT
be reused when allocating a regular Type.
The Type Field values 0x04-0x3f and 0x44-0x7f for regular types The Type field indicates where the Extended Community is transitive
(0x0400-0x3fff and 0x4400-0x7fff when expressed as extended types) or not.
are to be assigned by IANA, using the "First Come First Served" pol-
icy defined in RFC 2434.
The extended Type Field values 0x0000-0x0001, 0x0005-0x00ff, Future assignment are to be made using either the Standards Action
0x0100-0x0101, 0x0104-0x01ff, 0x0200-0x0201, 0x0204-0x02ff, process defined in [RFC2434], or the Early IANA Allocation process
0x0300-0x03ff, and 0x4000-0x43ff are to be assigned by IANA, using defined in [kompella-zinin], or the "First Come First Served" policy
the "First Come First Served" policy defined in RFC 2434. defined in [RFC2434].
The Type Field values 0x90-0xbf and 0xd0-0xff for regular types The following table summarizes the ranges for the assignment of
(0x9000-0xbfff and 0xd000-0xffff when expressed as extended types) Types:
are to be assigned by IANA, using the "IETF Consensus" policy defined
in RFC2434.
The Type Field values 0x80-0x8f and 0xc0-0xcf for regular types Type Standard Action First Come
(0x8000-0x8fff and 0xc000-0xcfff when expressed as extended types) Early IANA Allocation First Served
are experimental, and are not to be assigned by IANA. ------------------ --------------------- ------------
12. Security Considerations regular, transitive 0x90-0xbf 0x00-x3f
regular, non-transitive 0xd0-0xff 0x40-0x7f
extended, transitive 0x9000-0xbfff 0x0000-0x3fff
extended, non-transitive 0xd000-0xffff 0x4000-0x7fff
Assignments consist of a name and the value.
The Type values 0x80-0x8f and 0xc0-0xcf for regular Types, and
0x8000-0x8fff and 0xc000-0xcfff for extended Types are experimental,
and are not to be assigned by IANA.
This document defines a class of extended communities called two-
octet AS specific extended community for which the IANA is to create
and maintain a registry entitled Two-octet AS Specific Extended Com-
munity. All the communities in this class are of extended Types.
Future assignment are to be made using the "First Come First Served"
policy defined in [RFC2434]. The Type values for the transitive com-
munities of the two-octet AS specific extended community class are
0x0000-0x00ff, and for the non-transitive communities of that class
are 0x4000-0x40ff. Assignments consist of a name and the value.
This document makes the following assignments for the two-octet AS
specific extended community:
Name Type Value
---- ----------
two-octet AS specific Route Target 0x0002
two-octet AS specific Route Origin 0x0003
two-octet AS specific Link Bandwidth 0x0004
This document defines a class of extended communities called IPv4
address specific extended community for which the IANA is to create
and maintain a registry entitled IPv4 Address Specific Extended
Community. All the communities in this class are of extended Types.
Future assignment are to be made using the "First Come First Served"
policy defined in [RFC2434]. The Type values for the transitive
communities of the two-octet AS specific extended community class
are 0x0100-0x01ff, and for the non-transitive communities of that
class are 0x4100-0x41ff. Assignments consist of a name and the
value.
This document makes the following assignments for the IPv4 address
specific extended community:
Name Type Value
---- ----------
IPv4 address specific Route Target 0x0102
IPv4 address specific Route Origin 0x0103
This document defines a class of extended communities called
four-octet AS specific extended community for which the IANA is to
create and maintain a registry entitled Four-octet AS Specific
Extended Community. All the communities in this class are of
extended Types. Future assignment are to be made using the "First
Come First Served" policy defined in [RFC2434]. The Type values for
the transitive communities of the two-octet AS specific extended
community class are 0x0200-0x02ff, and for the non-transitive
communities of that class are 0x4200-0x42ff. Assignments consist
of a name and the value.
This document makes the following assignments for the four-octet
AS specific extended community:
Name Type Value
---- ----------
four-octet AS specific Route Target 0x0202
four-octet AS specific Route Origin 0x0203
This document defines a class of extended communities called opaque
extended community for which the IANA is to create and maintain a
registry entitled Opaque Extended Community. All the communities
in this class are of extended Types. Future assignment are to be
made using the "First Come First Served" policy defined in [RFC2434].
The Type values for the transitive communities of the opaque extended
community class are 0x0300-0x03ff, and for the non-transitive
communities of that class are 0x4300-0x43ff. Assignments consist
of a name and the value.
When requesting an allocation from more than one registry defined
above, one may ask for allocating the same Type value from
these registries. If possible, the IANA should accommodate such
requests.
9. Security Considerations
This extension to BGP does not change the underlying security issues. This extension to BGP does not change the underlying security issues.
13. Acknowledgements 10. Intellectual Property Considerations
This section is taken from Section 10.4 of [RFC2026].
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to per-
tain to the implementation or use of the technology described in this
document or the extent to which any license under such rights might
or might not be available; neither does it represent that it has made
any effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses
to be made available, or the result of an attempt made to obtain a
general license or permission for the use of such proprietary rights
by implementors or users of this specification can be obtained from
the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
11. Copyright Notice
Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this doc-
ument itself may not be modified in any way, such as by removing the
copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop-
ing Internet standards in which case the procedures for copyrights
defined in the Internet Standards process must be followed, or as
required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER-
CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
12. Acknowledgements
The authors would like to thank John Hawkinson, Jeffrey Haas, Bruno The authors would like to thank John Hawkinson, Jeffrey Haas, Bruno
Rijsman, and Alex Zinin for their suggestions and feedback. Rijsman, and Alex Zinin for their suggestions and feedback.
14. Normative References 13. Normative References
[BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 [BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4
(BGP-4)", RFC 1771, March 1995. (BGP-4)", RFC 1771, March 1995.
[RFC1997] Chandra, R., Traina, P., Li, T., "BGP Communities [RFC1997] Chandra, R., Traina, P., Li, T., "BGP Communities
Attribute", RFC1997, August 1996. Attribute", RFC1997, August 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
15. Author Information 14. Author Information
Srihari R. Sangli Srihari R. Sangli
Procket Networks, Inc. Cisco Systems, Inc.
1100 Cadillac Court
Milpitas, CA - 95035
e-mail: srihari@procket.com
Dan Tappan Dan Tappan
Cisco Systems, Inc. Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
e-mail: tappan@cisco.com e-mail: tappan@cisco.com
Yakov Rekhter Yakov Rekhter
Juniper Networks, Inc. Juniper Networks, Inc.
1194 N. Mathilda Ave 1194 N. Mathilda Ave
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/