From ketant.ietf@gmail.com Tue Mar 19 19:22:07 2024 Return-Path: X-Original-To: bess@ietfa.amsl.com Delivered-To: bess@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58EB5C1519B4; Tue, 19 Mar 2024 19:22:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.104 X-Spam-Level: X-Spam-Status: No, score=-2.104 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BjoB6Gwj5aEa; Tue, 19 Mar 2024 19:22:03 -0700 (PDT) Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 782EDC151072; Tue, 19 Mar 2024 19:22:00 -0700 (PDT) Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-56ba73c02b2so912079a12.0; Tue, 19 Mar 2024 19:22:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710901318; x=1711506118; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JDVHZZVfbUqek40pDj9tWlREvx2uY0BhwjMLt/jp2Yw=; b=bajTjWO533YaFCZ/zzuRC2j4AUh2miu7NcViSH6Lbm3MjfNhCOJlBAPE92vXsSucNs u0ZncDMLmhKrmPrQQ1SPLv1c25t4ovIkqHpZ9P6rK16LHxKBc/ZUuiUQ09LIYtGnGl0i reBBvHmHO3KV1N+qNssmKvEtZ2Q8c8yaeWR2tDLmCETpOdzNu7IgXMb5JlMVkSpX9crH y26Y4OhfqRUKJPa9B21fCY2ADzudKsM4CbkLRoiXIUCab99yztkggjQibYUmjfHnlfkx EdvpdD/6+MMTagzLDbeSp2xjKSoEQYACchSym210mjFp0Hom2MbpaGnaYyexrf3Pp4WG CkaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710901318; x=1711506118; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JDVHZZVfbUqek40pDj9tWlREvx2uY0BhwjMLt/jp2Yw=; b=rhXX5cGWvXecWoLB+1eVO99XwLdTJ6MKkoWGk+F8g1xUruEuXvq3v8fF7Z0rDS3J0J O/AhuPFY644c3zxMABQnOu09p1vtwlY3ZpSrr6wzpBPV31nE5W56kQ6E9V8pUjppXNEu eabFmeLwtVGaZD/4Nxw5ENPWWSnn23Lcn8g5rpNd503hcrqp9yI1bolYsMb8SpVublS8 MNCp7HlBzuosjSP3R6CBZxyawdk2fq4qSeeZsbfrjwwg8kMNTSry+GZ8yJa4a6qYoO0O MkC+Q0HJarqygQtXTt5yWAw0kMg1DB0TBoFBQaK/AdlyMQRiPGEw+kaWcmBO0oiz/clj XdLw== X-Gm-Message-State: AOJu0YzKxxHQTOdosga0Z9p9hNqFXd4G8+oaDDEM6AxgXvRgRZvf/qqA 8fUmiiq1zPVQpCzvUuLVwoV5/RAH5GUJkXJnLxMOg0CqPw0DQtZt95SbD1DtAcTztq9QPgqvBWu D/JVAv6OYP2bGlXBwEKln6mhT0A1BtbA+ X-Google-Smtp-Source: AGHT+IGP9kp8UTrnrAw2j9HqdGiQHapG7BP0CdOaijoEU3bhHKAY9AjHSB0nTKzAOHdpo700OAGHgX9sReAzI5phyUM= X-Received: by 2002:a17:906:28cf:b0:a46:dace:3fbf with SMTP id p15-20020a17090628cf00b00a46dace3fbfmr2568909ejd.30.1710901318103; Tue, 19 Mar 2024 19:21:58 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ketan Talaulikar Date: Wed, 20 Mar 2024 07:51:46 +0530 Message-ID: To: "bess-chairs@ietf.org" Cc: BESS Content-Type: multipart/alternative; boundary="0000000000004fb89306140e41bf" Archived-At: Subject: [bess] Request for an expedited WG last call for draft-ietf-bess-bgp-srv6-args X-BeenThere: bess@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: BGP-Enabled ServiceS working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Mar 2024 02:22:07 -0000 --0000000000004fb89306140e41bf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello WG/Chairs, The authors would like to request for an expedited WGLC for this document for the same reason as we requested for an expedited adoption - since it "updates" a WG RFC by clarifying aspects (no new functionality). We've already reported implementations (prior to WG adoption even). Thanks, Ketan (on behalf of co-authors) On Tue, Aug 1, 2023 at 11:48=E2=80=AFPM Ketan Talaulikar wrote: > +1 > > Cisco (IOS-XR) also has an implementation of this. > > Thanks, > Ketan > > > On Tue, Aug 1, 2023 at 11:16=E2=80=AFAM Jorge Rabadan (Nokia) < > jorge.rabadan@nokia.com> wrote: > >> Hi, >> >> >> >> Nokia has an implementation of draft-trr-bess-bgp-srv6-args in SROS. >> >> >> >> As Ketan says, it is important to make this work WG adopted as soon as >> possible so that new implementors become aware of the changes compared t= o >> RFC9252. >> >> >> >> Thanks, >> >> Jorge >> >> >> >> *From: *Matthew Bocci (Nokia) >> *Date: *Tuesday, August 1, 2023 at 10:25 AM >> *To: *Ketan Talaulikar , bess-chairs@ietf.org < >> bess-chairs@ietf.org> >> *Cc: *draft-trr-bess-bgp-srv6-args@ietf.org < >> draft-trr-bess-bgp-srv6-args@ietf.org>, BESS >> *Subject: *Re: Request for an expedited WG adoption call for >> draft-trr-bess-bgp-srv6-args >> >> Hi Ketan >> >> >> >> If we can do a quick implementation poll for the changes proposed in the >> draft, that would help. >> >> >> >> Thanks >> >> >> >> Matthew >> >> >> >> *From: *Ketan Talaulikar >> *Date: *Thursday, 27 July 2023 at 15:02 >> *To: *bess-chairs@ietf.org >> *Cc: *draft-trr-bess-bgp-srv6-args@ietf.org < >> draft-trr-bess-bgp-srv6-args@ietf.org>, BESS >> *Subject: *Request for an expedited WG adoption call for >> draft-trr-bess-bgp-srv6-args >> >> >> >> *CAUTION:* This is an external email. Please be very careful when >> clicking links or opening attachments. See the URL nok.it/ext for >> additional information. >> >> >> >> Hello Chairs, >> >> >> >> The authors would like to drop this gentle reminder of our request for a= n >> expedited WG adoption call for this draft that we had presented at IETF1= 16. >> >> >> >> The draft is in essence an "errata" for a certain portion our BESS WG >> RFC9252. The concerned portions of the specification have been in >> development at various vendors for quite some time now. Interop issues w= ere >> identified and these clarifications are needed for smooth interop and >> deployments that are ongoing. >> >> >> >> Thanks, >> >> Ketan (on behalf of co-authors) >> >> >> >> On Thu, Apr 27, 2023 at 10:12=E2=80=AFAM Ketan Talaulikar >> wrote: >> >> Hello All, >> >> >> >> We had presented >> https://datatracker.ietf.org/doc/draft-trr-bess-bgp-srv6-args/ at the >> IETF 116. >> >> >> >> The slides are available at: >> https://datatracker.ietf.org/meeting/116/materials/slides-116-bess-draft= -trr-bess-srv6-args-00.pdf >> >> >> >> Since this draft aims to fix some issues in the RFC9252 that was >> published by BESS WG, we had sought feedback/review from the WG and >> requested the WG chairs for an expedited WG adoption. >> >> >> >> We also wanted to check if any follow-up was required for the comments >> that were discussed at the meeting. >> >> >> >> Thanks, >> >> Ketan (on behalf of co-authors) >> >> >> >> --0000000000004fb89306140e41bf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello WG/Chairs,

The authors= would like to request for an expedited WGLC for this document for the same= reason as we requested for an expedited adoption - since it "updates&= quot; a WG RFC by clarifying aspects (no new functionality).=C2=A0

We've already reported implementations (prior to WG ad= option even).=C2=A0

Thanks,
Ketan (on be= half of co-authors)


On Tue, Aug 1, 2023 at 11:48=E2=80=AFPM K= etan Talaulikar <ketant.ietf@gm= ail.com> wrote:
+1

Cisco (IOS-XR) also has a= n implementation of this.

Thanks,
Ketan<= /div>


On Tue, Aug 1, 2023 at 11:16=E2=80=AFAM Jorge Rabadan (= Nokia) <jor= ge.rabadan@nokia.com> wrote:

Hi,

=C2=A0

Nokia has an implementation of draft-trr-bess-bgp-srv6-args in SROS.

=C2=A0

As Ketan says, it is important to make this work WG adopte= d as soon as possible so that new implementors become aware of the changes = compared to RFC9252.

=C2=A0

Thanks,

Jorge

=C2=A0

From: <= /b>Matthew Bocci = (Nokia) <ma= tthew.bocci@nokia.com>
Date: Tuesday, August 1, 2023 at 10:25 AM
To: Ketan Talaulikar <ketant.ietf@gmail.com>, bess-chairs@ietf.org <bess-chairs@ietf.org>
Cc: draft-trr-bess-bgp-srv6-args@ietf.org <draft-trr-bess-bg= p-srv6-args@ietf.org>, BESS <bess@ietf.org>
Subject: Re: Request for an expedited WG adoption call for draft-trr= -bess-bgp-srv6-args

Hi Ketan

=C2=A0

If we can do a quick implementation poll for the chang= es proposed in the draft, that would help.

=C2=A0

Thanks

=C2=A0

Matthew

=C2=A0

From: <= /b>Ketan Talaulik= ar <ketant.ie= tf@gmail.com>
Date: Thursday, 27 July 2023 at 15:02
To: bess-c= hairs@ietf.org <bess-chairs@ietf.org>
Cc: draft-trr-bess-bgp-srv6-args@ietf.org <draft-trr-bess-bg= p-srv6-args@ietf.org>, BESS <bess@ietf.org>
Subject: Request for an expedited WG adoption call for draft-trr-bes= s-bgp-srv6-args

=C2=A0

CAUTION: This is an external email= . Please be very careful when clicking links or opening attachments. See th= e URL nok.it/ext for ad= ditional information.

=C2=A0

Hello Chairs,

=C2=A0

The authors would like to drop this gentle reminder of= our request for an expedited WG adoption call for this draft that we had p= resented at IETF116.

=C2=A0

The draft is in essence an "errata" for a ce= rtain portion our BESS WG RFC9252. The concerned portions of the specificat= ion have been in development at various vendors for quite some time now. Interop issues were identified and these clarific= ations are needed for smooth interop and deployments that are ongoing.

=C2=A0

Thanks,

Ketan (on behalf of co-authors)

=C2=A0

On Thu, Apr 27, 2023 at 10:12=E2=80=AFAM Ketan Talauli= kar <ketant.i= etf@gmail.com> wrote:

Hello All,

=C2=A0

=C2=A0

=C2=A0

Since this draft aims to fix some issues in the RFC925= 2 that was published=C2=A0by BESS WG, we had sought feedback/review from th= e WG and requested the WG chairs for an expedited WG adoption.

=C2=A0

We also wanted to check if any follow-up was required = for the comments that were discussed at the meeting.

=C2=A0

Thanks,

Ketan (on behalf of co-authors)

=C2=A0

--0000000000004fb89306140e41bf--