Dear Chairs and WG, We've had good interoperability testing to prove that the issue #1 has been addressed well. I think it’s time to close the issue #1.
Best Regards, Shunwan From: spring [mailto:spring-boun...@ietf.org] On Behalf Of Xing James Jiang (jamjiang) Sent: Friday, August 18, 2023 7:25 PM To: Joel Halpern <j...@joelhalpern.com>; SPRING WG List <spring@ietf.org> Subject: [spring] 回复: Issue 1 regarding draft-ietf-spring-srv6-srh-compression Dear chair, I hope this email finds you well. I wanted to express my support for the statement made by the editor regarding the coexistence of different flavor SIDs within the same SRH data plane. Based on my experience with multiple client interoperability tests, this approach has been proven effective. I believe it is time to consider this issue as resolved, as it has been supported by practical evidence and has shown positive results in various customer tests. Thank you for your attention to this matter. Best regards, Xing James Jiang Principal Architect Cisco Systems 发件人: spring <spring-boun...@ietf.org<mailto:spring-boun...@ietf.org>> 代表 Joel Halpern 发送时间: 2023年8月1日 5:09 收件人: SPRING WG List <spring@ietf.org<mailto:spring@ietf.org>> 主题: [spring] Issue 1 regarding draft-ietf-spring-srv6-srh-compression As per the discussions on list and at IETF 117, the SPRING WG chairs (myself and Alvaro specifically) are attempting to determine if we can close the open issues regarding https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-srh-compression/ The editors have entered proposed resolutions for all open issues. This email is to determine if the working group considers issue 1 closable. Issue 1 reads: Given that the working group has said that it wants to standardize one data plane solution, and given that the document contains multiple SRv6 EndPoint behaviors that some WG members have stated are multiple data plane solutions, the working group will address whether this is valid and coherent with its one data plane solution objective. The editors have entered: All SIDs of the SRv6 dataplane (defined in this document and in other documents) can co-exist in the same SRH. This make SRv6 a single, consistent dataplane solution. Please speak up if you agree this resolves this issue, or if you consider that it does not resolve the issue. Objections (and even support if practical) should be specific as to the technical grounds for the statement. Silence will not be considered consent. This call will run for 3 weeks to allow time for at least some people's August vacations and in hopes fo getting a clear reading from the WG. Separate calls for other issues will be issued on a schedule that the chairs have selected to try to balance getting sufficient focus with getting this done, as it has been a long time. Note that if the WG agrees that all issues may be marked as closed, the chairs anticipate issuing the WG last call shortly after that is determined. Speaking up early will help us in all dimensions. If we determine that not all issues can be marked as closed, the chairs will work with the document editors to determine suitable next steps. Thank you, Joel
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
