[mpls] Re: Poll: IOAM and PSD

Greg Mirsky <gregimirsky@gmail.com> Mon, 05 August 2024 22:43 UTC

Return-Path: <gregimirsky@gmail.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 D2267C151552 for <mpls@ietfa.amsl.com>; Mon, 5 Aug 2024 15:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, HTML_MESSAGE=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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 M0R5MY0pXXtl for <mpls@ietfa.amsl.com>; Mon, 5 Aug 2024 15:43:15 -0700 (PDT)
Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC46BC14F71D for <mpls@ietf.org>; Mon, 5 Aug 2024 15:43:14 -0700 (PDT)
Received: by mail-yb1-xb34.google.com with SMTP id 3f1490d57ef6-e0b10e8b6b7so15598276.2 for <mpls@ietf.org>; Mon, 05 Aug 2024 15:43:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722897794; x=1723502594; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=apou4bXB+pCBDLCkTaZX/rtTcZScINGvTskiP2sau1A=; b=Q0lnNCcttwUqMPAQz0Gxua0iqdCM3h/ccs1wNEH/28nYS26sM2ewZWjZhLAa4gSxS+ HwqaoSqAWie/cjNsvZ8Y7EZ29J5W/V1HTy5IlWje/532q5Q0zpJV8+txVFvtZZnERZ/c pevcxgphWJc5txSbF01LiSSZV3nBkZY82V/z1ZFPnXch3E8Afhmw4HBxaYxAr+N85jC/ 3fsKprq80LLzYS7pLhE4C+RKrba7FAXgBHgIjWDkh5B1TJiZQx3U3yicQgVpNIqSuHy0 v3dZufGhh0hQ9iEgk2azMMfVNflueqGbZ7j2QB2U4HTIaT0Ef7A33USrpZM+B7YPF+Vt z7fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722897794; x=1723502594; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=apou4bXB+pCBDLCkTaZX/rtTcZScINGvTskiP2sau1A=; b=KqyBEu4SWUHxUADynaQk81aNWMTywaf3LVL/d4udCChbPTsc7nbu/mjqqg5lndlMpI PPYLAA1WaLO/OaRKc3D5F77ZWY/hd07hC37d2YOdQz5qkiTjrTa2fSmufvCKNSoG0jkF CS4XonMQWprBm1IU+nCGhmBvKNQSCAG7q3bvkFvzA/39ix4QYSt+/wZD6ogyTgdX+iHh TSjnzCiCyJ7TeLkbrAwjFgz4KFqAD5xQ473JRArZXR8WRW4HOagrJuqEesSvJooj6HCm N6JOqxFU6+cEfCyqNXFYpltwtg2Xqe/qF8gWadjQVdphETgKFXk6TeomCeOHIXtTWEOs ibwQ==
X-Forwarded-Encrypted: i=1; AJvYcCWzKp3r+NxiC1aBjgpZZAMaqOR+TFEr8bIerjN1mdgvcoDFY1NlFmSFTkCBOJ9HFx6nTqyNvsScQHtO9xhU
X-Gm-Message-State: AOJu0YyQ22LPjuzmF9m21MlhN1ITFJYSDe3BTsajVLBOzece8DoRUh0E SnCeIqoJr7R2Necot+tb/Gr01NZKknD5MhiJbZKPsoLRZw8IfOwUNqn05WNojOmlWxrrs8cx7ff pUGVJLv96pp/elAnbtfHexxtnw1c=
X-Google-Smtp-Source: AGHT+IGKEdAC+5is+Ozr8K3/mRxKk614KloVyrU9G7Lg4/oxItS+XXJJUdKP17m2qse3U6I65lP84MfU4D3IEb2dd50=
X-Received: by 2002:a25:ef46:0:b0:e0b:be99:1fd3 with SMTP id 3f1490d57ef6-e0bde5217cbmr14076225276.48.1722897793869; Mon, 05 Aug 2024 15:43:13 -0700 (PDT)
MIME-Version: 1.0
References: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li> <CAMZsk6fHoUgNg8psgTPmFgwopnPprPiL95Q7QLnsic6CJyHgQQ@mail.gmail.com>
In-Reply-To: <CAMZsk6fHoUgNg8psgTPmFgwopnPprPiL95Q7QLnsic6CJyHgQQ@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 05 Aug 2024 15:43:02 -0700
Message-ID: <CA+RyBmXavHMDHbC1OoCyZAW12CXPA80MHZBfcawJ=gt0JdSubw@mail.gmail.com>
To: Rakesh Gandhi <rgandhi.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000fcf391061ef76613"
Message-ID-Hash: PZYS5Q2ZAKQITNTBB3IVO3AQQETOIH6C
X-Message-ID-Hash: PZYS5Q2ZAKQITNTBB3IVO3AQQETOIH6C
X-MailFrom: gregimirsky@gmail.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 <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/hd_7_NszVbjAzgcclWeeOJ1eTb4>
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>

Hi Rakesh,
I have a number of questions based on you responses and would greatly
appreciate your helping me to better understand. I'll top-post below and
tag my questions with GIM>>:

   - Based on my understanding, two IOAM option-types, namely,
   Pre-allocated Trace (value 0) and Direct-Export (value 4) are popular.

GIM>> What is the measure of "popular"? HW implementations?

   - Data fields such as 32-bit Sequence Number or 32-bit Timestamp in
   In-Stack LSE can lead to undesired ECMP behavior on nodes that use labels
   for ECMP hashing

GIM>> Could you please point me where the use of Timestamp in RFC 9326
IOAM-DEX is required or even discussed as optional?

Regards,
Greg

On Mon, Aug 5, 2024 at 3:32 PM Rakesh Gandhi <rgandhi.ietf@gmail.com> wrote:

> Hi Tony,
>
>
>
> Although not directly related to the question in the poll but since PSD is
> mentioned in the title of this email for poll, like to highlight the
> certain advantages of adding IOAM data fields in Post-Stack Network Action
> for both post-card based and passport-based methods.
>
>
>
>    1. IOAM E2E/POT/TRACE/DEX option-types contain various data fields as
>    defined in RFC 9197 and RFC 9326
>    <https://datatracker.ietf.org/doc/html/rfc9326>.
>    2. Data fields such as 32-bit Sequence Number or 32-bit Timestamp in
>    In-Stack LSE can lead to undesired ECMP behavior on nodes that use labels
>    for ECMP hashing
>       - Data fields in Post-Stack are not included in ECMP hashing
>    3. 32-bit data fields do not fit into 30-bit data in In-Stack LSE,
>    limited to 11-bit as variable or mutable data
>    - RFC standard IOAM format data fields fit well into 32-bit Post-Stack
>       Network Action Data
>       4. IOAM option types support extensibility to optionally add many
>    data fields
>       - Node can easily skip In-Stack network action and process the next
>       one even when Data in Post-Stack is outside RLD
>    5. IOAM-DEX data fields can be seen as metadata in the received
>    packets that data plane exports
>       - Metadata could easily be in Post-Stack
>
>
> P.S. The IOAM network action and offset for the data fields for both IOAM
> methods would be in-stack. The above points are for the data fields.
>
>
> Thanks,
>
> Rakesh
>
>
>
> On Tue, Jul 30, 2024 at 11:27 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?
>>    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
>>
> _______________________________________________
> mpls mailing list -- mpls@ietf.org
> To unsubscribe send an email to mpls-leave@ietf.org
>