[mpls] Re: Poll: IOAM and PSD

Joel Halpern <jmh@joelhalpern.com> Sun, 04 August 2024 04:02 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 2BF67C151088 for <mpls@ietfa.amsl.com>; Sat, 3 Aug 2024 21:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.109
X-Spam-Level:
X-Spam-Status: No, score=-7.109 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_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 (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 xR339qyZ0Vgp for <mpls@ietfa.amsl.com>; Sat, 3 Aug 2024 21:02:52 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 C7540C14CE29 for <mpls@ietf.org>; Sat, 3 Aug 2024 21:02:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4Wc5Wc2hsYz6Gwk6; Sat, 3 Aug 2024 21:02:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1722744172; bh=4Wd2+9BGWNM5zrHP9Mir0F6d14K33f2ANg+gG82DCLE=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=qt1CoZvu25NvPfKBu87sHS+qz8N1/qCWum2UVvD8C8Zm8GqLJMcJdJChIy2Iyzuc0 wvBekmqE6lrBUvSyt13wCjDzLoo14GTg0e56iXcBRdrxGqDBzWcv1MzNz+3RAQJPDd HvMd+TBzxOUtGxgderpqgtXdAJWtLc3mHDiQMTj0=
X-Quarantine-ID: <Vdzbwikdcj31>
X-Virus-Scanned: Debian amavisd-new at a2.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) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4Wc5WY5pT9z6G9cH; Sat, 3 Aug 2024 21:02:49 -0700 (PDT)
Message-ID: <3a0edc38-2224-469d-a38b-830509e4c3a3@joelhalpern.com>
Date: Sun, 04 Aug 2024 00:02:46 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Loa Andersson <loa@pi.nu>, Greg Mirsky <gregimirsky@gmail.com>, Michael Menth <menth@uni-tuebingen.de>
References: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li> <d919b570-2c63-4ca9-a3b9-6171cfb5fadf@uni-tuebingen.de> <CA+RyBmWc96DG5Ce-NgYKVoJ+XCj0nEu_tMv5vL5Ot4y=44H0HQ@mail.gmail.com> <751cd9a6-06d6-4e4b-bf14-3e29ba85dacd@pi.nu>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <751cd9a6-06d6-4e4b-bf14-3e29ba85dacd@pi.nu>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: 22NPQQOMWI23UEGXUF7SXLZ4MB6R7JXE
X-Message-ID-Hash: 22NPQQOMWI23UEGXUF7SXLZ4MB6R7JXE
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
CC: mpls@ietf.org
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/pnuJ-7HjZJK1VzlPHPY-sBYPkgg>
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 wondeer if we can find some better terminology.  You are correct that 
the sequence number on packets is not the same in successive packets in 
a flow.  So, depending upon how you use the term "mutable" it is mutable 
between packets in a flow.  It is not changed (mutatated) by the devices 
that process it.  We have other use cases where we use "mutable" to mean 
that.   Can we disentangle them?

Thanks,

Joel

On 8/3/2024 11:44 PM, Loa Andersson wrote:
> Greg,
>
> I think Michael is right.
>
> DEX is useful and we need it, but it does not solve all and any problem.
>
> I thought DEX was about transporting data/info generated by a node, 
> and outgoing packet. This data is by defiintion immutable and is for 
> example never hashed for load sharing purposes
>
> The issue with mutable data, e.g. the sequence number, is that it is 
> in an incoming packet and mutable. If the network is doing ECMP by 
> scanning the label stack, then the sequence number can't in the first 
> 20 bits of an LSE.
>
> Right?
>
> /Loa
>
> Den 04/08/2024 kl. 22:58, skrev Greg Mirsky:
>> Hi Michael,
>> I don't think that "IOAM requires mutable data" is an accurate 
>> statement. RFC 9326 IOAM Direct Export 
>> <https://datatracker.ietf.org/doc/rfc9326/> indeed defines optional 
>> parameters, Flow ID and Sequence Number, to ease the correlation 
>> process of collected telemetry data. For some applications, e.g., 
>> DetNet over MPLS <https://datatracker.ietf.org/doc/rfc8964/>, both 
>> these parameters already are present as part of the DetNet MPLS 
>> encapsulation as S-label (Service) and Sequence Number in d-CW or 
>> d-ACH, respectively. Furthermore, the IPPM WG draft on collecting 
>> telemetry data 
>> <https://datatracker.ietf.org/doc/draft-ietf-ippm-hybrid-two-step/> can 
>> be used without the use of the optional IOAM-DEX fields, i.e., 
>> Flow-ID and Sequence Number.
>>
>> Regards,
>> Greg
>>
>> On Sat, Aug 3, 2024 at 6:43 AM Michael Menth <menth@uni-tuebingen.de> 
>> wrote:
>>
>>     Hi all,
>>
>>     we're not operators but researchers who implemented some IOAM
>>     flavors in combination with SR using P4 on Tofino. We've presented
>>     some results at an interim meeting before:
>> https://datatracker.ietf.org/meeting/interim-2024-mpls-01/session/mpls
>>
>>     IOAM requires mutable data. In combination with multiple labels,
>>     e.g., for SR, these mutable data need to be near the bottom of the
>>     stack, otherwise they get popped along the way. Moving them to PSD
>>     makes encoding more efficient without increasing the effective
>>     header length that needs to be parsed. Therefore, we think PSD is
>>     the better option for applications like IOAM.
>>
>>     Regards
>>
>>     Michael
>>
>>     Am 30.07.2024 um 17:25 schrieb 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 tompls-leave@ietf.org
>>
>>     --     Prof. Dr. habil. Michael Menth
>>     University of Tuebingen
>>     Faculty of Science
>>     Department of Computer Science
>>     Chair of Communication Networks
>>     Sand 13, 72076 Tuebingen, Germany
>>     phone: (+49)-7071/29-70505
>>     mailto:menth@uni-tuebingen.de <mailto:menth@uni-tuebingen.de>
>>     http://kn.cs.uni-tuebingen.de
>>
>>     _______________________________________________
>>     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
>