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

[nusenu <[e-mail]>]

Patrick McManus wrote:
> That's mostly true imo (modulo perhaps edns client subnet)
> 
> Using HTTPS as a transport therefore introduces
>> + new privacy concerns over DNS over UDP, TCP or TLS (RFC7858) with regard
>> to
>> + additional data that may be visible to a DoH server compared to a DNS
>> resolver.
>>
>>
> I do agree that HTTP adds additional considerations, which is what the
> existing text describes. But I don't agree with this sentence which,
> significantly through the use of therefore, indicates HTTPS has client
> identifiers and other transports do not.
> 
> The previous several paragraphs have enumerated client identifiers also
> present in IP (therefore UDP), TCP, and TLS. Everything that transports
> wireformat.
> 
> What if, instead, we add a new first paragraph to the "In the server"
> section along the lines of
> 
> "The original DNS wireformat contains no client identifiers, however
> various transports of the DNS wireformat do provide data that can be used
> for request correlation. HTTPS presents new considerations for correlation
> ranging from explicit HTTP cookies to implicit fingerprinting of the unique
> set and ordering of request headers."


"various transports" is less specific than previous proposals.

Note the delta between "HTTPS presents new considerations for correlation" and clearly stating: "introduces new privacy concerns" (previously proposed)

Generally speaking I consider this less frank about the privacy implications of DoH than previous proposals
from Sara but it is understandable that draft authors dislike having "introduces new privacy concerns" in their draft.

>> + ### HTTP Specific considerations (#HTTPconsiderations)
>>
>>
> I think this is largely what the paragraph that begins "The DoH protocol
> design allows applications to fully leverage.." is conveying. Maybe it can
> move towards what you are thinking.. wdyt of:
> 
> 
> The DoH protocol design allows applications to fully leverage the HTTP
> ecosystem, including features not enumerated here. Utilizing the full
> set of HTTP features enables DoH to be more than an HTTP tunnel, but
> also opens implementations up to the full set of privacy
> considerations of HTTP.

also here, note "considerations" vs. "concerns"
 
I find Sara's version made it more clear that here has been made a 
deliberate design decision to accept the privacy concerns 
to retain full functionality.





-- 
https://twitter.com/nusenu_
https://mastodon.social/@nusenu