Re: [Teas] New Version Notification for draft-ietf-teas-assoc-corouted-bidir-frr-01.txt

"Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com> Thu, 25 May 2017 11:51 UTC

From: "Rakesh Gandhi (rgandhi)" <rgandhi@cisco.com>
To: "teas@ietf.org" <teas@ietf.org>
CC: Himanshu Shah <hshah@ciena.com>, Jeremy Whittaker <jeremy.whittaker@verizon.com>
Thread-Topic: New Version Notification for draft-ietf-teas-assoc-corouted-bidir-frr-01.txt
Thread-Index: AQHS1Oj1mhLJ2C+pzEK4o1TYYFjKIqIFAXwA
Date: Thu, 25 May 2017 11:51:38 +0000
Message-ID: <C4619309-A255-47C9-AC08-7918CF55FC84@cisco.com>
References: <149567001401.8600.7329512822043989999.idtracker@ietfa.amsl.com>
In-Reply-To: <149567001401.8600.7329512822043989999.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/f.1d.0.161209
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.248.123]
Content-Type: text/plain; charset="utf-8"
Content-ID: <FB6D707944135F4FB2DE6B76ABC2044C@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/3C0BozZJ2ijewtGdQMf5Wc1IiVQ>
Subject: Re: [Teas] New Version Notification for draft-ietf-teas-assoc-corouted-bidir-frr-01.txt
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 May 2017 11:51:42 -0000

Hi WG,

The document draft-ietf-teas-assoc-corouted-bidir-frr has been updated as following:

Added Section 1.1. on assumptions and considerations (e.g. bypass tunnels are also bidirectional)
Added reference and text in Section 1 for PCE initiated bidirectional LSPs
Move definition of Forward LSPs to terminology Section
Added Section 3.2 and 4.1.1 on node protection bypass tunnels
Added usage of path errors in Section 4.1
Added Section 4.1.2 on unidirectional link failures
Added Section 4.1.3 on revertive behavior after FRR
Added Section 4.1.4 on bypass tunnel provisioning
Various editorial changes

We welcome your review comments and suggestions.

Thanks,
Rakesh (for authors)


On 2017-05-24, 7:53 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org> wrote:

    
    A new version of I-D, draft-ietf-teas-assoc-corouted-bidir-frr-01.txt
    has been successfully submitted by Rakesh Gandhi and posted to the
    IETF repository.
    
    Name:		draft-ietf-teas-assoc-corouted-bidir-frr
    Revision:	01
    Title:		Fast Reroute Procedures for Associated Bidirectional Label Switched Paths (LSPs)
    Document date:	2017-05-24
    Group:		teas
    Pages:		15
    URL:            https://www.ietf.org/internet-drafts/draft-ietf-teas-assoc-corouted-bidir-frr-01.txt
    Status:         https://datatracker.ietf.org/doc/draft-ietf-teas-assoc-corouted-bidir-frr/
    Htmlized:       https://tools.ietf.org/html/draft-ietf-teas-assoc-corouted-bidir-frr-01
    Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-teas-assoc-corouted-bidir-frr-01
    Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-assoc-corouted-bidir-frr-01
    
    Abstract:
       Resource Reservation Protocol (RSVP) association signaling can be
       used to bind two unidirectional LSPs into an associated bidirectional
       LSP.  When an associated bidirectional LSP is co-routed, the reverse
       LSP follows the same path as its forward LSP.  This document
       describes Fast Reroute (FRR) procedures for both single-sided and
       double-sided provisioned associated bidirectional LSPs.  The FRR
       procedures can ensure that for the co-routed LSPs, traffic flows on
       co-routed paths in the forward and reverse directions after a failure
       event.
    
    
                                                                                      
    
    
    Please note that it may take a couple of minutes from the time of submission
    until the htmlized version and diff are available at tools.ietf.org.
    
    The IETF Secretariat

Re: [Teas] New Version Notification for draft-iet… Rakesh Gandhi (rgandhi)