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> Fri, 30 September 2022 22:43 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 96736C14CF10 for <idr@ietfa.amsl.com>; Fri, 30 Sep 2022 15:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level:
X-Spam-Status: No, score=-7.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_HI=-5, 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=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 5SwnzdzbEgyU for <idr@ietfa.amsl.com>; Fri, 30 Sep 2022 15:43:51 -0700 (PDT)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 0C1B5C14CF0D for <idr@ietf.org>; Fri, 30 Sep 2022 15:43:50 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id 130-20020a1c0288000000b003b494ffc00bso5294687wmc.0 for <idr@ietf.org>; Fri, 30 Sep 2022 15:43:50 -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=0LJU8WWP8ltirfonT3I39owLPjU1eWsJwgfkF90DIIo=; b=D44/CDafg2gX5Cr9n390v89fhIflhx4019q5A3JK5DY5Y0Acd8eh++u4iJG5TYsYyR FOIuXaJ8C2SO4dMTY82DxdqJ8dUjfHksFVuTUHrLdC7Ipz5D/KIhjOwMG/Go1+s4qDLY HOBjCYH8FSFXwZ6PKWPb4ai/Ab0Cz9gzc7BVEqVhPI6M8obyf+fOElN0MWWyqMWG4giL x6LXXK9NU4IOMGdWbHSj8d40IJ1RFH6d07A4TX34rv6VD4N0cbz+aQhFVDhi7otghSuD PhDvuFey/TZrHU9rmeMz8joHJi6zfwJtbdHtorCSTL/8iyZtdkEMv5cvgiW0iSnrJWYi rUoA==
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=0LJU8WWP8ltirfonT3I39owLPjU1eWsJwgfkF90DIIo=; b=FpwpcIcImDf0jp/3wV/l3HH9xLpgurwJwCZrxn9q43w+PqpvQWtfvf+cECiBMNFpCT HQkwOAfeFpBNHnhwPkFF/SxKn7qiPhLsOJ/MygYrbDBoGTPlHzfzq9Ci5vPps1eBww7i ekEW906bbx+oh7Z1hgHO503JSmcQGoaCWW6ml8Yj2CMlzbJ3txPKiF9FmRDjpVuPDfN9 8vFiKCGEs6obs0sz642SaIry5/RGcNS9lrkdgLsuYNKRX5HYPcwmxyvFvPNNTxaXGK3d 4Q6tprnQqaX4+OQNAwdxvgiL7u5TN26qi8O+Aq06KKMiFc8VtlondayvIVvZ2JjwEQia 29eA==
X-Gm-Message-State: ACrzQf0H3OrYRvjdNVcvP9kxEwZWCqEwPznvtXkCShCK2jy60eHUd+g8 VFgTmkd3FZTySqEStXFyxTw0SZfkHCL7zCvRcTuoGFh+i3AgIQ==
X-Google-Smtp-Source: AMsMyM6BnSVKuqrUtG2bsQbYs+uhXEXKKFejfPuBVCwRRCRoCOO62mZkQTy1CRDpMSZUN/iM4O0ExEaUXA2h2X940xE=
X-Received: by 2002:a05:600c:3844:b0:3b4:becc:e43 with SMTP id s4-20020a05600c384400b003b4becc0e43mr194493wmr.33.1664577828660; Fri, 30 Sep 2022 15:43:48 -0700 (PDT)
MIME-Version: 1.0
References: <20220930215902.D389590007B@hmail-m121149.qiye.163.com> <64E9038A-77DD-4C18-8351-68DC849D9363@tsinghua.org.cn>
In-Reply-To: <64E9038A-77DD-4C18-8351-68DC849D9363@tsinghua.org.cn>
From: Robert Raszuk <robert@raszuk.net>
Date: Sat, 01 Oct 2022 00:44:18 +0200
Message-ID: <CAOj+MMGuykXVU=dwV2K_viVraSKXTw9o9JDsdvrdx-KcdAs-3w@mail.gmail.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>
Cc: Susan Hares <shares@ndzh.com>, idr@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002dbc3305e9ecba30"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/VzYyHRac5S-kQ2rEyWZdlGSjrvY>
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: Fri, 30 Sep 2022 22:43:55 -0000

Aijun,

> There is one direct route to reach the destination, why did we select the
detour one?

Because the direct route is still under construction and some of us
enjoy sightseeing.

Moreover no one knows how long it will take to complete it - if at all
currently imposed limits and restrictions on it will ever be lifted
to accommodate the subject use case effectively.

Rgs,
R.


On Sat, Oct 1, 2022 at 12:22 AM Aijun Wang <wangaijun@tsinghua.org.cn>
wrote:

> Hi, Sue:
>
> Thanks for your reply.
>
> What puzzling me for the current approach is that there is no one
> illustrate the reason that why we can’t meet the requirements based on the
> existing WG document, given the authors of
> [I-D.ietf-idr-next-hop-capability has described the potential
> changes/updates , and it has also several other advantages over  document
> of draft-scudder-idr-entropy-label-01.
>
>  I would like to get the answers from your write up of this adoption, or
> from the discussions of the coming interim meeting.
>
> There is one direct route to reach the destination, why did we select the
> detour one?
>
> Aijun Wang
> China Telecom
>

v2.23.0 | Report a Bug | By Email