[bess] Request for an expedited WG last call for draft-ietf-bess-bgp-srv6-args

Ketan Talaulikar <ketant.ietf@gmail.com> Wed, 20 March 2024 02:22 UTC

Return-Path: <ketant.ietf@gmail.com>
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: <CAH6gdPxqnYAGCFU0erj+vcvgzWG9iZbJJpSHEL=6Q14-x8YWbw@mail.gmail.com> <CAH6gdPzm_Nbzma3KJu+Bio0-qkJT4rgh=LFR+e3o2dybt1TjtA@mail.gmail.com> <DU0PR07MB9218AC8A4BC260E34EDA5823EB0AA@DU0PR07MB9218.eurprd07.prod.outlook.com> <BY3PR08MB7060B78501D49D5DE4BA4EE3F70AA@BY3PR08MB7060.namprd08.prod.outlook.com> <CAH6gdPzkCHFDK1yKRd2A4mN+WnY026cdfZ56swoQTaSiAOcHOA@mail.gmail.com>
In-Reply-To: <CAH6gdPzkCHFDK1yKRd2A4mN+WnY026cdfZ56swoQTaSiAOcHOA@mail.gmail.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Wed, 20 Mar 2024 07:51:46 +0530
Message-ID: <CAH6gdPzGH15rhEh0oqCrbRwBPWgcx+bUanB+UZyzM_QBxa_FBg@mail.gmail.com>
To: "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Cc: BESS <bess@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004fb89306140e41bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/4QbQdW0VcKm4EJOwKF2ueEmz-Is>
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 <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2024 02:22:07 -0000

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 PM Ketan Talaulikar <ketant.ietf@gmail.com>
wrote:

> +1
>
> Cisco (IOS-XR) also has an implementation of this.
>
> Thanks,
> Ketan
>
>
> On Tue, Aug 1, 2023 at 11:16 AM 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 to
>> RFC9252.
>>
>>
>>
>> Thanks,
>>
>> Jorge
>>
>>
>>
>> *From: *Matthew Bocci (Nokia) <matthew.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-bgp-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
>>
>>
>>
>> If we can do a quick implementation poll for the changes proposed in the
>> draft, that would help.
>>
>>
>>
>> Thanks
>>
>>
>>
>> Matthew
>>
>>
>>
>> *From: *Ketan Talaulikar <ketant.ietf@gmail.com>
>> *Date: *Thursday, 27 July 2023 at 15:02
>> *To: *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 <bess@ietf.org>
>> *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 an
>> expedited WG adoption call for this draft that we had presented at IETF116.
>>
>>
>>
>> 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 were
>> 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 AM Ketan Talaulikar <ketant.ietf@gmail.com>
>> 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)
>>
>>
>>
>>