[IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
Bob Hinden <bob.hinden@gmail.com> Fri, 16 May 2025 18:29 UTC
Return-Path: <bob.hinden@gmail.com>
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 3FFD3297F5FA; Fri, 16 May 2025 11:29:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.com
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 4AhPrjf96kwS; Fri, 16 May 2025 11:29:52 -0700 (PDT)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 517CC297F5E7; Fri, 16 May 2025 11:29:52 -0700 (PDT)
Received: by mail-pf1-x42a.google.com with SMTP id d2e1a72fcca58-7424ccbef4eso2700349b3a.2; Fri, 16 May 2025 11:29:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1747420191; x=1748024991; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=2fD5ZopeLIzyMe4YGeuBhMrs5vUUKTbAgzmL53VvFB8=; b=ChOmmWH2WuqUUJM9d2jsp7WHEr2OlDb4QP35pbpy5+eMa1ISN/Vs3g1WruYXR3Fp83 BcQjWq/D1wYxs6eSR8nc3PAbjCNVUTr1wnqBLaTTvLA2cfqfZTXRy2KThFSHMnCYy1Mr v9gsJisEOT3iLBbD3WLMb5CKKd+yQbKlUUt26OwPDi0KPmzBT9zY8fdmMR/Yq6K2mCd1 f2SEOHbBYkiHNTB0LajniTFlGfYvxX4ab5/ZsnsEumjz4ouYvBVNSK/KNt1ylNZccJ+s bTdsfYZcqcIEmQ0/1gqIJ7nCGqDxBXwAPLIBtTtnWuU89t1j1xzHg/BZWwVaLbFKenIk 5EzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747420191; x=1748024991; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=2fD5ZopeLIzyMe4YGeuBhMrs5vUUKTbAgzmL53VvFB8=; b=U5q67YMfQxU1HGDnyEB4g/fN1U+rPM0Y4CM7tUso7vgFjZXnhYq67Jb8+BnoI/KuXZ EV0wHH3tb6nwx0xmsQhNeErMHTHQd48cIcv3LeEq9/vOW6hBVUz5Zu5a9MtVyzeXuXj0 O7nnM3woNBqJVlSfpLXZox7NjwAWqjnT5nGH/AvN6JRlGbJOGpxpbXSQS69rl4mUwDKZ BvPRQ8S+KvmdCgsesy2H50mWBHdhlmK6a2C6EqDwDD5BXbtbWANT0okHhLOa0LrlSEDm FEeE2Nd+KsuaR5wHhC1wrJ/MN4QNn4R5xO80x7tAWd0gcymjSvNU/rbS5h1mbxwwTQLp wEaA==
X-Forwarded-Encrypted: i=1; AJvYcCVTfknDW2o6w21rDbbNlpJzwD/C6EBfG/dvNQtFbCDQmaQ69mWD8gZTPKZB6GP75x2DvCsGlsiAi2eFdg==@ietf.org, AJvYcCVwPXZ9hDzrPhhndRaR3hEpD4w3Ah2t4cPm6BgSkSTaUN8rX5YuVxawPBPL/JtyznMcHobVgcR7RZoUGgiAiI/TqzLOW6NeVng1HrhCGrWaLNEG@ietf.org, AJvYcCWv9jZn/ttuqA66RXV8GbgpxICZctQhjBAS54iO/4spEk6IuGUdeRTexTAfbvrqLvWXMPzFFg==@ietf.org
X-Gm-Message-State: AOJu0YzSIwkx5FreZ4uWNXePcULClaGLis/MEEjVXonJGMUYzlTUZFro FOEwD6xx8rELyHmI3d76fvkVHR7T8i79sCok6JmQniJlNT9KtbKBYUHI
X-Gm-Gg: ASbGncsRnn2svGizFMYZEidAOdtJIy/12IO6+DqSBB7g0bujNGHYfoz9JqTqYiKy/md BaSkwFvkMKVj6cQay4KEy90/t5hkqORlD40KRdBXhgJ2loPLxEY2ICMJX2bh5tc88f2S9beppPs AwNDNsNncmwCyCfSLj+5fEkikhpVwIAxAr3dUqdF3Ur7OObpRleIz0EGd0nNUo0jn6u3w4QWs6S ++XMucWccoH4Fj0NWMRXGx91+WO5aBrJVhFzJou7+2AB9So7sZVzUiz1X3UQF+SVvdTlMN/LM0i P2j9669GerLa2ZM8FtdS2uTl5jF3IMOWBUbkSMxItNlEkM+PJpv8jGkE526dfrnZbQ0Ye6i32h9 JvYeF
X-Google-Smtp-Source: AGHT+IGf4qk2ydaT/b3vz7ZVIVfs9jlrQ3+QoQVozh2UFN8DNoH1F2M7lIGrTvT4GKHTLjf2SkOHMg==
X-Received: by 2002:a05:6a21:999c:b0:215:f6ab:cf77 with SMTP id adf61e73a8af0-216219359aemr5993534637.23.1747420191056; Fri, 16 May 2025 11:29:51 -0700 (PDT)
Received: from smtpclient.apple ([2600:1700:4383:c05f:ec92:227a:3f38:72f2]) by smtp.gmail.com with ESMTPSA id 41be03b00d2f7-b26eaf5c6bbsm1906890a12.6.2025.05.16.11.29.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 May 2025 11:29:50 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <71D6F2FB-4F75-4F21-9D1F-C5BA83A4DEFC@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F5D3B9EF-AC41-4346-BFD8-355BD2660D17"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
Date: Fri, 16 May 2025 11:29:28 -0700
In-Reply-To: <PH0PR05MB87047FDBD9B268569BC80815AE93A@PH0PR05MB8704.namprd05.prod.outlook.com>
To: Ron Bonica <rbonica@juniper.net>
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> <CB3EACA3-D34D-4477-921F-8F1EAFEAB950@gmx.de> <PH0PR05MB87047FDBD9B268569BC80815AE93A@PH0PR05MB8704.namprd05.prod.outlook.com>
X-Mailer: Apple Mail (2.3826.500.181.1.5)
Message-ID-Hash: QZVGG43FAGPL3OX2VJKU3YG5MIQO6BVG
X-Message-ID-Hash: QZVGG43FAGPL3OX2VJKU3YG5MIQO6BVG
X-MailFrom: bob.hinden@gmail.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
CC: Bob Hinden <bob.hinden@gmail.com>, Sebastian Moeller <moeller0@gmx.de>, "Zafar Ali (zali)" <zali=40cisco.com@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/5hfiFW7BvSQ2kNMQ0q8JzYRgUcg>
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>
Ron, > On May 16, 2025, at 10:46 AM, Ron Bonica <rbonica@juniper.net> wrote: > > Sebastian, > > In the past, 6man has levied requirements on middle boxes. For example, RFC 8200 says: To be clear, RFC8200 does not make any mention of middle boxes. Just IPv6 Nodes and Routers. Bob > "The third-highest-order bit of the Option Type specifies whether or > not the Option Data of that option can change en route to the > packet's final destination. When an Authentication header is present > in the packet, for any option whose data may change en route, its > entire Option Data field must be treated as zero-valued octets when > computing or verifying the packet's authenticating value. > > 0 - Option Data does not change en route > 1 - Option Data may change en route". > > Granted, this rule was not limited to middle boxes. It was intended for all IPv6 devices. But it does resemble the requirement that I just agreed to remove. > > Ron > > > Juniper Business Use Only > > From: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>> > Sent: Friday, May 16, 2025 12:16 PM > To: Zafar Ali (zali) <zali@cisco.com <mailto:zali@cisco.com>> > Cc: Ron Bonica <rbonica@juniper.net <mailto:rbonica@juniper.net>>; Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org <mailto:zali=40cisco.com@dmarc.ietf.org>>; Tal Mizrahi <tal.mizrahi.phd@gmail.com <mailto:tal.mizrahi.phd@gmail.com>>; 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>; 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto:draft-ietf-6man-icmpv6-reflection@ietf.org>> > Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection > > [External Email. Be cautious of content] > > > Hi Zafar, > > > > On 16. May 2025, at 14:59, Zafar Ali (zali) <zali@cisco.com <mailto:zali@cisco.com>> wrote: > > > > 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. > > I might be naive here, but why? > > Consider RFC3168, which among other things states: > > A router > MUST NOT set CE instead of dropping a packet when the drop that would > occur is caused by reasons other than congestion or the desire to > indicate incipient congestion to end nodes (e.g., a diffserv edge > node may be configured to unconditionally drop certain classes of > traffic to prevent them from entering its diffserv domain). > > This is clearly setting normative requirements on middleboxes. So I think there is precedent for doing so. I note we can not actually police this or even reliably detect whether routers actually do this. Now, we might not want to make normative requirements for middleboxes, that has the same effect but is different from us not being able to do so. > Note, for what it is worth, I am fine with removing that sentence from the draft, I am trying to understand what the IETF's consistent position should be on this. > > Regards > Sebastian > > > 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 <mailto:rbonica@juniper.net>> > > Date: Friday, May 16, 2025 at 7:47 AM > > To: Zafar Ali (zali) <zali@cisco.com <mailto:zali@cisco.com>>, Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org <mailto:zali=40cisco.com@dmarc.ietf.org>>, Tal Mizrahi <tal.mizrahi.phd@gmail.com <mailto:tal.mizrahi.phd@gmail.com>> > > Cc: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>, 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>, 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto: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 <mailto:zali@cisco.com>> > > Sent: Thursday, May 15, 2025 8:06 PM > > To: Ron Bonica <rbonica@juniper.net <mailto:rbonica@juniper.net>>; Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org <mailto:zali=40cisco.com@dmarc.ietf.org>>; Tal Mizrahi <tal.mizrahi.phd@gmail.com <mailto:tal.mizrahi.phd@gmail.com>> > > Cc: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>; 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>; 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto:draft-ietf-6man-icmpv6-reflection@ietf.org>>; Zafar Ali (zali) <zali@cisco.com <mailto: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 <mailto:rbonica@juniper.net>> > > Date: Thursday, May 15, 2025 at 4:58 PM > > To: Zafar Ali (zali) <zali@cisco.com <mailto:zali@cisco.com>>, Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org <mailto:zali=40cisco.com@dmarc.ietf.org>>, Tal Mizrahi <tal.mizrahi.phd@gmail.com <mailto:tal.mizrahi.phd@gmail.com>> > > Cc: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>, 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>, 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto: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 <mailto:zali@cisco.com>> > > Sent: Thursday, May 15, 2025 4:24 PM > > To: Ron Bonica <rbonica@juniper.net <mailto:rbonica@juniper.net>>; Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org <mailto:zali=40cisco.com@dmarc.ietf.org>>; Tal Mizrahi <tal.mizrahi.phd@gmail.com <mailto:tal.mizrahi.phd@gmail.com>> > > Cc: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>; 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>; 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto:draft-ietf-6man-icmpv6-reflection@ietf.org>>; Zafar Ali (zali) <zali@cisco.com <mailto: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 <mailto:rbonica@juniper.net>> > > Date: Thursday, May 15, 2025 at 12:07 PM > > To: Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org <mailto:zali=40cisco.com@dmarc.ietf.org>>, Tal Mizrahi <tal.mizrahi.phd@gmail.com <mailto:tal.mizrahi.phd@gmail.com>> > > Cc: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>, 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>, 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto:draft-ietf-6man-icmpv6-reflection@ietf.org>>, Zafar Ali (zali) <zali@cisco.com <mailto: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 <mailto:zali=40cisco.com@dmarc.ietf.org>> > > Sent: Thursday, May 15, 2025 12:47 AM > > To: Tal Mizrahi <tal.mizrahi.phd@gmail.com <mailto:tal.mizrahi.phd@gmail.com>> > > Cc: Ron Bonica <rbonica@juniper.net <mailto:rbonica@juniper.net>>; Ron Bonica <rbonica@juniper.net <mailto:rbonica@juniper.net>>; Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>; 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>; 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto:draft-ietf-6man-icmpv6-reflection@ietf.org>>; Zafar Ali (zali) <zali@cisco.com <mailto: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 <mailto:tal.mizrahi.phd@gmail.com>> > > Date: Thursday, May 15, 2025 at 12:33 AM > > To: Zafar Ali (zali) <zali@cisco.com <mailto:zali@cisco.com>> > > Cc: Ron Bonica <rbonica@juniper.net <mailto:rbonica@juniper.net>>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org <mailto:rbonica=40juniper.net@dmarc.ietf.org>>, Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>, 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>, 6man@ietf.org <mailto:6man@ietf.org><6man@ietf.org <mailto:6man@ietf.org>>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto: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 <mailto: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 <mailto: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 <mailto:zali@cisco.com>> > > > > Date: Monday, April 28, 2025 at 8:34 PM > > > > To: Ron Bonica <rbonica@juniper.net <mailto:rbonica@juniper.net>>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org <mailto:rbonica=40juniper.net@dmarc.ietf.org>>, Erik Auerswald <auerswal@unix-ag.uni-kl.de <mailto:auerswal@unix-ag.uni-kl.de>> > > > > Cc: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>, 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>, 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto:draft-ietf-6man-icmpv6-reflection@ietf.org>>, Zafar Ali (zali) <zali@cisco.com <mailto: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 <mailto:rbonica@juniper.net>> > > > > Date: Monday, April 28, 2025 at 2:30 PM > > > > To: Zafar Ali (zali) <zali@cisco.com <mailto:zali@cisco.com>>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org <mailto:rbonica=40juniper.net@dmarc.ietf.org>>, Erik Auerswald <auerswal@unix-ag.uni-kl.de <mailto:auerswal@unix-ag.uni-kl.de>> > > > > Cc: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>, 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>, 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto: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 <mailto:zali@cisco.com>> > > > > Sent: Monday, April 28, 2025 12:17 PM > > > > To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org <mailto:rbonica=40juniper.net@dmarc.ietf.org>>; Erik Auerswald <auerswal@unix-ag.uni-kl.de <mailto:auerswal@unix-ag.uni-kl.de>> > > > > Cc: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>; 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>; 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto:draft-ietf-6man-icmpv6-reflection@ietf.org>>; Zafar Ali (zali) <zali@cisco.com <mailto: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 <mailto:rbonica=40juniper.net@dmarc.ietf.org>> > > > > Date: Monday, April 28, 2025 at 9:41 AM > > > > To: Erik Auerswald <auerswal@unix-ag.uni-kl.de <mailto:auerswal@unix-ag.uni-kl.de>> > > > > Cc: Sebastian Moeller <moeller0@gmx.de <mailto:moeller0@gmx.de>>, 6man Chairs <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>, 6man@ietf.org <mailto:6man@ietf.org> <6man@ietf.org <mailto:6man@ietf.org>>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org <mailto: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 <mailto: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$
- [IPv6]Comments on draft-ietf-6man-icmpv6-reflecti… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Sebastian Moeller
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Sebastian Moeller
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Erik Auerswald
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Erik Auerswald
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Erik Auerswald
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Tal Mizrahi
- [IPv6]回复:Re: Comments on draft-ietf-6man-icmpv6-r… Xiaoming He
- [IPv6]Re: 回复:Re: Comments on draft-ietf-6man-icmp… xiao.min2
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Tal Mizrahi
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Sebastian Moeller
- [IPv6]Middleboxes [was Comments on draft-ietf-6ma… Bob Hinden
- [IPv6]Re: Middleboxes [was Comments on draft-ietf… Zafar Ali (zali)
- [IPv6]Re: Middleboxes [was Comments on draft-ietf… Bob Hinden
- [IPv6]Re: Middleboxes [was Comments on draft-ietf… Sebastian Moeller
- [IPv6]Re: Middleboxes [was Comments on draft-ietf… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Sebastian Moeller
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Tal Mizrahi
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Sebastian Moeller
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Sebastian Moeller
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Bob Hinden
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Sebastian Moeller
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Sebastian Moeller
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Sebastian Moeller
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Erik Auerswald
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Zafar Ali (zali)
- [IPv6]Re: Comments on draft-ietf-6man-icmpv6-refl… Ron Bonica