Hi

I uploaded version 18 of the ti-lfa draft to address the two DISCUSS items in
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-segment-routing-ti-lfa/ballot/

- To address John Scudder's Discuss, I made the modifications to remove the word "key" from the abstract as suggested by Sasha at
https://mailarchive.ietf.org/arch/msg/rtgwg/nWR4uYaT3T30XRiyRdAoIqO22AM/
and Pierre at
https://mailarchive.ietf.org/arch/msg/rtgwg/zHP2qvP2Ew1oWl5G7Gq8niu8vy8/

- To address Murray Discuss (as well as as comments from others) I removed the word "SHOULD" from sections 6.2, 6.3, and 9 as I suggested during my presentation during the rtgwg meeting last Tuesday Nov/5/24.
The entire recording of the RTGWG meeting can be found in
https://meetecho-player.ietf.org/playout/?session=IETF121-RTGWG-20241105-0930
The slides that I presented in in PDF format can be found in
https://datatracker.ietf.org/meeting/121/materials/slides-121-rtgwg-02-tilfa-bgppic-00.pdf


Please take a look and see if the modifications areĀ  good to address the two DISCUSS Items


Thanks

Ahmed


On 11/13/24 11:16 AM, internet-dra...@ietf.org wrote:
A new version of Internet-Draft draft-ietf-rtgwg-segment-routing-ti-lfa-18.txt
has been successfully submitted by Ahmed Bashandy and posted to the
IETF repository.

Name:     draft-ietf-rtgwg-segment-routing-ti-lfa
Revision: 18
Title:    Topology Independent Fast Reroute using Segment Routing
Date:     2024-11-13
Group:    rtgwg
Pages:    27
URL:      
https://www.ietf.org/archive/id/draft-ietf-rtgwg-segment-routing-ti-lfa-18.txt
Status:   
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-segment-routing-ti-lfa/
HTMLized: 
https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-segment-routing-ti-lfa
Diff:     
https://author-tools.ietf.org/iddiff?url2=draft-ietf-rtgwg-segment-routing-ti-lfa-18

Abstract:

    This document presents Topology Independent Loop-free Alternate Fast
    Reroute (TI-LFA), aimed at providing protection of node and adjacency
    segments within the Segment Routing (SR) framework.  This Fast
    Reroute (FRR) behavior builds on proven IP Fast Reroute concepts
    being LFAs, remote LFAs (RLFA), and remote LFAs with directed
    forwarding (DLFA).  It extends these concepts to provide guaranteed
    coverage in any two-connected networks using a link-state IGP.
    Although not a TI-LFA requirement or constraint, TI-LFA also brings
    the benefit of the ability to provide a backup path that follows the
    expected post-convergence path, reducing the operational need to
    control the tie-breaks among various FRR options.



The IETF Secretariat



_______________________________________________
rtgwg mailing list -- rtgwg@ietf.org
To unsubscribe send an email to rtgwg-le...@ietf.org

Reply via email to