IETF Logo Mail Archive

Re: [Doh] GDPR and IETF protocols

Jim Reid <jim@rfc1035.com> Tue, 12 March 2019 15:44 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 5FE4E13121C for <doh@ietfa.amsl.com>; Tue, 12 Mar 2019 08:44:53 -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 iDIa7dDOiE8j for <doh@ietfa.amsl.com>; Tue, 12 Mar 2019 08:44:52 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D630613118A for <doh@ietf.org>; Tue, 12 Mar 2019 08:44:51 -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 80AD924211EE; Tue, 12 Mar 2019 15:44:43 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <20190312152556.ivzzvz6kcexkkxhq@nic.fr>
Date: Tue, 12 Mar 2019 15:44:42 +0000
Cc: DoH WG <doh@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <76DC1BD1-98A6-4F51-AB33-957061359099@rfc1035.com>
References: <155218771419.28706.1428072426137578566.idtracker@ietfa.amsl.com> <FACB852B-4BC4-4234-A728-9068708EFB10@rfc1035.com> <20190310080101.GA11452@laperouse.bortzmeyer.org> <1964B641-FA66-4245-82B4-1351AA042BD2@rfc1035.com> <20190312152556.ivzzvz6kcexkkxhq@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/M-7iJp7og8H955aXkf8CVRS3dgQ>
Subject: Re: [Doh] GDPR and IETF protocols
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: Tue, 12 Mar 2019 15:44:59 -0000


> On 12 Mar 2019, at 15:25, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> 
> But in the case of DoH, I'm not sure it is the case. The GDPR issues
> seem very close to the issues of HTTP.

Some GDPR issues are the same for both DoH and HTTP. After all the protocol for the former is a subset of the protocol for the latter. However there are additional GDPR issues for DoH. An obvious one is the underlying query data.

v2.23.0 | Report a Bug | By Email