Network Working Group Yakov Rekhter
Internet Draft Juniper Networks
Expiration Date: March 2009
Intended Status: Proposed Standard
IPv6 Address Specific BGP Extended Communities Attribute
draft-ietf-l3vpn-v6-ext-communities-00.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of 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.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract
Current specifications of BGP Extended Communities [BGP-EXTCOMM]
support IPv4 Address Specific Extended Community, but do not support
IPv6 Address Specific Extended Community. The lack of IPv6 Address
Specific Extended Community may be a problem when an application uses
IPv4 Address Specific Extended Community, and one wants to use this
application in a pure IPv6 environment. This document defines a new
BGP attribute, IPv6 Address Specific Extended Community that
addresses this problem. The IPv6 Address Specific Extended Community
is similar to the IPv4 Address Specific Extended Community, except
that it carries an IPv6 address rather than an IPv4 address.
Expiration Date October 2008 [Page 1]
Internet Draft draft-ietf-l3vpn-v6-ext-communities-00.txt September 2008
Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
1. Introduction
Current specifications of BGP Extended Communities [BGP-EXTCOMM]
support IPv4 Addres Specific Extended Community, but do not support
IPv6 Address Specific Extended Community. The lack of IPv6 Address
Specific Extended Community may be a problem when an application uses
IPv4 Address Specific Extended Community, and one wants to use this
application in a pure IPv6 environment.
Because the BGP Extended Community attribute defines each BGP
Extended Community as being 8 octets long, it is not possible to
define the IPv6 Specific Extended Community using the existing BGP
Extended Community attribute [BGP-EXTCOMM]. Therefore this document
defines a new BGP attribute, IPv6 Address Specific Extended Community
that has structure similar to the IPv4 Address Specific Extended
Community, and thus could be used in a pure IPv6 environment as a
replacement of the IPv4 Address Specific Extended Community.
2. IPv6 Address Specific BGP Extended Communities Attribute
The IPv6 Address Specific Extended Communities Attribute is a
transitive optional BGP attribute [BGP-4]. The attribute consists of
a set of "IPv6 Address Specific extended communities". All routes
with the IPv6 Address Specific Extended Communities attribute belong
to the communities listed in the attribute.
Just like all other BGP extended communities, the IPv6 Address
Specific extended community supports multiple Sub-types.
Each IPv6 Address Specific extended community is encoded as a twenty
octets quantity, as follows:
Expiration Date October 2008 [Page 2]
Internet Draft draft-ietf-l3vpn-v6-ext-communities-00.txt September 2008
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x00 or 0x40 | Sub-Type | Global Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Administrator (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Administrator (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Administrator (cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Global Administrator (cont.) | Local Administrator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The first high-order octet indicates whether a particular Sub-type of
this community is transitive across ASes (0x00), or not (0x40). The
second high-order octet of this extended type is used to indicate
Sub-types. The Sub-types are the same as for IPv4 Address Specific
extended community.
Global Administrator field: 16 octets
This field contains an IPv6 unicast address assigned by one of
the Internet registries.
Local Administrator: 2 octets
The organization which has been assigned the IPv6 address in
the Global Administrator field, can encode any information in
this field. The format and meaning of this value encoded in
this field should be defined by the sub-type of the community.
Expiration Date October 2008 [Page 3]
Internet Draft draft-ietf-l3vpn-v6-ext-communities-00.txt September 2008
3. IANA Considerations
This document defines a new BGP attribute, called IPv6 Address Spe-
cific Extended Community.
This document defines a class of extended communities called IPv6
Address Specific extended community for which the IANA is to create
and maintain a registry entitled "IPv6 Address Specific Extended Com-
munity". Future assignment are to be made using the "First Come
First Served" policy defined in [RFC2434]. The Sub-type values for
the transitive communities of the IPv6 Address Specific Extended Com-
munity class are 0x0100-0x01ff, and for the non-transitive communi-
ties of that class are 0x4100-0x41ff. Assignments consist of a name
and the value.
This document makes the following assignments for the IPv6 Address
Specific extended community types:
Name Sub-type Value
---- --------------
IPv6 address specific Route Target 0x0002
IPv6 address specific Route Origin 0x0003
4. Security Considerations
All the security considerations for BGP Extended Communities apply
here.
5. Acknowledgements
6. Normative References
[BGP-4] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4
(BGP-4)", RFC 4271, January 2006
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T., Alvestrand, H., "Guidelines for Writing an IANA
Considerations Section in RFCs", RFC2434, October 1998.
[BGP-EXTCOMM] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, February 2006.
Expiration Date October 2008 [Page 4]
Internet Draft draft-ietf-l3vpn-v6-ext-communities-00.txt September 2008
7. Non-normative References
8. Author Information
Yakov Rekhter
Juniper Networks, Inc.
e-mail: yakov@juniper.net
9. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain 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; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assur-
ances 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 implementers or users of this specification can
be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
10. Copyright Notice
Copyright (C) The IETF Trust (2008).
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.
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, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
Expiration Date October 2008 [Page 5]
Internet Draft draft-ietf-l3vpn-v6-ext-communities-00.txt September 2008
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.
11. Disclaimer of validity:
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain 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; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. Copies of IPR disclosures made to
the IETF Secretariat 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
implementers or users of this specification can be obtained from the
IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Expiration Date October 2008 [Page 6]