Internet-Draft draft-ietf-rtgwg-srv6-egress-protection-22.txt is now
available. It is a work item of the Routing Area Working Group (RTGWG) WG of
the IETF.

   Title:   SRv6 Path Egress Protection
   Authors: Tao He
            Zhibo Hu
            Huaimo Chen
            Mehmet Toy
            Chang Cao
   Name:    draft-ietf-rtgwg-srv6-egress-protection-22.txt
   Pages:   22
   Dates:   2025-12-02

Abstract:

   TI-LFA specifies fast protections for transit nodes and links of an
   SR path.  However, it does not present any fast protections for the
   egress node of the SR path.  This document describes protocol
   extensions for fast protecting the egress node and link of a Segment
   Routing for IPv6 (SRv6) path.  The solution uses IGP extensions and a
   Mirror SID (End.M) behavior to steer traffic to a protector egress
   upon failure of the primary egress.

   This document operates within a single link-state IGP area/level and
   uses IS-IS/OSPFv3 to advertise a Mirror SID and the protected
   locators for egress node/link protection.  While the mechanism can
   protect traffic whose active segment at the egress is a Service SID
   (e.g., VPN SID), it is not suitable for large-scale deployments with
   a high cardinality of VPN/service instances or random multi-homing
   patterns, because the amount of egress-protection information to be
   flooded in the IGP increases and may impact convergence and control-
   plane load.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-srv6-egress-protection/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-ietf-rtgwg-srv6-egress-protection-22.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-rtgwg-srv6-egress-protection-22

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts


_______________________________________________
rtgwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to