From nobody Wed Oct 6 01:46:41 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 1E1263A183A for ; Wed, 6 Oct 2021 01:46:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uniroma1.it 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 w3XY1PrvAkt0 for ; Wed, 6 Oct 2021 01:46:34 -0700 (PDT) Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 49C123A1837 for ; Wed, 6 Oct 2021 01:46:32 -0700 (PDT) Received: by mail-io1-xd30.google.com with SMTP id 134so1922090iou.12 for ; Wed, 06 Oct 2021 01:46:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uniroma1.it; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KKwLrYgM38xXn4CT6JnfWY9u7eBN7XUfJWXyewpdhlM=; b=n6e/Fs+VY/dttXpvgSc5I1ZBTS9UBNXlkDD131iHA7PlDFQsXmDIZeUkj/19JHI4Zm S/1rtKxSEDKNp+gqlub8hFqO6v8nFG5s4ME2g55cQpetw2L971EA6Rmc8rzmeyMhp3SP Z3PqOI060RjS2dfLOS/6gMldpDUVEgiB8pk06JCm200E2ORPuaZOAhtUlyHDNWuHP3Al Sw6in4CKcL5TkQq1T6HRUFVYmoYjmPNvQ71HR31R2+KcbJ2orzVzVeafVh8T7qCTHihF lrN3HJHH0HGEZERYnRcUne5jAhhRkaBlUb3nH7l4CeprnfTgLblL63l4b5MH2l5Un0sZ WszQ== 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:cc; bh=KKwLrYgM38xXn4CT6JnfWY9u7eBN7XUfJWXyewpdhlM=; b=WGoctOxAdjQ1rgp5JRsAS+HyBcIDeVYSIwMTvRFvMBIEmwDQEiUzwVwWWsS0S6fLSp ZMp1bTso9fTJt86SL/R8dkVe/W1SqEL/Ol1CQJVE3at9CCjSWaKWLOHFr9hUSVEinVRa 4RfuUBhIjAKkA0mQFCkfHPj/Dtmd6E32LNlifvDBfsD6iMUch7bByEXKtVW3a41x86kQ RGy8SKqhauqSkcmjrW2PmyAYnozlGvMNivSjbiOGKVkOJCxo6yduIPzi3iScg8AYjK/J OPYKiMJXCqDcFEFTCzjhvfTsNevNZJP7+woOQIKnaTArqGFAtYTJFqVPxUJ+NIUCL1IL 6vVQ== X-Gm-Message-State: AOAM5330R5X5mXM4QkvKYnPm5MAqKmy3gP3nW+ixnmQ6I/q4SghPR+6e sDJV5Nasm6M1+aXXjDy0921XW11f7IAUk2qPGuJW9n22/uQU2boNznpvGPu1LA6+RYTEsylY6ps 8TTuHKe5LcvOgTMTt X-Google-Smtp-Source: ABdhPJxKS/lbSYzN+h6jiFkPEBerE6KHMdhbJMsRFThaHid+fm/WwujFPxFZRVWqnKoGFCIA3mJWeTJv3+nf1azj9V8= X-Received: by 2002:a6b:f915:: with SMTP id j21mr5557586iog.98.1633509991845; Wed, 06 Oct 2021 01:46:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Antonio Cianfrani Date: Wed, 6 Oct 2021 10:47:16 +0200 Message-ID: To: "Darren Dukes (ddukes)" Cc: James Guichard , SPRING WG , "spring-chairs@ietf.org" Content-Type: multipart/alternative; boundary="000000000000cd254505cdab2efe" 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: Wed, 06 Oct 2021 08:46:40 -0000 --000000000000cd254505cdab2efe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I support the WG adoption of the CSID draft. I understand that CSID draft defines multiple SRv6 behaviors, but they are based on a single SRv6 data plane solution. Kind regards, Antonio Cianfrani Il giorno mer 6 ott 2021 alle ore 06:30 Darren Dukes (ddukes) ha scritto: > I support the WG adoption of this draft. > > > > I=E2=80=99ve spent a year and a half with the design team studying requir= ements > and analyzing all solutions to SRv6 SID list compression with multiple WG > reviews and many hours of work. The CSID proposal is the strongest, and > fully based on the SRv6 data plane. > > > > Combined with the breadth of contributors, implementations and deployment= s > it makes a very good solution for the working group to adopt and progress= . > I am certain there will be no shortage of interest nor energy to complete > it. > > > > Sincerely > > Darren > > > > > > On 2021-10-01, 10:05 AM, "spring" 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 chan= ge 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 documente= d > 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 a= n > open issue be added to the document in the above-described open issues > section: > > =C2=B7 "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 thi= s > 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 ________________________________________________________ Le informazioni=20 contenute in questo messaggio di posta elettronica sono strettamente=20 riservate e indirizzate esclusivamente al destinatario. Si prega di non=20 leggere, fare copia, inoltrare a terzi o conservare tale messaggio se non= =20 si =C3=A8 il legittimo destinatario dello stesso. Qualora tale messaggio si= a=20 stato ricevuto per errore, si prega di restituirlo al mittente e di=20 cancellarlo permanentemente dal proprio computer. The information contained=20 in this e mail message is strictly confidential and intended for the use of= =20 the addressee only.=C2=A0 If you are not the intended recipient, please do = not=20 read, copy, forward or store it on your computer. If you have received the= =20 message in error, please forward it back to the sender and delete it=20 permanently from your computer system. --=20 Fai crescere i nostri giovani ricercatori dona il=C2=A05=C2=A0per=C2=A0mille=C2=A0alla=20 Sapienza *codice=C2=A0fiscale=C2=A080209930587* --000000000000cd254505cdab2efe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I support the WG adoption of the CSID draft.
I underst= and that CSID draft defines multiple SRv6 behaviors, but they are based on = a single SRv6 data plane solution.
Kind regards,
Antoni= o Cianfrani

Il giorno mer 6 ott 2021 alle ore 06:30 Darren Dukes (dduk= es) <ddukes=3D40cisco.com@= dmarc.ietf.org> ha scritto:

I support the WG adoption of th= is draft.

=C2=A0

I=E2=80=99ve spent a year and a= half with the design team studying requirements and analyzing all solution= s to SRv6 SID list compression with multiple WG reviews and many hours of w= ork.=C2=A0 The CSID proposal is the strongest, and fully based on the SRv6 data plane.

=C2=A0

Combined with the breadth of co= ntributors, implementations and deployments it makes a very good solution f= or the working group to adopt and progress.=C2=A0 I am certain there will b= e no shortage of interest nor energy to complete it.

=C2=A0

Sincerely<= /p>

=C2=A0 Darren

=C2=A0

=C2=A0

On 2021-10-01, 10:05 AM, = "spring" <spring-bounces@ietf.org> wrote:

=C2=A0

Dear= WG:

<= /u>=C2=A0

The = chairs would like to express their appreciation for all the responses recei= ved to our emails with reference to how the working group wishes to move fo= rward with respect to a solution for SRv6 compression.

<= /u>=C2=A0

The = apparent inclination of the working group is to use https://da= tatracker.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.=

<= /u>=C2=A0

Beca= use of the above the chairs would like to issue a 2-week WG call for adopti= on ending October 15th for https://da= tatracker.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 fu= lly aware of and are acknowledging that:

<= /u>=C2=A0

1.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The SPRING working group i= s adopting a document that has multiple SRv6 Endpoint behaviors.

2.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 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.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 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 document editor in conjunction wi= th the chairs.

4.=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 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:

=C2=B7=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 "Given that the worki= ng group has said that it wants to standardize one data plane solution, and= given that the document contains multiple SRv6 EndPoint behaviors that som= e 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.".<= /u>

<= /u>=C2=A0

Plea= se consider the above guidelines as you decide on whether to support or not= this WG adoption. Please express clearly your reasoning for support/non-su= pport as well as any open discussion points you would like addressed should the document be adopted into the wo= rking group.

<= /u>=C2=A0

Than= ks!

<= /u>=C2=A0

Jim,= Bruno & Joel

<= /u>=C2=A0

<= /u>=C2=A0

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

_= _______________________________________________________<= /div>Le informazioni contenute i= n questo messaggio di posta elettronica sono strettamente riservate e indir= izzate esclusivamente al destinatario. Si prega di non leggere, fare copia,= inoltrare a terzi o conservare tale messaggio se non si =C3=A8 il legittim= o destinatario dello stesso. Qualora tale messaggio sia stato ricevuto per = errore, si prega di restituirlo al mittente e di cancellarlo permanentement= e dal proprio computer.
The information contained in this e mail message is strictly confident= ial and intended for the use of the addressee only.=C2=A0 If you are not th= e intended recipient, please do not read, copy, forward or store it on your= computer. If you have received the message in error, please forward it bac= k to the sender and delete it permanently from your computer system.=


Fai = crescere i nostri giovani ricercatori
dona il=C2=A05=C2=A0per=C2=A0mille= =C2=A0alla Sapienza
= codice=C2=A0fiscale=C2=A080209930587
--000000000000cd254505cdab2efe--