Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues

Klaus Frank <klaus.frank@posteo.de> Mon, 07 February 2022 03:01 UTC

Return-Path: <klaus.frank@posteo.de>
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 D60CB3A125F for <behave@ietfa.amsl.com>; Sun, 6 Feb 2022 19:01:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=posteo.de
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 rTC_V8yjpGhg for <behave@ietfa.amsl.com>; Sun, 6 Feb 2022 19:01:49 -0800 (PST)
Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (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 2E32F3A124A for <behave@ietf.org>; Sun, 6 Feb 2022 19:01:48 -0800 (PST)
Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 04BDB240026 for <behave@ietf.org>; Mon, 7 Feb 2022 04:01:46 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1644202906; bh=28kPAmgoBQYGxxD01i38m7wH90NSIuAmA+daJLrq3/w=; h=Date:Subject:To:From:From; b=EVE6SOi00xZ/iCR6BtTU+cMY9PZiwguYMPtMgsTr+EdMMV0NBDozA6XjBAYi3T/MY lbI6aV3Mnl+Pf2fA5QTlaDwIPle3ys9lLJvo1RlWpp6+ExDupiDD1YCR9iFB+vl3Gp NqzEXKVISjBNzQ9SYyL8QqW5xKtSUjNfg5xBSP6SiDwbUu0g0t8yeCMHFAJmeb+NuA d6c4pDm3H+FOwdwauMZV7x/rb6gU631GIA3zqm9wMQ7MAuESrmip4qWnBY+5hOVbhd z2LpVZ3+vSEqBtGgasTX17pBEXzD/P/+8aKZ8+vPx/+g7BmsSpcWylyS+szui8QwWN OL9UiWl/L+UFg==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4JsWBc3pS1z6tm4; Mon, 7 Feb 2022 04:01:44 +0100 (CET)
Message-ID: <560f2cdc-a315-58a3-eb4f-96a1d6d1dec5@posteo.de>
Date: Mon, 07 Feb 2022 03:01:42 +0000
MIME-Version: 1.0
Content-Language: en-US
To: Keith Moore <moore@network-heretics.com>, Christian Huitema <huitema@huitema.net>, behave@ietf.org
References: <45e423cc-4095-cca2-bf8c-aa15e977b19c@posteo.de> <ff858dee-a21a-a50d-72a5-da7915ac2de4@network-heretics.com> <71b5cdb0-78af-0f77-debc-84e178fe5e3a@posteo.de> <7a008cc2-e8a3-f91d-c782-96866c36a9db@network-heretics.com> <ee760818-a3c4-3755-6bdf-afcec6fcaaad@posteo.de> <B7DFC369-E7B7-4171-9C85-F75986B5AEF6@gmail.com> <6123a322-e9a7-7f90-391f-9b4c4461ce45@network-heretics.com> <e95993e4-4166-4b3d-1637-8ca451b093b6@huitema.net> <7b7cf541-3387-6d0b-0fbe-273a08fd37ed@posteo.de> <0d18c171-f713-4590-d9a6-3c5729a3384c@huitema.net> <a4dbfa8c-abb4-e4e7-e53c-d7f54a2e5bf9@posteo.de> <f2aee64b-658f-7d12-6409-cff2c8a0df3e@network-heretics.com>
From: Klaus Frank <klaus.frank@posteo.de>
In-Reply-To: <f2aee64b-658f-7d12-6409-cff2c8a0df3e@network-heretics.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms010700030609080402030903"
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/GIEN9NQuYSiggr_Kry76kSs-wek>
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 03:01:55 -0000

🙄This is just anti DNS64 all together... Can we assume for the sake of 
this discussion that one actually wants to use the DNS64 resolver?

On 2022-02-07 03:55, Keith Moore wrote:
> On 2/6/22 21:48, Klaus Frank wrote:
>
>> Also the noted "smtp server and DNS may not be under the same 
>> management" is also one of the reasons why it should be within DNS64. 
>
> Disagree.  One of the general problem with DNS, BTW, is that the 
> people who operate the DNS servers and the people who operate the 
> applications that require correct DNS configuration are often not the 
> same people, and often don't even work with the same company. So DNS 
> already gets out-of-sync with reality too often as it is.
>
> If a NAT takes it upon itself to alter DNS records in flight, there's 
> even more potential for the DNS to get out-of-sync with reality, and 
> three different parties that have to potentially be reconciled to fix 
> the problem.
>
> Of course this is a big reason that applications are increasingly 
> using DoH or DoT to query a trusted server whenever possible - to 
> minimize the potential for some third party to have screwed things up.
>
> Keith
>
>