draft-ietf-idr-ix-bgp-route-server-01.txt		draft-ietf-idr-ix-bgp-route-server-02.txt
	IDR Working Group E. Jasinska		IDR Working Group E. Jasinska
	Internet-Draft Limelight Networks		Internet-Draft Microsoft Corporation
	Intended status: Standards Track N. Hilliard		Intended status: Standards Track N. Hilliard
	Expires: January 17, 2013 INEX		Expires: August 29, 2013 INEX
	R. Raszuk		R. Raszuk
	NTT MCL Inc.		NTT MCL Inc.
	N. Bakker		N. Bakker
	AMS-IX B.V.		AMS-IX B.V.
	July 16, 2012		February 25, 2013
	Internet Exchange Route Server		Internet Exchange Route Server
	draft-ietf-idr-ix-bgp-route-server-01		draft-ietf-idr-ix-bgp-route-server-02
	Abstract		Abstract
	This document outlines a specification for multilateral		This document outlines a specification for multilateral
	interconnections at Internet exchange points (IXPs). Multilateral		interconnections at Internet exchange points (IXPs). Multilateral
	interconnection is a method of exchanging routing information between		interconnection is a method of exchanging routing information between
	three or more exterior BGP speakers using a single intermediate		three or more exterior BGP speakers using a single intermediate
	broker system, referred to as a route server. Route servers are		broker system, referred to as a route server. Route servers are
	typically used on shared access media networks, such as Internet		typically used on shared access media networks, such as Internet
	exchange points (IXPs), to facilitate simplified interconnection		exchange points (IXPs), to facilitate simplified interconnection
	skipping to change at page 1, line 42		skipping to change at page 1, line 42
	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 January 17, 2013.		This Internet-Draft will expire on August 29, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2013 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 9, line 43		skipping to change at page 9, line 43
	Protocol 4 (BGP-4)", RFC 4271, January 2006.		Protocol 4 (BGP-4)", RFC 4271, January 2006.
	[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended		[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
	Communities Attribute", RFC 4360, February 2006.		Communities Attribute", RFC 4360, February 2006.
	6.2. Informative References		6.2. Informative References
	[I-D.ietf-grow-diverse-bgp-path-dist]		[I-D.ietf-grow-diverse-bgp-path-dist]
	Raszuk, R., Fernando, R., Patel, K., McPherson, D., and K.		Raszuk, R., Fernando, R., Patel, K., McPherson, D., and K.
	Kumaki, "Distribution of diverse BGP paths.",		Kumaki, "Distribution of diverse BGP paths.",
	draft-ietf-grow-diverse-bgp-path-dist-07 (work in		draft-ietf-grow-diverse-bgp-path-dist-08 (work in
	progress), May 2012.		progress), July 2012.
	[I-D.ietf-idr-add-paths]		[I-D.ietf-idr-add-paths]
	Walton, D., Chen, E., Retana, A., and J. Scudder,		Walton, D., Retana, A., Chen, E., and J. Scudder,
	"Advertisement of Multiple Paths in BGP",		"Advertisement of Multiple Paths in BGP",
	draft-ietf-idr-add-paths-07 (work in progress), June 2012.		draft-ietf-idr-add-paths-08 (work in progress),
			December 2012.
	[RFC1863] Haskin, D., "A BGP/IDRP Route Server alternative to a full		[RFC1863] Haskin, D., "A BGP/IDRP Route Server alternative to a full
	mesh routing", RFC 1863, October 1995.		mesh routing", RFC 1863, October 1995.
	[RFC4223] Savola, P., "Reclassification of RFC 1863 to Historic",		[RFC4223] Savola, P., "Reclassification of RFC 1863 to Historic",
	RFC 4223, October 2005.		RFC 4223, October 2005.
	[RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route		[RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route
	Reflection: An Alternative to Full Mesh Internal BGP		Reflection: An Alternative to Full Mesh Internal BGP
	(IBGP)", RFC 4456, April 2006.		(IBGP)", RFC 4456, April 2006.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", BCP 26, RFC 5226,		IANA Considerations Section in RFCs", BCP 26, RFC 5226,
	May 2008.		May 2008.
	Authors' Addresses		Authors' Addresses
	Elisa Jasinska		Elisa Jasinska
	Limelight Networks		Microsoft Corporation
	222 South Mill Avenue		One Microsoft Way
	Tempe, AZ 85281		Redmond, WA 98052
	US		US
	Email: elisa@llnw.com		Email: ejas@microsoft.com
	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
	Robert Raszuk		Robert Raszuk
End of changes. 11 change blocks.
	14 lines changed or deleted		15 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/