IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

Philip Homburg <pch-dnsop-3@u-1.phicoh.com> Wed, 10 July 2019 13:48 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 E13DE120140 for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2019 06:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 VLyEKJ_SPdML for <dnsop@ietfa.amsl.com>; Wed, 10 Jul 2019 06:48:47 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2125E1200F7 for <dnsop@ietf.org>; Wed, 10 Jul 2019 06:48:46 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1hlCxh-0000KdC; Wed, 10 Jul 2019 15:48:45 +0200
Message-Id: <m1hlCxh-0000KdC@stereo.hq.phicoh.net>
To: dnsop@ietf.org
From: Philip Homburg <pch-dnsop-3@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.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> <F7952048-F71F-4140-80B2-AC7CDE7EEF31@rfc1035.com>
In-reply-to: Your message of "Wed, 10 Jul 2019 14:37:10 +0100 ." <F7952048-F71F-4140-80B2-AC7CDE7EEF31@rfc1035.com>
Date: Wed, 10 Jul 2019 15:48:43 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lDGEDuqxw9oyKArosWRwN38ntSc>
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:48:49 -0000

> > As far as I know, there is no issue with whois and the GDRP when it comes
> > to voluntarily publishing information in whois.
> 
> Nope. Its 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.

When you register a domain, your registrar already has to have your informed
consent to process any PII you supply. And as far as I know,
registrars routinely ask for your name and credit card.

So all GDRP-related processes are already in place.

Looking at it from a technical point of view, whois has a referal mechanism.
So if GDRP compliance would be a big issue, then allowing the handful of
people who wish to publish anything in whois to run their own whois server
would also solve the issue.

v2.23.0 | Report a Bug | By Email