IETF Logo Mail Archive

Re: [BEHAVE] RFC6147 and RFC7208 interoperability issues

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 07 February 2022 18:49 UTC

Return-Path: <prvs=1037410fe8=jordi.palet@consulintel.es>
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 85A103A1107 for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 10:49:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 0d9xVIkgQJl8 for <behave@ietfa.amsl.com>; Mon, 7 Feb 2022 10:49:11 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id 1EEB03A1106 for <behave@ietf.org>; Mon, 7 Feb 2022 10:49:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1644259748; x=1644864548; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=+tfL/lIc fgg55sLy7oX9xuskWjcSeJy6D+ET4/+a+MU=; b=YFzCZZKya1Dgt2ROQ4C/SpWx 6WBP6nEHCaEc4ZUXmvXwszN7DAWnpcAIscirBkBzlxjz4d8nYOhKhFpwCqPFEVZV PCv6fr3VUakYPtI2uYcv7n/3qbY8PdE8qjJ7So7gLFTafgLHDCyAOiT7JrCcqx1T NiflH3bHEPVHAiJ14N8=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Mon, 07 Feb 2022 19:49:08 +0100
X-Spam-Processed: mail.consulintel.es, Mon, 07 Feb 2022 19:49:06 +0100
Received: from [10.10.10.105] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000799977.msg for <behave@ietf.org>; Mon, 07 Feb 2022 19:49:06 +0100
X-MDRemoteIP: 2001:470:1f09:495:8565:ead9:3b9f:b14e
X-MDHelo: [10.10.10.105]
X-MDArrival-Date: Mon, 07 Feb 2022 19:49:06 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1037410fe8=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: behave@ietf.org
User-Agent: Microsoft-MacOutlook/16.59.22020201
Date: Mon, 07 Feb 2022 19:49:02 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: behave@ietf.org
Message-ID: <896B2818-975A-49FD-A691-FD20EE262603@consulintel.es>
Thread-Topic: [BEHAVE] RFC6147 and RFC7208 interoperability issues
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> <50b919ba-22e5-cfd0-5e44-b905d42c50b7@it.uc3m.es> <8c10d7d6-ad60-2373-c809-1b75b8d1448c@huitema.net> <ab06597f-d312-1707-7d46-95ff00eb5bda@posteo.de>
In-Reply-To: <ab06597f-d312-1707-7d46-95ff00eb5bda@posteo.de>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/behave/JN1bZnXXZK_FZjvWcWhwsc8q1vY>
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 18:49:20 -0000

And those resolvers will not work if instead of the WKP a NSP is being used.

https://datatracker.ietf.org/doc/rfc8683/

Regards,
Jordi
@jordipalet
 
 

El 7/2/22 19:39, "Behave en nombre de Klaus Frank" <behave-bounces@ietf.org en nombre de klaus.frank@posteo.de> escribió:

    Cloudflare and google both have also DNS64 revolvers exactly for that 
    reason...

    On 2022-02-07 19:03, Christian Huitema wrote:
    > Maybe. But the situation has changed since April 2011. ISPs cannot any 
    > more assume that all hosts will be using the resolver embedded in the 
    > NAT64 gateway -- some hosts, or some applications, may very well use 
    > some alternate encrypted DNS service, e.g., using DoH and connect to 
    > Quad9, Cloudflare or Google. The cases describe in section 6 of 
    > RFC6147 are going to be more and 
    _______________________________________________
    Behave mailing list
    Behave@ietf.org
    https://www.ietf.org/mailman/listinfo/behave



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

v2.23.0 | Report a Bug | By Email