[mpls] Re: Fwd: New Version Notification for draft-li-mpls-mna-entropy-03.txt

Tony Li <tony1athome@gmail.com> Mon, 02 September 2024 21:08 UTC

Return-Path: <tony1athome@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08177C151077 for <mpls@ietfa.amsl.com>; Mon, 2 Sep 2024 14:08:09 -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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 oP3Udyv2lDep for <mpls@ietfa.amsl.com>; Mon, 2 Sep 2024 14:08:04 -0700 (PDT)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAED1C151063 for <mpls@ietf.org>; Mon, 2 Sep 2024 14:08:04 -0700 (PDT)
Received: by mail-pf1-x42e.google.com with SMTP id d2e1a72fcca58-714226888dfso3752706b3a.1 for <mpls@ietf.org>; Mon, 02 Sep 2024 14:08:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725311284; x=1725916084; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=d0XJjLaKqGSPwUDGAJlXOXOipkp1RhcWuNYXtXydMNw=; b=amWSbcq2Q6oV1HclPtyoCrrEWUciubdvgvwfbDdQU/QW078fTUIIFwfZRXFOE3Rjob VI+CzMD+Cj1pH9uqbP7S5t0nYPcxPl3stBJT+8+mgZGSEkRPfKymcl2+Jt8UjKZeLd1S ELFgBjxF1jfNx0vQilWlM5UYjFgokvTIBe15D0FDksi2IeVZtYsErDx4dfVTAksDMXcA z9wTVWTByUS6Wq8+Eomm3/a89C+GWvE+b0Lqe8I2dsenfqGXzRz+OIzMVALhAunjTO8n Iha5e3CuvrG4mGhCyrT5qFl1whu16xpKspI1yiZ9BI5Dc14ngBZj9M4Tcc9D0SUOcQtg 1A5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725311284; x=1725916084; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=d0XJjLaKqGSPwUDGAJlXOXOipkp1RhcWuNYXtXydMNw=; b=S49IHprpn3VbGgdVXh0Vk0S0GE7/4RxRU3wxMzMQnnidn/sYvqBrj2HKStqrrVtAkW QTzXodlO39zPyPYRQs6zkgRoABeSNk3tVSz/mJkM92wrftjTsNofWeqZD9gTPRcE7jMF nnRDoz8eD2JhicTg+iG3wpK8CV06XxnQcBc29ifcTykQG2vAKlizQwhZYeIGrrko6wT2 Wzsg/lQRcCjaETKvm9kVJ3GK0BDbmxLGIdtZf3JulBXZiV43EoousQayBbKvnooPJ/vP AFqQY9BQq5C75BldcS9I3fCRbGQ8BmiGr1FBCpFqKHtdHA92aJzVbLhNKiexdP6BzJXa 3PDg==
X-Forwarded-Encrypted: i=1; AJvYcCU/9VG6I0zrFy0rNfcCfb3wyTMMR6OGpbn75RBP9D3lrWuO22B33LkS8y1K6SmdoFGVadX2@ietf.org
X-Gm-Message-State: AOJu0YyjFhEKMY666A8yW0skfeWhmb0593Ho+uEuRr3114TfUbLTVJEe y+9mBXDfL3TzAKvHZiAI2URii3dxv912MPEGGFdkdMtY2VT8gzPy
X-Google-Smtp-Source: AGHT+IHobsjZzcIf7xoyGj426sqOcj4flY1njqpqBNjv8y/ZDhCI0jB7LAk+xAJVzPzMn3Juypia3A==
X-Received: by 2002:a05:6a20:9f47:b0:1ce:f752:46ad with SMTP id adf61e73a8af0-1cef7524723mr1076651637.42.1725311283756; Mon, 02 Sep 2024 14:08:03 -0700 (PDT)
Received: from smtpclient.apple (192-184-144-109.fiber.dynamic.sonic.net. [192.184.144.109]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7174397aa7bsm3993785b3a.98.2024.09.02.14.08.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 02 Sep 2024 14:08:03 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-4CBAA66E-793D-49C6-811C-E6C348105A63"
Content-Transfer-Encoding: 7bit
From: Tony Li <tony1athome@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Mon, 02 Sep 2024 14:07:52 -0700
Message-Id: <FE89AAD8-1CBB-44C7-A3AF-F300D69DD142@gmail.com>
References: <b4a957c6-b60f-487e-9519-656fcf86b85c@pi.nu>
In-Reply-To: <b4a957c6-b60f-487e-9519-656fcf86b85c@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: iPad Mail (20H350)
Message-ID-Hash: IEST3OPNCU2T5Z5WTKLWNHS26ID3D7HR
X-Message-ID-Hash: IEST3OPNCU2T5Z5WTKLWNHS26ID3D7HR
X-MailFrom: tony1athome@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-mpls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mpls <mpls@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [mpls] Re: Fwd: New Version Notification for draft-li-mpls-mna-entropy-03.txt
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/D1ll7rcCrFhe3Jr3T0hPkeJ1pXs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Owner: <mailto:mpls-owner@ietf.org>
List-Post: <mailto:mpls@ietf.org>
List-Subscribe: <mailto:mpls-join@ietf.org>
List-Unsubscribe: <mailto:mpls-leave@ietf.org>

Loa,

We have discussed this before.  Please see https://datatracker.ietf.org/doc/html/draft-li-mpls-entropy.

Yes, more entropy is always better, but a 16-bit entropy value seems sufficient for the foreseeable future.

If someone in the future decides that more bits of entropy are a necessity, then it would be trivia itself to extend the entropy action by another LSE.

Tony


> On Sep 2, 2024, at 1:10 AM, Loa Andersson - loa at pi.nu <mailforwards@cloudmails.net> wrote:
> 
> Stewart and Tony,
> 
> This might be classified as naive questions :).
> 
>> Den 02/09/2024 kl. 15:15, skrev Stewart Bryant:
>> Hi Tony
>> 
>> I am struggling to see whether this has a sufficient advantage over the existing EL/ELI mechanism to justify us recommending it existence.
>> 
>> It is obvious that this can be done, and it saves an LSE, but is that sufficient justification for the complexity introduced by having two mechanisms that of necessity need to co-exist?
>> 
>> We also need to understand what happens in a legacy routers that are looking for EL/ELI and older routers that just hash the stack. I think they just provide less (no?) entropy.
> 
> Is there a scientific way of calculating "how much" entropy the different  generate?
> 
> Is more entropy always better?
> 
> What are the factors that determine how much entropy you need?
> 
> /Loa
> 
> 
>> 
>> I imagine this ends with routers needing to parse for both types of entropy which is not a great position to be in.
>> 
>> Best regards
>> 
>> Stewart
>> 
>>>> On 30 Aug 2024, at 5:26 PM, Tony Li <tony.li@tony.li> wrote:
>>> 
>>>  [WG chair hat: off]
>>> 
>>> Hi,
>>> 
>>> This update addresses comments from Adrian Farrel as part of the WG adoption process.
>>> 
>>> Comments and corrections are most welcome.
>>> 
>>> Thanks,
>>> Tony
>>> 
>>> 
>>>> Begin forwarded message:
>>>> 
>>>> *From: *"internet-drafts at ietf.org" <mailforwards@cloudmails.net>
>>>> *Subject: **New Version Notification for draft-li-mpls-mna-entropy-03.txt*
>>>> *Date: *August 30, 2024 at 9:24:05 AM PDT
>>>> *To: *"John Drake" <je_drake@yahoo.com>, "Tony Li" <tony.li@tony.li>
>>>> *Reply-To: *internet-drafts@ietf.org
>>>> 
>>>> A new version of Internet-Draft draft-li-mpls-mna-entropy-03.txt has been
>>>> successfully submitted by Tony Li and posted to the
>>>> IETF repository.
>>>> 
>>>> Name:     draft-li-mpls-mna-entropy
>>>> Revision: 03
>>>> Title:    MPLS Network Action for Entropy
>>>> Date:     2024-08-28
>>>> Group:    Individual Submission
>>>> Pages:    5
>>>> URL:      https://www.ietf.org/archive/id/draft-li-mpls-mna-entropy-03.txt
>>>> Status:   https://datatracker.ietf.org/doc/draft-li-mpls-mna-entropy/
>>>> HTMLized: https://datatracker.ietf.org/doc/html/draft-li-mpls-mna-entropy
>>>> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-li-mpls-mna-entropy-03
>>>> 
>>>> Abstract:
>>>> 
>>>>   Load balancing is a powerful tool for engineering traffic across a
>>>>   network and has been successfully used in MPLS as described in RFC
>>>>   6790, "The Use of Entropy Labels in MPLS Forwarding".  With the
>>>>   emergence of MPLS Network Actions (MNA), there is signficant benefit
>>>>   in being able to invoke the same load balancing capabilities within
>>>>   the more general MNA infrastructure.
>>>> 
>>>>   This document describes a network action for entropy to be used in
>>>>   conjunction with "MPLS Network Action (MNA) Sub-Stack Solution".
>>>> 
>>>> 
>>>> 
>>>> The IETF Secretariat
>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> mpls mailing list -- mpls@ietf.org
>>> To unsubscribe send an email to mpls-leave@ietf.org
>> 
>> _______________________________________________
>> mpls mailing list -- mpls@ietf.org
>> To unsubscribe send an email to mpls-leave@ietf.org
> 
> -- 
> Loa Andersson
> Senior MPLS Expert
> Bronze Dragon Consulting
> loa@pi.nu
> loa.pi.nu.@gmail.com
>