Hi, Alvaro et al.
I read the current version, and I support progressing the draft to IESG.
The draft is well-written and addresses the essential requirements for
DetNet by providing packet replication and elimination functionality (PREF)
in an SRv6 environment. Please find my notes below:
- Redundancy protection can help to achieve zero packet loss target
when failure on either path happens.
Although zero packet loss is an ultimate goal, it might not be achievable,
even using PREF. Perhaps the value of the PREF can be conveyed as follows:
Redundancy protection can reduce the packet loss level to conform
to the Service Level Objective of a DetNet service.
- I got confused by:
It is RECOMMENDED to add the sequence number in
forwarding plane as performance and scalability is required.
Could it be edited as:
A sequence number MUST be included in the data plane.
WDYT?
Regards,
Greg
On Fri, Jun 19, 2026 at 9:30 AM Alvaro Retana via Datatracker <
[email protected]> wrote:
> 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
> [email protected] 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
>
> _______________________________________________
> detnet mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]
