Hi SPRING， Sorry for the late response due to the National days break. It seems like I miss a lot of discussion, and it did cost me a lot of time to read all the threads.
As a member of the design team, and a person who participates in IETF SR standards for a long time, I know who how difficult for us to get here. Many thanks for the contributions from anyone. From the outputs of DT team, we know that CSID meets all the requirements and provide the best performance. As an author of CSID draft, I can say that over 10 vendors have implemented CSID, which proves that CSID has been adopted by the industry very well. Therefore, no matter from the aspect of rough consensus and running code, I do think we should adopt CSID and it is the right way for sure. Also, from many polls in the mailing list, we also see the consensus of using CSID as the basis of SRv6 compression standard. Till now, many our customers have chosen the CSID as the SRv6 compression solution, and some inter-op test and trial deployment have been finished even one year ago in CMCC’s lab and live network, and we will have more product network deployments in the near future. It proves that CSID can work very well in the product network. Many thanks for the customers and partners who choose CSID in their networks and products. There may be some issues discussed in the mailing list, that is good! It also proves that people are interested in the topic as well, we are very welcome anyone to make the contributions to the solution, and let’s do it together to produce a good solution for the industry, that is what we are doing all the long way. Therefore, also thanks to the people provide comments in the mailing list. Will reply to the mailing list to answer the questions ASAP. At the end, as an author, the member of the design team, and a person who focus on SR standards for a long time, I strongly support the CSID adoption. Respect, Cheng 发件人: spring [mailto:spring-boun...@ietf.org] 代表 James Guichard 发送时间: 2021年10月1日 22:05 收件人: SPRING WG <spring@ietf.org> 抄送: spring-cha...@ietf.org 主题: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/ 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-compression/ 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 spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
