draft-ietf-idr-bgp-optimal-route-reflection-12.txt		draft-ietf-idr-bgp-optimal-route-reflection-13.txt
	IDR Working Group R. Raszuk, Ed.		IDR Working Group R. Raszuk, Ed.
	Internet-Draft Bloomberg LP		Internet-Draft Bloomberg LP
	Intended status: Standards Track C. Cassar		Intended status: Standards Track C. Cassar
	Expires: January 9, 2017 Cisco Systems		Expires: July 9, 2017 Cisco Systems
	E. Aman		E. Aman
	TeliaSonera		Telia Company
	B. Decraene		B. Decraene
	S. Litkowski		S. Litkowski
	Orange		Orange
	K. Wang		K. Wang
	Juniper Networks		Juniper Networks
	July 8, 2016		January 5, 2017
	BGP Optimal Route Reflection (BGP-ORR)		BGP Optimal Route Reflection (BGP-ORR)
	draft-ietf-idr-bgp-optimal-route-reflection-12		draft-ietf-idr-bgp-optimal-route-reflection-13
	Abstract		Abstract
	This document proposes a solution for BGP route reflectors to allow		This document proposes a solution for BGP route reflectors to allow
	them to choose the best path their clients would have chosen under		them to choose the best path their clients would have chosen under
	the same conditions, without requiring further state or any new		the same conditions, without requiring further state or any new
	features to be placed on the clients. This facilitates, for example,		features to be placed on the clients. This facilitates, for example,
	best exit point policy (hot potato routing). This solution is		best exit point policy (hot potato routing). This solution is
	primarily applicable in deployments using centralized route		primarily applicable in deployments using centralized route
	reflectors.		reflectors.
	skipping to change at page 2, line 7 ¶		skipping to change at page 2, line 7 ¶
	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 9, 2017.		This Internet-Draft will expire on July 9, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2017 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 13 ¶		skipping to change at page 9, line 13 ¶
	seems appropriate.		seems appropriate.
	5. Advantages and Deployment Considerations		5. Advantages and Deployment Considerations
	The solutions described provide a model for integrating the client		The solutions described provide a model for integrating the client
	perspective into the best path computation for RRs. More		perspective into the best path computation for RRs. More
	specifically, the choice of BGP path factors in either the IGP cost		specifically, the choice of BGP path factors in either the IGP cost
	between the client and the nexthop (rather than the distance from the		between the client and the nexthop (rather than the distance from the
	RR to the nexthop) or user configured policies.		RR to the nexthop) or user configured policies.
	Implementation to be declared as complaint with this memo should		Implementation to be declared as compliant with this memo should
	allow to configure per instance or per group of peers logical		allow to configure per instance or per group of peers logical
	location from which either for the entire instance or for set of		location from which either for the entire instance or for set of
	peers best path will be computed.		peers best path will be computed.
	These solutions can be deployed in traditional hop-by-hop forwarding		These solutions can be deployed in traditional hop-by-hop forwarding
	networks as well as in end-to-end tunneled environments. In the		networks as well as in end-to-end tunneled environments. In the
	networks where there are multiple route reflectors and hop-by-hop		networks where there are multiple route reflectors and hop-by-hop
	forwarding without encapsulation, such optimizations should be		forwarding without encapsulation, such optimizations should be
	enabled in a consistent way on all route reflectors. Otherwise		enabled in a consistent way on all route reflectors. Otherwise
	clients may receive an inconsistent view of the network and in turn		clients may receive an inconsistent view of the network and in turn
	skipping to change at page 12, line 13 ¶		skipping to change at page 12, line 13 ¶
	Email: robert@raszuk.net		Email: robert@raszuk.net
	Christian Cassar		Christian Cassar
	Cisco Systems		Cisco Systems
	10 New Square Park		10 New Square Park
	Bedfont Lakes, FELTHAM TW14 8HA		Bedfont Lakes, FELTHAM TW14 8HA
	UK		UK
	Email: ccassar@cisco.com		Email: ccassar@cisco.com
	Erik Aman		Erik Aman
	TeliaSonera		Telia Company
	Marbackagatan 11		Solna SE-169 94
	Farsta SE-123 86
	Sweden		Sweden
	Email: erik.aman@teliasonera.com		Email: erik.aman@teliacompany.com
	Bruno Decraene		Bruno Decraene
	Orange		Orange
	38-40 rue du General Leclerc		38-40 rue du General Leclerc
	Issy les Moulineaux cedex 9 92794		Issy les Moulineaux cedex 9 92794
	France		France
	Email: bruno.decraene@orange.com		Email: bruno.decraene@orange.com
	Stephane Litkowski		Stephane Litkowski
End of changes. 9 change blocks.
	11 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/