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

Sebastian Moeller <moeller0@gmx.de> Thu, 10 April 2025 09:50 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 388AC1A17232 for <ipv6@mail2.ietf.org>; Thu, 10 Apr 2025 02:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level:
X-Spam-Status: No, score=-2.547 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_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 84czA3OvG7N5 for <ipv6@mail2.ietf.org>; Thu, 10 Apr 2025 02:50:01 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 431AC1A1722C for <6man@ietf.org>; Thu, 10 Apr 2025 02:50:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de; s=s31663417; t=1744278598; x=1744883398; i=moeller0@gmx.de; bh=gT2tB8V0SAFVGQtMbk0KnEVaTNzgOL71Ab+dFFDHIVA=; 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=KWZxzsOWEvRS/SpiZM7iUpAyUbgORIjtvHcwHH3loBrZ8OBBOwE4u8mYEVsq4uPZ aPgjkcpMeqYfL1taF29ap4jx9s2Fe7jUOETwGFpbsU/SFJxPxW+R7MgudoCeI0ZeV zzfKaookbFkvWypmBmFrqWLWkEG/Ua189zRSiDQhdBZEaR5xHUsznTqgkc8RMrwvr szwCVsO//Vy5/SQEql2ABiMgqXXGQ/42CF6mOvUAmmL7BJO4RIUAdmNdjEA9epb9L zKS6jsjadVG55CRf1YMQy44pO4E1PIh5iy9fHVvhTsL2lxzkmIupR6kT2gNmQyagN 22IrCSGny9XIwTisYQ==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from smtpclient.apple ([77.3.219.42]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MV67y-1taro01Rri-00UL7A; Thu, 10 Apr 2025 11:49:58 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <DM6PR05MB6169A7DA793BEA323E99C90EAEB42@DM6PR05MB6169.namprd05.prod.outlook.com>
Date: Thu, 10 Apr 2025 11:49:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABA1B56D-EF4A-4F42-9F29-975403D695B4@gmx.de>
References: <DM6PR11MB46928702B82E5B577D3E0976DEDB2@DM6PR11MB4692.namprd11.prod.outlook.com> <DM6PR05MB61693FC32AE4621C1DB86171AEDB2@DM6PR05MB6169.namprd05.prod.outlook.com> <DM6PR11MB46921FFD3FB62AFE268C1F39DEAA2@DM6PR11MB4692.namprd11.prod.outlook.com> <DM6PR05MB6169900CD058B46820454A2CAEB42@DM6PR05MB6169.namprd05.prod.outlook.com> <DM6PR11MB4692FDDA63996F0D9E216F8CDEB42@DM6PR11MB4692.namprd11.prod.outlook.com> <DM6PR05MB6169533D4A0D97B01A80B2F2AEB42@DM6PR05MB6169.namprd05.prod.outlook.com> <DM6PR11MB4692C14FCA96B02359AC0086DEB42@DM6PR11MB4692.namprd11.prod.outlook.com> <DM6PR05MB6169A7DA793BEA323E99C90EAEB42@DM6PR05MB6169.namprd05.prod.outlook.com>
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3826.500.181.1.5)
X-Provags-ID: V03:K1:Ahgy8cUhWYpFQhg6G9LUzAghIwy6n/f9299Xndr/jk0cytSaGBw l7MPZAzwL98A1dhurv4CUyLhnuYV8rjqKt2sW82pZCTOZewUIIOYxA2aSVBzoKk4fSJW0tX WHdinF1qF0qRscBOkPzKpSuJ1OPJydtJ0JYkigiG3eKBzbiz+V8jyMfU8n9BHDuUamxOW+U 2BzRSeBdDYoFVF8GEfo/Q==
UI-OutboundReport: notjunk:1;M01:P0:1iTAZiXLrO8=;WqzkRYhNx/ilyj49NVQ5BKZ1tsl hBcax8mofQiJn6296wWzoT0yhRHbPR+MjxDfk58D0eldAR1ljdSLnEVlNar5QQMOEXe4MAuiJ oaklIK4MWCWZgJ6cT1HX+tsrp1eti2J3yUBQq3yoHmfhSKulyqO5+0GAnAlbE5HFgO1D8M4mJ GWG4atv1udIM0nP6hZsLLSp6vjgRwRoDYIoHe4Qt+r3amorZmIp0dbdzifDhxDd4fb559501M Edgtvw841EujVMrozfDK/qFdkinsIhTsW1cnhquiOzBwdLhg8UEO4e9Hu3XuCoQ8Ut6emUFgE rATF5myBDe4uGE+PuK7Si64lwjpMs5bGix03hDjfXffFfm/WRQWeF+IgRjgUHXD8SoID98Kwu /8uWYopQlttsy/RE6Fb5UoXd8kwq3hw9Igi96tkC6JvCtckz5uUAlku1gVbgYmOheYOIxd/YJ XAhX//TlsEcSYfs0rSSPOrDIBpObbg7IxkFvvFGc+k67akOMVZUgKsp9CNKNjEWNSSyIdyrLq P3MeO0Xm0UcmNS3GFBGzkU/Gqbkqri09PwLiM5lsm4Rb75677HSVBqikThWlq20bPWE44vPpZ l9q7rSMmnbkpbPG1X/AE0f3/nVP+o0ndrAElgn8qznDxiH3k6Xbg+enQboe74gGAzW+dLfwMj U1LcIO2j7VE9pPX+2gfotPxt9DtatoAsHZV2ulBXCf2CSZrzo/cF1bLMtIMU4gtM59goOuG6e 0rJa2zaXZbJRNiwgF/dtOsNVo5hpPJAtp5pW1T+s8L755PwJamJvLbx9BiZzQUy2B664vfzE5 3Sus4ZDlCgmeGV4/Mpc5ROcRnUiZVW7G2EVBn3yw8+nyoVPt9Oxo8fvRnBSyrEHRkZAhtydnh sMUqIVUQb+k+ECLJ+M5YkWtEZs3gTme6CPDzXt9uPIosXjhS4foyeMfzJfbqfQ6+BPZUYYueY g3L1cG53FlqFXj/5O5aKEK/F0+Yjn3ngyz+CO7X+qi/pdnShHGUL/ZxD8lcogMhL6sgmUPUDq rg3XIvG+aXj8qfg/mIuVby84rtpMO7hPt9528sgeTuqBPsW862ay/5uy7GRbIqfgME+BM2qGL zSO43EUoaEW6TN+SJFG1ggOhNsl/5tdZk/BhU/61J4JLYIqFMkXWFVWNpfXnTAPzLc27JOiwM R9Rf5cdYtZ8Xnw/7kQDsCBlGRefOvFoPXlxOFA47aNIFZzTUGGfOgHnrzmsviukN0aTlnR8kT 41/lJn9pVlJQ1rN4WrEu35p31zZ0hfL6Vuf3rxp9Q+zLtIQX6hSA8Qdf3dgoyzLtmLmXFDAwb 2dTTMWrPwoaxg4mXwfDXaEGKIxJ8aplX4sEj/xbePKAqhtNP9ov6db2RiFyLd/gMXgQLXSPtl DnWybJwfOlC/FuVhwFhqGY8+7amAn+MdEkV4WXJ6XyCQFZCX7wRrh3BFBeEw97M4Wptx3kzcv rI8lGF9RMQTCGFgJxfiVr9J24segtq6AZfTwSNwqP7KMZ1NEp
Message-ID-Hash: CNUSWXRMVFRLHOBB4LKH5UBGTX3CLJ64
X-Message-ID-Hash: CNUSWXRMVFRLHOBB4LKH5UBGTX3CLJ64
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: "6man@ietf.org" <6man@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/v7JITT8HXsaiPd2yc470jCj5E-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 Ron,


I wonder whether defining an invalid port might not be easier...
That way participating nodes would simply need to reserve one port and not assign it and ICMP destination unreachable error messages would just work, without needing any fancy new reflector software... (in any case a participating node will need to do something, not assigning a service on port X should be possible on most deployed devices)
And I believe proposing such a port would be within the IETFs wheelhouse (and IANA's), no?
There are likely good reasons why this is not a good way forward, I think the draft should explain this as well.


Regards
	Sebastian





> On 9. Apr 2025, at 17:44, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> wrote:
> 
> Zafar,
> 
> I would be glad to include a section called "alternative approach". However, it would have to describe the following flaws of the alternative approach:
> 
>     • Before executing the traceroute, the user needs to identify a path that includes, but does not terminate on, the probed node.
>     • The user will get feedback from every node on the path, whether they want it or not
>     • The procedure will take much longer to execute.
> 
>                                                                 Ron
> 
> Juniper Business Use Only
> From: Zafar Ali (zali) <zali@cisco.com>
> Sent: Wednesday, April 9, 2025 11:04 AM
> To: Ron Bonica <rbonica@juniper.net>
> Cc: 6man@ietf.org <6man@ietf.org>; Zafar Ali (zali) <zali@cisco.com>
> Subject: Re: Comments on draft-ietf-6man-icmpv6-reflection
>  [External Email. Be cautious of content]
> 
> Hi Ron
>  I was thinking:
>     • Include it in introduction to prime the need for reflection (my preference)
>     • Add a section “alternate approach”.
>  Thanks
>  Regards … Zafar
>  From: Ron Bonica <rbonica@juniper.net>
> Date: Wednesday, April 9, 2025 at 10:44 AM
> To: Zafar Ali (zali) <zali@cisco.com>
> Cc: 6man@ietf.org <6man@ietf.org>
> Subject: Re: Comments on draft-ietf-6man-icmpv6-reflection
> Zarar,
>  Would you mind if I included this in a section called "Rejected Approaches" or something like that?
>                                                                         Ron
>  Juniper Business Use OnlyFrom: Zafar Ali (zali) <zali@cisco.com>
> Sent: Wednesday, April 9, 2025 10:19 AM
> To: Ron Bonica <rbonica@juniper.net>
> Cc: 6man@ietf.org <6man@ietf.org>; Zafar Ali (zali) <zali@cisco.com>
> Subject: Re: Comments on draft-ietf-6man-icmpv6-reflection
>  [External Email. Be cautious of content]
>  Hi Ron  Yes – 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 (as per the WGLC comments).
>  Thanks
>  Regards … Zafar
>  From: Ron Bonica <rbonica@juniper.net>
> Date: Wednesday, April 9, 2025 at 10:00 AM
> To: Zafar Ali (zali) <zali@cisco.com>
> Cc: 6man@ietf.org <6man@ietf.org>
> Subject: Re: Comments on draft-ietf-6man-icmpv6-reflection
> Zafar,
>  You say that the traceroute should be addressed to the probed node. But there is the problem.
>  Even if a packet arrives at its destination address with a hop count of 1, its TTL will not expire. The packet will be delivered to an upper-layer protocol on that node.
>  If you want this strategy to work, you need to send the traceroute through a path the includes, but does not terminate on, the probed node.
>                                                            Ron
>   Juniper Business Use OnlyFrom: Zafar Ali (zali) <zali@cisco.com>
> Sent: Tuesday, April 8, 2025 10:35 PM
> To: Ron Bonica <rbonica@juniper.net>
> Cc: 6man@ietf.org <6man@ietf.org>; Zafar Ali (zali) <zali@cisco.com>
> Subject: Re: Comments on draft-ietf-6man-icmpv6-reflection
>  [External Email. Be cautious of content]
>  Hi Ron  Many thanks for your follow-up.
>  As you mentioned, “In an Error Message, the data field represents “as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU”. This is exactly the information that we seek!”
>  You also mentioned, “The following are a few possibilities:”
>     • “Send a packet whose Hop Count expires on the probed node”
> This is the traceroute functionality implementations are using today to what otherwise this draft is addressing.
> Re: But wouldn't this packet have to be addressed to a node other than the probed node?
> You traceroute to the target node/ address.
> You get information about the invoking packet from each hop, including the target node (which is what you are trying to reflect from the target node).
> Re: And how would the probing node know that the probed node is on the path to that node?
> You issue traceroute to what you call “probed node”
> n.b. Honestly in most cases, you want to know how packet appears at each hop for debugging, anyway.
> Thanks
>  Regards … Zafar
>  From: Ron Bonica <rbonica@juniper.net>
> Date: Friday, March 21, 2025 at 11:34 AM
> To: Zafar Ali (zali) <zali@cisco.com>
> Cc: 6man@ietf.org <6man@ietf.org>
> Subject: Re: Comments on draft-ietf-6man-icmpv6-reflection
> Hello Zafar,
>  It's good to hear from you again. Thanks for reading the document and thanks for your comments.
>  I think that a close reading of RFC 4443 might help us to answer your question. RFC 4443 defines the following ICMP message classes:
>  
>     • Error Messages
>     • 
> Informational Messages
> 
>  IPv6 forwarding errors elicit Error Messages. For example, a Hop Count expiration elicits a Time Exceeded message. By contrast, Informational Messages convey network layer information. They are frequently defined as request/response pairs. For example, the Echo Reply message is a response to the Echo Request message.
>  Both Error Messages and Informational Messages contain a data field. In an Error Message, the data field represents “as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU”. This is exactly the information that we seek!
>  In an Informational Message, the data field contains arbitrary data. The arbitrary data is specified in the request and returned in the response.
>  So, the only way to obtain the information that we seek using existing ICMPv6 functionality would be to cause a IPv6 forwarding error on the probed node. The forwarding error elicits an Error Message that contains the information that we seek.
>  It is difficult to reliably cause a forwarding error on the probed node. The following are a few possibilities:
>  
>     • Send a packet to an unused port on the probed node, eliciting a Destination Unreachable message
>         • 
> But how does the probing node know which ports are unused on the probed node?
>     • 
> Send a packet whose Hop Count expires on the probed node
>         • 
> But wouldn't this packet have to be addressed to a node other than the probed node?
>         • 
> And how would the probing node know that the probed node is on the path to that node?
> 
>                                                                                Ron
>     Juniper Business Use OnlyFrom: Zafar Ali (zali) <zali@cisco.com>
> Sent: Friday, March 21, 2025 12:16 AM
> To: Ron Bonica <rbonica@juniper.net>
> Cc: Zafar Ali (zali) <zali@cisco.com>; 6man@ietf.org <6man@ietf.org>
> Subject: Comments on draft-ietf-6man-icmpv6-reflection
>  [External Email. Be cautious of content]
>  Hi Ron
>  Thanks for the presentation.
>  The comments I mentioned that there are implementations that uses contents from the existing ICMP error to get the information you are probing.
> It will be beneficial for you to also document how the goals in the draft can be accomplished using the existing techniques.
> ·         RFC4443 says that ICMP error contains “as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU”. 
> ·         The ingress node parses the copy of the invoking packet to check how packet contents changes hop by hop (using traditional traceroute). 
> ·         The security and local policies aspect remain common between what you presented and this method. 
>  Thanks
>  Regards … Zafar
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> List Info: https://mailman3.ietf.org/mailman3/lists/ipv6@ietf.org/
> --------------------------------------------------------------------