grow: RFC 4264 on BGP Wedgies

rfc-editor@rfc-editor.org Wed, 23 November 2005 01:41 UTC

Message-Id: <200511230119.jAN1JZE23323@boreas.isi.edu>
To: ietf-announce@ietf.org
Subject: grow: RFC 4264 on BGP Wedgies
Cc: rfc-editor@rfc-editor.org, grow@lists.uoregon.edu
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 22 Nov 2005 17:19:35 -0800
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

A new Request for Comments is now available in online RFC libraries.


        RFC 4264

        Title:      BGP Wedgies
        Author(s):  T. Griffin, G. Huston
        Status:     Informational
        Date:       November 2005
        Mailbox:    Timothy.Griffin@cl.cam.ac.uk, gih@apnic.net
        Pages:      10
        Characters: 24139
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-grow-bgp-wedgies-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4264.txt


It has commonly been assumed that the Border Gateway Protocol (BGP)
is a tool for distributing reachability information in a manner that
creates forwarding paths in a deterministic manner.  In this memo we
will describe a class of BGP configurations for which there is more
than one potential outcome, and where forwarding states other than
the intended state are equally stable.  Also, the stable state where
BGP converges may be selected by BGP in a \%non-deterministic manner.
These stable, but unintended, BGP states are termed here "BGP
Wedgies".

This document is a product of the Global Routing Operations 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.

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.

ftp://ftp.isi.edu/in-notes/rfc4264.txt"><ftp://ftp.isi.edu/in-notes/rfc4264.txt>

grow: RFC 4264 on BGP Wedgies rfc-editor