Re: [ippm] FW: New Version Notification for draft-filsfils-spring-path-tracing-00.txt

Tal Mizrahi <> Tue, 15 March 2022 10:27 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 735FC3A1B9D; Tue, 15 Mar 2022 03:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Status: No, score=-2.107 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2Rzy3GUOLveM; Tue, 15 Mar 2022 03:27:48 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::1131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 67AB03A1B9C; Tue, 15 Mar 2022 03:27:32 -0700 (PDT)
Received: by with SMTP id 00721157ae682-2e5757b57caso39726967b3.4; Tue, 15 Mar 2022 03:27:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=qiYGAhIoP72te+lpmEoA9ZCebtlVo+plHRAP1rhzNiM=; b=BVULhlfzc6SwtxSyXo2tOxXtQ8MNPV+Vb8vkqP+HldgdVQilyJ4Oi18ecQrUbXSFqF TPUqH3v3GkvF3RBUg9LZOeXZ4OF5osEzivjbklaORYYgAK8sTULoOfaCDmUjndutdyXs wi2e7LD9tsDLHL0mJfZGancrwOEOmezQMhQwh2Hnse5e1HaloyUlrTvltdkaeRRUcgUt JFV/QeBAoEC3rRYydTwkHjEuI8EfDGjxLf7mN8b87RVBgsL165CBEimkSB4NLp0EiisQ ZYW0I8i/THSGscXEHn214UTANy1pkw3jIYU1WeSRXsAsBYXwnWOxOOsXMLzZdLLKGIwn Pf/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=qiYGAhIoP72te+lpmEoA9ZCebtlVo+plHRAP1rhzNiM=; b=lu5VbRQgVHpnn6rmBplTIDazS9oPBLczpEHJPcgiAQHK09s4pNfB73zttIs0J+4BsE OZYVVwejiVV0qWxHJAaQB5qnpIR93+sfv1KI7SrVtKnJP4HvAXJFd7AYvArIVuGhHUVJ y1kXqu8zFczEupe12dSFqhgNp4v271Jlk5cDvrvIv11oYQd35/BptU+ydA3Kb8Ob9PAN VjOk9acrbTVAJ73TjMeJSvTPP3biAlc8HyfJ9CNiw/6JnJ1ueNusNxyhdu5jIzBRe+GY JZlbqnNrxOa5i8jykbQywH5RM0AYRRLy5jVQYcLtcKi/5w1c8iiZ3gbCztVdvH90ZFox xFjw==
X-Gm-Message-State: AOAM530N+oel2mr6PFv4AOhcEPddeB108of+/pDwgF7eq+/c6QnSBAGY 9mYouLZLWgAM4I17bkVX+cJi1IXAyJ6ogAvXt6s=
X-Google-Smtp-Source: ABdhPJyiQAnCME9UJCIAqyeX0Vz/MnjLJxTuxCXstaou48VuSjTiziy5qFN1K1SUwTQGfxEyij0sTwUgltO4Vhccl/M=
X-Received: by 2002:a81:a882:0:b0:2ca:287c:6bc4 with SMTP id f124-20020a81a882000000b002ca287c6bc4mr24118482ywh.105.1647340046302; Tue, 15 Mar 2022 03:27:26 -0700 (PDT)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Tal Mizrahi <>
Date: Tue, 15 Mar 2022 12:27:15 +0200
Message-ID: <>
To: "Ahmed Abdelsalam (ahabdels)" <>, "" <>, "" <>,
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [ippm] FW: New Version Notification for draft-filsfils-spring-path-tracing-00.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 15 Mar 2022 10:28:01 -0000

Dear authors,

Thanks for sharing this interesting draft.
Per-hop measurement and reporting is a very important OAM tool, and
there is quite a bit of ongoing / previously proposed work in the IETF
about this topic.

A few comments:
1. It looks like the draft defines two aspects:  (a) the path tracing
IPv6 option, which is not specific to segment routing, but is actually
applicable to IPv6 routers in general, and (b) an SRH TLV. It seems
like the SRH TLV could alternatively be defined as a generic IPv6
destination option. Is there anything that functionally limits this
feature to networks that use segment routing?
2. As Greg pointed out in a previous email, the functionality here
seems very similar to IOAM. The PT option could actually be
implemented by using an IOAM trace option: by defining a couple of new
data fields you could get an equally compact number of bits as the PT
option in the current draft.  The SRH TLV could alternatively be
defined as an IOAM Edge-to-edge option (again, maybe with a couple of
new data fields). Is there a reason why this is a new protocol, rather
than just defining new data field types in IOAM?
3. Time synchronization is defined as a 'MUST' in the draft, but it
seems like you can benefit from path tracing even in cases where
synchronization is not possible. Have you considered such use cases?
4. Regarding 'MCD.TTS (Truncated Timestamp)': rather than defining
some of the bits to represent milliseconds and other bits to represent
microseconds, it may be more hardware-friendly to define a subset of
the bits of timestamp formats that are commonly implemented in
hardware, such as the PTP timestamp format or the NTP timestamp


On Wed, Mar 9, 2022 at 4:14 PM Ahmed Abdelsalam (ahabdels)
<> wrote:
> We have submitted a new I-D for Path Tracing in SRv6 networks ( to SPRING WG.
> We are looking for your feedback and comments.
> Path Tracing provides a record of the packet path as a sequence of interface ids. In addition, it provides a record of end-to-end delay, per-hop delay, and load on each egress interface along the packet delivery path to facilitate operation of SR networks.
> Path Tracing allows to trace 14 hops with only a 40-octet IPv6 Hop-by-Hop extension header.
> We will present Path Tracing to the SPRING WG at next IETF (
> Thanks,
> Ahmed
> From: <>
> Date: Friday, 4 March 2022 at 16:48
> To: Ahmed Abdelsalam (ahabdels) <>, cf(mailer list) <>, Mark Yufit <>, Pablo Camarillo (pcamaril) <>, Pablo Camarillo (pcamaril) <>, Satoru Matsushima <>, Thomas.Graf <>, Yuanchao Su <>
> Subject: New Version Notification for draft-filsfils-spring-path-tracing-00.txt
> A new version of I-D, draft-filsfils-spring-path-tracing-00.txt
> has been successfully submitted by Pablo Camarillo Garvia and posted to the
> IETF repository.
> Name:           draft-filsfils-spring-path-tracing
> Revision:       00
> Title:          Path Tracing in SRv6 networks
> Document date:  2022-03-04
> Group:          Individual Submission
> Pages:          15
> URL:  
> Status:
> Htmlized:
> Abstract:
>    Path Tracing provides a record of the packet path as a sequence of
>    interface ids.  In addition, it provides a record of end-to-end
>    delay, per-hop delay, and load on each egress interface along the
>    packet delivery path.
>    Path Tracing allows to trace 14 hops with only a 40-bytes IPv6 Hop-
>    by-Hop extension header.
>    Path Tracing supports fine grained timestamp.  It has been designed
>    for linerate hardware implementation in the base pipeline.
> The IETF Secretariat
> _______________________________________________
> ippm mailing list