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

Tal Mizrahi <tal.mizrahi.phd@gmail.com> Thu, 18 April 2024 15:35 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 BE90BC14F712 for <ippm@ietfa.amsl.com>; Thu, 18 Apr 2024 08:35:49 -0700 (PDT)
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, 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 mOnmGNLKxzah for <ippm@ietfa.amsl.com>; Thu, 18 Apr 2024 08:35:46 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 32E2AC14F6FF for <ippm@ietf.org>; Thu, 18 Apr 2024 08:35:46 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id ca18e2360f4ac-7d9c78d7f98so6019639f.2 for <ippm@ietf.org>; Thu, 18 Apr 2024 08:35:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713454545; x=1714059345; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=r5WAQgrYEHOMV491aoRnOiKC0udtt5i2ThngviJu4wg=; b=DQdz3afSw5yMxZ10ywTrjK5Tjt1pil1ROiCeej0inhXkG6g8rOK4FUBUinVuyzISw7 xYT8qtOg3mb/uzofu4faq0Iaqayr2mcnczaaAdS48hZRztBAM5//OPbyMQnSsPTu3yU9 OCGRcxihld1vYFTOGvNFpo/hP0WLnENnQKZbWzZ1SG0bl1+tWCRccffWUkeg6jR9gtGj dUxXVtRVnm0sH80VOhfXDyExiLdEQstqCmaFt8T/b+UMuY22I9eNdxVrnUYF/pTPw2mK DIOMHXrmv8RUuKd82ucBxGsSx1/wGieyiidFCpALlt06Tw4kIGfh+PBQjXzKGm9QeMEI 34XQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713454545; x=1714059345; h=content-transfer-encoding:cc: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=r5WAQgrYEHOMV491aoRnOiKC0udtt5i2ThngviJu4wg=; b=O1AQZeHd8FPtof9Etp8pfJGgc3+NtpZsMTkpe80wXSmRZJv9rEIXGvwe5nDQmRlTuk 1KP6iwFskaIAdeBsBSk4iN89H1lpWvouPTkOT0mVM8B48vwr3kgmUy1aFCBj/9ZemrDM 1UdA0xCYWY3lIfrQBiqsgflC5YBh3tSdoSGz+ESLdUoy4q6Cp5ggFsOGUxMlONx8aOxq kW/l/Dr+JnMHUleA6aF/Eg+1jqA44rxvHttNd1/Dr9GMJU+tvwDKr6Bj4Lpxv1METSUy C/k9GLhx/HwXEKgnvoSwD3QtymHYLaBgonHKdBrYAC0TsVaXqAtDKIct32sSvaq/1dOo iSLQ==
X-Gm-Message-State: AOJu0Yw2vqnwJajXL2nT+XQKiNsPDqgefAbREWopoSHSCG/Gk56DQJZF C/N0tPtrI5XCITvdJzgANmh+WoQxv8+igO5lLwyZFyWvdJM5TA1cupCXip1vUw2EM1bk/XCYiPQ 1rnI1z6N06yn/yq25tbO+uFaTx+E=
X-Google-Smtp-Source: AGHT+IFPqg/e8v3jyBOVkGKF0D1gKdEkSVQEUEixaOWGIoktlOLvuDEv/CX8PNJo7thLhCTOLpQhGMocTlAHwFpJom4=
X-Received: by 2002:a05:6e02:546:b0:36b:15e0:de18 with SMTP id i6-20020a056e02054600b0036b15e0de18mr3617255ils.0.1713454544976; Thu, 18 Apr 2024 08:35:44 -0700 (PDT)
MIME-Version: 1.0
References: <CABUE3Xkprxs9BFbisYGhbyU8ECGtfXgigRzPvVzRZ2y-ugHqEg@mail.gmail.com> <LV2PR01MB7622C5C42A945A1498817E459F0E2@LV2PR01MB7622.prod.exchangelabs.com>
In-Reply-To: <LV2PR01MB7622C5C42A945A1498817E459F0E2@LV2PR01MB7622.prod.exchangelabs.com>
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Date: Thu, 18 Apr 2024 18:35:33 +0300
Message-ID: <CABUE3Xnk4GrPdeXrZfa87orpcAUtm3QYQjnhdN9_pFiGb3Gvgw@mail.gmail.com>
To: "Overcash, Michael (CCI-Atlanta)" <michael.overcash@cox.com>
Cc: IETF IPPM WG <ippm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/Hh9QZWDgeQuor2WvAFUBfxzcvRc>
Subject: Re: [ippm] [EXTERNAL] Demo: IOAM Ping using ICMPv6 Loopback
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: Thu, 18 Apr 2024 15:35:49 -0000

Hi Michael,

Thanks for the feedback.
ICMPv6 Loopback is generic, so it can return any information collected
along the path.
Specifically, IOAM (RFC 9197) does not support DSCP or ECN in the
currently defined fields.
Regarding collecting the ECN state along the path, there is a
different draft that suggests to do this (see below), and combined
with the ICMPv6 Loopback it can return the per-hop ECN status back to
the sender.
https://datatracker.ietf.org/doc/draft-mzbc-ippm-transit-measurement-option/

Cheers,
Tal.

On Thu, Apr 18, 2024 at 3:44 PM Overcash, Michael (CCI-Atlanta)
<michael.overcash@cox.com> wrote:
>
> Very cool. Can you add an option to display the DSCP value and ECN bits as well? That would be very valuable in troubleshooting issues related to DSCP and/or ECN bleaching.
>
> --
> Michael Overcash
> Cox Technology, CPE Engineering
>
> -----Original Message-----
> From: ippm <ippm-bounces@ietf.org> On Behalf Of Tal Mizrahi
> Sent: Thursday, April 18, 2024 5:09 AM
> To: IETF IPPM WG <ippm@ietf.org>
> Subject: [EXTERNAL] [ippm] Demo: IOAM Ping using ICMPv6 Loopback
>
> 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://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-mcb-intarea-icmpv6-loopback/__;!!Hit2Ag!0auFUzR3u9l5zYXe2X0GPpyX6F7zZ1d6xdKt-2MVX0OJGPeFPyRKNk_Jzv6eexk554ZRuqTpDEWGf-7iY36-pmlln36cEA$
>
> 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://urldefense.com/v3/__https://github.com/talmi/IOAM-Ping-Demo__;!!Hit2Ag!0auFUzR3u9l5zYXe2X0GPpyX6F7zZ1d6xdKt-2MVX0OJGPeFPyRKNk_Jzv6eexk554ZRuqTpDEWGf-7iY36-pmm0hNUoDA$
>
> Feedback about ICMPv6 Loopback and about the Ping demo will be welcome.
>
> Thanks,
> The authors.
>
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/ippm__;!!Hit2Ag!0auFUzR3u9l5zYXe2X0GPpyX6F7zZ1d6xdKt-2MVX0OJGPeFPyRKNk_Jzv6eexk554ZRuqTpDEWGf-7iY36-pmnxFi_Shg$