--- 1/draft-ietf-idr-bgp-optimal-route-reflection-01.txt 2012-05-03 17:13:58.938756445 +0200 +++ 2/draft-ietf-idr-bgp-optimal-route-reflection-02.txt 2012-05-03 17:13:58.978754842 +0200 @@ -1,23 +1,23 @@ IDR Working Group R. Raszuk Internet-Draft NTT MCL Intended status: Standards Track C. Cassar -Expires: March 18, 2012 Cisco Systems +Expires: November 4, 2012 Cisco Systems E. Aman TeliaSonera B. Decraene France Telecom - September 15, 2011 + May 3, 2012 BGP Optimal Route Reflection (BGP-ORR) - draft-ietf-idr-bgp-optimal-route-reflection-01 + draft-ietf-idr-bgp-optimal-route-reflection-02 Abstract [RFC4456] asserts that, because the Interior Gateway Protocol (IGP) cost to a given point in the network will vary across routers, "the route reflection approach may not yield the same route selection result as that of the full IBGP mesh approach." One practical implication of this assertion is that the deployment of route reflection may thwart the ability to achieve hot potato routing. Hot potato routing attempts to direct traffic to the closest AS egress @@ -51,25 +51,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 March 18, 2012. + This Internet-Draft will expire on November 4, 2012. Copyright Notice - Copyright (c) 2011 IETF Trust and the persons identified as the + Copyright (c) 2012 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 @@ -769,27 +769,28 @@ Communities Attribute", RFC 4360, February 2006. [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement with BGP-4", RFC 5492, February 2009. 9.2. Informative References [I-D.ietf-grow-diverse-bgp-path-dist] Raszuk, R., Fernando, R., Patel, K., McPherson, D., and K. Kumaki, "Distribution of diverse BGP paths.", - draft-ietf-grow-diverse-bgp-path-dist-04 (work in - progress), June 2011. + draft-ietf-grow-diverse-bgp-path-dist-06 (work in + progress), November 2011. [I-D.ietf-idr-add-paths] Walton, D., Chen, E., Retana, A., and J. Scudder, "Advertisement of Multiple Paths in BGP", - draft-ietf-idr-add-paths-05 (work in progress), July 2011. + draft-ietf-idr-add-paths-06 (work in progress), + September 2011. [RFC1997] Chandrasekeran, R., Traina, P., and T. Li, "BGP Communities Attribute", RFC 1997, August 1996. [RFC1998] Chen, E. and T. Bates, "An Application of the BGP Community Attribute in Multi-home Routing", RFC 1998, August 1996. [RFC4384] Meyer, D., "BGP Communities for Data Collection", BCP 114, RFC 4384, February 2006.