Re: [DNSOP] Proposal: Whois over DNS

John Bambenek <jcb@bambenekconsulting.com> Tue, 09 July 2019 15:14 UTC

Return-Path: <jcb@bambenekconsulting.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 7B6C912049D for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bambenekconsulting.com
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 ALmNEQ6dPfN9 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:14:24 -0700 (PDT)
Received: from chicago.bambenekconsulting.com (chicago.bambenekconsulting.com [99.198.96.122]) (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 A3C1D120165 for <dnsop@ietf.org>; Tue, 9 Jul 2019 08:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bambenekconsulting.com; s=default; h=Content-Transfer-Encoding:Content-Type :In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject: Sender:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=TLxl7BLOjTuQBvxxIwMxaZaPG/hvDVDfe09R5tTGgr4=; b=ZcrIkeC0hVUrJ6hhc+YKelBsoj dzowzsARKmfxkniqwgSZrJHHMUgnVOL0xJ2n8R7ygAXZyqJRbZWey6EOvPYOS1ODbSSN4iLQzrUo+ O9AU2tufDqzL1CHxD5Ap46jQWCmgj+w/2ypHrKeAVIf9GYIANt0CiwlwP7GgenEM5dH0=;
Received: from [216.169.1.210] (port=21722 helo=jcb.local) by chicago.bambenekconsulting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <jcb@bambenekconsulting.com>) id 1hkroq-0000n4-7h; Tue, 09 Jul 2019 11:14:12 -0400
To: Bjarni Rúnar Einarsson <bre@isnic.is>
Cc: Jim Reid <jim@rfc1035.com>, dnsop@ietf.org
References: <1ff4dcb0-f8aa-6fcd-eafd-ec8fe9a633ea@bambenekconsulting.com> <mAakCAacGpsKdvoi8MI7DM6aAZGudPx3DLh77azT2353@mailpile>
From: John Bambenek <jcb@bambenekconsulting.com>
Openpgp: preference=signencrypt
Message-ID: <38f1b45c-435d-67d4-b366-623e3866d295@bambenekconsulting.com>
Date: Tue, 09 Jul 2019 10:14:11 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <mAakCAacGpsKdvoi8MI7DM6aAZGudPx3DLh77azT2353@mailpile>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - chicago.bambenekconsulting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bambenekconsulting.com
X-Get-Message-Sender-Via: chicago.bambenekconsulting.com: authenticated_id: jcb@bambenekconsulting.com
X-Authenticated-Sender: chicago.bambenekconsulting.com: jcb@bambenekconsulting.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PDyzUuozy-oexWstC63rjCAGGYA>
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:14:27 -0000

> Hi :-)
>
> John Bambenek <jcb@bambenekconsulting.com> wrote:
> >> That said, I agree it cannot solve GDPR or other policy concerns.
>
> > Why? GDPR applies to IP addresses, that doesn't impact DNS yet.
>
> You appear to have confused IP with P(I)I: personally identifying
> information.
>
> All whois data is PII, in the case where people register
> individual details, as opposed to organizational roles. I think
> you may need to do a bit more research on this topic, you seem to
> have misunderstood a thing or two.

One, IP addresses in some cases are PII (see here:
https://eugdprcompliant.com/personal-data/).

Two, in some cases whois data is NOT PII (i.e. role based accounts,
which are allowed here).

You could set contact info to "Mail Administrator" and
"abuse@domain.com" and that's fine here.

>
> > I'm genuinely curious of something. The most I've engaged in
> > this debate about WHOIS records and what is or is useful in
> > fighting abuse, the opinions of those who actually fight abuse
> > for a living are discarded a priori.
>
> I also have done this for a living. I expect everyone on this
> list has, to a certain degree.
>
> I guess what I'm saying is, I probably wouldn't buy what you're
> selling.
>
> Further, I agree with others that it's not our job to standardize
> and encourage the kind of large scale self-doxxing such products
> would undeniably benefit from. That would be to throw the
> average-Joe under the bus, for the benefit of the minority who
> decide to invest in such tools (whether they are actually
> effective or not).
If you put personal information, that's your choice. If you put
role-based info, that's your choice. Same as what you post on twitter,
facebook, or whatever. This enables the choice to "self-dox" (something
I think is an odd formulation.
> So this is me changing my mind, I don't think potential
> automation use-cases justify this.
>
> Cheers,
>  - Bjarni
>