Hi Jie, Thank you for your support and valuable comments. We will incorporate your feedback and update appendix A.1 and A.3 in the upcoming version.
Thanks, Changwang 发件人: Dongjie (Jimmy) <[email protected]> 发送时间: 2026年5月18日 18:27 收件人: Susan Hares <[email protected]>; idr@ietf. org <[email protected]>; spring <[email protected]>; Path Computation Element Discussion List <[email protected]> 主题: [spring] Re: WG LC for draft-ietf-idr-sr-policy-seglist-id-09.txt (5/10/2026 to 5/31/2026) Hi Sue, WG, After the discussion with the authors and WG members about the relationship between candidate path and segment lists in SR Policy architecture on the SPRING list, I agree it is suitable to have the segment list ID scoped under the candidate path hierarchy. This is also consistent with the specification of segment list ID in BGP-LS and PCEP extensions. Thus I support progressing this document. I have one comment about the newly added appendix. The text in appendix A.1 has much overlap with the text in the introduction, and is not about the related work in SPRING WG. It is suggested to clear up the text and focus on the work or discussion in SPRING WG related to this draft. Similarly, the text in appendix A.3 about RFC 9857 is not related to SRv6OPS. Best regards, Jie From: Susan Hares <[email protected]<mailto:[email protected]>> Sent: Monday, May 11, 2026 3:47 AM To: idr@ietf. org <[email protected]<mailto:[email protected]>>; spring <[email protected]<mailto:[email protected]>>; Path Computation Element Discussion List <[email protected]<mailto:[email protected]>> Subject: [Pce] WG LC for draft-ietf-idr-sr-policy-seglist-id-09.txt (5/10/2026 to 5/31/2026) Greetings: This is a 3-week WG LC for draft-ietf-idr-sr-policy-seglist-id-09.txt (5/10/2026 to 5/31/2026). The authors of draft-ietf-idr-sr-policy-seglist-id-09.txt should respond to this email with IPR statements. This IDR WG LC is being cross-posted to Spring, PCE, and SRv6ops. This document’s WG LC needs input from these 3 WGs. IDR WG members should discuss this draft and include in their discussion an indication of “support” or “no Support”. IDR members should consider the following: 1) Is this document ready for publication? 2) Does the segment list identifier specified at the candidate path (CP) scope help deployments? 3) Are there any technical flaws in this document? Appendix A of this draft contains a “cross-WG” information regarding Spring and PCE. This WG LC includes Spring and PCE to validate the cross-WG information. In addition, SRV6ops will be informed of the WG LC. This draft limits the scope of the segment list identifier to a candidate path. During January – March, the spring WG discussed whether this should be limited to just the Candidate Path or whether the scope of Segment List ID as unique within the headend node. The discussion is at: https://mailarchive.ietf.org/arch/msg/spring/JVzsniFIj3sSQ93HT4Sl4fbJDpE/ Spring WG – please review the author's decision to limit the BGP mechanism to a candidate path. Does this limitation align with Spring’s view on the segment list identifier? PCE WG - please check that the reference material related to draft-ietf-pce-multipath are correct and valid. Thank you, Susan Hares PS – the SRv6ops is an operational WG – so I will send notification and summarize results. ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出的个人或群组。 禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。 如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
_______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
