Hi, Similar to my comment on the chat during SPRING last Monday. The mailing list has been flooded of opinions, exchanges, technical arguments on all variations, to the extent that it triggered the WG to initiate that DT effort to help get better clarity. I really do think that it would be counterproductive to go back to the list, restart another lengthy technical discussion thread and discard the outcome of what the DT has produced. This discussion has slowed progress on various aspects of the industry (from ASIC SDKs, to large incumbents and new vendors support) and in turn slowed down our ability to deploy. Nonetheless, the community is moving forward with efforts like SONIC on normalizing CSID and SRH within the SAI for broad homogeneous adoption.
So, to the question "Should the working group standardize one data plane behavior for compressing SRv6 information?" I would say a Yes and please follow the outcome of the DT work Cheers, Dan B On 2021-08-04, 2:52 PM, "spring on behalf of Joel M. Halpern" <[email protected] on behalf of [email protected]> wrote: The SPRING Working Group Chairs thank the design team for their efforts on the requirements and analysis drafts. The question of how the working group wants to progress that part of the work will be the topic for a separate email a bit later. Right now, we are hearing the discussion about how many solutions, and the perspectives being expressed. While the topic was well-raised, the discussion to date has not been structured in a way that makes clear to everyone what the purpose is. In particular, the chairs have decided to re-ask the question. We ask that even those who have responded in the discussion respond to this thread. Preferably with both what their opinion is and an explanation of why. The question we are asking you to comment on is: Should the working group standardize one data plane behavior for compressing SRv6 information? Please speak up. We are looking to collect responses until close of business PDT on 20-August-2021. Thank you, Joel, Jim, and Bruno _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring ------------------------------------------------------------------------------ External Email: Please use caution when opening links and attachments / Courriel externe: Soyez prudent avec les liens et documents joints _______________________________________________ spring mailing list [email protected] https://www.ietf.org/mailman/listinfo/spring
