--- 1/draft-ietf-idr-ix-bgp-route-server-07.txt 2015-08-31 10:15:01.017904062 -0700 +++ 2/draft-ietf-idr-ix-bgp-route-server-08.txt 2015-08-31 10:15:01.041904635 -0700 @@ -1,92 +1,91 @@ IDR Working Group E. Jasinska Internet-Draft BigWave IT Intended status: Standards Track N. Hilliard -Expires: December 10, 2015 INEX +Expires: March 3, 2016 INEX R. Raszuk Mirantis Inc. N. Bakker Akamai Technologies B.V. - June 8, 2015 + August 31, 2015 Internet Exchange BGP Route Server - draft-ietf-idr-ix-bgp-route-server-07 + draft-ietf-idr-ix-bgp-route-server-08 Abstract This document outlines a specification for multilateral interconnections at Internet exchange points (IXPs). Multilateral interconnection is a method of exchanging routing information between three or more exterior BGP speakers using a single intermediate broker system, referred to as a route server. Route servers are typically used on shared access media networks, such as Internet exchange points (IXPs), to facilitate simplified interconnection between multiple Internet routers. -Status of this Memo +Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. 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 December 10, 2015. + This Internet-Draft will expire on March 3, 2016. Copyright Notice Copyright (c) 2015 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents - 1. Introduction to Multilateral Interconnection . . . . . . . . . 3 - 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 3 - 2. Technical Considerations for Route Server Implementations . . 4 - 2.1. Client UPDATE Messages . . . . . . . . . . . . . . . . . . 4 - 2.2. Attribute Transparency . . . . . . . . . . . . . . . . . . 4 - 2.2.1. NEXT_HOP Attribute . . . . . . . . . . . . . . . . . . 4 + 1. Introduction to Multilateral Interconnection . . . . . . . . 2 + 1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3 + 2. Technical Considerations for Route Server Implementations . . 3 + 2.1. Client UPDATE Messages . . . . . . . . . . . . . . . . . 3 + 2.2. Attribute Transparency . . . . . . . . . . . . . . . . . 4 + 2.2.1. NEXT_HOP Attribute . . . . . . . . . . . . . . . . . 4 2.2.2. AS_PATH Attribute . . . . . . . . . . . . . . . . . . 4 - 2.2.3. MULTI_EXIT_DISC Attribute . . . . . . . . . . . . . . 5 - 2.2.4. Communities Attributes . . . . . . . . . . . . . . . . 5 - 2.3. Per-Client Policy Control in Multilateral - Interconnection . . . . . . . . . . . . . . . . . . . . . 5 - 2.3.1. Path Hiding on a Route Server . . . . . . . . . . . . 6 - 2.3.2. Mitigation of Path Hiding . . . . . . . . . . . . . . 7 - 2.3.2.1. Multiple Route Server RIBs . . . . . . . . . . . . 7 - 2.3.2.2. Advertising Multiple Paths . . . . . . . . . . . . 7 - 2.3.3. Implementation Recommendations . . . . . . . . . . . . 8 + 2.2.3. MULTI_EXIT_DISC Attribute . . . . . . . . . . . . . . 4 + 2.2.4. Communities Attributes . . . . . . . . . . . . . . . 5 + 2.3. Per-Client Policy Control in Multilateral Interconnection 5 + 2.3.1. Path Hiding on a Route Server . . . . . . . . . . . . 5 + 2.3.2. Mitigation of Path Hiding . . . . . . . . . . . . . . 6 + 2.3.2.1. Multiple Route Server RIBs . . . . . . . . . . . 6 + 2.3.2.2. Advertising Multiple Paths . . . . . . . . . . . 7 + 2.3.3. Implementation Recommendations . . . . . . . . . . . 8 3. Security Considerations . . . . . . . . . . . . . . . . . . . 8 - 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 - 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 - 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 6.1. Normative References . . . . . . . . . . . . . . . . . . . 9 - 6.2. Informative References . . . . . . . . . . . . . . . . . . 9 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10 + 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 + 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 + 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 + 6.1. Normative References . . . . . . . . . . . . . . . . . . 9 + 6.2. Informative References . . . . . . . . . . . . . . . . . 9 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 1. Introduction to Multilateral Interconnection Internet exchange points (IXPs) provide IP data interconnection facilities for their participants, typically using shared Layer-2 networking media such as Ethernet. The Border Gateway Protocol (BGP) [RFC4271], an inter-Autonomous System routing protocol, is commonly used to facilitate exchange of network reachability information over such media. @@ -371,56 +370,69 @@ In addition, the authors would like to acknowledge the developers of BIRD, OpenBGPD, Quagga and IOS whose BGP implementations include route server capabilities which are compliant with this document. Route server functionality was described in 1995 in [RFC1863] and modern route server implementations are based on concepts developed in the 1990s by the Routing Arbiter Project and the Route Server Next Generation Project, managed by ISI and Merit. Although the original RSNG code is no longer in use at any IXPs, the IXP community owes a debt of gratitude to the many people who were involved in route - server development in the 1990s. + server development in the 1990s. Please note that [RFC1863] has been + made historical by [RFC4223]. 6. References 6.1. Normative References - [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP - Communities Attribute", RFC 1997, August 1996. + [RFC1997] Chandra, R., Traina, P., and T. Li, "BGP Communities + Attribute", RFC 1997, DOI 10.17487/RFC1997, August 1996, + . [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, + DOI 10.17487/RFC2119, March 1997, + . - [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway - Protocol 4 (BGP-4)", RFC 4271, January 2006. + [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A + Border Gateway Protocol 4 (BGP-4)", RFC 4271, + DOI 10.17487/RFC4271, January 2006, + . [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended - Communities Attribute", RFC 4360, February 2006. + Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, + February 2006, . 6.2. Informative References [I-D.ietf-idr-add-paths] Walton, D., Retana, A., Chen, E., and J. Scudder, - "Advertisement of Multiple Paths in BGP", - draft-ietf-idr-add-paths-10 (work in progress), - October 2014. + "Advertisement of Multiple Paths in BGP", draft-ietf-idr- + add-paths-10 (work in progress), October 2014. [RFC1863] Haskin, D., "A BGP/IDRP Route Server alternative to a full - mesh routing", RFC 1863, October 1995. + mesh routing", RFC 1863, DOI 10.17487/RFC1863, October + 1995, . + + [RFC4223] Savola, P., "Reclassification of RFC 1863 to Historic", + RFC 4223, DOI 10.17487/RFC4223, October 2005, + . [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route Reflection: An Alternative to Full Mesh Internal BGP - (IBGP)", RFC 4456, April 2006. + (IBGP)", RFC 4456, DOI 10.17487/RFC4456, April 2006, + . - [RFC6774] Raszuk, R., Fernando, R., Patel, K., McPherson, D., and K. - Kumaki, "Distribution of Diverse BGP Paths", RFC 6774, - November 2012. + [RFC6774] Raszuk, R., Ed., Fernando, R., Patel, K., McPherson, D., + and K. Kumaki, "Distribution of Diverse BGP Paths", + RFC 6774, DOI 10.17487/RFC6774, November 2012, + . Authors' Addresses Elisa Jasinska BigWave IT ul. Skawinska 27/7 Krakow, MP 31-066 Poland Email: elisa@bigwaveit.org