Re: [DNSOP] New draft for helping browsers use the DoH server associated with a resolver

"John Dickinson" <> Fri, 31 August 2018 14:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5E962130DE8 for <>; Fri, 31 Aug 2018 07:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id TB34c9NrXXej for <>; Fri, 31 Aug 2018 07:39:29 -0700 (PDT)
Received: from ( [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EC5D8130E4D for <>; Fri, 31 Aug 2018 07:39:28 -0700 (PDT)
Received: from [2001:b98:204:102:fff1::f145] (port=51753 helo=[]) by with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <>) id 1fvka2-0001dR-Jq; Fri, 31 Aug 2018 15:39:26 +0100
From: "John Dickinson" <>
To: "Paul Hoffman" <>
Cc: dnsop <>
Date: Fri, 31 Aug 2018 15:36:29 +0100
X-Mailer: MailMate (1.11.3r5509)
Message-ID: <>
In-Reply-To: <>
References: <>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BlackCat-Spam-Score: 0
Archived-At: <>
Subject: Re: [DNSOP] New draft for helping browsers use the DoH server associated with a resolver
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 31 Aug 2018 14:39:32 -0000

Hi Paul,

Just trying to read this draft in detail and I find section 3 a bit 
confusing. You use terms such as client and resolver but at times it is 
not clear if you are referring to the OS stub, a third party stub, 
caching resolver, application or browser. Maybe using terms from your 
terminology draft would help.


On 24 Aug 2018, at 1:01, Paul Hoffman wrote:

> Greetings again. Some of the people in the recent thread about 
> "dynamic discovery of secure resolvers" have expressed an interest in 
> something that was mentioned at the DRIU BoF in Montréal: they want 
> their browser to use a DoH server that is related to the DNS resolver 
> that their OS is already using. I don't think DHCP can help with that 
> problem (I could be wrong), but I do think that resolver operators 
> should be able to tell browsers the DoH resolvers that they would want 
> their customers to be using.
> Please see the draft below. If folks like it, I can continue to work 
> on it. Or, if you like the use case but have a better technical 
> solution, that would be great too. I wanted to bring it to this list 
> before taking it to the DOH WG because it really is an operational 
> issue, not all that related to the DoH protocol.
> Thoughts?
> --Paul Hoffman
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories.
> Title : Associating a DoH Server with a Resolver
> Author : Paul Hoffman
> Filename : draft-hoffman-resolver-associated-doh-00.txt
> Pages : 8
> Date : 2018-08-23
> Abstract:
> Some clients will want to know if there are one or more DoH servers
> associated with the DNS recursive resolver that the client is already
> using. This document describes a protocol for a resolver to tell a
> client what its associated DoH servers are.
> The IETF datatracker status page for this draft is:
> There are also htmlized versions available at:
> Please note that it may take a couple of minutes from the time of 
> submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> DNSOP mailing list

John Dickinson

Sinodun Internet Technologies Ltd.
Magdalen Centre
Oxford Science Park
Robert Robinson Avenue
Oxford OX4 4GA