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