--- 1/draft-ietf-idr-legacy-rtc-01.txt 2013-10-02 15:14:27.212178536 -0700 +++ 2/draft-ietf-idr-legacy-rtc-02.txt 2013-10-02 15:14:27.236179140 -0700 @@ -1,22 +1,23 @@ Network Working Group P. Mohapatra -Internet-Draft A. Sreekantiah -Intended status: Standards Track K. Patel -Expires: September 14, 2013 B. Pithawala +Internet-Draft Cumulus Networks +Intended status: Standards Track A. Sreekantiah +Expires: April 05, 2014 K. Patel + B. Pithawala Cisco Systems A. Lo Arista Networks - March 13, 2013 + October 02, 2013 Automatic Route Target Filtering for legacy PEs - draft-ietf-idr-legacy-rtc-01.txt + draft-ietf-idr-legacy-rtc-02.txt Abstract This document describes a simple procedure that allows "legacy" BGP speakers to exchange route target membership information in BGP without using mechanisms specified in [RFC4684]. The intention of the proposed technique is to help in partial deployment scenarios and is not meant to replace [RFC4684]. Status of This Memo @@ -27,21 +28,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." - This Internet-Draft will expire on September 14, 2013. + This Internet-Draft will expire on April 05, 2014. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -63,33 +64,33 @@ it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Basic Idea . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Detailed Operation . . . . . . . . . . . . . . . . . . . . . 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 legacy PE clients . . . . . . . . . . . . . . . . . . 6 - 4. ROUTE_FILTER Community . . . . . . . . . . . . . . . . . . . 6 - 5. Deployment Considerations . . . . . . . . . . . . . . . . . . 7 - 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 7 - 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 - 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 - 9. Security Considerations . . . . . . . . . . . . . . . . . . . 7 - 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 10.1. Normative References . . . . . . . . . . . . . . . . . . 7 - 10.2. Informational References . . . . . . . . . . . . . . . . 8 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 + 4. ROUTE_FILTER Community . . . . . . . . . . . . . . . . . . . 7 + 5. Deployment Considerations . . . . . . . . . . . . . . . . . . 8 + 6. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 8 + 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 + 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 + 9. Security Considerations . . . . . . . . . . . . . . . . . . . 8 + 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 + 10.1. Normative References . . . . . . . . . . . . . . . . . . 8 + 10.2. Informational References . . . . . . . . . . . . . . . . 9 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 1. Introduction [RFC4684] provides a powerful and general means for BGP speakers to exchange and propagate Route Target reachability information and constrain VPN route distribution to achieve high scale. However, it requires that all the BGP speakers in the network are upgraded to support this functionality. For example, in a network with route reflectors (RR), if one PE client in the cluster doesn't support constrained distribution, the cluster degenerates into storing and @@ -145,58 +146,101 @@ route-filter VRF. o The translation of the IRTs is necessary in order to refrain from importing "route-filter" VRF routes into VPN VRFs that would import the same route-targets. The translation of the IRTS is done as follows. For a given IRT, the equivalent translated RT (TRT) is constructed by means of swapping the value of the high- order octet of the Type field for the IRT (as defined in [RFC4360]). - 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 - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | 0x00 | 0x02 | | 0x01 | 0x02 | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |2B AS | |2B AS => IP(high) | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |Local Admin(high) | |Local Admin(high) => IP(low) | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |Local Admin(low) | |Local Admin(low) => Local Admin| - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 0 1 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | 0x00 | 0x02 | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |2B AS | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |Local Admin(high) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |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 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 | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |IP(high) | |IP(high) => 4B AS(high) | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |IP(low) | |IP(low) => 4B AS(low) | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |Local Admin | |Local Admin => Local Admin | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 0 1 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | 0x01 | 0x02 | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |IP(high) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |IP(low) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |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 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 | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |4B AS(high) | |4B AS(high) => 2B AS | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<=>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |4B AS(low) | |4B AS(low) => Local Admin(high)| - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |Local Admin | |Local Admin => Local Admin(low)| - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 0 1 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | 0x02 | 0x02 | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |4B AS(high) | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |4B AS(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), equivalent route-filter TRT: 255.220.0.0:12244(hex: + 0x0102ffdc00002fd4). One shortcoming of the translation mechanism is a possible collision between IRTs and TRTs if the network has been configured with RTs of multiple higher order octet types (2-byte AS, IP address, and 4-byte AS). It is expected that such a configuration is rare in practice. 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 as described earlier) as "export route-target extended communities" with each route so as to evenly distribute the RTs @@ -343,42 +386,39 @@ [I-D.keyur-bgp-af-specific-rt-constrain] Patel, K., Raszuk, R., Djernaes, M., Dong, J., and M. Chen, "IPv6 AF Extensions for Route Target Distribution", draft-keyur-bgp-af-specific-rt-constrain-01 (work in progress), March 2011. Authors' Addresses Pradosh Mohapatra - Cisco Systems - 170 W. Tasman Drive - San Jose, CA 95134 - USA + Cumulus Networks - Email: pmohapat@cisco.com + Email: mpradosh@yahoo.com Arjun Sreekantiah Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 USA Email: asreekan@cisco.com + Keyur Patel Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 USA Email: keyupate@cisco.com - Burjiz Pithawala Cisco Systems 170 W. Tasman Drive San Jose, CA 95134 USA Email: bpithaw@cisco.com Alton Lo Arista Networks