[mpls] Re: Poll: IOAM and PSD

Joel Halpern <jmh@joelhalpern.com> Mon, 12 August 2024 01:59 UTC

Return-Path: <jmh@joelhalpern.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 46009C14F6EA for <mpls@ietfa.amsl.com>; Sun, 11 Aug 2024 18:59:31 -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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 (1024-bit key) header.d=joelhalpern.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 Tj1HD5xx9vIW for <mpls@ietfa.amsl.com>; Sun, 11 Aug 2024 18:59:27 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 687C6C14F6E1 for <mpls@ietf.org>; Sun, 11 Aug 2024 18:59:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4WhyPV5dwlz1ppmj; Sun, 11 Aug 2024 18:59:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1723427966; bh=aQDPgpkdeFt4GrjmqkHzkrpi8sv2X3EzgC0Si4kqbNQ=; h=Date:Subject:To:References:From:In-Reply-To:From; b=GWhka30Ep3GppEaYj9O/rKzD5/lVQbq8LDv0RPM6sBqnC4f5pOEHggFOY5SQFtcTq U2m+rIOjzj3yyMrl+vEF6eiRR4FYZMZ/BAgB6ZTQuSg8uDnzsOGvbORZYCtdxFWjon SFfBi1LhZw2V1WfAYMdyxE01/T06E/bapFdd7Dd8=
X-Quarantine-ID: <e4PkLGS1Umj6>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.20.161] (unknown [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4WhyPV2L1sz1pp34; Sun, 11 Aug 2024 18:59:25 -0700 (PDT)
Message-ID: <f03f0a92-58bf-4186-a582-f67a3f5e0cbd@joelhalpern.com>
Date: Sun, 11 Aug 2024 21:59:24 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Haoyu Song <haoyu.song@futurewei.com>, mpls <mpls@ietf.org>
References: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li> <BY3PR13MB4787298A531DFA3812CAAB9F9AB92@BY3PR13MB4787.namprd13.prod.outlook.com> <582a0bbd-9536-44aa-85d5-113fea48c663@pi.nu> <BY3PR13MB47871EB1BCAD4FAE0142130B9A852@BY3PR13MB4787.namprd13.prod.outlook.com>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <BY3PR13MB47871EB1BCAD4FAE0142130B9A852@BY3PR13MB4787.namprd13.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: GE47ZM5UKNRGHEBCOH3JJUXMW57RYPYT
X-Message-ID-Hash: GE47ZM5UKNRGHEBCOH3JJUXMW57RYPYT
X-MailFrom: jmh@joelhalpern.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
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/MFLQ0Jv7hLITOnTAfFiEnCk6aPk>
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>

I presume I am misunderstanding your reply Haoyu?  For every technology 
the IETF has ever agreed on, when we agreed on it, we knew there were 
future possibilities whose solutiosn would be affected by the choices we 
made.  But, lacking knowledge of what problems we would find in 3, 5, or 
10 years, we made the choices based on the information we had.  That 
does include making sensible provisions for future expansions.  But it 
also includes excluding some paths so that we can build effective 
technology.

Yours,

Joel

On 8/11/2024 9:40 PM, Haoyu Song wrote:
> Hi Loa,
>
> Currently I'm not sure but just sense the needs for the future expansion.
>
> Thanks,
> Haoyu
>
> -----Original Message-----
> From: Loa Andersson <loa@pi.nu>
> Sent: Sunday, August 11, 2024 7:38 PM
> To: Haoyu Song <haoyu.song@futurewei.com>; Tony Li <tony.li@tony.li>; mpls <mpls@ietf.org>
> Subject: Re: [mpls] Re: Poll: IOAM and PSD
>
> Haoyu,
>
> While your response to the question and the first part of the second question is clear, I'm not clear what you mean by the second part of the response 2nd question.
>
>      I’d like also see the support of application level ID and metadata to
>      better support the application-aware networking.
>
> Do you care to expand om this, are you referring to draft-song-apn-dns-application-aware-networking? Which IDs do you think need to support application-aware networking?
>
> /Loa
>
>
> Den 09/08/2024 kl. 07:35, skrev Haoyu Song:
>> Hi Tony,
>>
>> My response is inline.
>>
>> Regards,
>>
>> Haoyu
>>
>> *From:* Tony Li <tony1athome@gmail.com> *On Behalf Of *Tony Li
>> *Sent:* Tuesday, July 30, 2024 8:26 AM
>> *To:* mpls <mpls@ietf.org>
>> *Subject:* [mpls] Poll: IOAM and PSD
>>
>> [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?
>>
>> [HS] I’d like MNA to support IOAM DEX and Trace option as specified in
>> RFC9326 and RFC9197 using PSD. The reasons are:
>>
>>       1. Comply with existing standards, can be directly used without
>>          any hassle
>>       2. Support potential cross-domain interoperation (e.g., cross the
>>          boundary of MPLS domain and non-MPLS domain)
>>       3. IOAM trace (i.e., the passport mode) is very useful in many
>>          realtime measurement/congestion control applications (e.g.,
>>          HPCC and tons of published research papers), therefore it has
>>          great potential for future wider application.
>>
>>   2. Do you have other applications of MNA that have not been proposed yet?
>>
>> [HS] I’d like to see a simple flag-based action to support the
>> postcard mode telemetry.
>>
>> I’d like also see the support of application level ID and metadata to
>> better support the application-aware networking.
>>
>>   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
>
> _______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org