[mpls] Re: Poll: IOAM and PSD

Loa Andersson <loa@pi.nu> Mon, 12 August 2024 04:14 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 A1A1CC14CE24 for <mpls@ietfa.amsl.com>; Sun, 11 Aug 2024 21:14:15 -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 3WHqFl7YIrpU for <mpls@ietfa.amsl.com>; Sun, 11 Aug 2024 21:14:14 -0700 (PDT)
Received: from srv.pi.nu (srv.pi.nu [46.246.39.30]) (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 694C3C14F5E3 for <mpls@ietf.org>; Sun, 11 Aug 2024 21:14:13 -0700 (PDT)
Message-ID: <a0b1bed8-6fa5-4ed1-9d2e-b0bf9ba6766f@pi.nu>
Date: Mon, 12 Aug 2024 12:14:09 +0800
MIME-Version: 1.0
To: Greg Mirsky <gregimirsky@gmail.com>
References: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li> <BY3PR13MB4787298A531DFA3812CAAB9F9AB92@BY3PR13MB4787.namprd13.prod.outlook.com> <d19ebf6a-732a-4f43-853c-45e6ad04e45c@pi.nu> <BY3PR13MB47877435A56586A7417FF20D9A852@BY3PR13MB4787.namprd13.prod.outlook.com> <2b8a3cf3-b036-4763-8520-8be020aa4d52@pi.nu> <CA+RyBmV3Nfh9uWss2tbVkaLrz9zMSr+TJxpUcXbr2yKQLnCv3g@mail.gmail.com>
Content-Language: sv, en-GB
From: Loa Andersson <loa@pi.nu>
In-Reply-To: <CA+RyBmV3Nfh9uWss2tbVkaLrz9zMSr+TJxpUcXbr2yKQLnCv3g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: ITM3B2F4RXJM57S3KNTXKNLRC7RUDDJC
X-Message-ID-Hash: ITM3B2F4RXJM57S3KNTXKNLRC7RUDDJC
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
CC: mpls <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/ZyAhVCl5kyIJhBvddJSj8q6l0Z4>
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>

Greg,

inline please.

Den 12/08/2024 kl. 11:32, skrev Greg Mirsky:
> Hi Loa,
> could you please clarify when you state
>
>     Which would place it higher in priority of "to be implemented"
>     secifications than draft-mb-mpls-ioam-dex.
>
> you express:
>
>   * your personal opinion
>
I'm an old-timer, even been called grey-beard a couple of times. I 
always speak my opinion, regardless if it aligns with any company or 
another.

Since you have to ask, don't you do that too?

/Loa
>
>   * position of a company you are currently affiliated with
>   * something else
>
> Regards,
> Greg
>
> On Sun, Aug 11, 2024 at 8:26 PM Loa Andersson <loa@pi.nu> wrote:
>
>     Haoyu,
>
>     It is not the BoS bit only. Since uses type D LSEs, the zero bit is
>     already in use. Set to "1" to avoid confusion with Special Purpose
>     Labels, so only 22 bits for flags.
>
>     Another thing is that RFC RFC 9326 specifies 8 extension flags, while
>     draft-mb-mpls-ioam-dex only have 6 flags. Ity should be noted that
>     draft-gandhi-mpls-mna-ioam-dex nicely aligns with RFC 9326. Which
>     would
>     place it higher in priority of "to be implemented" secifications than
>     draft-mb-mpls-ioam-dex.
>     /Loa
>     Den 12/08/2024 kl. 09:39, skrev Haoyu Song:
>     > Yes. The BOS bit in the label field changes a lot of things.
>     >
>     > Haoyu
>     >
>     > -----Original Message-----
>     > From: Loa Andersson <loa@pi.nu>
>     > Sent: Sunday, August 11, 2024 8:26 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,
>     >
>     > do you mean that since specification of IOAM-DEX (RFC 9326)
>     following
>     > RFC9197 specifies
>     >
>     > - IOAM-Trace-Types of 24 bit flag fields And Optional Fields -
>     Flow ID
>     > 32 bits - Sequence Number 32 bits And draft-mb-mpls-ioam-dex
>     specifies - IOAM Trace Types of 22 flag bits And optional fields -
>     Flow ID 30 bits - sequence number 11 bits (variable) That
>     draft-mb-mpls-ioam-dex is strictly not compatible with RFC 9326?
>     /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
>     >
>
>     -- 
>     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
>

-- 
Loa Andersson
Senior MPLS Expert
Bronze Dragon Consulting
loa@pi.nu
loa.pi.nu.@gmail.com