From nobody Fri Mar 3 08:54:39 2023 Return-Path: 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 ADB12C14EB1E for ; Fri, 3 Mar 2023 08:54:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.228 X-Spam-Level: X-Spam-Status: No, score=-0.228 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_HELO_IP_MISMATCH=2.368, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 qzsV1lwg8DWx for ; Fri, 3 Mar 2023 08:54:34 -0800 (PST) Received: from smtpout02-ext4.partage.renater.fr (smtpout02-ext4.partage.renater.fr [194.254.241.31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 000C3C14EB1A for ; Fri, 3 Mar 2023 08:54:32 -0800 (PST) Received: from zmtaauth04.partage.renater.fr (zmtaauth04.partage.renater.fr [194.254.241.26]) by smtpout20.partage.renater.fr (Postfix) with ESMTP id 26D2FC053A; Fri, 3 Mar 2023 17:54:28 +0100 (CET) Received: from zmtaauth04.partage.renater.fr (localhost [127.0.0.1]) by zmtaauth04.partage.renater.fr (Postfix) with ESMTPS id 1C1931C001E; Fri, 3 Mar 2023 17:54:28 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by zmtaauth04.partage.renater.fr (Postfix) with ESMTP id 14F181C00D0; Fri, 3 Mar 2023 17:54:28 +0100 (CET) Received: from zmtaauth04.partage.renater.fr ([127.0.0.1]) by localhost (zmtaauth04.partage.renater.fr [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id d9CL9uVQXvQy; Fri, 3 Mar 2023 17:54:28 +0100 (CET) Received: from 134.214.146.150 (unknown [194.254.241.250]) by zmtaauth04.partage.renater.fr (Postfix) with ESMTPA id C7A201C001E; Fri, 3 Mar 2023 17:54:27 +0100 (CET) From: Alex Huang Feng Message-Id: <00C45E5E-0797-443B-BEB6-81AF1E845905@insa-lyon.fr> Content-Type: multipart/alternative; boundary="Apple-Mail=_EF007A5F-0CB9-4577-A0D0-A6E83406A77F" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.2\)) Date: Fri, 3 Mar 2023 17:54:27 +0100 In-Reply-To: <167786164701.47548.4590359889410617737@ietfa.amsl.com> Cc: Benoit Claise , Pierre Francois , Thomas Graf To: ippm@ietf.org References: <167786164701.47548.4590359889410617737@ietfa.amsl.com> X-Mailer: Apple Mail (2.3696.120.41.1.2) X-Virus-Scanned: clamav-milter 0.103.8 at clamav02 X-Virus-Status: Clean X-Renater-Ptge-SpamState: clean X-Renater-Ptge-SpamScore: -100 X-Renater-Ptge-SpamCause: gggruggvucftvghtrhhoucdtuddrgedvhedrudelledgkeekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecutffgpfetvffgtfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffktgggufffjgevvfhfofesrgdtmherhhdtjeenucfhrhhomheptehlvgigucfjuhgrnhhgucfhvghnghcuoegrlhgvgidrhhhurghnghdqfhgvnhhgsehinhhsrgdqlhihohhnrdhfrheqnecuggftrfgrthhtvghrnhepkeeggeevteffiedtueeukeduiedvveehfeeltdfhieetkeetgffhkeegtdfhheefnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepudelgedrvdehgedrvdeguddrvdehtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpeduleegrddvheegrddvgedurddvhedtpdhhvghlohepudefgedrvddugedrudegiedrudehtddpmhgrihhlfhhrohhmpeetlhgvgicujfhurghnghcuhfgvnhhguceorghlvgigrdhhuhgrnhhgqdhfvghnghesihhnshgrqdhlhihonhdrfhhrqedpnhgspghrtghpthhtohepgedprhgtphhtthhopehiphhpmhesihgvthhfrdhorhhgpdhrtghpthhtohepsggvnhhoihhtrdgtlhgrihhsvgeshhhurgifvghirdgtohhmpdhrtghpthhtohepphhivghrrhgvrdhfrhgrnhgtohhishesihhnshgrqdhlhihonhdrfhhrpdhrtghpthhtohepthhhohhmrghsrdhgrhgr fhesshifihhsshgtohhmrdgtohhm Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2023 16:54:37 -0000 --Apple-Mail=_EF007A5F-0CB9-4577-A0D0-A6E83406A77F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 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=E2=80=9D= 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 wrote: >=20 >=20 > 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. >=20 > 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 > Status: = https://datatracker.ietf.org/doc/draft-ahuang-ioam-on-path-delay/ > Htmlized: = https://datatracker.ietf.org/doc/html/draft-ahuang-ioam-on-path-delay >=20 >=20 > 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. >=20 >=20 >=20 >=20 >=20 > The IETF Secretariat >=20 >=20 --Apple-Mail=_EF007A5F-0CB9-4577-A0D0-A6E83406A77F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 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=E2=80=9D 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 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
Status: =         https://datatracker.ietf.org/doc/draft-ahuang-ioam-on-path-dela= y/
Htmlized:       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



= --Apple-Mail=_EF007A5F-0CB9-4577-A0D0-A6E83406A77F--