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

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$