[mpls] Re: Poll: IOAM and PSD

Loa Andersson <loa@pi.nu> Fri, 09 August 2024 03:43 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 95134C16941A for <mpls@ietfa.amsl.com>; Thu, 8 Aug 2024 20:43:16 -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 aBNbUJrxaMi6 for <mpls@ietfa.amsl.com>; Thu, 8 Aug 2024 20:43:15 -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 3E34FC169416 for <mpls@ietf.org>; Thu, 8 Aug 2024 20:43:13 -0700 (PDT)
Message-ID: <21af6559-3ded-4b21-a99f-68d676206d73@pi.nu>
Date: Fri, 09 Aug 2024 11:43:07 +0800
MIME-Version: 1.0
To: Tony Li <tony.li@tony.li>, mpls <mpls@ietf.org>
References: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li>
Content-Language: sv, en-GB
From: Loa Andersson <loa@pi.nu>
In-Reply-To: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: LDKD7IGEHUPWUXSCRWBKQQISEG2NB5OX
X-Message-ID-Hash: LDKD7IGEHUPWUXSCRWBKQQISEG2NB5OX
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
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [mpls] Re: Poll: IOAM and PSD
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/n8PhNsKQ_c9bK24f2gE-zgKnuJ8>
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 chairs, working group,

Preamble
--------
I have been a bit reluctant to respond to this poll, the reason is that 
I do not clearly see how mine (or anyone else) responses will be used. 
Will for example an "other application" that show up in a few weeks or 
months be able to make it on to the "preferred list" or will the second 
question be used to "close the line"?

I have had off-line discussions, and a impression that I have is that 
surprisingly many participants are not yet ready (sic!) to exclude 
anything, while they might have their preferences. Some of which I 
share, others not.

Haoyu correctly mention that we should align a closely as possible with 
existing standards, I concur.

My responses to the questions from the chairs

1. There are many flavors of IOAM.  Which ones would you like to 
deploy/implement with MNA? It is true that IOAM is flavour and feature 
rich. I have always thought that there is is a reason for this, e.g. 
while A and both can x and y, A is significantly better doing x, and B 
is significantly better doing y. I don't want to particularly exclude 
any flavour or feature. I believe that we need some information 
in-stack, e.g. "presence" and some OpCodes/flags. I also believe that
- IOAM Pre-allocated Trace (value 0) option in Post-Stack MNA
- IOAM Direct-Export (value 4) in Post-Stack MNA
      are valid starting points, while we should not take any action to 
disallow
      other options.

2. Do you have other applications of MNA that have not been proposed 
yet? No, if I had they would have been proposed :). I see that other 
responses tentatively lists "other applications", I think it is worth 
investigating those, and adopt if viable. I don't want a consolidated 
"no" response to this question to disallow "other applications" to be 
brought to the table. /Loa

Den 30/07/2024 kl. 23:25, skrev Tony Li:
>
> [WG chair hat: on]
>
> Hi all,
>
> We’ve had many discussions about IOAM and PSD over the last few years. 
> We need to reach consensus on the problems that need to be addressed 
> in these areas. Therefore, we would like to hear from everyone, 
> especially independent operators:
>
> 1.
>
>     There are many flavors of IOAM.  Which ones would you like to
>     deploy/implement with MNA?
>
> 2.
>
>     Do you have other applications of MNA that have not been proposed yet?
>
>  This poll will close in two weeks, at 9am PDT, Aug 13.
>
> Regards,
>
> MPLS chairs
>
>
> _______________________________________________
> 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