[ippm] Re: Demo: IOAM Ping using ICMPv6 Loopback

Tal Mizrahi <tal.mizrahi.phd@gmail.com> Tue, 28 May 2024 10:21 UTC

Return-Path: <tal.mizrahi.phd@gmail.com>
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 8C6E4C180B4C for <ippm@ietfa.amsl.com>; Tue, 28 May 2024 03:21:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 RYLF5o1Y69B9 for <ippm@ietfa.amsl.com>; Tue, 28 May 2024 03:21:41 -0700 (PDT)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00108C169425 for <ippm@ietf.org>; Tue, 28 May 2024 03:21:40 -0700 (PDT)
Received: by mail-il1-x12e.google.com with SMTP id e9e14a558f8ab-3745600bb97so291255ab.0 for <ippm@ietf.org>; Tue, 28 May 2024 03:21:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716891700; x=1717496500; darn=ietf.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ntxpR+0b6jGiNfqvEo1Lv9IysVSDspU5g98bVRmQOIU=; b=nr2wm6kN25B3vQQdQmZ6HRDX8JRbKoQEmLqGBr+B2PU6GTtVasZS7RgKiz+jaKVeL1 zOZMmaiUBrAVKen2LfzPGqjIedTC1dFNLVJXnzijWjfh+2zfcpEJ/wNe9WRFcpWLaTZ8 jlPP+YKc3MhuDnAQca5Uwt8yeFhtzyNVvR33nVKCZg5C98iW86sE7iSbaRUjOZgnzlyM vsahVkXl0qeTTXbYjcSd1kTAorTX82l8cyFyVbZIGrveX0z+BH1yjDT2b4JAj0rI8SmR NbJGZnZGN1/tr58w/YKUuDIAjN35DV8vk0sGKgBveo75C0J6rTCasDcNjUUbD+ZNHMtT eVYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716891700; x=1717496500; h=content-transfer-encoding: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=ntxpR+0b6jGiNfqvEo1Lv9IysVSDspU5g98bVRmQOIU=; b=MyOfRivAWH9zyoDOqF9fFGzYWpnc4w33XWnAq9DfuCOpEMctKCczilK3RKSoyuHdES MaJaDAj9R/WaZvs3qMkSbJq3blKK+46KUnNKKCy5a8XaoQGDgj9aW+0r5EtvPhlG39AT XBeWEyqlQ8/9MoTHaCT0moT8CuwxkAkL5d0MeM1maAsHz02vkJl/allFIJZ0Igvp5aFR jhpwgefzrVVk+b+SqbWTr6kPCvI10C1H53hz6ZIVZAg6ucrLU3DqT+4Ogevgdu3b56zp pcoPqbedm9gcmC3oqPcV22OzspVL6DjGfR7cInSEBbGyuN9vxpJ2CrDarH1jpR/dyGoD ufNw==
X-Gm-Message-State: AOJu0YwlIFBjtAJlf0pqUyyx4V3auXpC0X223DtMVVEDAIbucP2EP66U CkHwpGFutGKQDBpty/vQiATfzc/VstNelysT9sMpj3PF29SRKYcPbtNjFm8o5k/Y8XdwcBfYc5F dDP7MhZ82e8HO2FoTtyTggXoyxzLIgFzrPUoqCQ==
X-Google-Smtp-Source: AGHT+IHAYbRA3y/aERZLLvd31L+l3+CAdUO8je8oVJvIP2XQZ4p1yZWmAOMDMXJFPF0lQBkE29L7BN31i3jRoc1osk4=
X-Received: by 2002:a5e:df49:0:b0:7de:f48e:36c3 with SMTP id ca18e2360f4ac-7e8c15fd963mr1195947539f.0.1716891699952; Tue, 28 May 2024 03:21:39 -0700 (PDT)
MIME-Version: 1.0
References: <CABUE3Xkprxs9BFbisYGhbyU8ECGtfXgigRzPvVzRZ2y-ugHqEg@mail.gmail.com>
In-Reply-To: <CABUE3Xkprxs9BFbisYGhbyU8ECGtfXgigRzPvVzRZ2y-ugHqEg@mail.gmail.com>
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Date: Tue, 28 May 2024 13:21:25 +0300
Message-ID: <CABUE3XmwLi0v39L2-bDUKmxi-n1qo5kDUxFUE2PaVyNWqGEQcg@mail.gmail.com>
To: IETF IPPM WG <ippm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: GRTOOXAU2GTLKKDJIRJR726GFKC6BH4N
X-Message-ID-Hash: GRTOOXAU2GTLKKDJIRJR726GFKC6BH4N
X-MailFrom: tal.mizrahi.phd@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ippm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [ippm] Re: Demo: IOAM Ping using ICMPv6 Loopback
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/8MyMMPf-Du_8KleGmnp8-ap_7As>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Owner: <mailto:ippm-owner@ietf.org>
List-Post: <mailto:ippm@ietf.org>
List-Subscribe: <mailto:ippm-join@ietf.org>
List-Unsubscribe: <mailto:ippm-leave@ietf.org>

Hi,

I have been asked offline about the difference between IOAM Ping and
draft-gandhi-ippm-stamp-ext-hdr.

So here is a clarification. IOAM Ping is a demo utility that measures
and presents per-hop IOAM data. The demo uses ICMPv6 Loopback messages
(draft-mcb-6man-icmpv6-loopback), although a different implementation
of IOAM Ping could in theory use STAMP messages.

ICMPv6 and STAMP are two different IETF protocols, intended for
different scenarios. Therefore, ICMPv6 Loopback and stamp-ext-hdr can
be viewed as two complementary extensions that extend ICMPv6 and STAMP
respectively.

Cheers,
Tal.

On Thu, Apr 18, 2024 at 12:08 PM Tal Mizrahi <tal.mizrahi.phd@gmail.com> wrote:
>
> Hi,
>
> We have recently proposed ICMPv6 Loopback, a new ICMPv6 type which is
> similar to ICMPv6 Echo, except that the Loopback reply includes the
> IPv6 header, extension headers and IPv6 payload of the corresponding
> Loopback request.
> https://datatracker.ietf.org/doc/draft-mcb-intarea-icmpv6-loopback/
>
> In the context of IOAM this means that an IOAM encapsulating node can
> send an ICMPv6 Loopback request that includes an IOAM option, and the
> Loopback reply includes the IOAM data of the request. This can be
> used, for example, in a Ping-like application.
>
> We have prepared a demo which leverages the existing IOAM
> implementation in the Linux kernel, and uses ICMPv6 Loopback in order
> to implement a Ping-like utility that presents the IOAM data of the
> nodes along the path.
>
> An example of the output of IOAM Ping with two IOAM nodes is shown
> below, with three data fields per hop (Hop limit/node id, timestamp
> seconds, timestamp fraction).
>
> PING db01::1 (db01::1) 56 data bytes
> 152 bytes from db01::1: icmp_seq=1 ttl=64 time=0.192 ms IOAM:
> NodeID=1,HopLim=64,RcvTime=NA
> NodeID=2,HopLim=63,RcvTime=1712811441.126
> 152 bytes from db01::1: icmp_seq=2 ttl=64 time=0.078 ms IOAM:
> NodeID=1,HopLim=64,RcvTime=NA
> NodeID=2,HopLim=63,RcvTime=1712811442.129
>
> The demo is available at:
> https://github.com/talmi/IOAM-Ping-Demo
>
> Feedback about ICMPv6 Loopback and about the Ping demo will be welcome.
>
> Thanks,
> The authors.