draft-ietf-idr-legacy-rtc-01.txt   draft-ietf-idr-legacy-rtc-02.txt 
Network Working Group P. Mohapatra Network Working Group P. Mohapatra
Internet-Draft A. Sreekantiah Internet-Draft Cumulus Networks
Intended status: Standards Track K. Patel Intended status: Standards Track A. Sreekantiah
Expires: September 14, 2013 B. Pithawala Expires: April 05, 2014 K. Patel
B. Pithawala
Cisco Systems Cisco Systems
A. Lo A. Lo
Arista Networks Arista Networks
March 13, 2013 October 02, 2013
Automatic Route Target Filtering for legacy PEs Automatic Route Target Filtering for legacy PEs
draft-ietf-idr-legacy-rtc-01.txt draft-ietf-idr-legacy-rtc-02.txt
Abstract Abstract
This document describes a simple procedure that allows "legacy" BGP This document describes a simple procedure that allows "legacy" BGP
speakers to exchange route target membership information in BGP speakers to exchange route target membership information in BGP
without using mechanisms specified in [RFC4684]. The intention of without using mechanisms specified in [RFC4684]. The intention of
the proposed technique is to help in partial deployment scenarios and the proposed technique is to help in partial deployment scenarios and
is not meant to replace [RFC4684]. is not meant to replace [RFC4684].
Status of This Memo Status of This Memo
skipping to change at page 1, line 38 skipping to change at page 1, line 39
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 September 14, 2013. This Internet-Draft will expire on April 05, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
skipping to change at page 2, line 28 skipping to change at page 2, line 29
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Basic Idea . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Basic Idea . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Detailed Operation . . . . . . . . . . . . . . . . . . . . . 3 3. Detailed Operation . . . . . . . . . . . . . . . . . . . . . 3
3.1. Legacy PE Behavior . . . . . . . . . . . . . . . . . . . 3 3.1. Legacy PE Behavior . . . . . . . . . . . . . . . . . . . 3
3.2. RR Behavior . . . . . . . . . . . . . . . . . . . . . . . 5 3.2. RR Behavior . . . . . . . . . . . . . . . . . . . . . . . 6
3.2.1. Generating Route Target Membership NLRIs for the 3.2.1. Generating Route Target Membership NLRIs for the
legacy PE clients . . . . . . . . . . . . . . . . . . 6 legacy PE clients . . . . . . . . . . . . . . . . . . 6
4. ROUTE_FILTER Community . . . . . . . . . . . . . . . . . . . 6 4. ROUTE_FILTER Community . . . . . . . . . . . . . . . . . . . 7
5. Deployment Considerations . . . . . . . . . . . . . . . . . . 7 5. Deployment Considerations . . . . . . . . . . . . . . . . . . 8
6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9. Security Considerations . . . . . . . . . . . . . . . . . . . 7 9. Security Considerations . . . . . . . . . . . . . . . . . . . 8
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 8
10.2. Informational References . . . . . . . . . . . . . . . . 8 10.2. Informational References . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
[RFC4684] provides a powerful and general means for BGP speakers to [RFC4684] provides a powerful and general means for BGP speakers to
exchange and propagate Route Target reachability information and exchange and propagate Route Target reachability information and
constrain VPN route distribution to achieve high scale. However, it constrain VPN route distribution to achieve high scale. However, it
requires that all the BGP speakers in the network are upgraded to requires that all the BGP speakers in the network are upgraded to
support this functionality. For example, in a network with route support this functionality. For example, in a network with route
reflectors (RR), if one PE client in the cluster doesn't support reflectors (RR), if one PE client in the cluster doesn't support
constrained distribution, the cluster degenerates into storing and constrained distribution, the cluster degenerates into storing and
skipping to change at page 4, line 22 skipping to change at page 4, line 15
route-filter VRF. route-filter VRF.
o The translation of the IRTs is necessary in order to refrain from o The translation of the IRTs is necessary in order to refrain from
importing "route-filter" VRF routes into VPN VRFs that would importing "route-filter" VRF routes into VPN VRFs that would
import the same route-targets. The translation of the IRTS is import the same route-targets. The translation of the IRTS is
done as follows. For a given IRT, the equivalent translated RT done as follows. For a given IRT, the equivalent translated RT
(TRT) is constructed by means of swapping the value of the high- (TRT) is constructed by means of swapping the value of the high-
order octet of the Type field for the IRT (as defined in order octet of the Type field for the IRT (as defined in
[RFC4360]). [RFC4360]).
0 1 0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x00 | 0x02 | | 0x01 | 0x02 | | 0x00 | 0x02 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|2B AS | |2B AS => IP(high) | |2B AS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Local Admin(high) | |Local Admin(high) => IP(low) | |Local Admin(high) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Local Admin(low) | |Local Admin(low) => Local Admin| |Local Admin(low) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
^
|
v
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x01 | 0x02 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|2B AS => IP(high) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Local Admin(high) => IP(low) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Local Admin(low) => Local Admin|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x01 | 0x02 | | 0x02 | 0x02 | | 0x01 | 0x02 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IP(high) | |IP(high) => 4B AS(high) | |IP(high) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IP(low) | |IP(low) => 4B AS(low) | |IP(low) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Local Admin | |Local Admin => Local Admin | |Local Admin |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
^
|
v
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x02 | 0x02 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IP(high) => 4B AS(high) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IP(low) => 4B AS(low) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Local Admin => Local Admin |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x02 | 0x02 | | 0x00 | 0x02 | | 0x02 | 0x02 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|4B AS(high) | |4B AS(high) => 2B AS | |4B AS(high) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|4B AS(low) | |4B AS(low) => Local Admin(high)| |4B AS(low) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Local Admin | |Local Admin => Local Admin(low)| |Local Admin |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
^
|
v
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| 0x00 | 0x02 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|4B AS(high) => 2B AS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|4B AS(low) => Local Admin(high)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Local Admin => Local Admin(low)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
As an example, if IRT R= 65500:12244(hex: 0x0002ffdc00002fd4), As an example, if IRT R= 65500:12244(hex: 0x0002ffdc00002fd4),
equivalent route-filter TRT: 255.220.0.0:12244(hex: equivalent route-filter TRT: 255.220.0.0:12244(hex:
0x0102ffdc00002fd4). One shortcoming of the translation mechanism 0x0102ffdc00002fd4). One shortcoming of the translation mechanism
is a possible collision between IRTs and TRTs if the network has is a possible collision between IRTs and TRTs if the network has
been configured with RTs of multiple higher order octet types been configured with RTs of multiple higher order octet types
(2-byte AS, IP address, and 4-byte AS). It is expected that such (2-byte AS, IP address, and 4-byte AS). It is expected that such
a configuration is rare in practice. a configuration is rare in practice.
o As an alternative to the translation of the IRTS, the subset of o As an alternative to the translation of the IRTS, the subset of
the 'IRTS' can be attached as-is (without swapping the type field the 'IRTS' can be attached as-is (without swapping the type field
as described earlier) as "export route-target extended as described earlier) as "export route-target extended
communities" with each route so as to evenly distribute the RTs communities" with each route so as to evenly distribute the RTs
skipping to change at page 8, line 33 skipping to change at page 9, line 23
[I-D.keyur-bgp-af-specific-rt-constrain] [I-D.keyur-bgp-af-specific-rt-constrain]
Patel, K., Raszuk, R., Djernaes, M., Dong, J., and M. Patel, K., Raszuk, R., Djernaes, M., Dong, J., and M.
Chen, "IPv6 AF Extensions for Route Target Distribution", Chen, "IPv6 AF Extensions for Route Target Distribution",
draft-keyur-bgp-af-specific-rt-constrain-01 (work in draft-keyur-bgp-af-specific-rt-constrain-01 (work in
progress), March 2011. progress), March 2011.
Authors' Addresses Authors' Addresses
Pradosh Mohapatra Pradosh Mohapatra
Cisco Systems Cumulus Networks
170 W. Tasman Drive
San Jose, CA 95134
USA
Email: pmohapat@cisco.com Email: mpradosh@yahoo.com
Arjun Sreekantiah Arjun Sreekantiah
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: asreekan@cisco.com Email: asreekan@cisco.com
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
Burjiz Pithawala Burjiz Pithawala
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
USA USA
Email: bpithaw@cisco.com Email: bpithaw@cisco.com
Alton Lo Alton Lo
Arista Networks Arista Networks
 End of changes. 14 change blocks. 
56 lines changed or deleted 97 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/