Skip to main content

Topology Independent Fast Reroute using Segment Routing
draft-ietf-rtgwg-segment-routing-ti-lfa-17

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-rtgwg-segment-routing-ti-lfa@ietf.org, james.n.guichard@futurewei.com, rfc-editor@rfc-editor.org, rtgwg-chairs@ietf.org, rtgwg@ietf.org, stewart.bryant@gmail.com
Subject: Protocol Action: 'Topology Independent Fast Reroute using Segment Routing' to Proposed Standard (draft-ietf-rtgwg-segment-routing-ti-lfa-13.txt)

The IESG has approved the following document:
- 'Topology Independent Fast Reroute using Segment Routing'
  (draft-ietf-rtgwg-segment-routing-ti-lfa-13.txt) as Proposed Standard

This document is the product of the Routing Area Working Group.

The IESG contact persons are Jim Guichard, Andrew Alston and John Scudder.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-segment-routing-ti-lfa/


Ballot Text

Technical Summary

   This document presents Topology Independent Loop-free Alternate Fast
   Re-route (TI-LFA), aimed at providing protection of node and
   adjacency segments within the Segment Routing (SR) framework.  This
   Fast Re-route (FRR) behavior builds on proven IP-FRR 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.  A key aspect of
   TI-LFA is the FRR path selection approach establishing protection
   over the expected post-convergence paths from the point of local
   repair, reducing the operational need to control the tie-breaks among
   various FRR options.

Working Group Summary

   It is strongly advocated by a few, but most are relatively silent. However, this is a widely implemented protocol with no WG objection for publication. 

Document Quality

   Widely implemented and deployed protocol. 

Personnel

   The Document Shepherd for this document is Stewart Bryant. The
   Responsible Area Director is Jim Guichard.

RFC Editor Note