RFC 3345 on Border Gateway Protocol (BGP) Persistent Route Oscillation Condition
rfc-editor@rfc-editor.org Thu, 01 August 2002 21:57 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17336; Thu, 1 Aug 2002 17:57:54 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id RAA00043 for ietf-123-outbound.10@ietf.org; Thu, 1 Aug 2002 17:55:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id RAA29856 for <all-ietf@loki.ietf.org>; Thu, 1 Aug 2002 17:45:43 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15840 for <all-ietf@ietf.org>; Thu, 1 Aug 2002 17:44:33 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g71LjgE06211; Thu, 1 Aug 2002 14:45:42 -0700 (PDT)
Message-Id: <200208012145.g71LjgE06211@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3345 on Border Gateway Protocol (BGP) Persistent Route Oscillation Condition
Cc: rfc-editor@rfc-editor.org, idr@merit.edu
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 01 Aug 2002 14:45:42 -0700
Sender: rfc-ed@ISI.EDU
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: danny@tcb.net, vijay@umbc.edu, dwalton@cisco.com,
aretana@cisco.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.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.