IETF Logo Mail Archive

[IPv6]Re: ICMPv6 Loopback Draft - New Version

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Thu, 27 June 2024 09:22 UTC

Return-Path: <giuseppe.fioccola@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC331C14F6B0; Thu, 27 Jun 2024 02:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham 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 3dfX-ojzTvBZ; Thu, 27 Jun 2024 02:22:39 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E835CC14F6AB; Thu, 27 Jun 2024 02:22:38 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4W8tN56Zr7z6K9X4; Thu, 27 Jun 2024 17:20:53 +0800 (CST)
Received: from frapeml500006.china.huawei.com (unknown [7.182.85.219]) by mail.maildlp.com (Postfix) with ESMTPS id 3136E1400D1; Thu, 27 Jun 2024 17:22:37 +0800 (CST)
Received: from frapeml500006.china.huawei.com (7.182.85.219) by frapeml500006.china.huawei.com (7.182.85.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 27 Jun 2024 11:22:37 +0200
Received: from frapeml500006.china.huawei.com ([7.182.85.219]) by frapeml500006.china.huawei.com ([7.182.85.219]) with mapi id 15.01.2507.039; Thu, 27 Jun 2024 11:22:36 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Tal Mizrahi <tal.mizrahi.phd@gmail.com>, 6man <ipv6@ietf.org>, IETF IPPM WG <ippm@ietf.org>
Thread-Topic: [IPv6]ICMPv6 Loopback Draft - New Version
Thread-Index: AQHatlCv+jwY7oSReE+MYKTRve2HILHZ9VkA
Date: Thu, 27 Jun 2024 09:22:36 +0000
Message-ID: <343f0c2198ca4593b6ca42d38c3a6d21@huawei.com>
References: <CABUE3X=Avf-gOODiQJasC_a1dRuS-+kWO7LeDBZWssi6q9Q8Zg@mail.gmail.com>
In-Reply-To: <CABUE3X=Avf-gOODiQJasC_a1dRuS-+kWO7LeDBZWssi6q9Q8Zg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.205.25]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Message-ID-Hash: GWGG7O5RNIJ2BJG6NZBQUAMEHD46K6WD
X-Message-ID-Hash: GWGG7O5RNIJ2BJG6NZBQUAMEHD46K6WD
X-MailFrom: giuseppe.fioccola@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.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: [IPv6]Re: ICMPv6 Loopback Draft - New Version
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gqI2MtY7ikOt6QS2pElcL_93vkA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>

Hi Tal,
I have read the document and I think that the ICMPv6 Loopback can have relevant diagnostic applications.
I suggest to add a section in the draft to describe application scenarios related to the possible active measurements. In this regard, I would also explain the relation with draft-gandhi-ippm-stamp-ext-hdr.
Let me also point out a new draft about on-path active measurements (draft-fioccola-ippm-on-path-active-measurements) and the ICMPv6 Loopback can be an example of how to carry performance data, especially in the case of IOAM.

Regards,

Giuseppe

-----Original Message-----
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com> 
Sent: Tuesday, June 4, 2024 9:26 AM
To: 6man <ipv6@ietf.org>; IETF IPPM WG <ippm@ietf.org>
Subject: [IPv6]ICMPv6 Loopback Draft - New Version

Hi,

We have uploaded a new version of the draft:
https://datatracker.ietf.org/doc/draft-mzbc-ippm-transit-measurement-option/

This version of the draft addresses the amplification issue that was raised about previous versions of the draft.

Please also note that we have a running demo of a utility called ioam-ping which uses ICMPv6 Loopback messages:
https://github.com/talmi/IOAM-Ping-Demo

Comments will be welcome.
Cheers,
Tal.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests:
--------------------------------------------------------------------

v2.28.0 | Report a Bug | By Email | System Status