[IPv6]Re: Middleboxes [was Comments on draft-ietf-6man-icmpv6-reflection]
Ron Bonica <rbonica@juniper.net> Thu, 15 May 2025 20:24 UTC
Return-Path: <rbonica@juniper.net>
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 B5D912903EEE; Thu, 15 May 2025 13:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-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_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net header.b="0xNO0KJE"; dkim=neutral reason="invalid (public key: not available)" header.d=juniper.net header.b="jO6LeIOL"
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 2tRRwUHw7GRl; Thu, 15 May 2025 13:24:45 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) by mail2.ietf.org (Postfix) with ESMTP id 5AE7B2903EDE; Thu, 15 May 2025 13:24:45 -0700 (PDT)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 54FJOskL015451; Thu, 15 May 2025 13:24:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h= cc:content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to; s=PPS1017; bh=9eXrtaWuUQvDkkFsrxOKJqdrVA xos9AYbxtkW1qy4Xo=; b=0xNO0KJEMreJx9D3gGcfJC2hFy7nQqDe4DgWhPzD0U ZZMq8MwSN+xRj6rkAuqTOTLZXTetqXCtTusEsVVgKf/LBolrahonfim7CvtajrLT RmmrIzCXMBnvi+7n69ju6TsuzW5e5MgOBLQxu5BfEsrWFLHO70o1/bwYrmfGsQhx aG9aLUeQEYnJzuWh9GBNyZFEQp/K8NfJ7o8qXMUutBSvwGDlIVzK0h+EO0Cyp+Ot eyTPwCagfRHSgZqQUIJ1yifmsj17Ty9vtjomQuA+p5mZN0bLTdURdPIvFTwDac1g 9u6bgVs/oeFEcArK3ACGva6rDB33oXYu+HxZGH5DO9uQ==
Received: from ch4pr04cu002.outbound.protection.outlook.com (mail-northcentralusazlp17013063.outbound.protection.outlook.com [40.93.20.63]) by mx0b-00273201.pphosted.com (PPS) with ESMTPS id 46npde043a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 May 2025 13:24:41 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=x2yuXgLr1Te2bdltdnBiDgl8ACB9HvbAwwcHBspQLWi9HbE0bl9hfJAv1eIw3iSizqPPunaWUJlVj5SgXZooGAs1CillYfEZikMrgXKWTohfn4yNI2Q3s0UWaExd2jfqDw/0jMcVKHb6aNmdLrgd5g47YWeJRW50Y4OZcz7MoFNJlvoynZAdrbRvPQuwxgcc6vqyhdlbh6bb2KoMJfeIwdzGRIa7mYNv+M8PBXLd8X9cckVVabiQer3+tVr78tcUQjR/NaR0XuYt847T/1ZdXuhZwZitTnqlaLj8OcxThxKYlskFlIZWKNQoRRG/P1XnqxSNB6ZJBhYIKhZ/nV+I2w==
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=9eXrtaWuUQvDkkFsrxOKJqdrVAxos9AYbxtkW1qy4Xo=; b=hqsuWzkupHKNhxsrlbJMU1YsGFDHGvQQ3GqQN2RVoizBH9JaQ0r6iZoNOeIwGqHnIDMp3o/iZKyjE0dPE3ZV862RzBC4QoItTEuvkN2W2ZNIAjOsdHSk2AP4V91gxXa+TEt71bRgXCw96q/b7pKfUSSWtiplOU62BenMFI46PcwuJz8iSGSrkC0VS3jNzbjRNok7sAUXVrn7hAKRTs/cB/0UEq+N/7tuYqEkSv33+ho0nTkYypesHw5AD+R1ZgWWfYwVnDcGB5Dkdd/tCoNJ7FsAvTmHbGVuPyLov+GgseEdshnzGI6ZsYjMOoISG2M0+y1rnI8RSyLYRe2+2pT0gQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=juniper.net; dmarc=pass action=none header.from=juniper.net; dkim=pass header.d=juniper.net; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9eXrtaWuUQvDkkFsrxOKJqdrVAxos9AYbxtkW1qy4Xo=; b=jO6LeIOLnQnpbFk313UEL7lkw1WKo/hKGslxX198IF9iRyHgHKo4c7Dhb1vuWWjM5wGWkuQiqUpnxdqhR9fA/zhrs+p4oWPfgMJpB1GBDMBjq57RvBqwHiSLaoP0N1vaYNTKtwBPpAvatlrkItn8GMGFKu9o45xN2RKp56MYNsE=
Received: from PH0PR05MB8704.namprd05.prod.outlook.com (2603:10b6:510:b8::13) by DM4PR05MB9414.namprd05.prod.outlook.com (2603:10b6:8:112::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8722.32; Thu, 15 May 2025 20:24:39 +0000
Received: from PH0PR05MB8704.namprd05.prod.outlook.com ([fe80::cd64:f833:f599:f85]) by PH0PR05MB8704.namprd05.prod.outlook.com ([fe80::cd64:f833:f599:f85%5]) with mapi id 15.20.8722.027; Thu, 15 May 2025 20:24:39 +0000
From: Ron Bonica <rbonica@juniper.net>
To: Sebastian Moeller <moeller0=40gmx.de@dmarc.ietf.org>, Bob Hinden <bob.hinden@gmail.com>
Thread-Topic: Middleboxes [was Comments on draft-ietf-6man-icmpv6-reflection]
Thread-Index: AQHbxa4yiEbf+2c6GUqTj+P0eRqhbrPT/IkAgAAhipU=
Date: Thu, 15 May 2025 20:24:39 +0000
Message-ID: <PH0PR05MB87044818E0F62F40AE1BA58BAE90A@PH0PR05MB8704.namprd05.prod.outlook.com>
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> <9A7AF919-7507-4BBA-A4B9-108144579930@gmx.de> <57267C04-50B8-41C7-9AA1-47AFFB1E30D2@gmail.com> <F2BB8C07-05D2-4C67-A13F-477FF6631FCA@gmx.de>
In-Reply-To: <F2BB8C07-05D2-4C67-A13F-477FF6631FCA@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Enabled=True;MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SiteId=bea78b3c-4cdb-4130-854a-1d193232e5f4;MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_SetDate=2025-05-15T20:13:57.438Z;MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Name=Juniper Business Use Only;MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_ContentBits=0;MSIP_Label_0633b888-ae0d-4341-a75f-06e04137d755_Method=Standard;
undefined: 1543111
drawingcanvaselements: []
composetype: reply
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: PH0PR05MB8704:EE_|DM4PR05MB9414:EE_
x-ms-office365-filtering-correlation-id: 98e53b36-8ad8-49c4-f792-08dd93ee84b1
x-ms-exchange-senderadcheck: 1
x-ms-exchange-antispam-relay: 0
x-microsoft-antispam: BCL:0;ARA:13230040|366016|1800799024|376014|38070700018|13003099007|8096899003;
x-microsoft-antispam-message-info: AWWV6r7uBCo5nBRPWN3anNpGroYGZucnC4x+dqqkp8ycFhLR6Z2iah6wEpfgra/A/wB2QgaMr8DsoeoLjfD4/chhOkAl+hygib+j2oIxk45niDjmI2LzyjWNJVp7Y6b7lJKJgy9Lh1hOe9e1PfOXtrl+0p44xhdujjfgC73ngaiKY2tHXH7MY//TKM3+lY2Zrfx392ZvzvcMQnS3HzgC0l2FjeN2yQMzUBVqrYvfMvLSjDE6vPq1zlSYv7aQOdN6Q7F+K0GPYK+iNsYvpjDxixoIoExmPyLSmD8BqCmoWoY0i34z8oU+MvEjPyx4zY+PITMM3R6tQe34Nyfl9YREpT08uqeyO9FNz3FGcWD86mziukaChI4Y9Z/dmCLJaBt+l4+XL4ZwnKxw6xUTohV6f/YjnH/QQ9qEH7lACpOhbR3xS/YS6pnopeXLbdYKD/Q0eoVImHgiCg12z7vL954o7pCQjIn3n3CNWUQ7ObsvnX5Nk4L7ipwSnCd2QyWAX4dbkgpN5mvHW7mZBcqGXXb0XKqd+6GsOnchh0Km7HAS1Z4sf1e6cMqv6nZWZJV2PTVzGf+6YeNUsQGP60DCw/iAcdmFTXizAWSOYg+yGQuWQorbmPfBMlxhZ81y+4EJXatgXFs1y4dbclM/x+F7GbgazeONgSAsnz2Rwzew48ZcoYcVU2+zgp1HJmtJZhUllSNxgb6cPWuESVDbyZz/rHj1Q88pZIp7oqUn+e1vkEa5HIJjz0Bskx4RoVnbTbaEKGItQGeonRPTYGV/otXStJD7ptgkn8Yk/3dw3c+AgeEgm2mlaZzLBDmc2jozwwjJ27tR6eX9TkVx0K+avDSGulcDY98KwpOBsNuoWnSmt/iWiBUWhOedlUNYM7zAj8+M62XFKl+p/8SEyfvnE+Bbd/FrSSjUeMLDScvfs5pyRxPD36CNVxSUB0ZDwv977ccCTt0qCWoiJFwXZKWjlqx2/4QlOjU1+8MxMsmsUtBMzsN7fiMWS2ZXswtPbxZyBrW/IS1tniVBMMBOZ06Hr0x5zJ7WvBQWcRVb1LUN8/Mgey2fYtnCgjhMOX5QADZxYA+zS/q3I4VeUiSXlZy1RPSCydTWAjcOBL3YNi5hCTCSyvKlFGSCXrLwKl1ZEmZxRTEW/z94xO1of2T//vMGTIHtJZi7E5BmxEeZpY5BDodZUPe6Gjg+cIckm94rS3prK4jRjH6vTpbNnf1j7KFM8mlWeTW/tKEQh830GjdfcMCYa/lm9r+eiryg+pN1Je3ZMcD00jqAHR52ULYmnP/G/DvDpPfYWHa+p5n/NnHDmy7N6R03poHZaD/O9+BuFaeF70BF2jGFUQwb/tjYJn945yuU9NuzcPSp/WnHQ81tBLhdi1+Bw9F6rfuLmZZUCzVnbrffj4r3f+CLZ3xBNGNnuvdZNc9GX2If7jbgmBQ/6pKpvvVfmmxu2sDIWEgS11zdEmVb9g+kCsPMS7jThCuulDcxL8v5T0odDxh8idAL9O6BSbq8Fr8=
x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:PH0PR05MB8704.namprd05.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230040)(366016)(1800799024)(376014)(38070700018)(13003099007)(8096899003);DIR:OUT;SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: WI7FoY1fiOoEmeJ0D2YDcTCnVd5U8pIAAyZMyFRmiSUxbIl7OQ2MxZCxS6OcS3mo4WXGrbjgqQ8MF71yuIRxbK3CvO9DsfnjMafXbUsBHPvd1K23ynoadb9RkzKAbcTUqoH4TfQnVHrlEXOtAdd40CJw3Y877gdxWyfSTGuiJWRrP7uKfhZqZbef0aQf4s1jPDkveF0LqUG+LTY23UHbufVDUabOjiWKKdQkPL+ntI0fFbAxTR9H+s8c3vY3PMegYrZG8wX2j77PIGReMHHSrK2ESWW1GhDLDdEAdiQ+1H3aTKjuqcrkPzbhMyNth7I4Dh7qqICg7836TUN65Aum6AxtZouZ4maBdk/jlcwSyqSHzbH2es/DIl3CKXv6E8ZEaww+K3iKchXKQ0EMA+sl5DZqRx5pzdVd0/ZdA8PvazAmQcRBibTu//18YtP+5n2QhZF2TdSrMx86OAkrIYCS/rT/kOV58T7Sb4ErM3rXH19l00dL+Jp0JuyFNyb75F/o+CNXlrI4IpI6dQsUs/Rmb/bJ9ku2MhOJsoU5/LJ7PIqp9CLrxvoiRlPQmH84hMngAocSwy5TgRHNvcBW0oxYluJzd3TdPSTe1PCWPZRutqHoIagDXqXAHiWdLOWfk2PVkV4JOX5kDt//CygsujYToRjbTaEaKnz64+P07f4/hi1QEDAB91sp6WeksoS8n9VgpiRgJIBWANxCYqP97KLcQAZVl2n0wgbp8hpRQQ9aDelPkh4WusrS2aOHAFr6iHqac4SrQECgwAZfOpPV68W/XCGW0KoLX3hXAXPNSky25PwyZgB/9ZDIr+0gpJb4ZkwL1W7trft45OhVU7WWuKOQXRd9XO+F0XjzLqQ1+LAdKQuwA5v7OGyki81asFnHjon1ggqWM80GSAHpVxF2mcLwo6i9yyDk/W6NduY0JN2Q+gnUVJzEBa81DHhlwYP8saLAytwru9AgcAve0xuKKsM6PfvRkMAqt2weHO8Y9Lr7O27NQb3dS1iUjq2+3VyUFk4+0SOPCJxC1beE21+5HGkuY4NA8zJr9cB3c2ms++5NopJMNSeppQuhcjE0DpHS8nR212MNIXnEMDJplDCPuOMRoMkxuU69mbHObVCRRWsrq/y+vJdbYtV/8weFjrShwllbNcaJKrTxJux1FJpX5q8ZNU0i+GQnVAc1X1CTlLWAn65RDlp66FCg5ejSE2V3RrSexqlnz6cAmX2eD/BlCdvVYNrkVhJxR77M4+fT6tNYenDlLPrF3KC1UKu5rUEYCE6gD8ngRnO1s6Tijeu2dXFw3omWUv6nJDEn8Hb9gyWofIBsflFFh7uz3eAAz6bkwcwuspkFOTHu/WEqxvvgSFsUavWh/OgUZCKb98XDvebo5laOx4fYhV2oonv/pogWWuAs9jqUjMbGb7Fy2t2eDnALwrweDNvVbMyqYWDRzazIHwk9qnis9P5TYjFV4/Kyi3Na53sZCDdkxzK8DJzPh8JsUVBp0rhmlONFd+O/yw60ooVUpeeX0qd15rZa77nTeyqSRdgD2OGac9g1u2/WwILAImxq2Spthe/up7AftCrj3wgt7bCi4hq5x0Gjsx8NjdDc
Content-Type: multipart/alternative; boundary="_000_PH0PR05MB87044818E0F62F40AE1BA58BAE90APH0PR05MB8704namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH0PR05MB8704.namprd05.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 98e53b36-8ad8-49c4-f792-08dd93ee84b1
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 May 2025 20:24:39.4196 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: DwfaHLhLMYOvcTT/oLQdT/JLVjIvXrnmekLXakazseoKchsWCNhtTMU6EB5hTLWYunaG3ocvaUwtya2RTYBozw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR05MB9414
X-Authority-Analysis: v=2.4 cv=SKlCVPvH c=1 sm=1 tr=0 ts=68264d89 cx=c_pps a=FN31aPQdsEfnd7fT0GsFIA==:117 a=lCpzRmAYbLLaTzLvsPZ7Mbvzbb8=:19 a=wKuvFiaSGQ0qltdbU6+NXLB8nM8=:19 a=Ol13hO9ccFRV9qXi2t6ftBPywas=:19 a=xqWC_Br6kY4A:10 a=dt9VzEwgFbYA:10 a=rhJc5-LppCAA:10 a=BqEg4_3jAAAA:8 a=48vgC7mUAAAA:8 a=pGLkceISAAAA:8 a=AUd_NHdVAAAA:8 a=OUXY8nFuAAAA:8 a=eoHDz2BH7MJ9RFZg5YcA:9 a=QEXdDO2ut3YA:10 a=cPjCS9iPJegA:10 a=In69hMrxKTsA:10 a=fI4JZSkZ6Kz0FSEo:21 a=frz4AuCg-hUA:10 a=_W_S_7VecoQA:10 a=0mFWnFbQd5xWBqmg7tTt:22 a=cAcMbU7R10T-QSRYIcO_:22
X-Proofpoint-ORIG-GUID: LGnhwZ2gbpbcVtH3o0U21kXkVq79cAk5
X-Proofpoint-GUID: LGnhwZ2gbpbcVtH3o0U21kXkVq79cAk5
X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUwNTE1MDIwMCBTYWx0ZWRfXyR0dzT2mIkkT vL79SWZb9nEgNKQm+qaCqEv4JB+jnljwxpUJWz7qHYsKW6NVyWXk9QZvgG1WQHlCorEJG6Chi2j q2AaRW/Y27Ga5QEnyyZIrXDAoT6V5k4vwl2jYuIAjOXVpH4FYguDD8HUyH0qJTyT/37iT0Bo8xp VgH7x7uTvZXnWmgyrB7TPnyR0Rg79FVa0Ae922VDNjvkQVYpK3LfSLykRCtJysxVIEyKYS2zLQW p6ShDrGGWTGsovrMzrTtokuL4cGvrgvZOQ38/5qons82LJfy6nDUtJKfOfyuh+uDT3ul0LUXeLI catR4YJBIxzGQya2u+2iSketQWNFgpul2iiJDYiaPKFYEAM+QHmEIaoEjDrjZeDDCAJPYXEQa6Z v0AWT6WckGtAbLkcUEh2tQrFGozHuCbhRIaL1yG5tWQTnoeYTiouKGO20N0j4vrzLrh14lHV
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1099,Hydra:6.0.736,FMLib:17.12.80.40 definitions=2025-05-15_09,2025-05-15_01,2025-03-28_01
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 adultscore=0 clxscore=1015 spamscore=0 mlxlogscore=999 mlxscore=0 impostorscore=0 malwarescore=0 bulkscore=0 lowpriorityscore=0 priorityscore=1501 suspectscore=0 phishscore=0 classifier=spam authscore=0 authtc=n/a authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.19.0-2505070000 definitions=main-2505150200
Message-ID-Hash: 3EGXYQRKSINGHBATSNMROEWUUBXUKMGE
X-Message-ID-Hash: 3EGXYQRKSINGHBATSNMROEWUUBXUKMGE
X-MailFrom: rbonica@juniper.net
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 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: Middleboxes [was 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/Yxt8YbUDNNlewhA5dTcEq1kAHqk>
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 Sebastian,
Inline.... RB>
Ron
Juniper Business Use Only
________________________________
From: Sebastian Moeller
Sent: Thursday, May 15, 2025 2:05 PM
To: Bob Hinden
Cc: Zafar Ali (zali); Tal Mizrahi; Ron Bonica; Ron Bonica; 6man Chairs; 6man@ietf.org; draft-ietf-6man-icmpv6-reflection
Subject: Re: Middleboxes [was Comments on draft-ietf-6man-icmpv6-reflection]
[External Email. Be cautious of content]
Hi Bob.
> On 15. May 2025, at 17:29, Bob Hinden <bob.hinden@gmail.com> wrote:
>
> Sebastian,
>
>> On May 14, 2025, at 10:58 PM, Sebastian Moeller <moeller0@gmx.de> wrote:
>>
>> Hi Zafar,
>>
>>
>>> On 15. May 2025, at 06:47, Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org> wrote:
>>>
>>> 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
>>
>> No objection against adding that text, yet, I strongly believe that "must not touch the payload" is the rule with a few explicitly enumerated exceptions. I would go as far, that this rule also includes header, where again we have an enumerated list of cases in which changing a header is permissible. So maybe:
>> “The payload of Extended Echo Reply messages (like almost all other payloads) MUST NOT be modified by middleboxes.”
>
>
> This is intended to be a more general question about modifications by middleboxes, not this specific email. It’s not clear to me that we can define rules for middleboxes.
Let me ask, how can we ever expect useful end to end communication if we allow any entity to perform arbitrary payload manipulations?
RB> Your question has global significance. We can't expect useful end-to-end communications if we allow any entity to perform arbitrary payload manipulations?!
RB> But a statement with such global significance shouldn't be hidden away in a 6man document about a diagnostic utility. It probably should be in an IAB statement dedicated exclusively to this topic. If the IAB were to address this issue, they would probably need to make exceptions for the manipulations specified by RFC 3022 and RFC 5508. Either that or UPDATE those RFCs.
RB> In any case, this global statement shouldn't be hidden away in a 6man document.
If we write MUST we are basically saying, something will break/not work if we violate the requirement, and that seems to be correct here, as fudging the reflected header (parts) will essentially invalidate the message, or worse silently corrupt it. A MUST, however will not bend reality, if a middlebox decides to violate a MUST there is no way of stopping it by text in a document, no matter the verbiage.
RB> The best we can do in a 6man document is to say what Tal has said. That is, "The payload of Extended Echo Reply messages MUST NOT be modified by middleboxes".
RB> Any more global statement would be beyond the scope of 6man and certainly above my pay grade ;-)
> There isn’t a good definition of what a middlebox is.
Let me give a quick and dirty definition that is IMHO still operationally useful: for any given flow/connection any node/hop that is neither the sender nor the receiver. We do have some guidance of where such middleboxes are allowed to manipulate a packet (e.g. DSCP field changes, or some ECN codepoint transitions, AQMs) that are proper standards and some that are only informational (NAPT, internet firewalls (dropping a packet is the ultimate manipulation)).
> This draft references RFC 3022, but that is informational.
But that seems to match what is happening out in the field... whether a draft is classified as informational or proposed standard is in the end a policy decision of the IETF that has little bearing on the deployed reality, no?
>
> Middlebox functionality is pretty varied and largely outside of IETF standards work.
Some is outside, sone is within, e.g. AQMs, no?
>
> Then there is the whole issue of will anyone building middleboxes follow what is in this document.
That holds true for all standards, we can not even assure that the endpoints follow the letter of RFCs...
> If this document depends on changing the behavior of middleboxes, I am not very optimistic it will be useful.
But as far as I can tell, the required behaviour is already the existing behaviour? Otherwise we already would see wide spread corruption of ICMP payloads, and we do have ICMP message types with meaningful payload where corruption should be obvious. IIRC Linux will put its time into the payload of echo requests, so it does not need to maintain state and hence we would expect fireworks to go off, if an ever increasing timestamp is interpreted as an IP header and treated to a reverse NAT transformation, no?
>
> A better approach might be to just include text that it won’t work if middleboxes change the header, or include some way to detect the change.
Ah, you are mostly concerned about the fact that we can not assert a MUST for middleboxes? As I said we can not assert that for end points either, so why should we treat middleboxes differently?
That said, if the solution to the issue is to simply drop that sentence I see not much harm in doing so either.
Regards
Sebastian
P.S.: Being relatively new to the IETF I might accidentally poked a bear here in that case just ignore my ramblings.
>
> Bob (speaking for myself)
>
>
>
>
>>
>>
>> If we assume/have data implying, that payload manipulations are ubiquitous we likely would need to add authentication or even encryption to the payload so such manipulations can be detected. That however seems pretty costly, so maybe only so this if absolutely required.
>>
>> Regards
>> Sebastian
>>
>>
>>
>>> Regards … Zafar
>>> From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
>>> Date: Thursday, May 15, 2025 at 12:33 AM
>>> To: Zafar Ali (zali) <zali@cisco.com>
>>> Cc: Ron Bonica <rbonica@juniper.net>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org<6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
>>> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
>>> Hi Zafar,
>>>
>>> A kind reminder: would you say that the text below addresses your main
>>> comment from WG last call, and if the answer is no, how would you
>>> suggest to rephrase the text?
>>>
>>> Thanks,
>>> Tal.
>>>
>>> On Mon, May 12, 2025 at 6:48 PM Tal Mizrahi <tal.mizrahi.phd@gmail.com> wrote:
>>>>
>>>> Hi Zafar,
>>>>
>>>> Many thanks for the feedback.
>>>> I re-read all your comments from working group last call, and I
>>>> believe the following comment you sent summarizes them (correct me if
>>>> I am wrong):
>>>> "the main point is that adding description of the use of existing
>>>> tools and compare it with reflection functionality will help the
>>>> reading of draft-ietf-6man-icmpv6-reflection"
>>>>
>>>> In order to address this comment we added a description of the UDP
>>>> probe and ICMP error message (quoted at the end of this message).
>>>>
>>>> Would you say that the new text addresses your feedback about
>>>> describing existing tools and comparing them to ICMP reflection? If
>>>> the answer is no, how would you suggest to change this text?
>>>>
>>>> Cheers,
>>>> Tal.
>>>>
>>>> Quoting the new text from draft-ietf-6man-icmpv6-reflection:
>>>>
>>>> An alternative approach that could be considered involves the probing
>>>> node sending a UDP packet with an unused destination port to the
>>>> probed node, causing the probed node to send an ICMPv6 Destination
>>>> Unreachable message, which includes "As much of invoking packet as
>>>> possible without the ICMPv6 packet exceeding the minimum IPv6 MTU"
>>>> [RFC4443]. The benefit of ICMPv6 Reflection is that it enables the
>>>> probing node to selectively request specific parts of the request
>>>> message to be included in the reply. Additionally, the payload of
>>>> ICMP error messages such as Destination Unreachable might be modified
>>>> by middleboxes (e.g. [RFC3022]), whereas ICMPv6 Reflection is
>>>> intended to reflect parts of the request message as received by the
>>>> probed node.
>>>>
>>>>
>>>>
>>>> On Wed, Apr 30, 2025 at 4:33 PM Zafar Ali (zali) <zali@cisco.com> wrote:
>>>>>
>>>>> Hi Ron,
>>>>>
>>>>>
>>>>>
>>>>> I also do not see how text in your draft can influence the middle boxes.
>>>>>
>>>>> Hence, the gain against sending UDP probes to an unused destination remains:
>>>>>
>>>>> Only about requesting “specific” parts of the invoking packet vs. copy of the (as much as possible) invoking packet.
>>>>>
>>>>> Can you please document, accordingly.
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> Regards … Zafar
>>>>>
>>>>>
>>>>>
>>>>> From: Zafar Ali (zali) <zali@cisco.com>
>>>>> Date: Monday, April 28, 2025 at 8:34 PM
>>>>> To: Ron Bonica <rbonica@juniper.net>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Erik Auerswald <auerswal@unix-ag.uni-kl.de>
>>>>> Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>, Zafar Ali (zali) <zali@cisco.com>
>>>>> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
>>>>>
>>>>> Hi Ron
>>>>>
>>>>>
>>>>>
>>>>> I think this is not a big limitation.
>>>>>
>>>>> When someone is running a traceroute outside of a limited domain, in which NAT is deployed, having some address mapping done on the invoking packet can be reasoned. I would suggest the limitation with the specifics.
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> Regards … Zafar
>>>>>
>>>>>
>>>>>
>>>>> From: Ron Bonica <rbonica@juniper.net>
>>>>> Date: Monday, April 28, 2025 at 2:30 PM
>>>>> To: Zafar Ali (zali) <zali@cisco.com>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, Erik Auerswald <auerswal@unix-ag.uni-kl.de>
>>>>> Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
>>>>> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
>>>>>
>>>>> Zafar,
>>>>>
>>>>>
>>>>>
>>>>> If we were to do this, would we need to add a note that saying that the utility may yield unreliable results when run outside of a limited domain, in which NATs are known to be absent? SHOULD we add a note saying that running the utility outside of such a limited domain is NOT RECOMMENDED?
>>>>>
>>>>>
>>>>>
>>>>> Ron
>>>>>
>>>>>
>>>>>
>>>>> Juniper Business Use Only
>>>>>
>>>>> ________________________________
>>>>>
>>>>> From: Zafar Ali (zali) <zali@cisco.com>
>>>>> Sent: Monday, April 28, 2025 12:17 PM
>>>>> To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>; Erik Auerswald <auerswal@unix-ag.uni-kl.de>
>>>>> Cc: Sebastian Moeller <moeller0@gmx.de>; 6man Chairs <6man-chairs@ietf.org>; 6man@ietf.org <6man@ietf.org>; draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>; Zafar Ali (zali) <zali@cisco.com>
>>>>> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
>>>>>
>>>>>
>>>>>
>>>>> [External Email. Be cautious of content]
>>>>>
>>>>>
>>>>>
>>>>> Hi Ron
>>>>>
>>>>>
>>>>>
>>>>> Documenting "traceroute method" as an alternative to ICMPv6 reflection's core functionality with the NAT specifics would be the right thing to do (given large set of implementations).
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>>
>>>>>
>>>>> Regards … Zafar
>>>>>
>>>>>
>>>>>
>>>>> From: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
>>>>> Date: Monday, April 28, 2025 at 9:41 AM
>>>>> To: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
>>>>> Cc: Sebastian Moeller <moeller0@gmx.de>, 6man Chairs <6man-chairs@ietf.org>, 6man@ietf.org <6man@ietf.org>, draft-ietf-6man-icmpv6-reflection <draft-ietf-6man-icmpv6-reflection@ietf.org>
>>>>> Subject: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
>>>>>
>>>>> Erik,
>>>>>
>>>>>
>>>>>
>>>>> Thanks for this good research.
>>>>>
>>>>>
>>>>>
>>>>> You say, "For IPv6, as long as no NAT is involved, the "traceroute method" seems promising as an alternative to ICMPv6 reflection's core functionality. NAT66 would most likely affect this negatively." I think that this statement is absolutely correct.
>>>>>
>>>>>
>>>>>
>>>>> But how does the user know if NAT is involved? Given that the user cannot know this, I conclude that ICMPv6 Reflection is the best solution. While it requires more work than the "traceroute method", its results are more reliable.
>>>>>
>>>>>
>>>>>
>>>>> Ron
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Juniper Business Use Only
>>>>>
>>>>> ________________________________
>>>>>
>>>>> From: Erik Auerswald
>>>>> Sent: Monday, April 28, 2025 8:16 AM
>>>>> To: Ron Bonica
>>>>> Cc: Sebastian Moeller; 6man Chairs; 6man@ietf.org; draft-ietf-6man-icmpv6-reflection
>>>>> Subject: Re: [IPv6]Re: Comments on draft-ietf-6man-icmpv6-reflection
>>>>>
>>>>>
>>>>>
>>>>> [External Email. Be cautious of content]
>>>>>
>>>>>
>>>>> Hi Ron,
>>>>>
>>>>> On Fri, Apr 25, 2025 at 05:00:40PM +0000, Ron Bonica wrote:
>>>>>> [...]
>>>>>> I have also done some research with a popular platform. I found that:
>>>>>>
>>>>>> * It complies with RFC 792 and 4443 regarding the number of bytes
>>>>>> in the invoking packet field.
>>>>>> * It does not modify the invoking packet field.
>>>>>>
>>>>>> However, your finding that a LINUX-based NAT box modifies the invoking
>>>>>> packet field is significant. [...]
>>>>>
>>>>> RFC 5508[1] (NAT Behavioral Requirements for ICMP), currently BCP 148,
>>>>> requires NAT to modify the embedded packet's addresses according to the
>>>>> matching NAT mapping that is also used to translate the ICMP packet's
>>>>> addresses (REQ-4 and REQ-5).
>>>>>
>>>>> Section 5.3 of RFC 6145[2] (IP/ICMP Translation Algorithm) also describes
>>>>> the translation of the invoking packet (called "packet in error").
>>>>>
>>>>> RFC 6296[3] (IPv6-to-IPv6 Network Prefix Translation) does not describe
>>>>> translation of ICMPv6 error messages.
>>>>>
>>>>> If I were to speculate, I would expect NAT66 to also translate invoking
>>>>> packet field addresses, if not now, then after deployment experience.
>>>>>
>>>>> Section 3.8 of the expired Internet-Draft
>>>>> draft-bctb-6man-rfc6296-bis-02[4] (RFC 6296bis IPv6-to-IPv6 Network
>>>>> Prefix Translation) requires translation of the invoking packet field:
>>>>>
>>>>> "For an ICMPv6 error, both the addresses in the outer IPv6 header
>>>>> and the embedded IPv6 header in the ICMPv6 error message must be
>>>>> translated."
>>>>>
>>>>> For IPv6, as long as no NAT is involved, the "traceroute method" seems
>>>>> promising as an alternative to ICMPv6 reflection's core functionality.
>>>>> NAT66 would most likely affect this negatively.
>>>>>
>>>>> ICMPv6 reflection does not address IPv4, but the "traceroute method"
>>>>> seems to be more limited for IPv4, because (1) RFC 792 specifies that
>>>>> only the IP (version 4) header and the 8 bytes following this header
>>>>> are included in ICMP error messages, and (2) NAT44 is prevalent.
>>>>>
>>>>>> [...]
>>>>>
>>>>> Best regards,
>>>>> Erik
>>>>>
>>>>> [1]: https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc5508__;!!NEt6yMaO-gk!EXQDayNijAz4qi0p1B4eh1p_gAylhXnL4qkhOdZeJneujeEno1k8DLAe8lhRjG-KKSoefsH9Ii8VZg3I7xhaKVw6FEg$
>>>>> [2]: https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc6145*section-5.3__;Iw!!NEt6yMaO-gk!EXQDayNijAz4qi0p1B4eh1p_gAylhXnL4qkhOdZeJneujeEno1k8DLAe8lhRjG-KKSoefsH9Ii8VZg3I7xhakGJfyO8$
>>>>> [3]: https://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc6296__;!!NEt6yMaO-gk!EXQDayNijAz4qi0p1B4eh1p_gAylhXnL4qkhOdZeJneujeEno1k8DLAe8lhRjG-KKSoefsH9Ii8VZg3I7xhaKxV-p-A$
>>>>> [4]: https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-bctb-6man-rfc6296-bis-02.html*name-icmpv6-error-forwarding__;Iw!!NEt6yMaO-gk!EXQDayNijAz4qi0p1B4eh1p_gAylhXnL4qkhOdZeJneujeEno1k8DLAe8lhRjG-KKSoefsH9Ii8VZg3I7xhabcv-pZk$
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> List Info: https://urldefense.com/v3/__https://mailman3.ietf.org/mailman3/lists/ipv6@ietf.org/__;!!NEt6yMaO-gk!FEQUsF4CbxPvhgJxtGAi05rhecQ5eOgg9guKSn2hc0UtjEbkbM2esuhb8jXgsEZOoVOEgdTfc4oi4cFd8E4yjStQ8aLIa8g$
>>> --------------------------------------------------------------------
>>
>>
>
- [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