draft-ietf-idr-avoid-transition-00.txt   draft-ietf-idr-avoid-transition-01.txt 
Network Working Group Enke Chen Network Working Group E. Chen
Internet Draft Redback Networks Internet Draft S. Sangli
Expiration Date: December 2004 Srihari R. Sangli Expiration Date: May 2005 Cisco Systems, Inc.
Procket Networks
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-00.txt draft-ietf-idr-avoid-transition-01.txt
1. Status of this Memo 1. Status of this Memo
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. 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 8 skipping to change at page 5, line 28
can be completely eliminated by using the existing mechanisms (such can be completely eliminated by using the existing mechanisms (such
as setting LOCAL_PREF or MED) if so desired. as setting LOCAL_PREF or MED) if so desired.
8. Security Considerations 8. Security Considerations
This extension does not introduce any security issues. This extension does not introduce any security issues.
9. Acknowledgments 9. Acknowledgments
The idea presented was inspired by a route oscillation case observed The idea presented was inspired by a route oscillation case observed
on the BBN/Genuity backbone in 1998 while both authors were at Cisco on the BBN/Genuity backbone in 1998. The algorithm was also
Systems. The algorithm was also implemented at that time. implemented at that time.
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-23.txt, November 2003. (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-03.txt>, December 2003. <draft-ietf-idr-bgp-identifier-04.txt>, September 2004.
[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
Redback Networks, Inc. Cisco Systems, Inc.
300 Holger Way e-mail: enkechen@cisco.com
San Jose, CA 95134
e-mail: enke@redback.com
Srihari R. Sangli Srihari R. Sangli
Procket Networks, Inc. Cisco Systems, Inc.
1100 Cadillac Court 170 W. Tasman Dr.
Milpitas, CA 95035 San Jose, CA 95134
e-mail: srihari@procket.com e-mail: rsrihari@cisco.com
12. Intellectual Property Considerations
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
13. Full Copyright Notice
Copyright (C) The Internet Society (2004). 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
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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