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

Loa Andersson <loa@pi.nu> Wed, 04 September 2024 13:27 UTC

Return-Path: <loa@pi.nu>
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 53DDFC180B47 for <mpls@ietfa.amsl.com>; Wed, 4 Sep 2024 06:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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] autolearn=ham autolearn_force=no
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 kOuU446fecRw for <mpls@ietfa.amsl.com>; Wed, 4 Sep 2024 06:27:27 -0700 (PDT)
Received: from srv.pi.nu (srv.pi.nu [IPv6:2a00:1a28:1410:5::1348]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73188C14CF1E for <mpls@ietf.org>; Wed, 4 Sep 2024 06:27:25 -0700 (PDT)
Content-Type: multipart/mixed; boundary="------------JgGnADZBbqJmvVfXW0e0zbUq"
Message-ID: <428b466d-3f01-4dcc-adad-aae197530f7c@pi.nu>
Date: Wed, 04 Sep 2024 21:27:18 +0800
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>
References: <85b392b8-8968-4ebd-ad37-af09a3ee3b8b@pi.nu> <9853DE1C-E8FB-4C98-A041-9F7CE46F335F@gmail.com> <93acdbb1-a3b4-447b-8a42-8f0477da4203@pi.nu> <6832D2EC-87BA-4D48-B2C2-9A6C12F2EE73@tony.li>
Content-Language: sv, en-GB
From: Loa Andersson <loa@pi.nu>
In-Reply-To: <6832D2EC-87BA-4D48-B2C2-9A6C12F2EE73@tony.li>
Message-ID-Hash: RV6R5GLXPKHOFEJZK5MOCZAGLX2KOWGF
X-Message-ID-Hash: RV6R5GLXPKHOFEJZK5MOCZAGLX2KOWGF
X-MailFrom: loa@pi.nu
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: 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/JLVzJYDl-a-m-1gAA4xtKhjf_do>
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>

Tony, et.al.,

not that is know now what it is worth, but I made a clearer version
of the figure.

/LoaI made a

Den 04/09/2024 kl. 02:28, skrev Tony Li:
>
> Hi Loa,
>
> Your diagram arrived here badly mangled.  I’ve changed to a fix width 
> font and taken the
> liberty of trying to repair it.  Apologies if I’ve only broken it further.
>
>> +-----------------------------------------+
>>                     |                                   |
>> +---+                                       |
>>            +------| D |                                       |
>>            | +---+                                       |
>>            |        |        |
>>          +---+ +---------------------------------------+ |
>>    +-----| B |      | |
>>    |     +---+ +-------------------------------------+ | |
>>    |       | |                                     | | |
>>    |       | +---+                                   | | |
>>    |       +------| E |                                   | | |
>>    | +---+                                   | | |
>>    | |                                     | | |
>>    | +-----------------------------------+ | | |
>> |                                                    | | | |
>>  +---+ +-------+
>>  | A | |   Z   |
>>  +---+ +-------+
>> |                                                    | | | |
>>    |  +-----------------------------------+ | | |
>>    | |                                     | | |
>>    | +---+                                   | | |
>>    |       +------| F |    | | |
>>    |       | +---+                                   | | |
>>    |       | |                                     | | |
>>    |     +---+  +-------------------------------------+ | |
>>    +-----|C  |      | |
>>          +---+ +---------------------------------------+ |
>>            | |                                         |
>>            | +---+                                       |
>>            +------| G |                                       |
>> +---+                                       |
>> |                                         |
>> +-----------------------------------------+
>>
>>
>> Not a network model, but a description of load-sharing option. You 
>> say that
>> we need the number of paths that a packet may take through the 
>> network. In the figure above a packet coming into node from the can 
>> be sent either "north" or "south". If it sent "north" it will enter 
>> node B and again go north or south. Once a packet reach node D, E, F, 
>> or G, it traverses a part of the network that does not do 
>> load-sharing. (Yes, I'm lazy!) To me the load-sharing decision seem 
>> to a local matter, what is the impact of the fact that there are 8 
>> routes through the network? What seem to have a bigger impact is the 
>> number of out going load-sharing interface, but again that is local.
>
> I’m assuming here that the traffic flows from A to Z.
>
> Yes, load sharing is a completely local decision.  The goal is for 
> each system that has multiple paths to select an appropriate next hop,
> consistent with the overall path and avoiding packet reordering within 
> a flow. Since intermediate nodes do not have a clear understanding
> of the flows within an LSP, the Entropy Label/Value gives a hint to 
> downstream nodes about how to forward particular flows. If done
> correctly, packets with the same Entropy Label/Value will follow the 
> same path and thus avoid reordering.
>
>
> Tony
>
>

-- 
Loa Andersson
Senior MPLS Expert
Bronze Dragon Consulting
loa@pi.nu
loa.pi.nu.@gmail.com