[mpls] Re: Poll: IOAM and PSD

Rakesh Gandhi <rgandhi.ietf@gmail.com> Mon, 05 August 2024 22:30 UTC

Return-Path: <rgandhi.ietf@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 DED4BC14F6F3 for <mpls@ietfa.amsl.com>; Mon, 5 Aug 2024 15:30:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, 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=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 9Em0cZp_tWT0 for <mpls@ietfa.amsl.com>; Mon, 5 Aug 2024 15:30:17 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 DCA93C151078 for <mpls@ietf.org>; Mon, 5 Aug 2024 15:30:16 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id 2adb3069b0e04-52efc89dbedso13049315e87.3 for <mpls@ietf.org>; Mon, 05 Aug 2024 15:30:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722897015; x=1723501815; 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=xZGZF+EUG9qB8OLZ1+SXrxF5NcnTIL6Ggc7LuS/N0o4=; b=cBSA6lSHg+EfmzXntf5GQmO+YRn9ew/+d8Gupg1HrGjPb4z+NpCdjL0E9qAwW8flq6 nwo5VU7/jgcuJ/xuNQJPlymKVXcKUQi4UnUL+JTE5jFI1mmfHyTuO+TUqccV1MKf3/E0 pyzvPdpLKEfeI7vUHDswvQSpSIS03NQh0Yo9hfnUQCd3yNHxA7ZReHuaPnneroN1q9IP RAZgC70mGt9ov6d4A14UBpejWMhh6UpI6XqdaFgXagaKp+kPqzfrFKFRne72CHultzL8 Jq4MpQjfRd8++K5cThUB9bf3qngKXXLZQCi/On7j7dog+0+EqP6I29IHv3OP+pLwO43d uvRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722897015; x=1723501815; 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=xZGZF+EUG9qB8OLZ1+SXrxF5NcnTIL6Ggc7LuS/N0o4=; b=cRmMYS+03Y6KtvUHrizgxw3nbYpOBydfMv2/o5WIX1L16hEGoTtwsV8Uy+zNiZXHgi 2XIz7FaFTrwLFSgXHIVIZ2suQHS4ynnKULQ7zBRI/q8XPvLXmosyYGmJejzWkOuLjwGE 4WViUYCYSAnxFhfaaQT3mqinwS1KM109pEyh/Gq+TPnruMpRHfobrvlW8GrIgHkzxQHg lyIPTrmEasDaqvtifyXC89MG9aghvC6+8v4D5VZPsN2v2NE9DwiWdz7/b2R52bKj9VOj GTHfsuqMNXabGM4G/4IqHOj6XVzkniykwt2vnI/jEhAGrFgy/w+ZmhmqHpQWz3Q65Hro uywg==
X-Gm-Message-State: AOJu0YwQSBtBqJjOIdwFE/sIurTjtIXPXd+xWVzrhlHr8O4qcnHBFPCJ TN30ll0ABAnOqvqM1YVhey/jKafDkZq6rsTPjXpuflA0KAxNdohOa2csN+TT2CfGZTJGsWJBo01 RDRCWOzlzdifEAkfGdBBt+fo9Crid4tTQkw==
X-Google-Smtp-Source: AGHT+IHKcqiQKIZl1dFLZggfJ3BT5hOSOxgDuuM5jFtY0viCOu6hloTRCuNc1CHazQhkhgwRcS5i5sCyOn1fwpNM4xY=
X-Received: by 2002:a05:6512:10c9:b0:52f:288:5664 with SMTP id 2adb3069b0e04-530bb3b1039mr9321613e87.51.1722897014762; Mon, 05 Aug 2024 15:30:14 -0700 (PDT)
MIME-Version: 1.0
References: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li>
In-Reply-To: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li>
From: Rakesh Gandhi <rgandhi.ietf@gmail.com>
Date: Mon, 05 Aug 2024 18:30:03 -0400
Message-ID: <CAMZsk6fHoUgNg8psgTPmFgwopnPprPiL95Q7QLnsic6CJyHgQQ@mail.gmail.com>
To: Tony Li <tony.li@tony.li>
Content-Type: multipart/alternative; boundary="0000000000008cb885061ef7386a"
Message-ID-Hash: ISC5GJQJIC56YQF3ABLRQ2C4ZHB6OZUM
X-Message-ID-Hash: ISC5GJQJIC56YQF3ABLRQ2C4ZHB6OZUM
X-MailFrom: rgandhi.ietf@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/WcNni_iotjffBanwRnG74cYwHWM>
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 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
>