[email protected]
[Top] [All Lists]

Fwd: I-D ACTION:draft-ietf-rtgwg-ipfrr-spec-base-02.txt

Subject: Fwd: I-D ACTION:draft-ietf-rtgwg-ipfrr-spec-base-02.txt
From: Alia Atlas
Date: Mon, 24 Jan 2005 18:21:43 -0500
The main changes to this draft are as follows:

1.  It better addresses multi-homed prefixes.
2.  It discusses SRLG protection in a bit more detail.
3. It describes the local micro-looping via alternates that can occur if an unprotected failure has occurred (and that this can be avoided using downstream paths).
4. It simplifies the alternate selection criteria slightly

Please send comments on these or any additional changes that might be desirable to the list.

To: [email protected]
From: [email protected]
Date: Mon, 24 Jan 2005 15:39:59 -0500
Cc: [email protected]
Subject: I-D ACTION:draft-ietf-rtgwg-ipfrr-spec-base-02.txt
X-BeenThere: [email protected]
X-Mailman-Version: 2.1.5
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
        <mailto:[email protected]?subject=unsubscribe>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[email protected]?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
        <mailto:[email protected]?subject=subscribe>
Sender: [email protected]
X-Avici-Primary-MailScanner-Information: Please contact the ISP for more information
X-Avici-Primary-MailScanner: Found to be clean
X-Avici-Primary-MailScanner-SpamCheck: not spam,
        SpamAssassin (score=-100.465, required 5, AV_BSPAMST2 2.00, AWL 1.18,
        BAYES_00 -4.90, MIME_BOUND_NEXTPART 0.90, NO_REAL_NAME 1.19,
        SARE_HEAD_XBEEN -0.91, TW_GW 0.08, USER_IN_WHITELIST -100.00)
X-MailScanner-From: [email protected]
X-MailScanner-To: [email protected], [email protected], [email protected],
        [email protected]
X-Avici-MailScanner-Information: Please contact the ISP for more information

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Routing Area Working Group Working Group of the IETF.
 Title : Basic Specification for IP Fast-Reroute:
Loop-free Alternates
        Author(s)       : A. Atlas
        Filename        : draft-ietf-rtgwg-ipfrr-spec-base-02.txt
        Pages           : 17
        Date            : 2005-1-24

This document defines an architecture and selection process for
   providing local protection for IP unicast and/or LDP traffic in the
   event of a single link or node failure until the router has
   converged.  When computing the primary next-hop for a prefix, a
   router S also determines an alternate next-hop which can be used if
   the primary next-hop fails.  The alternate next-hop is said to be a
   loop-free alternate, which goes to a neighbor whose shortest path to
   the prefix does not go back through the router S.

A URL for this Internet-Draft is:

To remove yourself from the I-D Announcement list, send a message to
[email protected] with the word unsubscribe in the body of the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-ietf-rtgwg-ipfrr-spec-base-02.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
        [email protected]
In the body type:
        "FILE /internet-drafts/draft-ietf-rtgwg-ipfrr-spec-base-02.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Content-Type: text/plain
Content-ID: <[email protected]>

FILE /internet-drafts/draft-ietf-rtgwg-ipfrr-spec-base-02.txt

Rtgwg mailing list
[email protected]

Rtgwg mailing list
[email protected]

<Prev in Thread] Current Thread [Next in Thread>