[Doh] Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh

Paul Hoffman <paul.hoffman@icann.org> Wed, 16 January 2019 00:26 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 867DC130F2F for <doh@ietfa.amsl.com>; Tue, 15 Jan 2019 16:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id MNkE_zE0Mg0X for <doh@ietfa.amsl.com>; Tue, 15 Jan 2019 16:25:58 -0800 (PST)
Received: from out.west.pexch112.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 4B16612D4F2 for <doh@ietf.org>; Tue, 15 Jan 2019 16:25:58 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org ( by PMBX112-W1-CA-2.pexch112.icann.org ( with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 15 Jan 2019 16:25:56 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1367.000; Tue, 15 Jan 2019 16:25:56 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: DoH WG <doh@ietf.org>
Thread-Topic: Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh
Thread-Index: AQHUrTILL2Y/75+a40yYwQM5QYeIWA==
Date: Wed, 16 Jan 2019 00:25:55 +0000
Message-ID: <8999D6F3-600E-4F1A-903C-10F8CAA6E4F3@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/signed; boundary="Apple-Mail=_699AC2E1-2CAA-4EF3-B70E-780747A21EE9"; protocol="application/pkcs7-signature"; micalg=sha-256
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/IWNS6f_x1vEmqqQ8Rkgfa_UVZes>
Subject: [Doh] Request for the DOH WG to adopt draft-hoffman-resolver-associated-doh
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, 16 Jan 2019 00:26:01 -0000

Greetings again after a long time. The still-alive DOH WG did not meet at IETF 103. However, I did a short presentation on "Associating a DoH Server with a Resolver" (https://datatracker.ietf.org/doc/draft-hoffman-resolver-associated-doh/) at the DNSOP WG. The presentation ended with the question of whether the draft should be taken up in a WG, and if so, where. Since then, there has been some off-list discussion that kinda ended up as "first see if the DOH WG wants to take it up".

People from a few browser vendors have expressed unofficial interest in implementing at least parts of it if it gets standardized, so it seems like a good idea to try to standardize it. There is still a reasonable amount of work to be done in the document itself, and it certainly needs input from both browser and DNS folks.

So, does this WG want to adopt this as a work item?

--Paul Hoffman