Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/

["Luc-Fabrice Ndifor Ngwa [ MTN Cameroon ]" <[e-mail]>]

Dear WG,

As a multi-national operator who has deployed SRv6 in some of our markets, we believe we need the SRv6 compression mechanism based on the SRv6 data plane. After reading the CSID, Compression requirements and analysis drafts, I think CSID is the way to go for standardization in IETF, and luckily, that is happening now, so I strongly support the adoption.

I also see many vendors have implemented CSID, and some interoperability test have been made on this, so I believe the mechanism is mature enough. Hope we can have CSID adopted soonest, while the issues can be addressed in the progress following IETF process.
Thanks so far for the work done by the Chairs and DT members.



​Warm regards,
Luc-Fabrice
 
Ndifor
Specialist - IP Access and Data center
[e-mail]
T [phone]
Head Office: 360, Rue Drouot
​P.O. Box 15 574 Douala, Cameroon
T [phone]
 | mtn.cm
This email is confidential. If you have received it in error, you are on notice of its status. Please notify ​the ​​sender immediately by 
​reply email and then delete this message from your system. Please do not copy it ​or use it for any purpose or disclose its content 
​to any other person as to do so could be a breach of ​confidentiality.
​
 Please be informed that no employee or agent is authorized to conclude any legally binding agreement ​on behalf of MTN Cameroon
​via email. This can be only done if the email is confirmed explicitly in writing ​by an MTN Cameroon authorized officer. In no event 
​will this email or its content be construed as a written ​approval.
From: spring <[e-mail]> On Behalf Of James Guichard
Sent: Friday, October 1, 2021 3:05 PM
To: SPRING WG <[e-mail]>
Cc: [e-mail]
Subject: [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