[mpls] Re: Poll: IOAM and PSD

Toerless Eckert <tte@cs.fau.de> Tue, 06 August 2024 16:23 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 14F71C169425; Tue, 6 Aug 2024 09:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.656
X-Spam-Level:
X-Spam-Status: No, score=-1.656 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=no 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 zaXuP8uVkvFs; Tue, 6 Aug 2024 09:23:15 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (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 75499C15154F; Tue, 6 Aug 2024 09:23:13 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4Wddrt3J2TznkMc; Tue, 6 Aug 2024 18:23:10 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4Wddrt2JYLzkwwd; Tue, 6 Aug 2024 18:23:10 +0200 (CEST)
Date: Tue, 06 Aug 2024 18:23:10 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Greg Mirsky <gregimirsky@gmail.com>
Message-ID: <ZrJN7tk66LqX9aWk@faui48e.informatik.uni-erlangen.de>
References: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li> <CA+RyBmUpSnjJwBqchCs4XTU-xT6H4MbiNz2+reT_NJH4JRgx=g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CA+RyBmUpSnjJwBqchCs4XTU-xT6H4MbiNz2+reT_NJH4JRgx=g@mail.gmail.com>
Message-ID-Hash: 5M6PAA2NOVGZUS6E3WDAEHUGRVBFS6LS
X-Message-ID-Hash: 5M6PAA2NOVGZUS6E3WDAEHUGRVBFS6LS
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
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>, detnet@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/kzHrF4sIQrLnPB3vOjcgw7oRHmc>
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>

[Cc'ing detnet WG]

Thanks Greg, for draft-varmir-mpls-detnet-mna

I have a few concerns:

1. This draft primarily seems to replace the DetNet control word, and expanding
   it with some latency information. It does not lay out why the approach of
   a control-word or PSD is not a viable or preferrable option.

2. It is unclear what exactly the new functionality of the new Latency element
   is, wether its meant to be rewriteable HbH or not.

3. I am worried about the 16-bit sequence number, because it will
   not allow to have sufficiently large sequence number space for example for
   cross-country pseudo-wire type detnet flows wih potentialy hundreds of gigabits
   of bandwidth. An application i would think would be quite likely for high-speed
   wide-area DetNet use.

Overall, as outlined in my other reply to this thread, i would prefer if we
could consider a more easily extensible and not necessarily MNA specific encoding
of such per-hop (or end-to-end) QoS metadata to accelerate their exploration.
This specifically of course includes the ability to apply the encoding to the
variety of proposals made to DetNet. E.g.: along  the lines of
draft-eckert-6man-qos-exthdr-discuss.

By making an encoding easily extensible, it would also allow to more easily
apply it to QoS mechanisms that do not necessarily have to be defined through IETF
standards track, but leaves the door open to definition through other tracks as
well. This would be good for experimentation and innovation.

Cheers
    Toerless

On Sat, Aug 03, 2024 at 02:05:36PM -0700, Greg Mirsky wrote:
> Hi Tony,
> please find my answers to your questions below tagged GIM>>.
> 
> Regards,
> Greg
> 
> On Tue, Jul 30, 2024 at 8:26 AM Tony Li <tony.li@tony.li> wrote:
> 
> > [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?
> >
> > GIM>> IOAM-DEX, as it provides all the richness of telemetry information
> IOAM can collect at the minimal impact on the length of the MPLS label
> stack.
> 
> >
> >    1.
> >
> >    Do you have other applications of MNA that have not been proposed yet?
> >
> > GIM>> We've published a draft-varmir-mpls-detnet-mna
> <https://datatracker.ietf.org/doc/draft-varmir-mpls-detnet-mna/> that
> proposes a new way to use ISD MNA in the DetNet environment.
> 
> >
> >
> >  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
> >

> _______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org


-- 
---
tte@cs.fau.de