--- 1/draft-ietf-grow-ix-bgp-route-server-operations-04.txt 2015-06-08 13:14:55.099018303 -0700 +++ 2/draft-ietf-grow-ix-bgp-route-server-operations-05.txt 2015-06-08 13:14:55.131019081 -0700 @@ -1,23 +1,23 @@ GROW Working Group N. Hilliard Internet-Draft INEX Intended status: Informational E. Jasinska -Expires: April 23, 2015 Netflix, Inc +Expires: December 10, 2015 BigWave IT R. Raszuk Mirantis Inc. N. Bakker Akamai Technologies B.V. - October 20, 2014 + June 8, 2015 - Internet Exchange Route Server Operations - draft-ietf-grow-ix-bgp-route-server-operations-04 + Internet Exchange BGP Route Server Operations + draft-ietf-grow-ix-bgp-route-server-operations-05 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. @@ -38,25 +38,25 @@ 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 April 23, 2015. + This Internet-Draft will expire on December 10, 2015. Copyright Notice - Copyright (c) 2014 IETF Trust and the persons identified as the + 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 @@ -281,21 +281,21 @@ of BGP path attribute sets, allowing more efficient transmission of BGP routes from the route server than the theoretical analysis suggests. In the analysis above, P_tot will increase monotonically according to the number of clients, but will have an upper limit of the size of the full default-free routing table of the network in which the IXP is located. Observations from production route servers have shown that most route server clients generally avoid using custom routing policies and consequently the route server may not need to deploy per-client Loc-RIBs. These practical bounds reduce the theoretical worst-case scaling scenario to the point where route- - server deployments are manageable on even on larger IXPs. + server deployments are manageable even on larger IXPs. 4.2.1. Tackling Scaling Issues The problem of scaling route servers still presents serious practical challenges and requires careful attention. Scaling analysis indicates problems in three key areas: route processor CPU overhead associated with BGP decision process calculations, the memory requirements for handling many different BGP path entries, and the network traffic bandwidth required to distribute these BGP routes from the route server to each route server client. @@ -587,21 +587,21 @@ The authors would like to thank Chris Hall, Ryan Bickhart, Steven Bakker and Eduardo Ascenco Reis for their valuable input. 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-05 (work in progress), June 2014. + route-server-06 (work in progress), December 2014. [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., @@ -637,26 +637,26 @@ Authors' Addresses Nick Hilliard INEX 4027 Kingswood Road Dublin 24 IE Email: nick@inex.ie Elisa Jasinska - Netflix, Inc - 100 Winchester Circle - Los Gatos, CA 95032 - USA + BigWave IT + ul. Skawinska 27/7 + Krakow, MP 31-066 + Poland - Email: elisa@netflix.com + Email: elisa@bigwaveit.org Robert Raszuk Mirantis Inc. 615 National Ave. #100 Mt View, CA 94043 USA Email: robert@raszuk.net Niels Bakker