IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

Jim Reid <jim@rfc1035.com> Tue, 09 July 2019 15:27 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92496120642 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 rhtDx7De_qnb for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:27:07 -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 7F7851204FC for <dnsop@ietf.org>; Tue, 9 Jul 2019 08:27:07 -0700 (PDT)
Received: from wallace.rfc1035.com (hutch.rfc1035.com [195.54.233.70]) (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 1995A24211C0; Tue, 9 Jul 2019 15:27:05 +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: <mAakCAacGpsKdvoi8MI7DM6aAZGudPx3DLh77azT2353@mailpile>
Date: Tue, 09 Jul 2019 16:27:04 +0100
Cc: dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1782C96A-BC85-4138-9E1B-1C90567B4771@rfc1035.com>
References: <1ff4dcb0-f8aa-6fcd-eafd-ec8fe9a633ea@bambenekconsulting.com> <mAakCAacGpsKdvoi8MI7DM6aAZGudPx3DLh77azT2353@mailpile>
To: John Bambenek <jcb@bambenekconsulting.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DqBBvQ1Y5rq9maV4lbCP_3Hf38c>
Subject: Re: [DNSOP] Proposal: Whois over DNS
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2019 15:27:09 -0000

> John Bambenek <jcb@bambenekconsulting.com> wrote:
> 
> > Why? GDPR applies to IP addresses that, doesn't impact DNS yet.

GDPR applies to *any* data which identifies a living European citizen.

If you think it only applies to IP addresses you are very badly mistaken. GDPR will also apply to anything in the DNS which happens to identify a living European citizen.

v2.23.0 | Report a Bug | By Email