draft-ietf-idr-bgp-optimal-route-reflection-07.txt | draft-ietf-idr-bgp-optimal-route-reflection-08.txt | |||
---|---|---|---|---|
IDR Working Group R. Raszuk | IDR Working Group R. Raszuk | |||
Internet-Draft Individual | Internet-Draft Mirantis Inc. | |||
Intended status: Standards Track C. Cassar | Intended status: Standards Track C. Cassar | |||
Expires: February 1, 2015 Cisco Systems | Expires: April 25, 2015 Cisco Systems | |||
E. Aman | E. Aman | |||
TeliaSonera | TeliaSonera | |||
B. Decraene | B. Decraene | |||
S. Litkowski | S. Litkowski | |||
Orange | Orange | |||
July 31, 2014 | October 22, 2014 | |||
BGP Optimal Route Reflection (BGP-ORR) | BGP Optimal Route Reflection (BGP-ORR) | |||
draft-ietf-idr-bgp-optimal-route-reflection-07 | draft-ietf-idr-bgp-optimal-route-reflection-08 | |||
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 20 | skipping to change at page 2, line 20 | |||
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 February 1, 2015. | This Internet-Draft will expire on April 25, 2015. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 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 21, line 47 | skipping to change at page 22, line 4 | |||
Specific BGP Extended Community", RFC 5668, October 2009. | Specific BGP Extended Community", RFC 5668, October 2009. | |||
[RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework", RFC | [RFC5714] Shand, M. and S. Bryant, "IP Fast Reroute Framework", RFC | |||
5714, January 2010. | 5714, January 2010. | |||
[RFC6774] Raszuk, R., Fernando, R., Patel, K., McPherson, D., and K. | [RFC6774] Raszuk, R., Fernando, R., Patel, K., McPherson, D., and K. | |||
Kumaki, "Distribution of Diverse BGP Paths", RFC 6774, | Kumaki, "Distribution of Diverse BGP Paths", RFC 6774, | |||
November 2012. | November 2012. | |||
Authors' Addresses | Authors' Addresses | |||
Robert Raszuk | Robert Raszuk | |||
Individual | Mirantis Inc. | |||
615 National Ave. #100 | ||||
Mt View, CA 94043 | ||||
USA | ||||
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 | TeliaSonera | |||
End of changes. 8 change blocks. | ||||
7 lines changed or deleted | 10 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/ |