[Doh] Maybe moving draft-ietf-doh-resolver-associated-doh to draft-sah-resolver-information

Paul Hoffman <paul.hoffman@icann.org> Wed, 22 May 2019 22:49 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E99B41200B7 for <doh@ietfa.amsl.com>; Wed, 22 May 2019 15:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id kxrv-McUffxi for <doh@ietfa.amsl.com>; Wed, 22 May 2019 15:49:47 -0700 (PDT)
Received: from mail.icann.org (out.west.pexch112.icann.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0FB0120088 for <doh@ietf.org>; Wed, 22 May 2019 15:49:47 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org ( by PMBX112-W1-CA-1.pexch112.icann.org ( with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 22 May 2019 15:49:46 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1367.000; Wed, 22 May 2019 15:49:46 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: doh WG <doh@ietf.org>
Thread-Topic: Maybe moving draft-ietf-doh-resolver-associated-doh to draft-sah-resolver-information
Thread-Index: AQHVEPCmpYtbMN8MwEyatKtOZMXDNA==
Date: Wed, 22 May 2019 22:49:45 +0000
Message-ID: <21EA7A61-2E10-431E-871F-CCE89728836F@icann.org>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6776AC099CEB7B4CAC706A404744243A@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/98frpM7cFeEl1SL0p69QP6ZB4ew>
Subject: [Doh] Maybe moving draft-ietf-doh-resolver-associated-doh to draft-sah-resolver-information
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: Wed, 22 May 2019 22:49:49 -0000

Greetings again. For those in the DOH WG who are not also in the DNSOP WG, you may not have seen that Puneet Sood, Roy Arends and I have new drafts that would replace draft-ietf-doh-resolver-associated-doh. During IETF 104, and on this list, people asked why the mechanisms in draft-ietf-doh-resolver-associated-doh were only for DoH. In response, we created draft-sah-resolver-information and draft-sah-resinfo-doh. The former is a general way of asking resolvers for information about them; the latter is the definition of the DoH-related information.

We've used the DNSOP WG mailing list to get input on the drafts, with the hope that the DNSOP WG will adopt the drafts soon so we can move the work from draft-ietf-doh-resolver-associated-doh to the more general solution. We have not yet asked for WG adoption, but will likely do so after people see these new drafts.

Both Google and Mozilla have said here that they look forward to a way to find the DoH server associated with a user's resolver, so we hope that the work can move forward at a reasonable pace. However, if people in this WG think we're doing it wrong by having a general mechanism for querying resolvers, please speak up here.

--Paul Hoffman