IETF Logo Mail Archive

Re: [Doh] [Ext] DNS64 and DOH

Paul Hoffman <paul.hoffman@icann.org> Mon, 19 March 2018 10:19 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 603D4126CE8 for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 03:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 0v4dRIyYmTla for <doh@ietfa.amsl.com>; Mon, 19 Mar 2018 03:19:18 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44842126CBF for <doh@ietf.org>; Mon, 19 Mar 2018 03:19:18 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 19 Mar 2018 03:19:16 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Mon, 19 Mar 2018 03:19:16 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Erik Nygren <erik+ietf@nygren.org>
CC: DoH WG <doh@ietf.org>
Thread-Topic: [Ext] [Doh] DNS64 and DOH
Thread-Index: AQHTvu43kfOSXubl4Um8L8KFA2lIOqPXzvOA
Date: Mon, 19 Mar 2018 10:19:16 +0000
Message-ID: <C03FF16F-CA2A-40AD-9138-C0F089ADA832@icann.org>
References: <CAKC-DJjtHE89A=vG5iS_0M_jqnWusDUDnwyernd+FC1VxxmU5Q@mail.gmail.com>
In-Reply-To: <CAKC-DJjtHE89A=vG5iS_0M_jqnWusDUDnwyernd+FC1VxxmU5Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <64A58650D035CC47B5E20F6819DAFBD1@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/FK5St3e-6Y2tMSVXA1mpMiO9qOY>
Subject: Re: [Doh] [Ext] DNS64 and DOH
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2018 10:19:19 -0000

On Mar 18, 2018, at 7:20 PM, Erik Nygren <erik+ietf@nygren.org> wrote:
> At least for mobile, not using DNS64 synthesis in the client will likely result in this either breaking the client in NAT64 environments or causing something lower in the stack to do the equivalent (a 464xlat CLAT on Android or bump-in-the-API on iOS).
>  

This is true for DNS64 in any environment, not just DOH, correct? If a client has two resolvers configured and only one is doing DNS64, or they are doing it differently, you have the same problem, yes?

--Paul Hoffman

v2.23.0 | Report a Bug | By Email