draft-ietf-idr-bgp-optimal-route-reflection-02.txt		draft-ietf-idr-bgp-optimal-route-reflection-03.txt
	IDR Working Group R. Raszuk		IDR Working Group R. Raszuk
	Internet-Draft NTT MCL		Internet-Draft NTT MCL
	Intended status: Standards Track C. Cassar		Intended status: Standards Track C. Cassar
	Expires: November 4, 2012 Cisco Systems		Expires: May 10, 2013 Cisco Systems
	E. Aman		E. Aman
	TeliaSonera		TeliaSonera
	B. Decraene		B. Decraene
	France Telecom		France Telecom
	May 3, 2012		November 6, 2012
	BGP Optimal Route Reflection (BGP-ORR)		BGP Optimal Route Reflection (BGP-ORR)
	draft-ietf-idr-bgp-optimal-route-reflection-02		draft-ietf-idr-bgp-optimal-route-reflection-03
	Abstract		Abstract
	[RFC4456] asserts that, because the Interior Gateway Protocol (IGP)		[RFC4456] asserts that, because the Interior Gateway Protocol (IGP)
	cost to a given point in the network will vary across routers, "the		cost to a given point in the network will vary across routers, "the
	route reflection approach may not yield the same route selection		route reflection approach may not yield the same route selection
	result as that of the full IBGP mesh approach." One practical		result as that of the full IBGP mesh approach." One practical
	implication of this assertion is that the deployment of route		implication of this assertion is that the deployment of route
	reflection may thwart the ability to achieve hot potato routing. Hot		reflection may thwart the ability to achieve hot potato routing. Hot
	potato routing attempts to direct traffic to the closest AS egress		potato routing attempts to direct traffic to the closest AS egress
	skipping to change at page 2, line 17		skipping to change at page 2, line 17
	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 November 4, 2012.		This Internet-Draft will expire on May 10, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2012 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
	skipping to change at page 18, line 26		skipping to change at page 18, line 26
	Communities Attribute", RFC 4360, February 2006.		Communities Attribute", RFC 4360, February 2006.
	[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement		[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
	with BGP-4", RFC 5492, February 2009.		with BGP-4", RFC 5492, February 2009.
	9.2. Informative References		9.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-06 (work in		draft-ietf-grow-diverse-bgp-path-dist-08 (work in
	progress), November 2011.		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., Chen, E., Retana, A., and J. Scudder,
	"Advertisement of Multiple Paths in BGP",		"Advertisement of Multiple Paths in BGP",
	draft-ietf-idr-add-paths-06 (work in progress),		draft-ietf-idr-add-paths-07 (work in progress), June 2012.
	September 2011.
	[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.
	[RFC1998] Chen, E. and T. Bates, "An Application of the BGP		[RFC1998] Chen, E. and T. Bates, "An Application of the BGP
	Community Attribute in Multi-home Routing", RFC 1998,		Community Attribute in Multi-home Routing", RFC 1998,
	August 1996.		August 1996.
	[RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114,		[RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114,
	RFC 4384, February 2006.		RFC 4384, February 2006.
End of changes. 6 change blocks.
	8 lines changed or deleted		7 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/