[IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection

Sebastian Moeller <moeller0@gmx.de> Fri, 16 May 2025 20:11 UTC

Return-Path: <moeller0@gmx.de>
X-Original-To: ipv6@mail2.ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 87566298784B; Fri, 16 May 2025 13:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level:
X-Spam-Status: No, score=-2.545 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmx.de
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QluaGqw3ra3h; Fri, 16 May 2025 13:11:01 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8B2D52987842; Fri, 16 May 2025 13:11:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de; s=s31663417; t=1747426259; x=1748031059; i=moeller0@gmx.de; bh=fzcVish32xRs2cUixuuE8VQ2lyxGTWF8fLUeoGSlZbk=; h=X-UI-Sender-Class:Content-Type:Mime-Version:Subject:From: In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id: References:To:cc:content-transfer-encoding:content-type:date:from: message-id:mime-version:reply-to:subject:to; b=kyq6YZexMlqcKd0kuj4eJMcMZpJSMS5mzJu/jRa5Sb7BSrj1m5Pdcwx2XJUuzK7V NRdknujwpjuCdQofVo6hX9VPtLLn8Q/JiVpVLJ5SBGMkKdE9vgK6lkvii9SyzV2lq 2IKagMPZsloeSqR7EFFAdT6WRcMj3K8ravlSKDWbH3AW2bGRbCU9/sHHopBNfJofc cetyWLz8MfW2Wpod/1FH2F1FnLsgpwQD1nzKaA4jlQUM0TAO3tD2Gr461JNx6kC0y JTmIwWSdeKVwNCbAz1PoRGzHeAiOxA5b9GNQSsvoKnM5h5cki3sE4nECxwY7SSsVU 204HG7o1BX7Rsayl6Q==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from smtpclient.apple ([2.241.154.102]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M26vL-1uHw8g28GP-0035QK; Fri, 16 May 2025 22:10:59 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <MW3PR11MB46996CAB16CE9C43DC8C4DBBDE93A@MW3PR11MB4699.namprd11.prod.outlook.com>
Date: Fri, 16 May 2025 22:10:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6584419-7056-4470-BD4C-B0A087C3A4D3@gmx.de>
References: <DM6PR11MB4692FDDA63996F0D9E216F8CDEB42@DM6PR11MB4692.namprd11.prod.outlook.com> <DM6PR05MB6169533D4A0D97B01A80B2F2AEB42@DM6PR05MB6169.namprd05.prod.outlook.com> <DM6PR11MB4692C14FCA96B02359AC0086DEB42@DM6PR11MB4692.namprd11.prod.outlook.com> <DM6PR05MB6169A7DA793BEA323E99C90EAEB42@DM6PR05MB6169.namprd05.prod.outlook.com> <ABA1B56D-EF4A-4F42-9F29-975403D695B4@gmx.de> <BYAPR05MB6168B18C83EF8CB0BABA0A04AEB22@BYAPR05MB6168.namprd05.prod.outlook.com> <1EDF7F8B-2977-4DEA-8803-F95E8D86926F@gmx.de> <DM6PR05MB61690D71319BB2413CD9D4B6AE852@DM6PR05MB6169.namprd05.prod.outlook.com> <20250425133330.GA2228@unix-ag.uni-kl.de> <DM6PR05MB6169574A992468A290FC6456AE842@DM6PR05MB6169.namprd05.prod.outlook.com> <20250428121644.GA17895@unix-ag.uni-kl.de> <DM6PR05MB61692BECA56AD96D08EAA463AE812@DM6PR05MB6169.namprd05.prod.outlook.com> <DM6PR11MB4692E70EDAA492B3234787D2DE812@DM6PR11MB4692.namprd11.prod.outlook.com> <DM6PR05MB6169453892C64E4368691C5EAE812@DM6PR05MB6169.namprd05.prod.outlook.com> <DM6PR11MB4692504C15EB5D892410E6D4DE812@DM6PR11MB4692.namprd11.prod.outlook.com> <DM6PR11MB4692511EE2434797B0A1E4D1DE832@DM6PR11MB4692.namprd11.prod.outlook.com> <CABUE3XmucsNCG0+77kj2XeuxWDm5hzMKCFZ2tNRfiBn4N98VYg@mail.gmail.com> <CABUE3Xnxy-zQf91sYaWYXxAxqZX9qPs04wRphQmiz0LSPBcTtw@mail.gmail.com> <DM6PR11MB4692E4526F3BD6AF6ED4651FDE90A@DM6PR11MB4692.namprd11.prod.outlook.com> <PH0PR05MB8704E33B623A73C6482C1C9BAE90A@PH0PR05MB8704.namprd05.prod.outlook.com> <DM6PR11MB4692501F3128B5A6350EE90DDE90A@DM6PR11MB4692.namprd11.prod.outlook.com> <PH0PR05MB8704852A8283241DE2D0D1E0AE90A@PH0PR05MB8704.namprd05.prod.outlook.com> <DM6PR11MB4692E6F580A0C086C217F94EDE93A@DM6PR11MB4692.namprd11.prod.outlook.com> <PH0PR05MB870426F5F4F856D7373F8216AE93A@PH0PR05MB8704.namprd05.prod.outlook.com> <MW3PR11MB4699E44ABCF6DA95CBF81F44DE93A@MW3PR11MB4699.namprd11.prod.outlook.com> <PH0PR05MB87042827107C921E354D82B1AE93A@PH0PR05MB8704.namprd05.prod.outlook.com> <MW3PR11MB46996CAB16CE9C43DC8C4DBBDE93A@MW3PR11MB4699.namprd11.prod.outlook.com>
To: "Zafar Ali (zali)" <zali@cisco.com>
X-Mailer: Apple Mail (2.3826.600.51.1.1)
X-Provags-ID: V03:K1:O5T9y1obl93fejsRosMvw+jM1PP6hz/BA8m36gh2LHtl2Yjt85o xmUz7qrkCG5z3vTw1e6+cPKIv7e4G9OxkNjcmsWUo3GCSUnPEeTNyAPIhhQbxfQ+a+Qs2gJ duY/o7r874cV4Gp7OCsa7AGnqiLy4MvAdxjDiNoiRyc2rH+YhEqsfPTcdIW9S10N4QLiIwQ 6NN1VwES3AT3/dbADP/4Q==
UI-OutboundReport: notjunk:1;M01:P0:hYsizdExLCo=;9NuMWO984GmoIm96CULZMl0bfJa HCh+7scMNVGG+IOyQGFPu7EaZkDmMzgB/jaDKF1mJ+5LiFrjxlKlSLFGjUuFfoipHK0JPEiWA IXF5JQHBv8e7RVkXYLaVraVWM2wJiTV4ysKRiuaBkgrvpg29yjFG4EFTa5PPxkIz+p7Sl0L5N RC0eYaqBzTmmbli40hoCVXocMg+EoWvBEzVZQhnOWh4cf4Mok+11QdtT80fTTeCkLMzyjGh+c 8+vOwcTrn38MqMyXN13cHlB+z9uYexU0xL6YEWU4BAxhn7QrnaIWmxM6rX5ADqcqTZj2d5ms3 T2CZ4tqrS6pmGMnklZjAUGUlMuM4R9GxDMn6E6BMlgNNEaxfdgrxdHY1idOAik76s+nJKE+Dr qmd9qLFdwbgfi7LJJqIjxYL0L2mho0LYrKSrxtj+FIyDmlPW/oqBsEqqgqdG8gso/9evbLBVY Z9IRZfmXLIsbq/kS2MD9FlRx6NPntdRy9JT/fyf69tYWTCv5xk0O/vjyqIZZlu4P8rfvoRchQ 5p60FtlXAtWqNap7cRR8ORuh0g4QxZFoABNuo6YUpA9txpLSLY9r+SPL+5CViTWpses3z8I3L rApvwvX5P5aoFzio4QEw1Da/JvWzBSWirNRzRyWZqQZpAKDPUvvfJHEv3farXfUDOpZtd4MTA iTcqdGQCZbduzEtQLFO9ji4AyKexONrg4m1Mfe/h1pWjXQ96MzNi8n7TxgS+/rK3OAIBQjYbS PC//3JNB6KnHDZ96L/ryu16Ss5GFUR9hliMssyFemJB6H3uSzqjoCjA9PJxLHY6QV69OoNjeZ jttSOJ+6Az1n2FaEf+y0UwFR4JnZUMRn6EKIAv7XfGDTbFyQGmFdgvnUJGOlza2g84GAoP+1V lI+aIdTDWw3V9nP3eNoAuWqTRbw8uN9I8KO01XfyzAq3Iv13gfv6n5WZubZ6NgwC+og/qMFVs 4OVCRmA5nQs3KoZicppDyVKJ/89HIROOjRA99OhuocX1PpvqUfWtoAz6Lj6NORuElwjUdRfLZ UMsBkYBUcygxtSVeVtIdSjYPGBlbF7mh5cBRS9R44c3hT+gzyLMz07U2bg8SHxbjvMpkzKyj+ kvRV+5iJeyli313NmpzR09E12LO38hOh6jKJ/+OJu7/8wJw/WmvD5CDVyOumzkqSp8vouhPVu LvxyXBf+6DZ9X93N70zKpIBoKEfyCcRZEhNBt0WILRfHWFsLli989xY0CGEey6qtqFtw+gIKL ghkQM+ccYYK5FFYz77uCZJMA+/SLrSd3PLjs4z6LC7qtA2UR/4f2SnrjdOICRp5UG42H7uLNR KD2dOmkD9L+dPXObZmuvqaL4ZE4lNEpvHIlm++Y4nMVN8IUJwLV2wjqFHyn6vSYDjhxBHQyXG pVCeqZUO9abjr3klWO9EX+7HrFzpio/brpuoBArsGLIWVbP6zdX0jBDdFWHoRaN4z9xjKKLAY sQqyrqhlb5JvKnBvdWUdRwwOw+wh8Lt24P6+yT/xeAJv3j4eJW6G6+6+M326gqV0zZlcWGBjX GeBRwnWghGKdd8noXNJx5LnLTeObfWC0rF0G+yc7RS0BR2leMVueW6nrzmcYVfSE5AfWt+xgI LfbKJu/9nbTyBa2jdkz6KZG/wPj6XXFj5OSHijRQZZ7mXyq7aMW2R558aapA8xT/0eC7VdTaQ lI/9yucQ1379tUpTKimbVQVQ/ArrNloxNCBJ9pSopv1qrPu07PVLqvCXGHAojU88ic0yw0IsT noX/5JiWmUWRVUfPCAyUfx0HIeRygJVe94qDtixAniuviCY6UkxqsY2enLec66QTIVklUkYgw OQrbmWrweGu3+REoik+hWGL7uyUx96UIlrY4S+0hhI6Lr7WLsGtzQO302SjEWRofMBqKcUezF Yk02IFpS/MQyGylhPSDlXjMVhsi3Q09+8eDgzJjGqgaITpJmGme0PhcJT1daxjNP5lj53PLXa x58lFedanvw1NZsKfqBgWDkvEUVaWckIw+74niUvsk1zNgYoP1j/PH+QwawThsIHEAyOFb4+g ztJ8sjmeKZ1izPlnJPj9qTgWmcOC832HfMpM60OCGb0jbEblxmYw8gV05yp2vZrHpIwcQ+Om3 FvE2hn7Z+zt2E7VFoIJeW7Pg2i8Kw6R9/wRJerqLiI5J6GjOulkoVSVCz/DicE4YayYzSh4Hq CMqswkKf3+2oLsqLnVcRp8GUs4lFdND1eYEAdq4l2kOEQowNinH4aC4XxArGO2EgD/6daXP3A iG4Elt0KxM5r5p/s4fujwkqZuE7iVUeHBljmOZpi4o2XSWu19D+keUYGpAFTi1UeAZms01gDr IEuRjTxL7AyycflIhXPqZfnQs4og6eQCmjVuFoOqUECRGynTBdqN5iQc2Q1CzRlpbnd8Hj257 0o5zbpJswa5oOgf6uzDuyLmDceD6wK94COxeyG6AUr+3Af7UH7zgmcwP5l4+H2psEq4Ld2fHu 00Jublt6RpDWohtZUXPiJSCxDpID+3yBxqmHSFm3DeWq4vmp4WDr8ZefVstpcIbNyczUnN7XM JN9bAeup4RE6eV6XIrNYpI4AR8GJDoJugWGCw9PFe8zzOe+go6pR9Nzu9SWf8gYpWOLNALNlt 53z+SbZ3nHgbmpxOSI5Kyq9bGMFoN0YofCF8OVTafMRAY6jvoh1JAvCtVRDROuX51ZtZ+LrOk OW/71am3jGOGDt5G72wyazFiR6dRFuEGg1IgOeUYhCu/oTu1GwB9ND7b3Cb50m/cMH0THJifB fXzin/ap3Rs+Urd/Ri+6sHi30qKRQ0h5M5ax7A6fI1qgieqpCiwm7pqWO/hGkQycWZw/ZU+px rEAlI9oVOwJJcsBftuqycSUtrwtXGCnqT+byYXqQ1rRVLWTUf75Jqbz2evhSB9DUjuf6T2p2G sKGt2DWRrCpUSOS6QPyvTUt+Gy7XLdpWml2YRj/g6qWJf4qy3b0qk/jGcZL/8WlVMyG4nQrws RsYfhL2Haa0fF71g3n8WWNmJIsaPi79+AWuq63gubdAYTA33NHGS7EyrOIwwjEN+c9f0DBc06 +xKa61AI+hzGpe733lqGQmByyZLZ/kZa+VCovszOYNtiYXEWBIN/1GKjJErqlGNVlBxKo+Uyx 3vX2WUDQ86hpACFLJJtysFLRiiI9rvihyC1+w2EBvQmLjAFmwUCs8Xg+hzET8NH9kjxEGiuTO 8YahVRwAJk7vCRDjrlo2ezC2vA3jAPyPSnzo+HiGY+uUNBYGaUQ9jhKFPNr+3FsolOUWbXOwK jpOijiEpWACUs4vT
Message-ID-Hash: 4BU5Z2H57GAS27GFJCS4RBZGSGW24JQP
X-Message-ID-Hash: 4BU5Z2H57GAS27GFJCS4RBZGSGW24JQP
X-MailFrom: moeller0@gmx.de
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
CC: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, 6man Chairs <6man-chairs@ietf.org>, "6man@ietf.org" <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aCNAIpGNihTi3pygCiIKLV7Zj_8>
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 Zafar,


> On 16. May 2025, at 18:18, Zafar Ali (zali) <zali@cisco.com> wrote:
> 
> Hi Ron
>  Given that you agree with the following changes (based on the WG discussion):
>  OLD> The payload of Extended Echo Reply messages MUST NOT be modified by middleboxes.
> NEW> <nothing>
>  Can you please clarify justification for the following text?
> Specifically, I am interested to learn how ICMPv6 Reflection addresses the NAT/ middle box issue.

As far as I can tell it side-steps the issue... what is observed in the wild and described in RFC3022 is that L3/L4 headers in ICMP error message payloads are treated to reverse NAT transformations, this only works because these nodes know to expect the first X octets of a packet starting with an IP header. Attempting to read arbitrary payloads and interpret them as packet headers to treat them to reverse NAT transformation is both costly and has very little utility, so our assumption should be, unless we see data to the opposite, that middleboxes do not do this except for the special cases where the identity of the payload object is unambiguous.... 




>  Additionally, the payload of
>    ICMP error messages such as Destination Unreachable might be modified
>    by middleboxes (e.g. [RFC3022]), whereas ICMPv6 Reflection is
>    intended to reflect parts of the request message as received by the
>    probed node.
>  Thanks
>  Regards … Zafar
>  From: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
> Date: Friday, May 16, 2025 at 10:40 AM
> To: Zafar Ali (zali) <zali@cisco.com>, Zafar Ali (zali) <zali@cisco.com>, Tal Mizrahi <tal.mizrahi.phd@gmail.com>
> Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> Zafar,
>  I will agree to the following change:
>  OLD> The payload of Extended Echo Reply messages MUST NOT be modified by middleboxes.
> NEW> <nothing>
>  However, I don't see the justification for the other deletions you propose. Again, I ask....
>  Do the sentences that you propose deleting make false or misleading statements? Are the not relevant to a discussion of the alternative solution?
>  If the answer to both of these questions is "no", why do they need to be deleted?
>                                                                                 Ron
>          Juniper Business Use OnlyFrom: Zafar Ali (zali)
> Sent: Friday, May 16, 2025 8:59 AM
> To: Ron Bonica; Zafar Ali (zali); Tal Mizrahi
> Cc: Sebastian Moeller; 6man Chairs; 6man@ietf.org; draft-ietf-6man-icmpv6-reflection; Zafar Ali (zali)
> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection  [External Email. Be cautious of content]
>  Hi Ron
>  As per the forked off thread – “Re: Middleboxes [was Comments on draft-ietf-6man-icmpv6-reflection]”, we cannot make normative requirements for middleboxes. Hence, the diffs are needed for apple-to-apple comparison of draft-ietf-6man-icmpv6-reflection and what is supported by existing specifications and implementations.
>  Thanks
>  Regards … Zafar
>  From: Ron Bonica <rbonica@juniper.net>
> Date: Friday, May 16, 2025 at 7:47 AM
> To: Zafar Ali (zali) <zali@cisco.com>, Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org>, Tal Mizrahi <tal.mizrahi.phd@gmail.com>
> Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> Zafar,
>  Do the sentences that you propose deleting make false or misleading statements? Are the not relevant to a discussion of the alternative solution?
>  If the answer to both of these questions is "no", why do they need to be deleted?
>                                                                                                           Ron
>   Juniper Business Use OnlyFrom: Zafar Ali (zali) <zali@cisco.com>
> Sent: Thursday, May 15, 2025 8:06 PM
> To: Ron Bonica <rbonica@juniper.net>; Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org>; Tal Mizrahi <tal.mizrahi.phd@gmail.com>
> Cc: Sebastian Moeller <moeller0@gmx.de>; 6man Chairs <6man-chairs@ietf.org>; 6man@ietf.org <6man@ietf.org>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>; Zafar Ali (zali) <zali@cisco.com>
> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
>  [External Email. Be cautious of content]
>  Hi Ron,
>  Sure; please see in the following:
>  In Section 1:
> Old Text:
>  An alternative approach that could be considered involves the probing
>    node sending a UDP packet with an unused destination port to the
>    probed node, causing the probed node to send an ICMPv6 Destination
>    Unreachable message, which includes "As much of invoking packet as
>    possible without the ICMPv6 packet exceeding the minimum IPv6 MTU"
>    [RFC4443].  The benefit of ICMPv6 Reflection is that it enables the
>    probing node to selectively request specific parts of the request
>    message to be included in the reply.  Additionally, the payload of
>    ICMP error messages such as Destination Unreachable might be modified
>    by middleboxes (e.g. [RFC3022]), whereas ICMPv6 Reflection is
>    intended to reflect parts of the request message as received by the
>    probed node.
>  New Text:
>  An alternative approach that could be considered involves the probing
>    node sending a UDP packet with an unused destination port to the
>    probed node, causing the probed node to send an ICMPv6 Destination
>    Unreachable message, which includes "As much of invoking packet as
>    possible without the ICMPv6 packet exceeding the minimum IPv6 MTU"
>    [RFC4443].  The benefit of ICMPv6 Reflection is that it enables the
>    probing node to selectively request specific parts of the request
>    message to be included in the reply. 
>  In section 4:
>  Old Text:
>  It should be noted that while some middleboxes might alter the
>    payload of ICMP error messages, such modifications do not apply to
>    ICMP informational messages, such as Extended Echo Request and Reply.
>    This ensures that the reflected information reaches the probing node
>    exactly as sent by the probed node.  The payload of Extended Echo
>    Reply messages MUST NOT be modified by middleboxes.
>  New Text:
> None (i.e., please remove the old text)
>  Thanks
>  Regards … Zafar
>  From: Ron Bonica <rbonica@juniper.net>
> Date: Thursday, May 15, 2025 at 4:58 PM
> To: Zafar Ali (zali) <zali@cisco.com>, Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org>, Tal Mizrahi <tal.mizrahi.phd@gmail.com>
> Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> Zafar,
>  I am having a hard time following your words. Could you please send your request in the form of old text / new text?
>                                                                     Ron
>   Juniper Business Use OnlyFrom: Zafar Ali (zali) <zali@cisco.com>
> Sent: Thursday, May 15, 2025 4:24 PM
> To: Ron Bonica <rbonica@juniper.net>; Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org>; Tal Mizrahi <tal.mizrahi.phd@gmail.com>
> Cc: Sebastian Moeller <moeller0@gmx.de>; 6man Chairs <6man-chairs@ietf.org>; 6man@ietf.org <6man@ietf.org>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>; Zafar Ali (zali) <zali@cisco.com>
> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
>  [External Email. Be cautious of content]
>  Hi Ron
>  Thanks for your follow up – much appreciated!
>  This comment was related to the normative text related to middleboxes for handing the Extended Echo Reply. Specifically, “The payload of Extended Echo Reply messages (like almost all other payloads) MUST NOT be modified by middleboxes.”
>  Given the thread Bob forked off for the middleboxes, I do not think we can add normative text for Extended Echo Reply messages either. Hence the middleboxes discussion is a moot point.
>  As one of the justifications for the draft-ietf-6man-icmpv6-reflection: the middleboxes (for NAT) manipulate the ICMP error message, can you please update the text in the draft that document the alternative (used today). I.e., can you please remove the following text from the draft:
>  “Additionally, the payload of ICMP error messages such as Destination Unreachable might be modified by middleboxes (e.g. [RFC3022]), whereas ICMPv6 Reflection is intended to reflect parts of the request message as received by the probed node.”
>  Thanks
>  Regards … Zafar
>  From: Ron Bonica <rbonica@juniper.net>
> Date: Thursday, May 15, 2025 at 12:07 PM
> To: Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org>, Tal Mizrahi <tal.mizrahi.phd@gmail.com>
> Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>, Zafar Ali (zali) <zali@cisco.com>
> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> Zafar,
>  I think that it would be best to make the statement that you propose in a separate document. The following are rationale:
>  
>     • I assume that you want the statement to apply to both ICMPv6 and ICMPv4. If so, the statement would be out of scope for the 6man WG. It would have to be made in an INTAREA WG document. 
>     • Draft-ietf-6man-icmpv6-reflection does not rely on or modify ICMP error messages. Therefore, the statement doesn't seem relevant to the rest of the document.
>  Furthermore,  Section 4.3 of RFC 3022 says:
>    "Changes to ICMP error message ([ICMP]) will include changes to IP and
>   ICMP headers on the outer layer as well as changes to headers of the
>   packet embedded within the ICMP-error message payload."
>  
> RFC 5508 is consistent with RFC  3022.
>  
> Do we really want to contradict or UPDATE RFCs 3022 and 5508 from this document? If so, would be overstepping the charter of the WG.
>  
> The chairs may want to weigh in.
>  
>                                                                                    Ron
>  
>  
>  
>   Juniper Business Use OnlyFrom: Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org>
> Sent: Thursday, May 15, 2025 12:47 AM
> To: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
> Cc: Ron Bonica <rbonica@juniper.net>; Ron Bonica <rbonica@juniper.net>; Sebastian Moeller <moeller0@gmx.de>; 6man Chairs <6man-chairs@ietf.org>; 6man@ietf.org <6man@ietf.org>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>; Zafar Ali (zali) <zali@cisco.com>
> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
>  [External Email. Be cautious of content]
>  Hi Tal, Ron, et al.  
>  The suggested text looks fine to me.
>  I have one question regarding the following text.
> “The payload of Extended Echo
>    Reply messages MUST NOT be modified by middleboxes.”
>  While we are at this, can you please also document that the middleboxes should not modify the payload of the ICMP error messages, as well.
>  Thanks
>  Regards … Zafar
>  From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
> Date: Thursday, May 15, 2025 at 12:33 AM
> To: Zafar Ali (zali) <zali@cisco.com>
> Cc: Ron Bonica <rbonica@juniper.net>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org<6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> Hi Zafar,
> 
> A kind reminder: would you say that the text below addresses your main
> comment from WG last call, and if the answer is no, how would you
> suggest to rephrase the text?
> 
> Thanks,
> Tal.
> 
> On Mon, May 12, 2025 at 6:48 PM Tal Mizrahi <tal.mizrahi.phd@gmail.com> wrote:
> >
> > Hi Zafar,
> >
> > Many thanks for the feedback.
> > I re-read all your comments from working group last call, and I
> > believe the following comment you sent summarizes them (correct me if
> > I am wrong):
> > "the main point is that adding description of the use of existing
> > tools and compare it with reflection functionality will help the
> > reading of draft-ietf-6man-icmpv6-reflection"
> >
> > In order to address this comment we added a description of the UDP
> > probe and ICMP error message (quoted at the end of this message).
> >
> > Would you say that the new text addresses your feedback about
> > describing existing tools and comparing them to ICMP reflection? If
> > the answer is no, how would you suggest to change this text?
> >
> > Cheers,
> > Tal.
> >
> > Quoting the new text from draft-ietf-6man-icmpv6-reflection:
> >
> >    An alternative approach that could be considered involves the probing
> >    node sending a UDP packet with an unused destination port to the
> >    probed node, causing the probed node to send an ICMPv6 Destination
> >    Unreachable message, which includes "As much of invoking packet as
> >    possible without the ICMPv6 packet exceeding the minimum IPv6 MTU"
> >    [RFC4443].  The benefit of ICMPv6 Reflection is that it enables the
> >    probing node to selectively request specific parts of the request
> >    message to be included in the reply.  Additionally, the payload of
> >    ICMP error messages such as Destination Unreachable might be modified
> >    by middleboxes (e.g. [RFC3022]), whereas ICMPv6 Reflection is
> >    intended to reflect parts of the request message as received by the
> >    probed node.
> >
> >
> >
> > On Wed, Apr 30, 2025 at 4:33 PM Zafar Ali (zali) <zali@cisco.com> wrote:
> > >
> > > Hi Ron,
> > >
> > >
> > >
> > > I also do not see how text in your draft can influence the middle boxes.
> > >
> > > Hence, the gain against sending UDP probes to an unused destination remains:
> > >
> > > Only about requesting “specific” parts of the invoking packet vs. copy of the (as much as possible) invoking packet.
> > >
> > > Can you please document, accordingly.
> > >
> > >
> > >
> > > Thanks
> > >
> > >
> > >
> > > Regards … Zafar
> > >
> > >
> > >
> > > From: Zafar Ali (zali) <zali@cisco.com>
> > > Date: Monday, April 28, 2025 at 8:34 PM
> > > To: Ron Bonica <rbonica@juniper.net>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Erik Auerswald <auerswal@unix-ag.uni-kl.de>
> > > Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>, Zafar Ali (zali) <zali@cisco.com>
> > > Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> > >
> > > Hi Ron
> > >
> > >
> > >
> > > I think this is not a big limitation.
> > >
> > > When someone is running a traceroute outside of a limited domain, in which NAT is deployed, having some address mapping done on the invoking packet can be reasoned. I would suggest the limitation with the specifics.
> > >
> > >
> > >
> > > Thanks
> > >
> > >
> > >
> > > Regards … Zafar
> > >
> > >
> > >
> > > From: Ron Bonica <rbonica@juniper.net>
> > > Date: Monday, April 28, 2025 at 2:30 PM
> > > To: Zafar Ali (zali) <zali@cisco.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Erik Auerswald <auerswal@unix-ag.uni-kl.de>
> > > Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
> > > Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> > >
> > > Zafar,
> > >
> > >
> > >
> > > If we were to do this, would we need to add a note that saying that the utility may yield unreliable results when run outside of a limited domain, in which NATs are known to be absent? SHOULD we add a note saying that running the utility outside of such a limited domain is NOT RECOMMENDED?
> > >
> > >
> > >
> > >                                                                                                            Ron
> > >
> > >
> > >
> > > Juniper Business Use Only
> > >
> > > ________________________________
> > >
> > > From: Zafar Ali (zali) <zali@cisco.com>
> > > Sent: Monday, April 28, 2025 12:17 PM
> > > To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; Erik Auerswald <auerswal@unix-ag.uni-kl.de>
> > > Cc: Sebastian Moeller <moeller0@gmx.de>; 6man Chairs <6man-chairs@ietf.org>; 6man@ietf.org <6man@ietf.org>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>; Zafar Ali (zali) <zali@cisco.com>
> > > Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> > >
> > >
> > >
> > > [External Email. Be cautious of content]
> > >
> > >
> > >
> > > Hi Ron
> > >
> > >
> > >
> > > Documenting "traceroute method" as an alternative to ICMPv6 reflection's core functionality with the NAT specifics would be the right thing to do (given large set of implementations).
> > >
> > >
> > >
> > > Thanks
> > >
> > >
> > >
> > > Regards … Zafar
> > >
> > >
> > >
> > > From: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
> > > Date: Monday, April 28, 2025 at 9:41 AM
> > > To: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
> > > Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
> > > Subject: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> > >
> > > Erik,
> > >
> > >
> > >
> > > Thanks for this good research.
> > >
> > >
> > >
> > > You say, "For IPv6, as long as no NAT is involved, the "traceroute method" seems promising as an alternative to ICMPv6 reflection's core functionality. NAT66 would most likely affect this negatively." I think that this statement is absolutely correct.
> > >
> > >
> > >
> > > But how does the user know if NAT is involved? Given that the user cannot know this, I conclude that ICMPv6 Reflection is the best solution. While it requires more work than the "traceroute method", its results are more reliable.
> > >
> > >
> > >
> > >                                                        Ron
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Juniper Business Use Only
> > >
> > > ________________________________
> > >
> > > From: Erik Auerswald
> > > Sent: Monday, April 28, 2025 8:16 AM
> > > To: Ron Bonica
> > > Cc: Sebastian Moeller; 6man Chairs; 6man@ietf.org; draft-ietf-6man-icmpv6-reflection
> > > Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
> > >
> > >
> > >
> > > [External Email. Be cautious of content]
> > >
> > >
> > > Hi Ron,
> > >
> > > On Fri, Apr 25, 2025 at 05:00:40PM +0000, Ron Bonica wrote:
> > > > [...]
> > > > I have also done some research with a popular platform. I found that:
> > > >
> > > >   * It complies with RFC 792 and 4443 regarding the number of bytes
> > > >     in the invoking packet field.
> > > >   * It does not modify the invoking packet field.
> > > >
> > > > However, your finding that a LINUX-based NAT box modifies the invoking
> > > > packet field is significant. [...]
> > >
> > > RFC 5508[1] (NAT Behavioral Requirements for ICMP), currently BCP 148,
> > > requires NAT to modify the embedded packet's addresses according to the
> > > matching NAT mapping that is also used to translate the ICMP packet's
> > > addresses (REQ-4 and REQ-5).
> > >
> > > Section 5.3 of RFC 6145[2] (IP/ICMP Translation Algorithm) also describes
> > > the translation of the invoking packet (called "packet in error").
> > >
> > > RFC 6296[3] (IPv6-to-IPv6 Network Prefix Translation) does not describe
> > > translation of ICMPv6 error messages.
> > >
> > > If I were to speculate, I would expect NAT66 to also translate invoking
> > > packet field addresses, if not now, then after deployment experience.
> > >
> > > Section 3.8 of the expired Internet-Draft
> > > draft-bctb-6man-rfc6296-bis-02[4] (RFC 6296bis IPv6-to-IPv6 Network
> > > Prefix Translation) requires translation of the invoking packet field:
> > >
> > >    "For an ICMPv6 error, both the addresses in the outer IPv6 header
> > >     and the embedded IPv6 header in the ICMPv6 error message must be
> > >     translated."
> > >
> > > For IPv6, as long as no NAT is involved, the "traceroute method" seems
> > > promising as an alternative to ICMPv6 reflection's core functionality.
> > > NAT66 would most likely affect this negatively.
> > >
> > > ICMPv6 reflection does not address IPv4, but the "traceroute method"
> > > seems to be more limited for IPv4, because (1) RFC 792 specifies that
> > > only the IP (version 4) header and the 8 bytes following this header
> > > are included in ICMP error messages, and (2) NAT44 is prevalent.
> > >
> > > > [...]
> > >
> > > Best regards,
> > > Erik
> > >
> > > [1]: https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc5508__;!!NEt6yMaO-gk!EXQDayNijAz4qi0p1B4eh1p_gAylhXnL4qkhOdZeJneujeEno1k8DLAe8lhRjG-KKSoefsH9Ii8VZg3I7xhaKVw6FEg$
> > > [2]: https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc6145*section-5.3__;Iw!!NEt6yMaO-gk!EXQDayNijAz4qi0p1B4eh1p_gAylhXnL4qkhOdZeJneujeEno1k8DLAe8lhRjG-KKSoefsH9Ii8VZg3I7xhakGJfyO8$
> > > [3]: https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc6296__;!!NEt6yMaO-gk!EXQDayNijAz4qi0p1B4eh1p_gAylhXnL4qkhOdZeJneujeEno1k8DLAe8lhRjG-KKSoefsH9Ii8VZg3I7xhaKxV-p-A$
> > > [4]: https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-bctb-6man-rfc6296-bis-02.html*name-icmpv6-error-forwarding__;Iw!!NEt6yMaO-gk!EXQDayNijAz4qi0p1B4eh1p_gAylhXnL4qkhOdZeJneujeEno1k8DLAe8lhRjG-KKSoefsH9Ii8VZg3I7xhabcv-pZk$