IETF Logo Mail Archive

Re: [bess] Request for an expedited WG adoption call for draft-trr-bess-bgp-srv6-args

Ketan Talaulikar <ketant.ietf@gmail.com> Tue, 01 August 2023 18:18 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 ADAD6C151539; Tue, 1 Aug 2023 11:18:40 -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 9HT-aIJCMGfR; Tue, 1 Aug 2023 11:18:37 -0700 (PDT)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (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 EF20AC14CE36; Tue, 1 Aug 2023 11:18:36 -0700 (PDT)
Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-997c4107d62so867880266b.0; Tue, 01 Aug 2023 11:18:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690913915; x=1691518715; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=W3Pn11ObK7xnPnJtEvYNOuG8mco17qp4QTUhEIPsHDM=; b=NHoqJUn2qI9hFg8/MOsyGpvElRCT7lRS0ids241syl9yZhHZp9mn6HiZHQRbjarl2T 170KDHvwdeLiwynrYt9MsvDGSG2+73u2XMRbhtO+uAylIXDYwo5GAKS96Q1nixMj0v7V +cNiHc+2i48hp2aEcUNNXtU4CzQsYax0fcvjiA5mM7cMC9JhWgT4S5O38XsUzqH2YoYu 025Is01pq0DReoWWOULh40ReNDegLAejiy7zClFU1G6K2TFNDfBquzV7d541bXh/my83 HJPwOSTJIWHUsyMNtqJnJbkzt/JEcWBSCyVi7NqtVK7gCDZDOLEMtUGlJbJWuELazoq3 +sIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690913915; x=1691518715; 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=W3Pn11ObK7xnPnJtEvYNOuG8mco17qp4QTUhEIPsHDM=; b=JT+NsDXwaQ+zZdPrHCKXeP/MSWk+n6zVR2v4vEN0VOsO8XeSCx9R2rDvWIMPgj/MCp 8Vm7Zc913KhTh31dyUNRXs5mzoOjEMTfrZ8gLh5wzbeWX8XeaEgS1J+dsjiKFxKynZKJ Z/SGP52dE+2Ij7j7yidxYG0RJ4W58A77znO/U3fT6SsWQ52tGj2LV7GBu6K4CBZEiK4V +ciEo+Z3nlx6BNx4z69UyONA5Vcg2XgjLO8XIvyQCYrHIDmroFgvGuLb96TGAiqkbi6N bE5DI33zStr8FLuQTwvdaOoV7XmvkHHLbbwAG4bseJmIouVaCZ5cR2ilb5kfpulwnav2 u7Ww==
X-Gm-Message-State: ABy/qLYjLexn/gOm016oFCVbuSDH5fpmgTafVu0BVyDMGq6adGrT2IfV 4/0nxFViLXzqDiDGnU3jyxU2bId1hWLb+OZvbvxww9TWdh4=
X-Google-Smtp-Source: APBJJlFgm83i8zguzIJF8uqpQh2WeL8qpyhJRdQ+YRpXCcxP+iKNsJtiDRc3yvGuB/Oyk/uLGVYEvIEU1UIJYgBO6XU=
X-Received: by 2002:a17:906:5d:b0:99b:5445:10ca with SMTP id 29-20020a170906005d00b0099b544510camr3149472ejg.58.1690913914352; Tue, 01 Aug 2023 11:18:34 -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>
In-Reply-To: <BY3PR08MB7060B78501D49D5DE4BA4EE3F70AA@BY3PR08MB7060.namprd08.prod.outlook.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Tue, 01 Aug 2023 11:18:24 -0700
Message-ID: <CAH6gdPzkCHFDK1yKRd2A4mN+WnY026cdfZ56swoQTaSiAOcHOA@mail.gmail.com>
To: "Jorge Rabadan (Nokia)" <jorge.rabadan@nokia.com>
Cc: "Matthew Bocci (Nokia)" <matthew.bocci@nokia.com>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "draft-trr-bess-bgp-srv6-args@ietf.org" <draft-trr-bess-bgp-srv6-args@ietf.org>, BESS <bess@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000035fe340601e09311"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/BuC55vHQzLj8SBWQM3MLxfx_K20>
Subject: Re: [bess] Request for an expedited WG adoption call for draft-trr-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: Tue, 01 Aug 2023 18:18:40 -0000

+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)
>
>
>
>

v2.43.4 | Report a Bug | By Email | System Status