IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

Jim Reid <jim@rfc1035.com> Wed, 10 July 2019 13:37 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 BA47C120047 for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2019 06:37:16 -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 6PXyQSnX09lc for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2019 06:37:14 -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 3567312003F for <dnsop@ietf.org>; Wed, 10 Jul 2019 06:37:14 -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 E5FB0242109D; Wed, 10 Jul 2019 13:37:11 +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: <m1hlCac-0000FUC@stereo.hq.phicoh.net>
Date: Wed, 10 Jul 2019 14:37:10 +0100
Cc: dnsop WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7952048-F71F-4140-80B2-AC7CDE7EEF31@rfc1035.com>
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <233E0AD8-97FE-466C-9B6C-D7A376031C3B@rfc1035.com> <93244821-6C22-457F-BA06-CF43CA9FD12B@bambenekconsulting.com> <EDE98437-E0B8-4B2E-8AA5-2F6B0079CE8B@hopcount.ca> <0ece2408-a1ec-fa5f-f8d1-ff65572de1ed@bambenekconsulting.com> <B520D17D-F258-41C3-97DD-3CE5C3A8E952@hopcount.ca> <6F0B44AA-902D-46E9-9E3B-DB88F5AC1419@isc.org> <A7A3C5BB-2705-47F2-9870-19552756423B@bambenekconsulting.com> <m1hlCac-0000FUC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-dnsop-3@u-1.phicoh.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/sxGGuzDNWTXRzWwLKvz759OUkKg>
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: Wed, 10 Jul 2019 13:37:17 -0000


> On 10 Jul 2019, at 14:24, Philip Homburg <pch-dnsop-3@u-1.phicoh.com> wrote:
> 
> As far as I know, there is no issue with whois and the GDRP when it comes
> to voluntarily publishing information in whois.

Nope. It’s OK for you to publish your Personal Data. For anything else, you need to get informed consent first. And be able to prove that. And give the Data Subjects the ability to modify those data or get them deleted.

v2.23.0 | Report a Bug | By Email