draft-ietf-grow-ix-bgp-route-server-operations-04.txt		draft-ietf-grow-ix-bgp-route-server-operations-05.txt
	GROW Working Group N. Hilliard		GROW Working Group N. Hilliard
	Internet-Draft INEX		Internet-Draft INEX
	Intended status: Informational E. Jasinska		Intended status: Informational E. Jasinska
	Expires: April 23, 2015 Netflix, Inc		Expires: December 10, 2015 BigWave IT
	R. Raszuk		R. Raszuk
	Mirantis Inc.		Mirantis Inc.
	N. Bakker		N. Bakker
	Akamai Technologies B.V.		Akamai Technologies B.V.
	October 20, 2014		June 8, 2015
	Internet Exchange Route Server Operations		Internet Exchange BGP Route Server Operations
	draft-ietf-grow-ix-bgp-route-server-operations-04		draft-ietf-grow-ix-bgp-route-server-operations-05
	Abstract		Abstract
	The popularity of Internet exchange points (IXPs) brings new		The popularity of Internet exchange points (IXPs) brings new
	challenges to interconnecting networks. While bilateral eBGP		challenges to interconnecting networks. While bilateral eBGP
	sessions between exchange participants were historically the most		sessions between exchange participants were historically the most
	common means of exchanging reachability information over an IXP, the		common means of exchanging reachability information over an IXP, the
	overhead associated with this interconnection method causes serious		overhead associated with this interconnection method causes serious
	operational and administrative scaling problems for IXP participants.		operational and administrative scaling problems for IXP participants.
	skipping to change at page 1, line 49		skipping to change at page 1, line 49
	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 April 23, 2015.		This Internet-Draft will expire on December 10, 2015.
	Copyright Notice		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.		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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 7, line 6		skipping to change at page 7, line 6
	of BGP path attribute sets, allowing more efficient transmission of		of BGP path attribute sets, allowing more efficient transmission of
	BGP routes from the route server than the theoretical analysis		BGP routes from the route server than the theoretical analysis
	suggests. In the analysis above, P_tot will increase monotonically		suggests. In the analysis above, P_tot will increase monotonically
	according to the number of clients, but will have an upper limit of		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		the size of the full default-free routing table of the network in
	which the IXP is located. Observations from production route servers		which the IXP is located. Observations from production route servers
	have shown that most route server clients generally avoid using		have shown that most route server clients generally avoid using
	custom routing policies and consequently the route server may not		custom routing policies and consequently the route server may not
	need to deploy per-client Loc-RIBs. These practical bounds reduce		need to deploy per-client Loc-RIBs. These practical bounds reduce
	the theoretical worst-case scaling scenario to the point where route-		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		4.2.1. Tackling Scaling Issues
	The problem of scaling route servers still presents serious practical		The problem of scaling route servers still presents serious practical
	challenges and requires careful attention. Scaling analysis		challenges and requires careful attention. Scaling analysis
	indicates problems in three key areas: route processor CPU overhead		indicates problems in three key areas: route processor CPU overhead
	associated with BGP decision process calculations, the memory		associated with BGP decision process calculations, the memory
	requirements for handling many different BGP path entries, and the		requirements for handling many different BGP path entries, and the
	network traffic bandwidth required to distribute these BGP routes		network traffic bandwidth required to distribute these BGP routes
	from the route server to each route server client.		from the route server to each route server client.
	skipping to change at page 13, line 44		skipping to change at page 13, line 44
	The authors would like to thank Chris Hall, Ryan Bickhart, Steven		The authors would like to thank Chris Hall, Ryan Bickhart, Steven
	Bakker and Eduardo Ascenco Reis for their valuable input.		Bakker and Eduardo Ascenco Reis for their valuable input.
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[I-D.ietf-idr-ix-bgp-route-server]		[I-D.ietf-idr-ix-bgp-route-server]
	Jasinska, E., Hilliard, N., Raszuk, R., and N. Bakker,		Jasinska, E., Hilliard, N., Raszuk, R., and N. Bakker,
	"Internet Exchange Route Server", draft-ietf-idr-ix-bgp-		"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		[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, March 1997.
	8.2. Informative References		8.2. Informative References
	[RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP		[RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP
	Communities Attribute", RFC 1997, August 1996.		Communities Attribute", RFC 1997, August 1996.
	[RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D.,		[RFC2622] Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D.,
	skipping to change at page 15, line 5		skipping to change at page 15, line 5
	Authors' Addresses		Authors' Addresses
	Nick Hilliard		Nick Hilliard
	INEX		INEX
	4027 Kingswood Road		4027 Kingswood Road
	Dublin 24		Dublin 24
	IE		IE
	Email: nick@inex.ie		Email: nick@inex.ie
	Elisa Jasinska		Elisa Jasinska
	Netflix, Inc		BigWave IT
	100 Winchester Circle		ul. Skawinska 27/7
	Los Gatos, CA 95032		Krakow, MP 31-066
	USA		Poland
	Email: elisa@netflix.com		Email: elisa@bigwaveit.org
	Robert Raszuk		Robert Raszuk
	Mirantis Inc.		Mirantis Inc.
	615 National Ave. #100		615 National Ave. #100
	Mt View, CA 94043		Mt View, CA 94043
	USA		USA
	Email: robert@raszuk.net		Email: robert@raszuk.net
	Niels Bakker		Niels Bakker
End of changes. 9 change blocks.
	13 lines changed or deleted		13 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/