[email protected]
[Top] [All Lists]

Fwd: I-D ACTION:draft-atlas-ip-local-protect-uturn-01.txt

Subject: Fwd: I-D ACTION:draft-atlas-ip-local-protect-uturn-01.txt
From: Alia Atlas
Date: Tue, 26 Oct 2004 21:49:42 -0400
I've revised the U-turn alternates draft.  The major changes are as follows:

a) Introduced the option for explicitly marking U-turn traffic.
This may simplify some hardware implementations, allows handling of more broadcast link cases, allows correct handling of traffic exiting a TE tunnel via PHP (if needed), and provides a method where only traffic that is explicitly requested to be sent to the alternate will be.
b) Added example algorithm for computing u-turn alternates. Worst-case is
N additional SPFs, where N is the number of neighbors that could be U-turn
alternates. This should also clarify reason for the alternate selection
procedure. There is a brief discussion on considering SRLGs.

To: [email protected]
From: [email protected]
Date: Tue, 26 Oct 2004 16:33:39 -0400
Subject: I-D ACTION:draft-atlas-ip-local-protect-uturn-01.txt
X-BeenThere: [email protected]
X-Mailman-Version: 2.1.5
Reply-To: [email protected]
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
        <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/i-d-announce>,
        <mailto:[email protected]?subject=subscribe>
Sender: [email protected]
X-Avici-MailScanner: Found to be clean, Found to be clean
X-Avici-MailScanner-SpamCheck: not spam, SpamAssassin (score=-100.08,
        required 5, AV_BSPAMST2 2.00, AWL 1.64, BAYES_00 -4.90,
        USER_IN_WHITELIST -100.00)
X-MailScanner-From: [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.

        Title           : U-turn Alternates for IP/LDP Local Protection
        Author(s)       : A. Atlas
        Filename        : draft-atlas-ip-local-protect-uturn-01.txt
        Pages           : 27
        Date            : 2004-10-26

This document defines and describes the use of u-turn alternates to
   provide local protection for IP unicast and/or LDP traffic in the
   event of a single link or node failure.  When a topology change
   occurs, a router S pre-computes for each prefix an alternate next-hop
   that can be used if the primary next-hop fails.  An acceptable
   alternate can be either a loop-free alternate or a U-turn alternate.
   A U-turn alternate uses a neighbor, whose primary next-hop to the
   prefix is router S itself and which has itself a loop-free
   node-protecting alternate, which thus does not go through router S to
   reach the destination prefix.

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-atlas-ip-local-protect-uturn-01.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-atlas-ip-local-protect-uturn-01.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-atlas-ip-local-protect-uturn-01.txt

I-D-Announce mailing list
[email protected]

Rtgwg mailing list
[email protected]

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