Dear WG,
I support the adoption call. CSID draft defines multiple SRv6 flavors, but they present a single SRv6 data plane based solution. Regards, Yuexia Fu 发件人: spring [mailto:[email protected]] 代表 Severin Dellsperger 发送时间: 2021年10月13日 16:00 收件人: James Guichard; SPRING WG 抄送: [email protected] 主题: Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compres sion/ Dear WG I strongly support the WG adoption for the Compressed SRv6 Segment List Encoding in SRH draft ( <https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compre ssion/> https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compres sion/). In different projects, I have worked with SRv6 and used the NEXT-C-SID flavor to enable Segment Routing Traffic Engineering applications, especially in the Service Programming field. The following points convinced me for my decision: * First, the CSID draft supports the different flavors defined in RFC8986 with its next and replace methods. * CSID only supports SRv6 based data plane, which is IMHO the right step for the future Kind Regards, Severin _____ From: spring <[email protected]> on behalf of James Guichard <james.n. [email protected]> Sent: Friday, October 1, 2021 4:04 PM To: SPRING WG <[email protected]> Cc: [email protected] <[email protected]> Subject: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compres sion/ Dear WG: The chairs would like to express their appreciation for all the responses received to our emails with reference to how the working group wishes to move forward with respect to a solution for SRv6 compression. The apparent inclination of the working group is to use https://datatracker. ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/ as the basis for its compression standardization work. That is part of what this email attempts to confirm. Because of the above the chairs would like to issue a 2-week WG call for adoption ending October 15th for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compres sion/ but with some clear guidelines as follows. By expressing support for adoption of this document you are fully aware of and are acknowledging that: 1. The SPRING working group is adopting a document that has multiple SRv6 Endpoint behaviors. 2. The document is a “living” document; it may change as it goes through review and analysis by the SPRING working group. 3. All open discussion points raised on our mailing list MUST be addressed BEFORE said document is allowed to progress from the working group to publication. A list of these discussion points will be documented in the WG document and maintained by the document editor in conjunction with the chairs. 4. If this document is adopted by the working group, the chairs specify as part of the adoption call that the following text describing an open issue be added to the document in the above-described open issues section: * "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.". Please consider the above guidelines as you decide on whether to support or not this WG adoption. Please express clearly your reasoning for support/non-support as well as any open discussion points you would like addressed should the document be adopted into the working group. Thanks! Jim, Bruno & Joel
_______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
