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

"Zafar Ali (zali)" <zali@cisco.com> Sat, 17 May 2025 13:11 UTC

Return-Path: <zali@cisco.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 8571429B8256; Sat, 17 May 2025 06:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -9.585
X-Spam-Level:
X-Spam-Status: No, score=-9.585 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_NONE=0.001, T_SPF_HELO_PERMERROR=0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cisco.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 8VY1TeWRVvBD; Sat, 17 May 2025 06:11:02 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (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 23F6429B8249; Sat, 17 May 2025 06:11:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.com; i=@cisco.com; l=147564; q=dns/txt; s=iport01; t=1747487462; x=1748697062; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=PAiS6uRpe5bXjMy7+lByB6UbK/WL44khf4bWSSiVd2M=; b=ZiAjr0jtaRzkFKSxgXcqhLWtgDocYhlYWfTNHiaSDnT3zf7KBqnEodEh faPQQFTwb86TNKyoGFLWxtwYE/oe2qo1DTZ8IjXT+rHc2cz6QL6cYTxWx mneODCaQZQ5riulkhVVcSmAY9NfS6Se6CJ+vBPsdDxUb4mRpWCyIml1tp iRQBbvQLfIuv2hJaGdRfe3qOzkggeAk52nXrORzhhfq2nWS8fysBBF86q H9D36EbemIKOnnOlSm3jGwjTC6InWgxnMEVowRNu6eRMhMRiqClmj9zip /+O310fMm0bxo/j5y1yIfeavZtfWVsPx/NvDm6EqUbUakwj0/lZP4S5nc Q==;
X-CSE-ConnectionGUID: Vfzgh+ElRAaOBNdA6JDFbQ==
X-CSE-MsgGUID: SNFxOK8mQOmXeN3uRYYxkA==
X-IPAS-Result: A0ADAAAsiiho/5T/Ja1aGQEBAQEBAQEBAQEBAQEBAQEBARIBAQEBAQEBAQEBAQFlgRoEAQEBAQELAYFAMVIHOD+BHEkEhFCDTAOETV+IdgOLZIVkjE4UgREDVg8BAQENAjgZBAEBhQcCFos2AiY0CQ4BAgQBAQEBAwIDAQEBAQEBAQEBAQELAQEFAQEBAgEHBYEOE4V7DYZaAQEBAQMSCAEICjoFCgMQAgEGAg4DAwEBAQEgAQkCAgIeER0IAgQBDQUIEweCYYIcBgEBAQERAzIDARCTYI9dAYFAAooreoEygQHdPQ2CVAaBSQGIMR4BKoEzAg6BdoIJGyCEPCcbgUlEgVeCaD6CH0ICAoEpAQsHASMDAw8IAQeDNDqCLwSBDoEGF0Q+FB2BI4IWToFAgmqBIoMpS4IHWAiBaiuCCicCgTWBTYcDUnUiAyYzLAFVExcLBwWBJhAzAyo0MSNLBS0dgg2CLYJsgg9wbAMDFhCDE3MchGOESitPgySBA3tlQYJ0QAMLbT03Bg4bBQSBNQWVZBwlGoJ7EBMCRgYuBBkZBBQbAxEOAhQMDx4CNhMHJhkBBgYSBQMtAQcOL5JeTYJpSYtWR4NVikCUJHEKhBuBX4o7jzmGMBeEBI0LhwGRZmaXDoFzIoI2iy+EB5FwAoUMAgQCBAUCEAEBBoFoPGlwcBWDIlIZD41/KxmDXoUTwUEBeAIBOQIHAQoBAQMJhkiJU4EdYAEB
IronPort-PHdr: A9a23:1aeWmxwl9vUePhTXCzPsngc9DxPP853uNQITr50/hK0LK+Ko/o/pO wrU4vA+xFPKXICO8/tfkKKWqKHvX2Uc/IyM+G4Pap1CVhIJyI0WkgUsDdTDCBjTJ//xZCt8F 8NHPGI=
IronPort-Data: A9a23:hWmM3azy5VOMpP37zwR6t+czxyrEfRIJ4+MujC+fZmUNrF6WrkUDm GJOXT/TP/mKZDP3c9EjbNi3oBsB7JeBm4AyHAc6+VhgHilAwSbn6Xt1DatR0we6dJCroJdPt p1GAjX4BJlqCCea/lH1b+CJQUBUjcmgXqD7BPPPJhd/TAplTDZJoR94kobVuKYw6TSCK13L4 I6aT/H3Ygf/hmYpaz1MsspvlTs21BjMkGJA1rABTagjUG/2zxE9EJ8ZLKetGHr0KqE8NvK6X evK0Iai9Wrf+Ro3Yvv9+losWhRXKlJ6FVHmZkt+A8BOsDAbzsAB+vpT2M4nVKtio27hc+adZ zl6ncfYpQ8BZsUgkQmGOvVSO3kW0aZuoNcrLZUj2CCe5xWuTpfi/xlhJH84L4IYuctzO0hH0 tY+JBlTTDytjdvjldpXSsE07igiBNPgMIVavjRryivUSK9/B5vCWK7No9Rf2V/chOgXQq2YP JVfM2cyKk2cM3WjOX9PYH46tPWhgnjXeDxDo1XTrq0yi4TW5FAujOmwbIWOIbRmQ+1uuGiIg UGW+l3eByEXEoeC8wu04nGF07qncSTTHdh6+KeD3qBviVvWzWwaCQcNfVq2vff/jVSxM/oBL kUS0isjsaZ081akJvHxRRS2vDuFswISHoRVGut/6QqI0rSKphyUCGwJRSJAb9oOtcIqS3otz FDhoj/yLSZkvLvQTTeW8a2Z6GrrfyMUNmQFIyQDSGPp/uXenW36tTqWJv5LG6+uhdqzEjb1q w1mZgBn71nPpabnD5mGwG0=
IronPort-HdrOrdr: A9a23:zs/1n6+m51zfejAfCc1uk+Gldr1zdoMgy1knxilNoENuA6+lfp GV/MjziyWUtN9IYgBfpTnhAsW9qXO1z+8S3WBjB8bSYOCGghrmEGgM1/qZ/9SNIVybygcZ79 YeT0EcMqy/MbEZt7eG3ODQKb9Jq7f3ktHMuQ6d9QYQcegAUdAY0+4NMHfhLqQAfng/OXNWLu v62uN34xCbVTA8aMO9CnMZX+7FieHqufvdCyIuNloM0iXLqSmnxoLbPnGjsyv2VQkh/Z4StU z+1yDp7KSqtP+2jjXG0XXI0phQkNz9jvNeGc2lkKEuW3XRozftQL4kd6yJvTgzru3qwk0tis PwrxApONk2w2/Nf1uyvQDm12DboXUTAj7ZuB2laEnY0IjErQEBeo18bEViA13kAn8bzZRBOW RwrjukXtRsfEv9dW/Glqj1vllR5zmJSDwZ4K8uZ7g1a/pFVFeXxrZvp399AdMOGjn355sgF/ QrBMbA5OxOeVffdHzBuHJzqebcFEjbMy32CnTqgPblmAR+jTR81Q8V1cYflnAP+NY0TIRF/f 3NNuBtmKtVRsEbYKphDKNZKPHHRlDlUFbJKiafMF7nHKYINzbErIP2+qw84KWvdIYTxJU/lZ zdWBdTtHI0eUjpFcqStac7vyzlUSG4R3Dg28te7592tvn1Q6fqKzSKTBQ0n86ps5wkc4Tmsj aISeRr6tPYXBzT8NxyrnjDcogXLWNbS8EcsMs6XVWVy/i7WLECntarBMruGA==
X-Talos-CUID: 9a23:bY4to2m8U2ms6CjYEYRnrcK0aODXOUPT3njQYGK8M09gb5ezRXbO2o9KmfM7zg==
X-Talos-MUID: 9a23:p5ky9wiUDqeU1BatPERK7cMpD+FG84ONWEU0tpA2tu/fKBZBCieepWHi
X-IronPort-Anti-Spam-Filtered: true
Received: from rcdn-l-core-11.cisco.com ([173.37.255.148]) by alln-iport-5.cisco.com with ESMTP/TLS/TLS_AES_256_GCM_SHA384; 17 May 2025 13:11:00 +0000
Received: from rcdn-opgw-1.cisco.com (rcdn-opgw-1.cisco.com [72.163.7.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by rcdn-l-core-11.cisco.com (Postfix) with ESMTPS id 9CE7D18000163; Sat, 17 May 2025 13:11:00 +0000 (GMT)
X-CSE-ConnectionGUID: hZUyAdKIRRubl6r7qcqnjg==
X-CSE-MsgGUID: +cvc0ZpATru2SXUv7ZdTDg==
Authentication-Results: rcdn-opgw-1.cisco.com; dkim=pass (signature verified) header.i=@cisco.com
X-IronPort-AV: E=Sophos;i="6.15,296,1739836800"; d="scan'208,217";a="29220505"
Received: from mail-mw2nam12lp2042.outbound.protection.outlook.com (HELO NAM12-MW2-obe.outbound.protection.outlook.com) ([104.47.66.42]) by rcdn-opgw-1.cisco.com with ESMTP/TLS/TLS_AES_256_GCM_SHA384; 17 May 2025 13:11:00 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=gzAzVpcffoUHg3kbyczUr+5xpzz/feZIYaBG+DLgj3VYhMK0fRT2iuA1BrQqFOSumKy8sRwS0EzBLn4QCzlwguQjGQJr1WolN98kHvTaVFyRDAyHHdenuXDxuidhMBiOCNkqTTHXJFtV9dpXNoLmJwLjEWWuOrxovZdgoFxpVpQCQjl5cC+/0GLJ4PJYOqhvgMZRyvtmx8gM0ELtIZBXrc5mknQZYQxy271pMtPZNdeoz32d0IOpVfPXN/+CwqybHDC7hjj4y41LKcnvAik+oWVbXxthiGtRV8St5diV42y7Fz1Bvy7Xs3RfgGo+Il73X1pjMwNFrqnwrTn7QIf/vw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=PAiS6uRpe5bXjMy7+lByB6UbK/WL44khf4bWSSiVd2M=; b=emQnkMR7KMn/wMYpcG906IMB0QuFK5LfS1LX0iel3OMvppzSKhrZk1VtSBFFDfmRBc1xDcc69lxf7YBZfHig5/PHgsgF/VgxuYJEtrc7JYv9tfNmQ1Q8kUAoC45eaqmPtQoYWy2qczTxWXkhxoVmF8x02bEgbwCBcnueRyiKlKUEFuPn3bH4YP5f+hkq5/xUhsvUPXENWRQeXJAGav+WhyJWg03Tfstp3IZJd0w96argqD21NNEbb4BlABWHS4sdPPMlNqe7i74LQEuZPQGCoFdrRiuAn9EsUSpQWI0fo8qx1R2yBvvhtRRBEAsaJpI2O5xEDv9qMNrH3OxvtPFDRg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
Received: from DM6PR11MB4692.namprd11.prod.outlook.com (2603:10b6:5:2aa::11) by CO1PR11MB4948.namprd11.prod.outlook.com (2603:10b6:303:9b::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8722.31; Sat, 17 May 2025 13:10:57 +0000
Received: from DM6PR11MB4692.namprd11.prod.outlook.com ([fe80::5900:df84:2093:a02d]) by DM6PR11MB4692.namprd11.prod.outlook.com ([fe80::5900:df84:2093:a02d%6]) with mapi id 15.20.8722.031; Sat, 17 May 2025 13:10:57 +0000
From: "Zafar Ali (zali)" <zali@cisco.com>
To: Ron Bonica <rbonica@juniper.net>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Thread-Topic: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
Thread-Index: AQHbmhSxvbj6+vsJ0k+4a16cCjNVeLN9oPpygBsdFIyAArtp4oAAA3hbgAAKVIWAAAUBa4AACggSgAExUwCACCrmLoANv+yAgACeUlSAAUhXAIAANwOfgARqiQCAABRohIAALUKJgAAlk4eAAA7p0YACw+VpgBMBnwCAA/pbAIAAAcrxgACrFluAAFj+64AADM+ggAAzxY2AAMSOZ4AAE+HagAAb2cuAABuh5IAAE1wQgAAluMeAABD5xYABFCu0
Date: Sat, 17 May 2025 13:10:57 +0000
Message-ID: <DM6PR11MB4692BC93D701A52FF3D65DDFDE92A@DM6PR11MB4692.namprd11.prod.outlook.com>
References: <MW3PR11MB46996CAB16CE9C43DC8C4DBBDE93A@MW3PR11MB4699.namprd11.prod.outlook.com> <PH0PR05MB8704398C05D487B0E285AD77AE93A@PH0PR05MB8704.namprd05.prod.outlook.com> <MW3PR11MB4699280829CAD4EC68896603DE93A@MW3PR11MB4699.namprd11.prod.outlook.com> <PH0PR05MB87040025B3217F3AFCABBB06AE93A@PH0PR05MB8704.namprd05.prod.outlook.com>
In-Reply-To: <PH0PR05MB87040025B3217F3AFCABBB06AE93A@PH0PR05MB8704.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-reactions: allow
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: DM6PR11MB4692:EE_|CO1PR11MB4948:EE_
x-ms-office365-filtering-correlation-id: 4d46db70-1d64-42b7-cae2-08dd95444307
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|376014|366016|10070799003|1800799024|8096899003|13003099007|38070700018|7053199007;
x-microsoft-antispam-message-info: 3Vvb3IWzZqKHtHh3tLeIx9cOWuDVCpEYc4MszL7E+kuV3BG95Q4Y7ucn/H9n9rw1M7obM1JxzwIfYIsPUALG/qWxZpWv48pdiEBOsxQVW9L8fw5Hexn5OchT4okHodfMY9B3LAG+nEl4tB5pWRRRF8/Mq0pnuWpQsJRV70MLTZcXT83uxHcKEE5//0JJfarXILaDnv9iwQwhEdwc6YvHNpHbLxtJda/fChH4Rqcr/d8h+e0fwdk6wwC4xLIFBtV6PwYRorMXvKYnwNOjJ8Cng3QiraqwpwbJPWo0c90fI4t7whwyIKyUj4FGNU4JwY9WB2yjfzGk1N3AceR2lSHwLqtxqJIj5iGQ3D+ASPp8Czapa5jYDKa8nwJcbw5b5ZDF8b9ZKrmVrjc69AhAX/RSVGd7qV2hkbq5WrVbdG3dNqaJiJFQ0NycG94X4UFdkrSTnnfILki5cMjM/0MEmlUzmlB2/R0/xYOKDnBPq5U7PasjOx9ePO70Y+DnO2My9eLaWHURj4XDTv1QxT8XxikWbC8MtEPfAHsjDVAxmTdmpVJ0Az8BP8Kuu98T7MbdM98Lo7u0VZMMkrUIEK5wfwlLB5XxEwkAXsOdMrnXDsLd+RrhRDhbfP4VdH6yuPl5hsx5RyS1OyHqadJBZCg/tlAfOj7Xa1UU/XqCljB6jyWkqyIh0cUUGUNRzrnhm8uge73P4Cc6wPepwBzpOrJk6CQFKaGppZy6q4Kpz0+ufBi48QR2hKhlRZ2mgThS8WmNLGwUZ/8H3FR9ob4b7rjYZiXdu5wEFKolM1heDYCAGCa0L7xzNzQBJ3avTFsyrPCIiBjxzoSpBOAs4X5X2kdSt8bPznnNHb8vmDRkONoyUPvqguF5rFYUm9B9l+1azX/s79o3dCJfm6Fmvw9kfzl5yVHd1iJa283GjnLN70IQYBxIt3237H4rPDtzQK15oFf8VVfCrqEJ55j7JvwKFzkGhpcblTDwbh4PfqBZcOoRiomzhM0RJQ8n+HTpWx2Oe1Lyt4L6uNpY8XrOLpBrmEPeOFS8GGT4ebL7OeluTdz60ibeEhlJTYt11FFaNviqwpvP/vkJMT9VTHGmqflnRw+wd0XyrjhIqVFBgqckRNVlb0i2C2XJ2yl8c2d5X5tyXsTM/+hb9M+sh845XGl28eq8R/clXKPWJM4hpe3Hli//K+MOXfdvf3JewF9/qzEdIUcIWIVnp7g0PyYFJI3IROTGCf5bc9SJk/KCObpPXV8jE9UP2wcF2WNRA2iNwt6DZ7XolxGDNxQ+s6WfAM85QatQiqt4RkFf40c0p2hBKaSLiiRuNSrkXep2XaHk5ZGjVA+tXYqcHWmKuVs/YENnTIilSB+LxDvZXt2qMcGH8oR3m5sqriHkR3lYO1xdUujnzCjup/9fxaGTbVfT20Vn/1oZ6bEnOFNjy0Ownke4W3jP8FBvB425rWg9O1oY/lsD8FLDDpLh
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DM6PR11MB4692.namprd11.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(376014)(366016)(10070799003)(1800799024)(8096899003)(13003099007)(38070700018)(7053199007);DIR:OUT;SFP:1101;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: lvJtTk8z0pUZimCFG/SBMk9cmJs8xqJ13kuzHlekrtXn72okz8UelVv2ahDrK4uR/ZF5m+dDD45qOy9ZEhP2fN1HsKwyw11zYj6y8iMDn57eoBgH1Wzaa9KNQauj/ulq4hB2SEy8a5lwx8FZFXN0XefmfSwbVoLvinyL31VIgUQ2jvzGSCxSHMNH8k26MJEwtvumeRQ7UtPJ/ldpBwOZ2Ldc5m6BAZznYY45uaDl+ndmkcXJwdsFAxwMnGmRqstm65gwnS7yOKHwRwWtsSnbpmOrRCQBbYPkg+X2cwqIMSpDObZA+JxFyKgXDOOYbKcBmpkI5Bw64yG//TLvXFJcOAFsyrTc9VzPsyl0U3dql3mKXghRS1NxqKhnDRnEZaiszJWiLrnJneHfJfcFOEMZ+9wdoVgueA759uTixEOxHRHa3n58yeZJgqdhU3+tpk4REj2IUSRwTJBU+JL4V8PMgIGXCxlTQTqxaWJZxRnrR7iKGRnSkLihert/LiPCn2+vPlOGVQ0DDbzUfVQy9wRO7nRKIsG8npt2iTkiCDgNSlkQkVoKxhsZW6MkPhHLx3NNXWc3wp019BuoP9UeP76jLvOTB8u4vSv4pr5AzCCw01IDD1cvTJaOhrU8lN9Sp0oSY8CzrhtAMNfUxzKQPQmfiw2mX6JJDkbIj9/TwLVmp4rAE29xT+U5MqBp4V+npyc7LQ2iRlD2Ex57tR+Wn0hPOVC1L2O7Vm7/iFMCswCfr9mGCDwgEdZosCpHRYeGm4rS3IzXmakoF3DBZVg44PLxgv8BfDlNhIl/vnOwT+/meELzDWjmzvMnHaDGe9rgi+LtGeUs8kpS9T5BP+jkvAeZmI8CJxiXpHriJAJiDU3w7TBcHt3lcu37yqMjACyRY2Sp0IujmzKZYoVMrEgroYMB1kuoA2hg19aN7qpIa8mwbdfUR7DKC+04X+7i7+2xC930HEzQke4544FBS4VIXMa0LPhJjmoDaDSu4fpaHa7n/RxIo9EGqM5EXwMBw9AOzd3bmsIVvx4doR7s9QS+fpLJvPvm1hPJMZkrnOyuky0EKUEds67rc4FCjyeVOJkhLeaGHFdsBED4pYal0e9qlNwkdPd9r2izGlhGsFZsVspG0P364vP8ITU76A/PlgKuoJR5Sc2ouClcIVwhLxJ0qQ/K03Tnnpk0FPZku2yMgWdLTslIPFTzYlhYzsZg1IoILnEAV/lYH/QHeLYglPjmA+/yvVLL802UV7uiIfNLJhOVmHLj2Wv82yEYzIsp6SFkuMssXaSchzAZ1uBQS0k3FbLa00jLUtw4e8XYZB9ETAUV9duEBJUR2F1QqHFDMaAL0sGxTGJy9PaQZPlu1ye1SvA5kHaigHYEezs4Il4y0YQe0SA0rqGNDEJQBBVWW0RIPQRk236ZkQJNZMeNF1smwm1s8jbpDcggcJ6Obyue4s9dHBwy4HU7QLhMrWE+9Y4re4/qPyK7spLwTzYUc5gxoNE3cIWnV0erjvTmz/UJ0ojA2JFF73STk9sj3LRhKX2jxQeM3k8VFLi+NNtsXtM6sgM7WyGnlzQ1MjitB2bc4CLPNOj8ZQNa0AkPo8phsWDwlRQEJWadN9kDCZrV5U8TxXdrBUVcFb38RcfFvANgTf5j88CCUYZwNx1J30Pqt2oo5gOG
Content-Type: multipart/alternative; boundary="_000_DM6PR11MB4692BC93D701A52FF3D65DDFDE92ADM6PR11MB4692namp_"
MIME-Version: 1.0
X-OriginatorOrg: cisco.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR11MB4692.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4d46db70-1d64-42b7-cae2-08dd95444307
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 May 2025 13:10:57.1257 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /+QzHdNCXvZ6yrxlfzFqotets3nalKCgTdAppx7WCeckat9UJXA6rwj1kDMWjsQ3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR11MB4948
X-Outbound-SMTP-Client: 72.163.7.162, rcdn-opgw-1.cisco.com
X-Outbound-Node: rcdn-l-core-11.cisco.com
Message-ID-Hash: AFF7VRM3SHAIDVXP42HB7QC3G5BP7UVV
X-Message-ID-Hash: AFF7VRM3SHAIDVXP42HB7QC3G5BP7UVV
X-MailFrom: zali@cisco.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: 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/OIzchLflYxVQmkDsj9iVd-bJQ00>
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 and Sebastian

Many thanks for your detailed follow up.

I agree with keeping the text in Section 1 referenced in this email.


Thanks

Regards … Zafar

From: Ron Bonica <rbonica@juniper.net>
Date: Friday, May 16, 2025 at 6:43 PM
To: Zafar Ali (zali) <zali@cisco.com>, Ron Bonica <rbonica=40juniper.net@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,

Once you understand why the rationale presented in Section 4.3 of RFC 3022 do not apply to draft-ietf-6man-icmpv6-reflection, you will also see that the other points are not so weak as you think.

Let's talk about RFC 3022........

The recipient of an ICMP error message frequently has to match the received message with one of its upper-layer sessions. Upper-layer sessions include TCP and application-layer protocols that rely on UDP.

The original solution to this problem was to embed the original (aka, invoking) packet in the ICMP error message. The original packet provided all the information that the recipient of the ICMP message needed to match the message with an upper-layer session.

This solution worked well until NAT was introduced. When NAT was introduced, the sender and receiver of the original packet no longer had a common understanding of each other's ports or IP addresses. So, it became impossible for the recipient of an ICMP message to match the received message with one of its upper-layer sessions.

RFC 3022 addressed this problem by modifying the embedded packet in ICMP error messages. Specifically, it translated ports and IP addresses and recalculated checksums.

Draft-ietf-6man-icmpv6-reflection does not rely on ICMP error messages. Instead, it relies on two ICMP informational messages (i.e., the ICMP Extended Echo Request and the ICMP Extended Echo Reply). Neither of these include an embedded, original packet. In stead they rely on an Identifier in the ICMP header to match requests with replies.

NATs will continue to translate the Identifier field in the ICMP header, as they do today.  However, the objects defined in draft-ietf-6man-icmpv6-reflection are not needed to match the ICMP Extended Echo Response with an ICMP Extended Echo Request. So, there is no motivation for middleboxes to modify them.

Even if we don't explicitly forbid modification of these objects, we define them as representing "the packet as it was when it arrived at the probed node". Modifying them cause them to be something other that what they purport to be.

                                               Ron








Juniper Business Use Only

________________________________
From: Zafar Ali (zali) <zali@cisco.com>
Sent: Friday, May 16, 2025 3:43 PM
To: Ron Bonica <rbonica@juniper.net>; Ron Bonica <rbonica=40juniper.net@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.



The other arguments except the Section 4.3 of RFC 3022 are weak.

What I am unsure why the “reasons” of Section 4.3 of RFC 3022 would not apply to the copy of the packet carried as per draft-ietf-6man-icmpv6-reflection.



Thanks



Regards … Zafar



From: Ron Bonica <rbonica@juniper.net>
Date: Friday, May 16, 2025 at 1:39 PM
To: Zafar Ali (zali) <zali@cisco.com>, Ron Bonica <rbonica=40juniper.net@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,



The following are reasons to believe that middle boxes won't modify ICMP Echo Messages:



  *   There is no RFC specifying how and why middle boxes should modify ICMP Echo Messages. This is not the case with ICMP error messages. See RFC 3022.
  *   Modifying an object defined in draft-ietf-6man-icmpv6-reflect would not benefit any party. This is not the case with the embedded packet in an ICMP error message. Again, see Section 4.3 of RFC 3022.
  *   Modifying an object defined in draft-ietf-6man-icmpv6-reflect would defeat the whole purpose of the ICMP message. It would be much more efficient to drop the packet.



                                                Ron









Juniper Business Use Only

________________________________

From: Zafar Ali (zali)
Sent: Friday, May 16, 2025 12:18 PM
To: Ron Bonica; 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



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.



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 Only

________________________________

From: 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 Only

________________________________

From: 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 Only

________________________________

From: 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<https://urldefense.com/v3/__https:/www.rfc-editor.org/rfc/rfc3022*ref-ICMP__;Iw!!NEt6yMaO-gk!C2ZXxhLevQBo6q2hjQidY-z_pxEafV3QS1ThCU2vJtdSI8thzrfuuIpUtsLX0FUsWReuzsQeIbg$>] 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 Only

________________________________

From: 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$<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$<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$<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$<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$>