draft-ietf-grow-diverse-bgp-path-dist-04.txt   draft-ietf-grow-diverse-bgp-path-dist-05.txt 
GROW Working Group R. Raszuk, Ed. GROW Working Group R. Raszuk, Ed.
Internet-Draft R. Fernando Internet-Draft NTT MCL
Intended status: Informational K. Patel Intended status: Informational R. Fernando
Expires: December 3, 2011 Cisco Systems Expires: March 18, 2012 K. Patel
Cisco Systems
D. McPherson D. McPherson
Verisign Verisign
K. Kumaki K. Kumaki
KDDI Corporation KDDI Corporation
Jun 2011 September 15, 2011
Distribution of diverse BGP paths. Distribution of diverse BGP paths.
draft-ietf-grow-diverse-bgp-path-dist-04 draft-ietf-grow-diverse-bgp-path-dist-05
Abstract Abstract
The BGP4 protocol specifies the selection and propagation of a single The BGP4 protocol specifies the selection and propagation of a single
best path for each prefix. As defined today BGP has no mechanisms to best path for each prefix. As defined today BGP has no mechanisms to
distribute paths other then best path between its speakers. This distribute paths other then best path between its speakers. This
behaviour results in number of disadvantages for new applications and behaviour results in number of disadvantages for new applications and
services. services.
This document presents an alternative mechanism for solving the This document presents an alternative mechanism for solving the
skipping to change at page 2, line 4 skipping to change at page 2, line 5
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 December 3, 2011.
This Internet-Draft will expire on March 18, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 20 skipping to change at page 21, line 20
13.2. Informative References 13.2. Informative References
[I-D.decraene-bgp-graceful-shutdown-requirements] [I-D.decraene-bgp-graceful-shutdown-requirements]
Decraene, B., Francois, P., pelsser, c., Ahmad, Z., and A. Decraene, B., Francois, P., pelsser, c., Ahmad, Z., and A.
Armengol, "Requirements for the graceful shutdown of BGP Armengol, "Requirements for the graceful shutdown of BGP
sessions", sessions",
draft-decraene-bgp-graceful-shutdown-requirements-01 (work draft-decraene-bgp-graceful-shutdown-requirements-01 (work
in progress), March 2009. in progress), March 2009.
[I-D.ietf-idr-add-paths] [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", "Advertisement of Multiple Paths in BGP",
draft-ietf-idr-add-paths-04 (work in progress), draft-ietf-idr-add-paths-05 (work in progress), July 2011.
August 2010.
[I-D.ietf-idr-best-external] [I-D.ietf-idr-best-external]
Marques, P., Fernando, R., Chen, E., Mohapatra, P., and H. Marques, P., Fernando, R., Chen, E., Mohapatra, P., and H.
Gredler, "Advertisement of the best external route in Gredler, "Advertisement of the best external route in
BGP", draft-ietf-idr-best-external-04 (work in progress), BGP", draft-ietf-idr-best-external-04 (work in progress),
April 2011. April 2011.
[I-D.ietf-idr-route-oscillation] [I-D.ietf-idr-route-oscillation]
McPherson, D., "BGP Persistent Route Oscillation McPherson, D., "BGP Persistent Route Oscillation
Condition", draft-ietf-idr-route-oscillation-01 (work in Condition", draft-ietf-idr-route-oscillation-01 (work in
skipping to change at page 22, line 9 skipping to change at page 22, line 8
[RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route
Reflection: An Alternative to Full Mesh Internal BGP Reflection: An Alternative to Full Mesh Internal BGP
(IBGP)", RFC 4456, April 2006. (IBGP)", RFC 4456, April 2006.
[RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous
System Confederations for BGP", RFC 5065, August 2007. System Confederations for BGP", RFC 5065, August 2007.
Authors' Addresses Authors' Addresses
Robert Raszuk (editor) Robert Raszuk (editor)
Cisco Systems NTT MCL
170 West Tasman Drive 101 S Ellsworth Avenue Suite 350
San Jose, CA 95134 San Mateo, CA 94401
US US
Email: raszuk@cisco.com Email: robert@raszuk.net
Rex Fernando Rex Fernando
Cisco Systems Cisco Systems
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
US US
Email: rex@cisco.com Email: rex@cisco.com
Keyur Patel Keyur Patel
 End of changes. 8 change blocks. 
13 lines changed or deleted 14 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/