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

Erik Auerswald <auerswal@unix-ag.uni-kl.de> Mon, 28 April 2025 12:16 UTC

Return-Path: <auerswal@unix-ag.uni-kl.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 D304921F8958; Mon, 28 Apr 2025 05:16:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 9UViTNQaoOfF; Mon, 28 Apr 2025 05:16:51 -0700 (PDT)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 7682321F8953; Mon, 28 Apr 2025 05:16:51 -0700 (PDT)
Received: from sushi.unix-ag.uni-kl.de (sushi.unix-ag.uni-kl.de [IPv6:2001:638:208:ef34:0:ff:fe00:65]) by mailgw1.uni-kl.de (8.17.1.9/8.17.1.9/Debian-2+deb12u2) with ESMTPS id 53SCGj5O1333925 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 28 Apr 2025 14:16:45 +0200
Received: from sushi.unix-ag.uni-kl.de (ip6-localhost [IPv6:::1]) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 53SCGjLB020432 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 28 Apr 2025 14:16:45 +0200
Received: (from auerswal@localhost) by sushi.unix-ag.uni-kl.de (8.14.4/8.14.4/Submit) id 53SCGiiV020429; Mon, 28 Apr 2025 14:16:44 +0200
Date: Mon, 28 Apr 2025 14:16:44 +0200
From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: Ron Bonica <rbonica@juniper.net>
Message-ID: <20250428121644.GA17895@unix-ag.uni-kl.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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DM6PR05MB6169574A992468A290FC6456AE842@DM6PR05MB6169.namprd05.prod.outlook.com>
Author: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
Message-ID-Hash: IMPFBKOE2N5GK4AMHVRGAKD3Q6SQDTUS
X-Message-ID-Hash: IMPFBKOE2N5GK4AMHVRGAKD3Q6SQDTUS
X-MailFrom: auerswal@unix-ag.uni-kl.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: 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>
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/oueKI3wd3K_fpRWxjxnic8l75Dg>
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,

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://www.rfc-editor.org/rfc/rfc5508
[2]: https://www.rfc-editor.org/rfc/rfc6145#section-5.3
[3]: https://www.rfc-editor.org/rfc/rfc6296
[4]: https://www.ietf.org/archive/id/draft-bctb-6man-rfc6296-bis-02.html#name-icmpv6-error-forwarding