idnits 2.17.1 draft-ietf-idr-route-oscillation-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3345 5 Title: Border Gateway Protocol (BGP) Persistent Route 6 Oscillation Condition 7 Author(s): D. McPherson, V. Gill, D. Walton, A. Retana 8 Status: Informational 9 Date: August 2002 10 Mailbox: danny@tcb.net, vijay@umbc.edu, dwalton@cisco.com, 11 aretana@cisco.com 12 Pages: 19 13 Characters: 38137 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-ietf-idr-route-oscillation-01.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3345.txt 20 In particular configurations, the BGP scaling mechanisms defined in 21 "BGP Route Reflection - An Alternative to Full Mesh IBGP" and 22 "Autonomous System Confederations for BGP" will introduce persistent 23 BGP route oscillation. This document discusses the two types of 24 persistent route oscillation that have been identified, describes 25 when these conditions will occur, and provides some network design 26 guidelines to avoid introducing such occurrences. 28 This document is a product of the Inter-Domain Routing Working Group 29 of the IETF. 31 This memo provides information for the Internet community. It does 32 not specify an Internet standard of any kind. Distribution of this 33 memo is unlimited. 35 This announcement is sent to the IETF list and the RFC-DIST list. 36 Requests to be added to or deleted from the IETF distribution list 37 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 38 added to or deleted from the RFC-DIST distribution list should 39 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 41 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 42 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 43 help: ways_to_get_rfcs. For example: 45 To: rfc-info@RFC-EDITOR.ORG 46 Subject: getting rfcs 48 help: ways_to_get_rfcs 50 Requests for special distribution should be addressed to either the 51 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 52 specifically noted otherwise on the RFC itself, all RFCs are for 53 unlimited distribution.echo 54 Submissions for Requests for Comments should be sent to 55 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 56 Authors, for further information.