Re: [Doh] [Ext] Privacy Considerations Text (#2)

[Mateusz Jończyk <[e-mail]>]

W dniu 22.06.2018 o 17:42, Paul Hoffman pisze:
> On Jun 22, 2018, at 8:34 AM, Mateusz Jończyk <[e-mail]> wrote:
>> W dniu 21.06.2018 o 20:43, Patrick McManus pisze:
>>> ## In The Server {#InTheServer}
>>>
>>> A DoH application is built on IP, TCP, TLS, and HTTP. Each layer
>>> contains one or more common features that can be used to correlate
>>> different queries to the same identity. DNS transports will generally
>>> carry the same privacy properties of the layers used to implement
>>> them. For example, the properties of IP, TCP, and TLS apply to DNS
>>> over TLS implementations.
>>
>> The sentence above is misleading. We are talking about DOH, not DNS over TLS.
> 
> Earlier, the WG wanted the document to compare (where appropriate) DoH and DoT. 
> It seems appropriate to do so in the privacy considerations to show that DoH > has one more layer that can  make user tracking more possible.
> 
OK

>>>
>>> The privacy considerations of using the HTTPS layer in DoH are
>>> incremental to those of DNS over TLS. DoH is not known to introduce
>>> new concerns beyond those associated with HTTPS.
>>
>> I have been thinking that a DoH client would open a long-running connection to a
>> DoH server. In such a case, request correlation could be simple and we should
>> drop the "is not known to introduce new concerns" sentence.
> 
> Both RFC 7766 (DNS in TCP) and RFC 7858 (DNS in TLS) recommend opening long-running connections, and explain the operational pros and cons of doing so.
> 

OK, now I have read that passage again and understand it.
I would argue that this should be discussed explicitly in the "Privacy
considerations" section.

Greetings,
Mateusz Jończyk