[mpls] Re: Discussion points for upcoming MPLS WG interim

Tony Li <tony.li@tony.li> Sun, 16 February 2025 17:38 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 D8324C1840D3 for <mpls@ietfa.amsl.com>; Sun, 16 Feb 2025 09:38:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.756
X-Spam-Level:
X-Spam-Status: No, score=-1.756 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=no 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 HN_-_FqI_4Zm for <mpls@ietfa.amsl.com>; Sun, 16 Feb 2025 09:38:35 -0800 (PST)
Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) (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 B442FC15154F for <mpls@ietf.org>; Sun, 16 Feb 2025 09:38:35 -0800 (PST)
Received: by mail-pl1-x62d.google.com with SMTP id d9443c01a7336-221206dbd7eso7185665ad.2 for <mpls@ietf.org>; Sun, 16 Feb 2025 09:38:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739727515; x=1740332315; darn=ietf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:from:to:cc:subject :date:message-id:reply-to; bh=rRyH0dVYB59p6ntqyoCLhMGRuWA7U6xgq+arxFli0qY=; b=lZ663XWuK3OTbwc+5rYadBxY/E73xEjFbWOP2XeqK0gq+9ZZ3rqimWFLMNe8VQ5aTk 0GjZ0Qq7COASiCH8LV6lLW9fWbs2IaSHKh6qerwqtvObEzw1pf1ejLdwbqf63WvP09Tc 8kp5Pp7yjIN/LOyjS9udijaHW9nQ4PQrHkrFnE8HyJB05+3xO7ZlRlIBbOznmwkxwfs9 A/MnurBZayHytxLUA0QX2RiyTtDbdXJKiUCHSd1iQ4mEwPQjdjlz0YjT+UYcW00a7wvE aH4wcxdC/ZL20pXPk8BZpW04SMsu7Wb4o7Ph2NssKLdyCRzNzEKcgHyzvUd0DcIs5cg3 jRww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739727515; x=1740332315; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:sender:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=rRyH0dVYB59p6ntqyoCLhMGRuWA7U6xgq+arxFli0qY=; b=s0uSsX8RzY3KJAUCWsXeN4XSzJP/bgGwIGzobPqLbr2YG4K/JS/BWdoC/lhQBCesn7 GQXTgQMDZhNQiyho0MXPGIHuR7eO+fjkZIHEcJNF+Y+Bx56Xk0McGPXfGp5peYelg3S6 Lh6lHJp0hi2PqUoJ5mcE1/CKqMgef8rSwLWNb64xXM1SX9DxOaiGLKEuHDm535ejiG9E hpeayToNtXsvlif6mNRvNM2vipeHwLu3XFPdqfqqlmC6YIF4VKSLyfiEbgzVhTcbU+4C nTRChfi9Wjtg4uHXufqfnuMta/0C+tuPUMbuE1Hzg8S9nVRC9lyA6YPEwgZyt+iT6T+3 iIEg==
X-Gm-Message-State: AOJu0Yw5XwibNzTMISXz+VxsxXzzId2qhFBsjO+UrWTnHdix5zQd6TQf hx1vBkhqIyZpgnM1fvBoIJhCKfjqStgyEWMLOVjpFfZOyzIC0lZM
X-Gm-Gg: ASbGncs7yEewnAaxYwU6Wa+dSPhaVveT1TsnYn+N+3TQ/k38H06f8HqDEjGz2tvDaxl Y0fRKkJFXSEP98QRC94QJUiCWK5VnylIQyDEcqTOm0bqc2Iirg19hbVdlJ6NVgdkR2Egz1Jzo+M AewAwQwuh3H6dGyq/ok24jvZb/Ivd4BO3GzMI3xbwujEj7yjFMZZM9NbtG1gSYThfaQ3Fw2U3MY T6KDcUk/4XL/KYJLyoJoMAHxFT+V+a/AN0JMIBwD/0osfcaBG8rehXAdKRe8EAIrYauAlCgUHog y3RTftN3Q0KYLT8+fi5Zh3ykqMswvHPDUgZ0b7lX19epg47b40Zss5J/gT4=
X-Google-Smtp-Source: AGHT+IFfVnU8+Cns7E5EnlJC1Iw39Qhf0G5d7Wp4QjanFIZcJ8Rgrn4AkfHIuEQqJJGucF8xJVGeSQ==
X-Received: by 2002:a05:6a00:198c:b0:730:794e:7ad6 with SMTP id d2e1a72fcca58-732617d97a9mr9465458b3a.14.1739727514759; Sun, 16 Feb 2025 09:38:34 -0800 (PST)
Received: from smtpclient.apple (c-73-93-167-4.hsd1.ca.comcast.net. [73.93.167.4]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7325f063782sm3660742b3a.148.2025.02.16.09.38.33 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Feb 2025 09:38:34 -0800 (PST)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <e77c19a7-5452-4a36-8f04-5c0a8483a153@pi.nu>
Date: Sun, 16 Feb 2025 09:38:23 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DB07F33-CE79-4526-8241-38A4F7066104@tony.li>
References: <CANZnSTqzxirZ+n=a_h=xLVmNxeQ3yjD+EspgDYXghAQCA2MKyQ@mail.gmail.com> <e77c19a7-5452-4a36-8f04-5c0a8483a153@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
Message-ID-Hash: S37YMYX224B252P3EKLTTQ2CDWR3S7EC
X-Message-ID-Hash: S37YMYX224B252P3EKLTTQ2CDWR3S7EC
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.9rc6
Precedence: list
Subject: [mpls] Re: Discussion points for upcoming MPLS WG interim
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/VC-B92P77NZXHar4ToQeSlfc_Fg>
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>

[WG chair hat: off]

Hi Loa,

This sorta sounds like you are proposing a wholly different form of ISD, but your proposal is very unclear to me.  If this is your intent, a document would be most helpful.

Regards,
Tony


> On Feb 16, 2025, at 7:22 AM, Loa Andersson - loa at pi.nu <mailforwards@cloudmails.net> wrote:
> 
> Working Group,
> 
> I made an addressing mistake, and the below weas only sent to Adrian, but was really intended for the entire WG.
> 
> /Loa
> 
> 
> Adrian and Joel,
> 
> If we are digging into LSE counting there are more alternatives :).
> 
> - we could assign an eSPL for PSD, and use 11 bits (TC and TTL) for the offset.
> 
> or
> 
> - we could appoint one eSPL per PSD network action type, 11 bits for offset
> 
> or
> 
> - one eSPL per combination of PSD network action types
> 
> or
> 
> - do the same for each combination of ISD and PSD
> 
> The efficiency of the above obviously depends on how many NAs we think we’ll have per packet. I have no answer to that.
> 
> I’m not particularly in favor of any of these, but sonfar I had no possibility to evaluate any of the ideas. This is one aspect where I believe “an experiment” could be useful.
> 
> /Loa
> 
> 
> On Sun, 16 Feb 2025 at 12:13, Adrian Farrel <adrian@olddog.co.uk <mailto:adrian@olddog.co.uk>> wrote:
> 
>    Hi Joel,
> 
>     > Well, since email discussion is useful to more folks than the interim
> 
>    :-)
> 
>     > I will respond to your primary question here.
>     >
>     > From where I sit, no, using an eSPL for the MNA HDR is not a good
>     > choice.  Running any kind of experiment will not tell us if using
>    a bSPL
>     > would be ffective / useful.  And from where I sit, the whole
>    point was
>     > to avoid using an eSPL.  If MNA HDR uses an eSPL, the marginal
>    value of
>     > using MNA HDR over defining new free-standing mYours,
> 
>    I'd like to untangle that a little because I think that the "should
>    it be / does it need to be experimental?" is a different question
>    from "bSPL or eSPL?"
> 
>    Your email is a little truncated, but your point appears to be that
>    the "minimal" MNA cost moves from 2 LSEs with bSPL (Format A plus
>    Format B) to 3 LSEs with eSPL, and that that increase makes the use
>    of MNA of marginal benefit compared to other approaches that could
>    be invented.
> 
>    I suppose that the marginality becomes less significant for larger
>    MNA constructs. For example, looking at draft-ietf-mpls-mna-ioam-00
>    for the ISD variant, results in Format A, Format B, and a number of
>    Format D LSEs. AFAICS there are two mandatory Format D LSEs and two
>    optional Format D LSEs. So a potential 7 LSEs with bSPL or 8 with eSPL.
> 
>    Now, I am not a hardware engineer and I am not trying to influence
>    this debate. I just want to get to the facts and then help people
>    decide bSPL or eSPL.
> 
>    My belief is that the debate over Experimental is orthogonal to this
>    discussion. It's a debate we should have, but we can make the
>    discussion of that point simpler if we first resolve the b/e discussion.
> 
>    Cheers,
>    Adrian
> 
>    On 2/15/2025 8:41 AM, Adrian Farrel wrote:
>     > Hi all,
>     >
>     > In the light of the agenda which reads...
>     >> Discuss the progress of MNA related WG documents, including:
>     >> - https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-hdr
>    <https://datatracker.ietf.org/doc/html/draft-ietf-mpls-mna-hdr>
>     >> - https://datatracker.ietf.org/doc/draft-jags-mpls-ps-mna-hdr
>    <https://datatracker.ietf.org/doc/draft-jags-mpls-ps-mna-hdr>
>     > ...I thought I would send out a couple of questions I would like
>    to see answered.
>     >
>     > 1. Are we happy to use an eSPL for MNA?
>     > The current version of draft-ietf-mpls-mna-hdr uses an eSPL. This
>    was introduced at 09 as part of moving to Experimental. I believe
>    the reasoning was that there is no scope for an Experimental bSPL.
>     > I understand that the resulting encoding is not optimal (an eSPL
>    takes two LSEs to sign MNA, where a bSPL would only take one).
>     > But how significant is this issue?
>     > Is it something we could live with or will it make MNA completely
>    infeasible?
>     >
>     > 2. If we can accept using an eSPL, would this remove the need to
>    be Experimental?
>     > There is clearly no shortage of eSPLs (while there is a
>    considerable restriction on the available bSPLs).
>     > The abundance of eSPLs means that we can effectively version MNA
>    using a new eSPL if we find the need to make changes to MNA.
>     > That would mean that we could safely publish MNA using eSPL on
>    the Standards Track.
>     >
>     > 3. If we remain as Experimental, what is the scope of the experiment?
>     > The current draft only says...
>     >     This document
>     >     describes an experiment whose purpose is to demonstrate that
>    the MNA
>     >     can be implemented and deployed.
>     > Looking at draft-bonica-gendispatch-exp, there is a lot more that
>    it would be helpful to add.
>     >
>     > Thanks for answering in advance, or for thinking about it and
>    arriving at the meeting with opinions.
>     >
>     > Cheers,
>     > Adrian
>     >
>     > _______________________________________________
>     > mpls mailing list -- mpls@ietf.org <mailto:mpls@ietf.org>
>     > To unsubscribe send an email to mpls-leave@ietf.org
>    <mailto:mpls-leave@ietf.org>
> 
>    _______________________________________________
>    mpls mailing list -- mpls@ietf.org <mailto:mpls@ietf.org>
>    To unsubscribe send an email to mpls-leave@ietf.org
>    <mailto:mpls-leave@ietf.org>
> 
> _______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org