IETF Logo Mail Archive

Re: [Doh] [Ext] Re: New version: draft-ietf-doh-resolver-associated-doh-03.txt

Paul Hoffman <paul.hoffman@icann.org> Sun, 24 March 2019 09:58 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 6DABD127979 for <doh@ietfa.amsl.com>; Sun, 24 Mar 2019 02:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 gLTUQdhYg1zY for <doh@ietfa.amsl.com>; Sun, 24 Mar 2019 02:58:32 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.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 D393012785F for <doh@ietf.org>; Sun, 24 Mar 2019 02:58:32 -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.1367.3; Sun, 24 Mar 2019 02:58:30 -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.1367.000; Sun, 24 Mar 2019 02:58:30 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Joseph Lorenzo Hall <joe@cdt.org>
CC: DoH WG <doh@ietf.org>
Thread-Topic: [Ext] Re: [Doh] New version: draft-ietf-doh-resolver-associated-doh-03.txt
Thread-Index: AQHU4hptyKjcm1FcoU67W4LREZZQWKYa9IIAgAAM5IA=
Date: Sun, 24 Mar 2019 09:58:29 +0000
Message-ID: <09A84CEA-2228-4DF0-93DB-7512F6FA755F@icann.org>
References: <155341529409.18062.10657099011172813446@ietfa.amsl.com> <55AE7511-5BDF-4E96-84B3-BD0B6E6C6FE3@icann.org> <CABtrr-WX3UVnT1ZEkVoP-njqvBRwDTtd0tofgjjrmX6c=JhKhg@mail.gmail.com>
In-Reply-To: <CABtrr-WX3UVnT1ZEkVoP-njqvBRwDTtd0tofgjjrmX6c=JhKhg@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: <F61E614F5CDF1E4DB518DD5AADC7BD8D@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/ambwqJc833bJepIYXr-qLH_KE18>
Subject: Re: [Doh] [Ext] Re: New version: draft-ietf-doh-resolver-associated-doh-03.txt
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 24 Mar 2019 09:58:34 -0000

Thanks for the quick read!

On Mar 24, 2019, at 10:12 AM, Joseph Lorenzo Hall <joe@cdt.org> wrote:
> 
> Couple of small things:
> 
> typo, Intro: "Users typically configure their DNS recursive resolvers with through automatic configuration"

Fixed.

> I don't get the "Do53" abbreviation, but I'll grab you and maybe you can help me make sense of it (a very small thing considering you could have said DoPotatoes or whatever).

I thought it was clearer than than "DoU/T". It is short for "DNS over port 53".

> Are there any outcomes you can see where IANA is compelled to delegate the SUDNs here?

No, very definitely not. That's why the "IANA Considerations" say explicitly MUST NOT. IANA follows the rules from the RFCs defining new entries.

> Or where an authoritarian government might require resolvers to collide, if that makes sense?

Governments, authoritarian or not, can intercede in the DNS in many ways.

> In privacy considerations the draft says, "can increase communication privacy because of the TLS protection." I'm wondering if it makes sense to say explicitly "confidentiality and integrity" in a parenthetical near privacy?

Sure.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email