draft-ietf-idr-avoid-transition-01.txt   draft-ietf-idr-avoid-transition-02.txt 
Network Working Group E. Chen Network Working Group E. Chen
Internet Draft S. Sangli Internet Draft S. Sangli
Expiration Date: May 2005 Cisco Systems, Inc. Expiration Date: December 2005 Cisco Systems
Avoid BGP Best Path Transitions from One External to Another Avoid BGP Best Path Transitions from One External to Another
draft-ietf-idr-avoid-transition-01.txt draft-ietf-idr-avoid-transition-02.txt
1. Status of this Memo 1. Status of this Memo
By submitting this Internet-Draft, I certify that any applicable By submitting this Internet-Draft, each author represents that any
patent or other IPR claims of which I am aware have been disclosed, applicable patent or other IPR claims of which he or she is aware
or will be disclosed, and any of which I become aware will be have been or will be disclosed, and any of which he or she becomes
disclosed, in accordance with RFC 3668. aware will be disclosed, in accordance with Section 6 of BCP 79.
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
2. Abstract 2. Abstract
In this document we propose a revision to the BGP route selection In this document we propose a revision to the BGP route selection
skipping to change at page 5, line 40 skipping to change at page 5, line 20
The authors would like to thank Yakov Rekhter and Ravi Chandra for The authors would like to thank Yakov Rekhter and Ravi Chandra for
their comments on the initial idea. their comments on the initial idea.
10. References 10. References
[1] Y. Rekhter, T. Li, and S. Hares, "A Border Gateway Protocol 4 [1] Y. Rekhter, T. Li, and S. Hares, "A Border Gateway Protocol 4
(BGP-4)", draft-ietf-idr-bgp4-26.txt, October 2004. (BGP-4)", draft-ietf-idr-bgp4-26.txt, October 2004.
[2] E. Chen and J. Yuan, "AS-wide Unique BGP Identifier for BGP-4", [2] E. Chen and J. Yuan, "AS-wide Unique BGP Identifier for BGP-4",
<draft-ietf-idr-bgp-identifier-04.txt>, September 2004. <draft-ietf-idr-bgp-identifier-05.txt>, April 2005.
[3] D. McPherson, V, Gill, D. Walton, and A. Retana, "Border Gateway [3] D. McPherson, V, Gill, D. Walton, and A. Retana, "Border Gateway
Protocol (BGP) Persistent Route Oscillation Condition", RFC 3345, Protocol (BGP) Persistent Route Oscillation Condition", RFC 3345,
August 2002. August 2002.
[4] T. Bates, R. Chandra, and E. Chen, "BGP Route Reflection - An [4] T. Bates, R. Chandra, and E. Chen, "BGP Route Reflection - An
Alternative to Full Mesh IBGP", RFC 2796, April 2000. Alternative to Full Mesh IBGP", RFC 2796, April 2000.
[5] Bradner, S., "Key words for use in RFCs to Indicate Requirement [5] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
11. Author Information 11. Author Information
Enke Chen Enke Chen
Cisco Systems, Inc. Cisco Systems, Inc.
170 W. Tasman Dr.
San Jose, CA 95134
e-mail: enkechen@cisco.com e-mail: enkechen@cisco.com
Srihari R. Sangli Srihari R. Sangli
Cisco Systems, Inc. Cisco Systems, Inc.
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
e-mail: rsrihari@cisco.com e-mail: rsrihari@cisco.com
12. Intellectual Property Considerations 12. Intellectual Property Considerations
skipping to change at page 7, line 7 skipping to change at page 6, line 31
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
13. Full Copyright Notice 13. Full Copyright Notice
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005).
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

This html diff was produced by rfcdiff 1.24, available from http://www.levkowetz.com/ietf/tools/rfcdiff/