--- 1/draft-ietf-grow-ix-bgp-route-server-operations-01.txt 2014-03-03 08:14:38.945053995 -0800 +++ 2/draft-ietf-grow-ix-bgp-route-server-operations-02.txt 2014-03-03 08:14:38.977054782 -0800 @@ -1,23 +1,23 @@ GROW Working Group N. Hilliard Internet-Draft INEX Intended status: Informational E. Jasinska -Expires: March 01, 2014 Microsoft Corporation +Expires: September 4, 2014 Netflix, Inc R. Raszuk NTT I3 N. Bakker - AMS-IX B.V. - August 28, 2013 + Akamai Technologies B.V. + March 3, 2014 Internet Exchange Route Server Operations - draft-ietf-grow-ix-bgp-route-server-operations-01 + draft-ietf-grow-ix-bgp-route-server-operations-02 Abstract The popularity of Internet exchange points (IXPs) brings new challenges to interconnecting networks. While bilateral eBGP sessions between exchange participants were historically the most common means of exchanging reachability information over an IXP, the overhead associated with this interconnection method causes serious operational and administrative scaling problems for IXP participants. @@ -37,68 +37,69 @@ 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 March 01, 2014. + This Internet-Draft will expire on September 4, 2014. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the + Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . 2 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Notational Conventions . . . . . . . . . . . . . . . . . 3 2. Bilateral BGP Sessions . . . . . . . . . . . . . . . . . . . 3 3. Multilateral Interconnection . . . . . . . . . . . . . . . . 4 4. Operational Considerations for Route Server Installations . . 5 4.1. Path Hiding . . . . . . . . . . . . . . . . . . . . . . . 5 4.2. Route Server Scaling . . . . . . . . . . . . . . . . . . 6 4.2.1. Tackling Scaling Issues . . . . . . . . . . . . . . . 6 4.2.1.1. View Merging and Decomposition . . . . . . . . . 7 4.2.1.2. Destination Splitting . . . . . . . . . . . . . . 7 4.2.1.3. NEXT_HOP Resolution . . . . . . . . . . . . . . . 8 4.3. Prefix Leakage Mitigation . . . . . . . . . . . . . . . . 8 4.4. Route Server Redundancy . . . . . . . . . . . . . . . . . 8 4.5. AS_PATH Consistency Check . . . . . . . . . . . . . . . . 9 4.6. Export Routing Policies . . . . . . . . . . . . . . . . . 9 4.6.1. BGP Communities . . . . . . . . . . . . . . . . . . . 9 4.6.2. Internet Routing Registry . . . . . . . . . . . . . . 9 4.6.3. Client-accessible Databases . . . . . . . . . . . . . 10 4.7. Layer 2 Reachability Problems . . . . . . . . . . . . . . 10 4.8. BGP NEXT_HOP Hijacking . . . . . . . . . . . . . . . . . 10 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 8.1. Normative References . . . . . . . . . . . . . . . . . . 12 8.2. Informative References . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 1. Introduction + 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] is normally used to facilitate exchange of network reachability information over these media. As bilateral interconnection between IXP participants requires operational and administrative overhead, BGP route servers [I-D.ietf-idr-ix-bgp-route-server] are often deployed by IXP operators to provide a simple and convenient means of interconnecting @@ -550,21 +549,21 @@ include route server capabilities which are compliant with this document. 8. References 8.1. Normative References [I-D.ietf-idr-ix-bgp-route-server] Jasinska, E., Hilliard, N., Raszuk, R., and N. Bakker, "Internet Exchange Route Server", draft-ietf-idr-ix-bgp- - route-server-02 (work in progress), February 2013. + route-server-03 (work in progress), August 2013. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 8.2. Informative References [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP Communities Attribute", RFC 1997, August 1996. [RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D., @@ -578,55 +577,51 @@ [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended Communities Attribute", RFC 4360, February 2006. [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)", RFC 4456, April 2006. [RFC4893] Vohra, Q. and E. Chen, "BGP Support for Four-octet AS Number Space", RFC 4893, May 2007. - [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an - IANA Considerations Section in RFCs", BCP 26, RFC 5226, - May 2008. - [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June 2010. [RS-ARCH] Govindan, R., Alaettinoglu, C., Varadhan, K., and D. Estrin, "A Route Server Architecture for Inter-Domain Routing", 1995, . Authors' Addresses Nick Hilliard INEX 4027 Kingswood Road Dublin 24 IE Email: nick@inex.ie Elisa Jasinska - Microsoft Corporation - One Microsoft Way - Redmond, WA 98052 - US + Netflix, Inc + 100 Winchester Circle + Los Gatos, CA 95032 + USA - Email: ejas@microsoft.com + Email: elisa@netflix.com Robert Raszuk NTT I3 101 S Ellsworth Avenue Suite 350 San Mateo, CA 94401 US Email: robert@raszuk.net Niels Bakker - AMS-IX B.V. - Westeinde 12 - Amsterdam, NH 1017 ZN + Akamai Technologies B.V. + Kingsfordweg 151 + Amsterdam 1043 GR NL - Email: niels.bakker@ams-ix.net + Email: nbakker@akamai.com