Re: [Doh] New Privacy Considerations Section Proposal

[Howard Chu <[e-mail]>]

Adam Roach wrote:
> [as an individual]
> 
> I agree with Patrick's analysis here, and think the proposed text (plus the 
> "minimal set of data" statement below) is likely to serve the purpose well. In 
> particular, I agree with Patrick that the various features that have been 
> cited so far each serve a useful purpose, and that such purposes may have a 
> place in DoH deployments. Giving implementors a heads up about the privacy 
> trade-offs seems appropriate. Mandating (MUST or SHOULD) that DoH runs over a 
> minimal profile of HTTP seems to remove several of the advantages of using 
> HTTP at all.

That's overstating things. It seems the primary benefit is being able to hide 
DoH traffic within standard HTTPS traffic, making it more difficult to filter 
out at firewalls. That benefit remains, even if barebones HTTP requests are used.

>> On Wed, Jun 20, 2018 at 6:14 PM, Ted Hardie <[e-mail] 
>> <mailto:[e-mail]>> wrote:
>>
>>     Repeating the comment I made at Github:
>>
>>     Is there a reason not to make a recommendation for the case of a
>>     DOH-only service? The current text says:
>>
>>     Implementations of DoH clients and servers need to consider the benefit
>>     and privacy impact of all these features, and their deployment context,
>>     when deciding whether or not to enable them.
>>
>>     Would you consider a recommendation like "For DOH clients which do not
>>     intermingle DOH requests with other HTTP suppression of these headers
>>     and other potentially identifying headers is an appropriate data
>>     minimization strategy."?

I would expect this to be the common case - most of the time, clients' HTTP(s) 
traffic will be to a wide variety of web servers, but only a single DNS/DoH 
server. And that particular DNS/DoH server is unlikely to be serving any 
interesting web pages for any clients. As such, the frequency of intermingled 
connections should be low-to-zero.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/