--- 1/draft-ietf-idr-bgp-optimal-route-reflection-00.txt 2011-09-15 16:16:17.000000000 +0200 +++ 2/draft-ietf-idr-bgp-optimal-route-reflection-01.txt 2011-09-15 16:16:17.000000000 +0200 @@ -1,22 +1,23 @@ IDR Working Group R. Raszuk -Internet-Draft C. Cassar -Intended status: Standards Track Cisco Systems -Expires: December 4, 2011 E. Aman +Internet-Draft NTT MCL +Intended status: Standards Track C. Cassar +Expires: March 18, 2012 Cisco Systems + E. Aman TeliaSonera B. Decraene France Telecom - June 2, 2011 + September 15, 2011 BGP Optimal Route Reflection (BGP-ORR) - draft-ietf-idr-bgp-optimal-route-reflection-00 + draft-ietf-idr-bgp-optimal-route-reflection-01 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,21 +51,21 @@ 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 December 4, 2011. + This Internet-Draft will expire on March 18, 2012. Copyright Notice Copyright (c) 2011 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 @@ -769,28 +769,27 @@ 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-03 (work in - progress), January 2011. + draft-ietf-grow-diverse-bgp-path-dist-04 (work in + progress), June 2011. [I-D.ietf-idr-add-paths] - Walton, D., Retana, A., Chen, E., and J. Scudder, + Walton, D., Chen, E., Retana, A., and J. Scudder, "Advertisement of Multiple Paths in BGP", - draft-ietf-idr-add-paths-04 (work in progress), - August 2010. + draft-ietf-idr-add-paths-05 (work in progress), July 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. @@ -808,26 +807,26 @@ [RFC5668] Rekhter, Y., Sangli, S., and D. Tappan, "4-Octet AS Specific BGP Extended Community", RFC 5668, October 2009. [RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework", RFC 5714, January 2010. Authors' Addresses Robert Raszuk - Cisco Systems - 170 West Tasman Drive - San Jose, CA 95134 + NTT MCL + 101 S Ellsworth Avenue Suite 350 + San Mateo, CA 94401 US - Email: raszuk@cisco.com + Email: robert@raszuk.net Christian Cassar Cisco Systems 10 New Square Park Bedfont Lakes, FELTHAM TW14 8HA UK Email: ccassar@cisco.com Erik Aman