[Detnet] Re: WG Last Call: draft-ietf-spring-sr-redundancy-protection-07 (Ends 2026-07-06)

[Xuesong Geng <[e-mail]>]

Hi WG,

I would like to express my support for publication as a co-author.
The document has received good discussion in both the SPRING and DetNet working groups, and ready to move forward.

Best
Xuesong

-----Original Message-----
From: Balázs Varga A <[e-mail]> 
Sent: Friday, June 26, 2026 6:32 PM
To: Alvaro Retana <[e-mail]>; [e-mail]; [e-mail]; [e-mail]; [e-mail]
Cc: [e-mail]
Subject: RE: WG Last Call: draft-ietf-spring-sr-redundancy-protection-07 (Ends 2026-07-06)

Hi WG/Chairs

I support (as a co-author) the publication of the draft.
It provides a generalized protection mechanism to achieve high reliability in SRv6 networks.

Thanks & Cheers
Bala'zs

-----Original Message-----
From: Alvaro Retana via Datatracker <[e-mail]>
Sent: Friday, June 19, 2026 6:30 PM
To: [e-mail]; [e-mail]; [e-mail]; [e-mail]
Cc: [e-mail]
Subject: WG Last Call: draft-ietf-spring-sr-redundancy-protection-07 (Ends 2026-07-06)

This message starts a WG Last Call for:
draft-ietf-spring-sr-redundancy-protection-07

This Working Group Last Call ends on 2026-07-06

Abstract:
   Redundancy Protection is a generalized protection mechanism to
   achieve high reliability for service provided in Segment Routing
   networks.  The mechanism uses the "Live-Live" methodology, i.e.,
   multiple copies of the data packets are sent on different paths to
   provide protection.  This document introduces one new SRv6 Segment
   Endpoint Behavior to provide replication and elimination functions on
   specific network nodes by leveraging SRv6 Network Programming
   capabilities.

File can be retrieved from:

Please review and indicate your support or objection to proceed with the publication of this document by replying to this email keeping [e-mail] in copy. Objections should be explained and suggestions to resolve them are highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [1].
Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be found at [3].

Thank you.

[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-spring-sr-redundancy-protection/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-spring-sr-redundancy-protection-07

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-spring-sr-redundancy-protection-07