From nobody Thu Oct 14 11:49:51 2021 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A943A0835 for ; Thu, 14 Oct 2021 11:49:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=noviflow.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XbBkXE9h5NTw for ; Thu, 14 Oct 2021 11:49:43 -0700 (PDT) Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E05F43A0869 for ; Thu, 14 Oct 2021 11:49:42 -0700 (PDT) Received: by mail-wr1-x42a.google.com with SMTP id m22so22203864wrb.0 for ; Thu, 14 Oct 2021 11:49:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=noviflow.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Ksv2NXZ2VgentXbShfjvEJeKKm8VPLN+TjYzdnh0Gbs=; b=X9HilCBGU/REkM0Lsc2bMrYloVfJJdc4nuOpx733VpXTgJkg4aAooOS+SjIcfPjr8a ewgmSVdlHTE4ZniCQU2u6vsTvHF76x509hjrOBrPXKEFd72MmzTRAXfJrgQNO8PiXCLh SRXpRvAKEMXi6pIApCYZ66gPfKHDCaRjmhqVQX4bg13w/jppmPOYCFc0R0T5HR3PJnkW CtsQKgDTL24pl31Cx4ZCP4CpbNsBL05Utka8tgW6l32myXni1y7d24FFkIzKcVSK9RTK ZKaL8CjtnriuRQf0PLNvrfX+ykV3NmZcC4abxQm4YUy3/5Nemmmv+i8D5VjZ0oF2coay Nj3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Ksv2NXZ2VgentXbShfjvEJeKKm8VPLN+TjYzdnh0Gbs=; b=vrMWLW6Qix+QsUNPywiKwXPmZv5hqerTGSNd2y4/vyx0F/IqWkWTMug++kAhj9uSoM 7g+KhShRD3PSXgH3/MASMEKyTcGVNtFtz5bP7ZbWeDnvwjOqDWlQe7ZDnsCLAprmwHHx b32vg/l98KiJOHJRT1lPCZsu/YMNsR/JfFZe+L6JEc69Z+KENQLgjFHUqOjpjhIYhci/ meWBVcg5EuioEy5QL4cnI615Wwpp1ZRfK2x4kWe4UE9ZvjIQYfto2DmAqJuISWcWH86r np4L2v5yB1bm/tFiaqWaFDmy6v/wAdQ/lOX+x/f9ZiEgg5v3ITk+dtuqQL9QDu/kUJ9B GSFQ== X-Gm-Message-State: AOAM530nengTvZ6bODNPlVikCcAvyzS7UXgqFZPJuTeETJu6KKhOtA/H x6GjFT/cbIFyioCiqC807hqyJ5384YxzqZiXTfNxx1Fb7B0= X-Google-Smtp-Source: ABdhPJzQfUZkbgGOwoZlhRNya0BXwIJWc5d+OwPczHg8fcbxE/5DC1Cx/plqaPww+wij2uHwSIJf1GrIhyP1Ede6bho= X-Received: by 2002:adf:b350:: with SMTP id k16mr8681503wrd.368.1634237378245; Thu, 14 Oct 2021 11:49:38 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: andre beliveau Date: Thu, 14 Oct 2021 14:49:26 -0400 Message-ID: To: SPRING WG , "spring-chairs@ietf.org" Content-Type: multipart/alternative; boundary="00000000000068d04705ce548adc" Archived-At: Subject: Re: [spring] WG Adoption call for https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compression/ X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2021 18:49:48 -0000 --00000000000068d04705ce548adc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Dear WG and the WG Chairs, The draft https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compre= ssion/ 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 additi= onal 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=C3=A9 B=C3=A9liveau NoviFlow On Fri, Oct 1, 2021 at 10:05 AM James Guichard < james.n.guichard@futurewei.com> 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-comp= ression/ > as the basis for its compression standardization work. That is part of wh= at > 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-comp= ression/ > 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 =E2=80=9Cliving=E2=80=9D 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 docume= nted > in the WG document and maintained by the document editor in conjunctio= n > 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 describin= g 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 co= ntains > multiple SRv6 EndPoint behaviors that some WG members have stated a= re > multiple data plane solutions, the working group will address wheth= er 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 > --=20 *Andr=C3=A9 B=C3=A9liveau* Director Product Management M : +1 514-502-9592 andre.beliveau@noviflow.com www.noviflow.com --00000000000068d04705ce548adc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= ">Dear WG and the WG= Chairs,

The draft=C2=A0https://datatracker.ietf.org/doc/draft-filsfilsch= eng-spring-srv6-srh-compression/=C2=A0=C2=A0is based on SRv6 data plane (RFC8986).=C2=A0 RFC8996 already defines mult= iple behaviors and flavors.=C2=A0=C2=A0As such, RFC8986 nor this draft mandates an SRv6 = data plane node to support all behaviors and flavors.=C2=A0=C2=A0It only=C2=A0 adds=C2= =A0additional= flavors for SRv6 compression to RFC8986.

We, at NoviFlo= w, have implemented a CSID solution.

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

Regards= ,=C2=A0
Andr=C3=A9 B=C3=A9liveau
NoviFlow


On= Fri, Oct 1, 2021 at 10:05 AM James Guichard <james.n.guichard@futurewei.com> wrote:

Dear WG:

=C2=A0

The chairs would like to express their appreciation = for all the responses received to our emails with reference to how the work= ing group wishes to move forward with respect to a solution for SRv6 compre= ssion.

=C2=A0

The apparent inclination of the working group is to = use https://datatracker.ietf.org/doc/draft-filsfilscheng-spring-srv6-srh-compre= ssion/ as the basis for its compression standardization work. That is p= art of what this email attempts to confirm.

=C2=A0

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-compre= ssion/ but with some clear guidelines as follows. By expressing support= for adoption of this document you are fully aware of and are acknowledging= that:

=C2=A0

  1. The SPRING working group is adopting a docume= nt that has multiple SRv6 Endpoint behaviors.
  2. The document is a =E2=80= =9Cliving=E2=80=9D document; it may change as it goes through review and an= alysis by the SPRING working group.
  3. All open discussion points= raised on our mailing list MUST be addressed BEFORE said document is allow= ed to progress from the working group to publication. A list of these discu= ssion points will be documented in the WG document and maintained by the documen= t editor in conjunction with the chairs.
  4. If this document is adopte= d by the working group, the chairs specify as part of the adoption call tha= t the following text describing an open issue be added to the document in t= he above-described open issues section:
    • "Given that the working group has said that it wants to standardiz= e one data plane solution, and given that the document contains multiple SR= v6 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.".

=C2=A0

Please consider the above guidelines as you decide o= n whether to support or not this WG adoption. Please express clearly your r= easoning for support/non-support as well as any open discussion points you = would like addressed should the document be adopted into the working group.

=C2=A0

Thanks!

=C2=A0

Jim, Bruno & Joel

=C2=A0

=C2=A0

_______________________________________________
spring mailing list
spring@ietf.org https://www.ietf.org/mailman/listinfo/spring


--

Andr=C3=A9 B=C3=A9liveau=

Director Product Management

M=C2=A0: +1 514-502-95= 92

andre.beliveau@noviflow.com

=

=C2=A0

www.no= viflow.com

--00000000000068d04705ce548adc--