[mpls] Re: Poll: IOAM and PSD

Tony Li <tony.li@tony.li> Mon, 05 August 2024 22:39 UTC

Return-Path: <tony1athome@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 E6DC7C14F693 for <mpls@ietfa.amsl.com>; Mon, 5 Aug 2024 15:39:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.754
X-Spam-Level:
X-Spam-Status: No, score=-6.754 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, 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, 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 62aNP0XTpKC9 for <mpls@ietfa.amsl.com>; Mon, 5 Aug 2024 15:39:12 -0700 (PDT)
Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (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 1E960C14F685 for <mpls@ietf.org>; Mon, 5 Aug 2024 15:39:12 -0700 (PDT)
Received: by mail-pf1-x429.google.com with SMTP id d2e1a72fcca58-70eaf5874ddso8446402b3a.3 for <mpls@ietf.org>; Mon, 05 Aug 2024 15:39:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722897551; x=1723502351; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:sender:from:to:cc:subject:date:message-id:reply-to; bh=0nWQOeKJcR43id+RBCmAlvkfijKmQ+XHeUsTy1cHLB0=; b=Za3IC+FOtNGk1HDU6D2Ze0mkBTUH2cZuYJBoeDATs5eGCf+W9UxIZC6hAh99jIdm+B RMHOFFVeuOmOuracn5eeQUnEnbDX8QXZAZufVTIXf/ym56EmoV2NIHlF/78PyfOl4s9C +mevbB0SMevE8kRfiyV+DgvhpxV+orK4Bxb3Dsokvh/iRYQJ04LLiJr3GZokE27tJVdt 1o16u6NacFg0XVS08aNu7LZcBs9L34tGHvPF+NTuGnUdH/EjQQfguhxzmZwLF1Wzwu/u uajK1cvNRwDIyZKauNZMV3PPTWt4JuBeOTWuxGB02Cy6+Juvnt5OkITI/d3ky1cvCln5 trAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722897551; x=1723502351; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0nWQOeKJcR43id+RBCmAlvkfijKmQ+XHeUsTy1cHLB0=; b=Z0qJ5oduxP8NqYMRWAEhEVsmlndpRNk5+cdA+iJgnaG9gZc/5XB1B3zyymBg5vFZ/3 vxl4CjO+ihTYQ5T1ACzRCX5rvkQPzCXBw2cgXRGrkbFBjGxgQUsQv9//pmnd9WC+bztn 7L/8lZtRE/WJmGQ5SczhKPZNXBfv/XnXYIQUFQBBm/0XWMbgYwc84jBfftQJukxF3DuO ZTUUdktsbFaQMzcLCghPc5RQ358sHzujwyFAUMpHspqwxrTXOXRX/mCW3b9SdM3He4rA hrcu7liQKvdTxZiZ5v57JpJaZC4rpHv/scHslefmg5W2kYbQW6Wae+KY6qkRyiF8UzZ/ Py8w==
X-Gm-Message-State: AOJu0YxChg1Wgg9nRzTs3XDeRE0rEEwfv2GFUbAlOYpPFzi6x9+mspm6 G2rcNIUbKHT+qIlz1zuRB6YRKhQWVOebXHTjPCTIJlYDo8YtO+tZ
X-Google-Smtp-Source: AGHT+IEoF9oqXUbD2zc+gxLKQBVbz9UJhowSRjiEt02Bd/NIg3ym5tGz/rE+HoRUL28hXVOZk8UzLg==
X-Received: by 2002:a05:6a00:9467:b0:710:6f54:bcac with SMTP id d2e1a72fcca58-7106f54bf82mr10316968b3a.1.1722897551272; Mon, 05 Aug 2024 15:39:11 -0700 (PDT)
Received: from smtpclient.apple (c-73-93-167-4.hsd1.ca.comcast.net. [73.93.167.4]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7106ec410b4sm5892473b3a.61.2024.08.05.15.39.10 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Aug 2024 15:39:10 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: Tony Li <tony.li@tony.li>
Message-Id: <D8B4518F-B2B5-401E-BFB0-AFA4938AC11D@tony.li>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1DADCEDE-35CA-4F1C-AE3F-ED3D4E836516"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Date: Mon, 05 Aug 2024 15:38:59 -0700
In-Reply-To: <CAMZsk6fHoUgNg8psgTPmFgwopnPprPiL95Q7QLnsic6CJyHgQQ@mail.gmail.com>
To: Rakesh Gandhi <rgandhi.ietf@gmail.com>
References: <F78CB19B-2880-48AB-99CE-D46280014A87@tony.li> <CAMZsk6fHoUgNg8psgTPmFgwopnPprPiL95Q7QLnsic6CJyHgQQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: AOIV66H6EYUJFLGBSXS6SI4PDXJSTBTJ
X-Message-ID-Hash: AOIV66H6EYUJFLGBSXS6SI4PDXJSTBTJ
X-MailFrom: tony1athome@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/T32EjJIss3ohCEVL7z32YNYiDWQ>
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>

[WG chair hat: on]

Hi Rakesh,

Thank you for responding, but we need responses that directly address the question in the poll as stated.  

Regards,
Tony


> On Aug 5, 2024, at 3:30 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.
>  
> 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>.
> 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
> 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
> 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
> 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 <mailto: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:
>>  
>> There are many flavors of IOAM.  Which ones would you like to deploy/implement with MNA?
>> 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 <mailto:mpls@ietf.org>
>> To unsubscribe send an email to mpls-leave@ietf.org <mailto:mpls-leave@ietf.org>