Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-protection-sr-te-paths-00.txt

From: Shraddha Hegde <[email-masked]>
Date: Mon, 5 Oct 2020 10:38:18 +0000

Hi All,

New version for draft-ietf-spring-node-protection-for-sr-te-paths has been posted.
Review comments received during adoption poll have been addressed in this new version.

1. draft name has changed to draft-ietf-spring-segment-protection-sr-te-paths
    As suggested by Bruno to distinguish procedures in this draft with normal 
    Node protection in LFA based mechanism
2. Details  for EPE-Sid and example for border node protection added in sec 3.4
3.  New section 4 added for 
" Determining node can be bypassed"
4. section 6.1 added that contains examples for optimization with same SRGB
5. updated security consideration section.

Let me know if you have further comments.

Rgds
Shraddha

Juniper Business Use Only

-----Original Message-----
From: spring <[email-masked]> On Behalf Of [email-masked]
Sent: Wednesday, September 30, 2020 10:22 PM
To: [email-masked]
Cc: [email-masked]
Subject: [spring] I-D Action: draft-ietf-spring-segment-protection-sr-te-paths-00.txt

[External Email. Be cautious of content]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Source Packet Routing in Networking WG of the IETF.

        Title           : Segment Protection for SR-TE Paths
        Authors         : Shraddha Hegde
                          Chris Bowers
                          Stephane Litkowski
                          Xiaohu Xu
                          Feng Xu
        Filename        : draft-ietf-spring-segment-protection-sr-te-paths-00.txt
        Pages           : 19
        Date            : 2020-09-30

Abstract:
   Segment routing supports the creation of explicit paths using Adj-
   Segment-ID (SID), Node-SIDs, and BSIDs.  It is important to provide
   fast reroute (FRR) mechanisms to respond to failures of links and
   nodes in the Segment-Routed Traffic-Engineered(SR-TE) path.  A point
   of local repair (PLR) can provide FRR protection against the failure
   of a link in an SR-TE path by examining only the first (top) label in
   the SR label stack.  In order to protect against the failure of a
   node, a PLR may need to examine the second label in the stack as
   well, in order to determine SR-TE path beyond the failed node.  This
   document specifies how a PLR can use the first and second label in
   the SR-MPLS label stack describing an SR-TE path to provide
   protection against node failures.

The IETF datatracker status page for this draft is:
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-spring-segment-protection-sr-te-paths/__;!!NEt6yMaO-gk!QqaTT67BPxBKYAvTUcLRWhgBq81bU0x08Souy4RAfT1nWitfU5X5osgDxpO64jMY$

There are also htmlized versions available at:
https://urldefense.com/v3/__https://tools.ietf.org/html/draft-ietf-spring-segment-protection-sr-te-paths-00__;!!NEt6yMaO-gk!QqaTT67BPxBKYAvTUcLRWhgBq81bU0x08Souy4RAfT1nWitfU5X5osgDxhjMsZC6$
https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-protection-sr-te-paths-00__;!!NEt6yMaO-gk!QqaTT67BPxBKYAvTUcLRWhgBq81bU0x08Souy4RAfT1nWitfU5X5osgDxoOh2iKm$

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.

Internet-Drafts are also available by anonymous FTP at:
https://urldefense.com/v3/__ftp://ftp.ietf.org/internet-drafts/__;!!NEt6yMaO-gk!QqaTT67BPxBKYAvTUcLRWhgBq81bU0x08Souy4RAfT1nWitfU5X5osgDxojuc4OH$

_______________________________________________
spring mailing list
[email-masked]
https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/spring__;!!NEt6yMaO-gk!QqaTT67BPxBKYAvTUcLRWhgBq81bU0x08Souy4RAfT1nWitfU5X5osgDxi4hqRwQ$