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

[andre beliveau <[e-mail]>]

Dear WG and the WG Chairs,

The draft
https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/
<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dfilsfilscheng-2Dspring-2Dsrv6-2Dsrh-2Dcompression_&d=DwMFAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=QmgeAx3FBTO5s5SiLkMF0kKr2hmFESV-Jif0H28xnCs&m=QyeZ7IN8W75uqLz5o-Ns01fXF6rFrEqm1-jvPcEWfX8&s=vTbmENGQL8KGlVuCpApLRywxBS56YlWlciQgqUdTu60&e=>
  is based on SRv6 data plane (RFC8986).  RFC8996 already defines multiple
behaviors and flavors.  As such, RFC8986 nor this draft mandates an SRv6
data plane node to support all behaviors and flavors.  It only  adds additional
flavors for SRv6 compression to RFC8986.

We, at NoviFlow, have implemented a CSID solution.

I strongly support the adoption of the draft and believe that it is valid
and coherent with the WG objective of one data plane solution.

Regards,
André Béliveau
NoviFlow


On Fri, Oct 1, 2021 at 10:05 AM James Guichard <
[e-mail]> wrote:

> 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/spring
>


-- 

*André Béliveau*

Director Product Management

M : [phone]

[e-mail]



www.noviflow.com