IETF Logo Mail Archive

Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues

Christian Huitema <huitema@huitema.net> Mon, 07 February 2022 17:44 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE2E3A102B for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 09:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.888
X-Spam-Level:
X-Spam-Status: No, score=-6.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4gXaAVS-ziPj for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 09:44:08 -0800 (PST)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A253D3A10A8 for <behave@ietf.org>; Mon, 7 Feb 2022 09:44:03 -0800 (PST)
Received: from xse152.mail2web.com ([66.113.196.152] helo=xse.mail2web.com) by mx257.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nH83P-0004oJ-PY for behave@ietf.org; Mon, 07 Feb 2022 18:43:58 +0100
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 4JstmT65g5z9pW for <behave@ietf.org>; Mon, 7 Feb 2022 09:43:53 -0800 (PST)
Received: from [10.5.2.16] (helo=xmail06.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nH83N-0008MO-Nm for behave@ietf.org; Mon, 07 Feb 2022 09:43:53 -0800
Received: (qmail 21251 invoked from network); 7 Feb 2022 17:43:53 -0000
Received: from unknown (HELO smtpclient.apple) (Authenticated-user:_huitema@huitema.net@[172.58.46.218]) (envelope-sender <huitema@huitema.net>) by xmail06.myhosting.com (qmail-ldap-1.03) with ESMTPA for <drc@virtualized.org>; 7 Feb 2022 17:43:53 -0000
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Christian Huitema <huitema@huitema.net>
Mime-Version: 1.0 (1.0)
Date: Mon, 07 Feb 2022 09:43:52 -0800
Message-Id: <9D44ABAB-63A1-42AD-AC0B-F8833F6DF7C7@huitema.net>
References: <3ae61684-10d1-dde6-222a-69f456dbe5e3@network-heretics.com>
Cc: David Conrad <drc@virtualized.org>, behave@ietf.org
In-Reply-To: <3ae61684-10d1-dde6-222a-69f456dbe5e3@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: iPhone Mail (19C56)
X-Originating-IP: 66.113.196.152
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.11)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT+kBr0xs2/HSqgLsQc1h5c/PUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5zVVrN4oC+7+v6H1pDHwMpu42UuDhyzVYcwl2RB+0Aaeu8t nWXdZrbiUvz668+JsuUh55uqY3MhMgFAHq5BxPxPXn36fLqvhISQ5ykyqUZqUd1jhnM/Mbva2XLV /LIEzaL2KoAZhJekBPedneT7f699iwgQ+2yl7BoDncKB+ziACIPAgTtUp75uqlx0KezvZHWM525h obRX+ccJ5ZEXtMPGWQaaSSaRcFTFxaRvADgOuFdAU5fRzM/QzQW9/IoH33AG8ECuCwECazCwODtO F78PiyQEs+dlGXUJLWZ+Gc08Nmllke3azHdKmySKNUVQl4ntlVxnbS8qIO7oudHyb2T1VQ58xe/l rqiRGalI3YPsxOTrFXToVyBmRCgQVX6zVyFUu8qzeMQP6uTHL0d9UjfY+eX5ZvcELCIKs663F/co VFYFvf25LVONYbYifH5OzZDcG6hsRQZiAIgw+z837AqgX7ewI8e1h7RITgN14BHmGVt/ReJ9Mfhz zmbKTH7wI9GEU1utNskUAORCV2WFZX0jMujG3f5uEi//7HghzjC/t6TeVLW3pB0Q/PTyowo5Afsn g+qdiMJ3xGaXkhlb9AI6CFXoGKtafvOtcW/mP16bynTCOInfd76oq4RH5afpA3RRyBl07OVp2D/S 9ogT8aIX6abOyKlLsxs8P4CT3FEuG6qJMS2HS9vixNLtqr+Qf5OC1AI9a3irbifzymzQYX+PGCcl cnXjljjaV/S9aS3Xtz2Szg10rY27j/r9OVCCeJ+KuZkMyFBGaEBYeh6pTEjU/Uebz9WOJBjPKo9/ 6sroZ36m+UeFXprlCOm3BAEbJtAT1BYHStA0OogdNtRxnRSLF+XCKxIG9XMEgRDdaWpvCv+zESlk TxdSCNcDfRohcehWBb39uS1TjWG2Inx+Ts2QNOYPIz4ynMa7pZQ4hi/HGtuWeHzx9sLaQmDwvYQn 76e9NXttZBkk6PeFqH6So31P
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/4VQ5NHiX8tnCegqz-i9RR3w-9E0>
Subject: Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/behave/>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Feb 2022 17:44:14 -0000

 

> On Feb 7, 2022, at 9:24 AM, Keith Moore <moore@network-heretics.com> wrote:
> 
> On 2/7/22 12:18, David Conrad wrote:
> 
>> ...
>> As far as I can tell, Klaus has identified a specific issue in which existing IETF specifications are deficient in order to facilitate interoperability in a specific protocol when NAT64 is in use.
> 
> To the extent that the specifications are deficient, it's because the approach was inherently deficient.

I think the approach in RFC6147 is a reasonable compromise for deploying 6to4: handle the common case for unmodified hosts; recognize that this is a kludge; steer to end-to-end solutions for all complex cases.

We are not going to undeploy NAT64, let alone NAT. But we can certainly provide guidance for implementing end to end solutions for all complex cases. Given deployment of DoH, this will be needed soon.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email