IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

John Bambenek <jcb@bambenekconsulting.com> Tue, 09 July 2019 16:08 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 F11E012029A for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 09:08:44 -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 8p3VVc6RH5eQ for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 09:08:43 -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 6886B120277 for <dnsop@ietf.org>; Tue, 9 Jul 2019 09:08:43 -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=zt93MqCUMPW5qfROwwgz+oEf/iR903h2ZQF8iEXwW0c=; b=Bqi6FgCrYyXUtmBjr2ZEGH+MLl X3qsm5sqVM8nXHLJRu/rUS9La9IzICuzvrOOd+CHrNbYfJfQ/lDfhNoeunmOpckiswQlAetakpXC/ 0yBRo1TjTnm9QPrXpEpJ5bCfEEAecRjRIq34VeH2ToHNE2u9k//RoqNa7MqS7XGJApQM=;
Received: from [216.169.1.210] (port=11188 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 1hksfY-00021w-8D; Tue, 09 Jul 2019 12:08:40 -0400
To: Jim Reid <jim@rfc1035.com>
Cc: dnsop <dnsop@ietf.org>
References: <1ff4dcb0-f8aa-6fcd-eafd-ec8fe9a633ea@bambenekconsulting.com> <mAakCAacGpsKdvoi8MI7DM6aAZGudPx3DLh77azT2353@mailpile> <1782C96A-BC85-4138-9E1B-1C90567B4771@rfc1035.com>
From: John Bambenek <jcb@bambenekconsulting.com>
Openpgp: preference=signencrypt
Message-ID: <23cae17b-9ca3-db40-bbad-bd534a3ac2cf@bambenekconsulting.com>
Date: Tue, 09 Jul 2019 11:08:40 -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: <1782C96A-BC85-4138-9E1B-1C90567B4771@rfc1035.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
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/px9B6OPoAVuFJ64S8aS43_o6S1Y>
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 16:08:45 -0000

On 7/9/19 10:27 AM, Jim Reid wrote:
>> 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.
>
You mistake my point, my point is that people publish IP addresses that
may refer to living European citizens and thus, is covered by GDPR. The
objections to WHOIS data in DNS apply just as much to IP addresses. So
if role-based info or self-disclosed personal info can't be in DNS
because GDPR, I'm curious as to why people think IP addresses can be?

v2.23.0 | Report a Bug | By Email