Dear Alvaro,

Many thanks for the detailed review.

We have created an update of the draft. It includes the comments received 
during WGLC.
All Your major and minor comments were addressed. Again, thanks for the details 
and the 
clear formulation of your suggestions, they helped a lot to improve the 
document. 

The changes in the draft have not affected the technical details of the 
solution, however 
they helped to make clear many implicit statements and spell them out 
explicitly.

Based on these comments major updates of the draft are:
- Section 3. was restructured to contain all building blocks of the Redundancy 
Protection. 
The former Section 5. (Meta Data) and Section 6. (Redundancy Policy) were 
integrated here.
- Section 3.3 (Redundancy Policy) was improved with an explicit list of 
information that is 
needed in the Redundancy Policy entries. 
- New section (6.  Implementation Description) was added. 
- New section (7.  Operational Considerations) was added to describe 
operational aspect.
- Section 8. (Security Considerations) were extended and clarifications were 
added.
- Reactions to Your numbered list are inline below. 

The new version will be uploaded when upload is re-opened before the meeting 
(i.e., Sunday).
In the meantime, you can find it here:
https://drive.google.com/drive/folders/1t-bodD468n4nI4uUkJQFnXD_QqpcKdn8?usp=sharing

Many thanks & Cheers
Bala'zs (and the Co-Authors/Contributors)


-----Original Message-----
From: Balázs Varga A 
Sent: Tuesday, July 7, 2026 11:59 AM
To: 'Alvaro Retana' <[email protected]>; 
[email protected]
Cc: [email protected]; [email protected]; [email protected]; Luis M. Contreras 
<[email protected]>
Subject: RE: Chair Review of draft-ietf-spring-sr-redundancy-protection-07 
(WGLC)

Dear Alvaro,
Many thanks for the detailed review.
We will come back soon with suggested changes/improvements.
The new version will be uploaded, when upload is re-opened before the meeting.
Thanks
Bala'zs

-----Original Message-----
From: Alvaro Retana <[email protected]>
Sent: Friday, July 3, 2026 11:52 PM
To: [email protected]
Cc: [email protected]; [email protected]; [email protected]; Luis M. Contreras 
<[email protected]>
Subject: Chair Review of draft-ietf-spring-sr-redundancy-protection-07 (WGLC)

Dear authors:

I have many questions and concerns, and I believe significant work is required. 
To be clear, I'm not opposed to this work progressing, but the draft is not 
ready in its current form.

Please see detailed comments inline below. I want to highlight some high-level 
issues:

1. Is Path Protection required? (line 105)
<VBalazs> It is optional. Text was updated.

2. Operational/Deployment guidance is present in several parts of the draft.
   Consider a standalone Operational Considerations section
   (see draft-ietf-opsawg-rfc5706bis).
<VBalazs> New section was added.

3. The relationship between this work and DetNet documents:
   draft-ietf-detnet-srv6-svc-protection (line 272), rfc8939 (line 466), and
   the DetNet architecture in general should be clarified.
<VBalazs> It defines the usage of RSID in the DetNet service sub-layer.

4. The elimination functionality adds state to the network at an egress node,
   which represents a departure from the SR Architecture (rfc8402). This needs
   to be discussed further (line 274).
<VBalazs> From the segment routing architecture perspective R-nodes are 
ingresss node for the served member flows. Text was updated.

5. What should be the characteristics of the FIDs? What happens if there are
   collisions? (line 443)
<VBalazs> FIDs are locally unique on the R-node. Text was updated.

6. Provide guidance about the size of the FID and SN (line 466).
<VBalazs> Text was updated with size requirements.

7. Expand on the concept of a Redundancy Policy and how it relates to
rfc9256 (line 480).
<VBalazs> Text was updated, it has a dedicated section 3.3.

8. An Implementation Description section is needed (line 494).
<VBalazs> New section was added.

9. Several threats have not been addressed in the Security Considerations
   section (line 503). Also, consider draft-spring-srv6-security.
<VBalazs> Section was updated.

Please take these comments with others that you may receive during the WGLC.

Thanks!

Alvaro.

... 
See the rest of the message: 
https://mailarchive.ietf.org/arch/msg/spring/sMJEvVO_i9DBC5dgbZRON4WvnR0/
_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to