IETF Logo Mail Archive

Re: [Idr] WG adoption call for draft-scudder-idr-entropy-label-01 (9/6/2022 to 9/20/2022)

Robert Raszuk <robert@raszuk.net> Wed, 28 September 2022 09:06 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C53FC14CE21 for <idr@ietfa.amsl.com>; Wed, 28 Sep 2022 02:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_BLOCKED=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=raszuk.net
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 j4flMHjqVsJO for <idr@ietfa.amsl.com>; Wed, 28 Sep 2022 02:06:37 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 2DAC3C14CF14 for <idr@ietf.org>; Wed, 28 Sep 2022 02:06:36 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id bq9so18752257wrb.4 for <idr@ietf.org>; Wed, 28 Sep 2022 02:06:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=aqyF1KZuVbKn3CDcoHN9ZX3/WOV/Qv3LIiG5Sfe04lE=; b=Gra+L/MlR2xcGdCF5g+yk4+fTcnsYkOz2gPC+D+1Adi/oXCu6cSS9TwfMMuBbBYEy7 kfnjzE3SqME+7b/iKjYWEM/61/uyT/BVnBXmyEcVkwBzk4IQsypyq7q0jhubVYUcmFUp Z17NQhGrmxQ6uzSJEH3F4OevdG+DE9NFgawrRnczH8HFMIjCUvvMp3CoKnzzQ8bpGwuQ NU7QrxBkuxSU/fYZz6Kt1vHU6PZNI79LV2vKLhzGEhsS+FRcXeY/BZjv083vLbnMMVDd aj1aXr9VO79bS4P8rbEa1O2N+mUZRrFwmZQ9+M+0SHXmMIKVV7Q5S24/qvyjaOLlj+Vd yUVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=aqyF1KZuVbKn3CDcoHN9ZX3/WOV/Qv3LIiG5Sfe04lE=; b=3zVEdt1sWEnCJZEAW8GC+nU2nm07gOykWIJyQYheZQ9hEidX5vuFP8DfMx9CnE7n7T +f14Z6QBbJVA9KlAzxKt7/iynQzCROdSfUBrGq5y7pXC77slF+61hNhVHLJFeDFfazD6 0fvY2/yPlNSmJyGILTQdHOdQzUMcO7WghyKpb9cqHmdLnOTR6jjWja3lXUqV5YG4fCbh qbQWGC5k0P4JHuwok2HNTCbWnAiFutcPoZ9buDt1b6n+61hklQacBgOCVNn6IBb3GBuH PmYyX29BOUkqEfRG6ns4wFT5Iz1dCYWAq0mnbqDAodOz5kUaWwqBOIX0ltaxyDMM8vnq 2yyQ==
X-Gm-Message-State: ACrzQf0n5B5AVMWkk/SQAkx00PDX5v3oxVFcT5FQjCZoeZ/sttEfwfht nRsu8hUghsomtCZsIIoAjShF6S1cO4c8WDpgTo6bFQ==
X-Google-Smtp-Source: AMsMyM6VlYG0/VmDw9n75VL7sWAf2glVndf2EUFAIRK+C9DcHs/0BtbNspak9lesjLBWa9Bf/4mauqv7vjGy7vSCSUI=
X-Received: by 2002:adf:fb88:0:b0:22a:f742:af59 with SMTP id a8-20020adffb88000000b0022af742af59mr19988468wrr.230.1664355995156; Wed, 28 Sep 2022 02:06:35 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB48721FE4114EA8C33BA893FDB3559@BYAPR08MB4872.namprd08.prod.outlook.com> <5245E2DE-6D17-4ED3-94DD-44E55D2008CD@tsinghua.org.cn>
In-Reply-To: <5245E2DE-6D17-4ED3-94DD-44E55D2008CD@tsinghua.org.cn>
From: Robert Raszuk <robert@raszuk.net>
Date: Wed, 28 Sep 2022 11:07:02 +0200
Message-ID: <CAOj+MMFcdOpxVGVzOWPaZmv2aDD_=vMuT+fxQr-pTac4c4Ykyg@mail.gmail.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>
Cc: Susan Hares <shares@ndzh.com>, idr@ietf.org
Content-Type: multipart/alternative; boundary="000000000000df224105e9b91364"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/tyq7pFbZqznNRaIvmHfkRrJ2psU>
Subject: Re: [Idr] WG adoption call for draft-scudder-idr-entropy-label-01 (9/6/2022 to 9/20/2022)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Sep 2022 09:06:41 -0000

Hi Aijun,

Signalling capability to process entropy labels IMO should be signalled in
a transitive manner. Requirement that BGP nodes like RRs which do not
modify the next hop understand the attribute is not justified.

On that basis alone I think the proposed document should progress. The fact
that it evolved with time from RFC6790 and got deployed is another factor.

If/when next-hop-capability adds transitive option and get's deployed I
guess this doc could be moved to historical however for now it attempts to
address real deployments by allocating valid codepoint for it.

Thx,
R.

On Wed, Sep 28, 2022 at 2:23 AM Aijun Wang <wangaijun@tsinghua.org.cn>
wrote:

> Hi, Sue:
>
> Want to ask where are the consensus on the list for this draft? Given this
> draft has contradicted with the existing WG draft which has been pointed
> out by several several service providers?
> As also mentioned in your list questions, there is necessary to discuss
> the short term and long term improvements of BGP next hop in the coming
> interim meeting, then what’s the reason to adopt this document in hurry?
>
> Aijun Wang
> China Telecom
>
> On Sep 28, 2022, at 01:14, Susan Hares <shares@ndzh.com> wrote:
>
> 
>
> The chairs have reviewed the IDR WG discussion and feedback from
> implementers on draft-ietf-idr-entropy-label-01.txt.
>
>
>
> The consensus from this review is that we should:
>
> 1) adopt draft-scudder-idr-entropy-label-01 as
>
> draft-ietf-idr-entropy-label-01
>
>
>
>
>
> 2) Hold a discussion of BGP Next-Hop technology to discuss
>
> the needs for current and future standards on BGP Next Hop.
>
>
>
> During this interim we will discuss the open proposals for
>
> BGP Next HOPS to determine what technology goes forward
>
> toward standardization.
>
>
>
> IDR needs the feedback from implementers and operators
>
> about the short term and long-term improvements to
>
> BGP Next hop.
>
>
>
> Cheerily, Sue
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

v2.23.0 | Report a Bug | By Email