Re: [Doh] GDPR and DoH

[Brian Dickson <[e-mail]>]

On Sat, Apr 6, 2019 at 3:20 PM Adam Roach <[e-mail]> wrote:

> On 4/6/19 5:08 PM, Brian Dickson wrote:
> > Again, the above is MHO, but also, this consent problems is an issue
> that crosses over the line where leaving it unsettled by stating it is an
> issue we don’t agree to, does a disservice to the community of users of DNS.
>
>
> Engineers and lawyers practice rather different professions, both of
> which require extensive training and experience. When all the dust
> settles, it really doesn't matter what *we* think on these topics, in
> much the same way that it's not terribly important what the American Bar
> Association might think about TCP window size management. Jim and Watson
> both wisely deferred, at least in the abstract, to legal experts. I
> advise that this is the proper tactic.
>

Maybe, yes, and no. The problem in the above is the use of pronouns. :-)

But seriously, there are multiple variations on the issue, where the need
for lawyers, and/or the length and depth of those discussions, vary
considerably.

The possibilities I see include the following (and possibly others, such as
DoT):

   - DoH is off by default, and the DoH server field is empty (requires
   explicit user entry)
   - DoH is off by default, and the DoH server field is a drop-down list
   plus "other" (user entered), with no selected choice
   - DoH is off by default, and the DoH server field is a drop-down list or
   user-entry field, pre-populated with the system's configured DNS entries
   (static or DHCP-provided)
   - DoH is off by default, and the DoH server field is a drop-down list or
   user-entry field, pre-populated with something other than the system's
   configured DNS entries
   - DoH upgrade is on by default,  and the DoH server field is a drop-down
   list or user-entry field, pre-populated with the system's configured DNS
   entries (static or DHCP-provided)
   - DoH is on by default, and the DoH server field is a drop-down list or
   user-entry field, pre-populated with something other than the system's
   configured DNS entries

In the above cases where there is no pre-populated entry, or the system
server is what is pre-populated, I would expect a conversation with a
lawyer knowledgable in the field to be very brief.
"The only way the user can change their DNS resolver choice is by actively
typing text or doing a list-select? Okay, sounds good."
"Turning on DoH doesn't change the DNS provider? Great."
"Can the user force the resolver operator to use DoH, or does the operator
also have to enable DoH? Has to enable it? Great."

For the other cases, I agree with Jim and Watson. I wanted to make the
distinction above, since those are apples and oranges (rooted in changing
the DNS provider, irrespective of anything else).

Brian