A new Request for Comments is now available in online RFC libraries. RFC 3345 Title: Border Gateway Protocol (BGP) Persistent Route Oscillation Condition Author(s): D. McPherson, V. Gill, D. Walton, A. Retana Status: Informational Date: August 2002 Mailbox: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Pages: 19 Characters: 38137 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-idr-route-oscillation-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3345.txt In particular configurations, the BGP scaling mechanisms defined in "BGP Route Reflection - An Alternative to Full Mesh IBGP" and "Autonomous System Confederations for BGP" will introduce persistent BGP route oscillation. This document discusses the two types of persistent route oscillation that have been identified, describes when these conditions will occur, and provides some network design guidelines to avoid introducing such occurrences. This document is a product of the Inter-Domain Routing Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.