draft-ietf-idr-bgp-ipv6-rt-constrain-03.txt   draft-ietf-idr-bgp-ipv6-rt-constrain-04.txt 
Network Working Group K. Patel Network Working Group K. Patel
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track R. Raszuk Intended status: Standards Track R. Raszuk
Expires: June 21, 2013 NTT MCL Inc. Expires: February 09, 2014 NTT MCL Inc.
M. Djernaes M. Djernaes
Juniper Networks Juniper Networks
J. Dong J. Dong
M. Chen M. Chen
Huawei Technologies Huawei Technologies
December 18, 2012 August 08, 2013
IPv6 Extensions for Route Target Distribution IPv6 Extensions for Route Target Distribution
draft-ietf-idr-bgp-ipv6-rt-constrain-03 draft-ietf-idr-bgp-ipv6-rt-constrain-04
Abstract Abstract
The current route target distribution specification described in The current route target distribution specification described in
RFC4684 defines Route Target NLRIs of maximum length of 12 bytes. RFC4684 defines Route Target NLRIs of maximum length of 12 bytes.
The IPv6 specific Route Target extended community is defined in The IPv6 specific Route Target extended community is defined in
[RFC5701] as length of 20 bytes. Since the current specification [RFC5701] as length of 20 bytes. Since the current specification
only supports prefixes of maximum length of 12 bytes, the lack of an only supports prefixes of maximum length of 12 bytes, the lack of an
IPv6 specific Route Target reachability information may be a problem IPv6 specific Route Target reachability information may be a problem
when an operator wants to use this application in a pure IPv6 when an operator wants to use this application in a pure IPv6
environment. This document defines an extension that allows BGP to environment. This document defines an extension that allows BGP to
exchange longer length IPv6 Route Target prefixes. exchange longer length IPv6 Route Target prefixes.
Requirements Language Requirements Language
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].
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on June 21, 2013. This Internet-Draft will expire on February 09, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. BGP IPv6 Constrained Route Target Capability . . . . . . . . . 4 2. BGP IPv6 Constrained Route Target Capability . . . . . . . . 2
3. IPv6 Constrained Route Target NLRI Advertisements . . . . . . . 4 3. IPv6 Constrained Route Target NLRI Advertisements . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
The current constrained route distribution specification defined in The current constrained route distribution specification defined in
[RFC4684] supports prefixes with a maximum length of 12 bytes. The [RFC4684] supports prefixes with a maximum length of 12 bytes. The
prefix length needs to be extended to support the IPv6 specific Route prefix length needs to be extended to support the IPv6 specific Route
Target extended community defined in [RFC5701] which is 20 bytes in Target extended community defined in [RFC5701] which is 20 bytes in
length. This document defines an extension to the current length. This document defines an extension to the current
constrained route distribution specification that allows BGP speakers constrained route distribution specification that allows BGP speakers
to distribute longer length Route Target prefixes. A new BGP to distribute longer length Route Target prefixes. A new BGP
skipping to change at page 4, line 42 skipping to change at page 3, line 23
3. IPv6 Constrained Route Target NLRI Advertisements 3. IPv6 Constrained Route Target NLRI Advertisements
Route Target membership NLRI is advertised in BGP UPDATE messages Route Target membership NLRI is advertised in BGP UPDATE messages
using the MP_REACH_NLRI and MP_UNREACH_NLRI attributes as defined in using the MP_REACH_NLRI and MP_UNREACH_NLRI attributes as defined in
[RFC4760]. The NLRI field in the MP_REACH_NLRI and MP_UNREACH_NLRI [RFC4760]. The NLRI field in the MP_REACH_NLRI and MP_UNREACH_NLRI
is a prefix of 0 to 24 octets, encoded as defined in Section 4 of is a prefix of 0 to 24 octets, encoded as defined in Section 4 of
[RFC4760] for all the constrained route distribution. [RFC4760] for all the constrained route distribution.
This prefix is structured as follows: This prefix is structured as follows:
+-------------------------------+ +-------------------------------+
| origin as (4 octets) | | origin as (4 octets) |
+-------------------------------+ +-------------------------------+
| route target (8 or 20 octets)| | route target (8 or 20 octets)|
~ ~ ~ ~
| | | |
+-------------------------------+ +-------------------------------+
Except for the default route target, which is encoded as a zero- Except for the default route target, which is encoded as a zero-
length prefix, the minimum prefix length is 32 bits. As the length prefix, the minimum prefix length is 32 bits. As the origin-
origin-AS field cannot be interpreted as a prefix. AS field cannot be interpreted as a prefix.
Route targets can then be expressed as prefixes, where, for instance, Route targets can then be expressed as prefixes, where, for instance,
a prefix would encompass all route target extended communities a prefix would encompass all route target extended communities
assigned by a given Global Administrator [RFC4360] and [RFC5701]. assigned by a given Global Administrator [RFC4360] and [RFC5701].
Alternatively, route target prefixes could be aggregated however if Alternatively, route target prefixes could be aggregated however if
done so, then only the Local Administrator field of the Route Target done so, then only the Local Administrator field of the Route Target
can be aggregated. Route Target Type and the Global Administrator can be aggregated. Route Target Type and the Global Administrator
Route Target fields MUST not be aggregated. Route Target fields MUST not be aggregated.
The default route target can be used to indicate to a peer the The default route target can be used to indicate to a peer the
skipping to change at page 6, line 18 skipping to change at page 4, line 45
[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
with BGP-4", RFC 5492, February 2009. with BGP-4", RFC 5492, February 2009.
[RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community [RFC5701] Rekhter, Y., "IPv6 Address Specific BGP Extended Community
Attribute", RFC 5701, November 2009. Attribute", RFC 5701, November 2009.
7.2. Informative References 7.2. Informative References
[RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter,
"Multiprotocol Extensions for BGP-4", RFC 4760, "Multiprotocol Extensions for BGP-4", RFC 4760, January
January 2007. 2007.
Authors' Addresses Authors' Addresses
Keyur Patel Keyur Patel
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: keyupate@cisco.com Email: keyupate@cisco.com
Robert Raszuk Robert Raszuk
NTT MCL Inc. NTT MCL Inc.
 End of changes. 11 change blocks. 
28 lines changed or deleted 28 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/