Re: [Doh] GDPR and DoH

Jim Reid <jim@rfc1035.com> Sun, 07 April 2019 13:34 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29DD120491 for <doh@ietfa.amsl.com>; Sun, 7 Apr 2019 06:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BIE2Plb22UWE for <doh@ietfa.amsl.com>; Sun, 7 Apr 2019 06:34:08 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD7AB120490 for <doh@ietf.org>; Sun, 7 Apr 2019 06:34:07 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id A903B242109D; Sun, 7 Apr 2019 13:34:04 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <5ce0d730-aac2-95c9-fead-64cbffa03d52@cs.tcd.ie>
Date: Sun, 7 Apr 2019 14:33:56 +0100
Cc: DoH WG <doh@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE840785-E355-4BCA-A9E1-AFFA069D801C@rfc1035.com>
References: <1700920918.12557.1552229700654@appsuite.open-xchange.com> <7667c4d7-2e78-0a27-84af-cf1c00fd4897@cs.tcd.ie> <1991054337.12802.1552259263075@appsuite.open-xchange.com> <eea64b30-aad0-a030-5360-1b1484f1d0e3@huitema.net> <CAPsNn2WhjHSEHJUEL8GB6X0d24fkajgPnY4YgkOQbXjyxb5q8Q@mail.gmail.com> <CACfw2hj07TDCxK9bm0T=JguKyuCEfW2zb_yRJnewjOYL4oxdjA@mail.gmail.com> <CACsn0cmk7NbF+ti0dU7Fp0PK8Gt4P5knC5hrHVLDY59-jaYYzA@mail.gmail.com> <6030358E-24FF-4033-B0A1-AB1123FED964@rfc1035.com> <5ce0d730-aac2-95c9-fead-64cbffa03d52@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/PZN3SJnwHsH7cv3Kl5UQbHy8lxw>
Subject: Re: [Doh] GDPR and DoH
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Apr 2019 13:34:11 -0000


> On 6 Apr 2019, at 19:53, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> FWIW, I also don't get the GDPR angle here. If it's meant as
> an issue of consent related to selection of DNS server....
> 
> So can you explain the specific GDPR-related issue that you
> think is relevant?

Hi Stephen. When has relevance ever mattered on an IETF list? :-)

From a strict protocol design perspective, GDPR issues probably never matter for the IETF. After all the IETF doesn’t exist so it can’t be sued or prosecuted. GDPR does however have an impact on how IETF protocols get used and deployed. Sometimes that might impact need to be assessed in an IETF setting, just like how IETF docs are expected to have security and human rights considerations these days.

GDPR is already covered in the T&Cs between an ISP and the end user. Or should be. [You’ve probably been bombarded by GDPR tweaks to the T&Cs for your bank, utility providers, etc.] When DoH is used, this is likely to introduce third parties - the DoH service provider and a DoH client. GDPR compliance will be an issue for them, particularly the requirement to get meaningful consent from the end user. How these third parties do that is unlikely to be a topic for the IETF.

That said, I think it’s important that this WG is at least aware of these problems and documents them somehow. ie It produces an RFC which somewhere says something like "If you’re responsible for a DoH platform, make sure you’ve sorted out the GDPR concerns”.