Re: [ippm] New Version Notification for draft-ahuang-ioam-on-path-delay-00.txt

Justin Iurman <justin.iurman@uliege.be> Tue, 07 March 2023 11:34 UTC

Return-Path: <justin.iurman@uliege.be>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6E3C14F749 for <ippm@ietfa.amsl.com>; Tue, 7 Mar 2023 03:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=uliege.be
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 d_m2u-fegc08 for <ippm@ietfa.amsl.com>; Tue, 7 Mar 2023 03:34:18 -0800 (PST)
Received: from serv108.segi.ulg.ac.be (serv108.segi.ulg.ac.be [139.165.32.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B1ACC14E515 for <ippm@ietf.org>; Tue, 7 Mar 2023 03:34:17 -0800 (PST)
Received: from [192.168.1.62] (148.24-240-81.adsl-dyn.isp.belgacom.be [81.240.24.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by serv108.segi.ulg.ac.be (Postfix) with ESMTPSA id 08A6C200BE43; Tue, 7 Mar 2023 12:34:14 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.11.0 serv108.segi.ulg.ac.be 08A6C200BE43
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uliege.be; s=ulg20190529; t=1678188854; bh=mzjwEHNJPGbVNvfz3inZCaMzaq1qQG0tak1F1IxjIew=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=hwFUzWPZDNlxQNLD5OuNA0IQV6vHHJzLD5E72ZG5rjeJ8QJtSDiXr6HAvMSvXL3Se 4EdH8wWIjKeVmpcufzkFnUhntILMz0OvgSYdgRQXXCNfei4w+LSTwzYew8VvGi2zCU UaBGAY+V78/XoBZe06q+mRiUVPJbJrgrITuGmsVL/NoTRJsP4qdgmO5aRLFeb5/Kdq FoO6Vrn5CVxfW8GUaztHUMOoZcmrrnI9KeexRKlfEAbmDAmBXXt9E10Rim6ruhrYaJ S7/aQ8cWcuQ2Y1JKi9blDptWytNobL0uK+LH2kmVfaYoMg0lKRG8EX3d0sX/6wjQzd LEMaEjQuk33Sg==
Message-ID: <1dee74d1-a903-753d-9261-2a0c4b3c6c13@uliege.be>
Date: Tue, 07 Mar 2023 12:34:13 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: Alex Huang Feng <alex.huang-feng@insa-lyon.fr>, ippm@ietf.org, Pierre Francois <pierre.francois@insa-lyon.fr>
References: <167786164701.47548.4590359889410617737@ietfa.amsl.com> <00C45E5E-0797-443B-BEB6-81AF1E845905@insa-lyon.fr> <6d1cbc46-c460-cd9d-657e-cc82746665f4@uliege.be> <CA+RyBmX1Sz--jWpYduO6a8Y-yL-4x_+QZ7M-a2KWgwVZonvKBA@mail.gmail.com>
Content-Language: en-US
From: Justin Iurman <justin.iurman@uliege.be>
In-Reply-To: <CA+RyBmX1Sz--jWpYduO6a8Y-yL-4x_+QZ7M-a2KWgwVZonvKBA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/SL7P_JKLqA-0P8TiqZKYvnViUOA>
Subject: Re: [ippm] New Version Notification for draft-ahuang-ioam-on-path-delay-00.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Mar 2023 11:34:23 -0000

Hi Greg,

On 3/3/23 22:17, Greg Mirsky wrote:
> Hi, Alex, Justin et al.,
> I read the draft and have some notes to share with you:
> 
>   * I think that I understand the motivation of the authors of the
>     draft. RFC 9197 does not specify when the timestamp SHOULD (less,
>     MUST) be taken. As a result, it is challenging to extract variable

True, "the time at which the packet was received by the node" 
([RFC9197]) can be vague, although all devices of an IOAM-Domain are 
expected to follow the same definition. But, then...

>     [...] Have you
>     considered using Bit 4 Transit delay as defined in RFC 9197?

... bit 4 Transit Delay has the same issue, i.e., RFC 9197 does not 
specify exactly when the ingress/egress timestamps SHOULD/MUST be taken. 
Besides, this data field is quite often hard to retrieve (and by "hard", 
I mean from a performance point of view).

Thanks,
Justin

> Regards,
> Greg
> 
> On Fri, Mar 3, 2023 at 10:52 AM Justin Iurman <justin.iurman@uliege.be 
> <mailto:justin.iurman@uliege.be>> wrote:
> 
>     Hi Alex,
> 
>     I don't understand why bits 2 and 3 (i.e., timestamp seconds &
>     fraction)
>     are not enough. If each node on the path timestamps its data part in
>     the
>     trace, then based on the entire trace you're able to recompute on-path
>     delays by simply substracting a node's timestamp by the one of the
>     encapsulating node. You can actually compute the on-path delay between
>     any node. Did I miss something?
> 
>     Thanks,
>     Justin
> 
>     On 3/3/23 17:54, Alex Huang Feng wrote:
>      > Dear IPPM WG,
>      >
>      > Some time ago I submitted draft-ahuang-ippm-dex-timestamp-ext that
>      > allows IOAM DEX to add a timestamp in the header.
>      > This allows IOAM in postcard mode to compute the on-path delay at
>     each node.
>      >
>      > To export the on-path delay in the IOAM architecture, a bit-field
>     is used.
>      > This new draft adds a new 32bit Data-field in the "IOAM Trace-Type”
>      > registry allowing the export of the On-path delay in the IOAM
>     architecture.
>      >
>      > I would like to request feedback from the WG on this draft.
>      >
>      > Cheers,
>      > Alex
>      >
>      >> On 3 Mar 2023, at 17:40, internet-drafts@ietf.org
>     <mailto:internet-drafts@ietf.org>
>      >> <mailto:internet-drafts@ietf.org
>     <mailto:internet-drafts@ietf.org>> wrote:
>      >>
>      >>
>      >> A new version of I-D, draft-ahuang-ioam-on-path-delay-00.txt
>      >> has been successfully submitted by Alex Huang Feng and posted to the
>      >> IETF repository.
>      >>
>      >> Name:draft-ahuang-ioam-on-path-delay
>      >> Revision:00
>      >> Title:On-Path delay Data Field for In Situ Operations,
>     Administration,
>      >> and Maintenance (IOAM)
>      >> Document date:2023-03-03
>      >> Group:Individual Submission
>      >> Pages:7
>      >> URL:
>      >>
>     https://www.ietf.org/archive/id/draft-ahuang-ioam-on-path-delay-00.txt <https://www.ietf.org/archive/id/draft-ahuang-ioam-on-path-delay-00.txt>
>      >>
>     <https://www.ietf.org/archive/id/draft-ahuang-ioam-on-path-delay-00.txt <https://www.ietf.org/archive/id/draft-ahuang-ioam-on-path-delay-00.txt>>
>      >> Status:
>      >>
>     https://datatracker.ietf.org/doc/draft-ahuang-ioam-on-path-delay/
>     <https://datatracker.ietf.org/doc/draft-ahuang-ioam-on-path-delay/>
>      >>
>     <https://datatracker.ietf.org/doc/draft-ahuang-ioam-on-path-delay/
>     <https://datatracker.ietf.org/doc/draft-ahuang-ioam-on-path-delay/>>
>      >> Htmlized:
>      >>
>     https://datatracker.ietf.org/doc/html/draft-ahuang-ioam-on-path-delay <https://datatracker.ietf.org/doc/html/draft-ahuang-ioam-on-path-delay>
>      >>
>     <https://datatracker.ietf.org/doc/html/draft-ahuang-ioam-on-path-delay <https://datatracker.ietf.org/doc/html/draft-ahuang-ioam-on-path-delay>>
>      >>
>      >>
>      >> Abstract:
>      >>   This document defines a Data Field In Situ Operations,
>      >>   Administration, and Maintenance (IOAM) architecture for
>     on-path delay
>      >>   information.  This data field is registered as a new entry in the
>      >>   "IOAM Trace-Type" registry.
>      >>
>      >>
>      >>
>      >>
>      >>
>      >> The IETF Secretariat
>      >>
>      >>
>      >
>      >
>      > _______________________________________________
>      > ippm mailing list
>      > ippm@ietf.org <mailto:ippm@ietf.org>
>      > https://www.ietf.org/mailman/listinfo/ippm
>     <https://www.ietf.org/mailman/listinfo/ippm>
> 
>     _______________________________________________
>     ippm mailing list
>     ippm@ietf.org <mailto:ippm@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ippm
>     <https://www.ietf.org/mailman/listinfo/ippm>
>