Re: [DNSOP] Proposal: Whois over DNS

Steve Crocker <steve@shinkuro.com> Mon, 08 July 2019 21:52 UTC

Return-Path: <steve@shinkuro.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 DB059120305 for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 14:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.601
X-Spam-Level:
X-Spam-Status: No, score=-0.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=shinkuro-com.20150623.gappssmtp.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 HvR6828iiXXU for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 14:52:56 -0700 (PDT)
Received: from mail-yw1-xc30.google.com (mail-yw1-xc30.google.com [IPv6:2607:f8b0:4864:20::c30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 873001202E7 for <dnsop@ietf.org>; Mon, 8 Jul 2019 14:52:52 -0700 (PDT)
Received: by mail-yw1-xc30.google.com with SMTP id x74so4916828ywx.6 for <dnsop@ietf.org>; Mon, 08 Jul 2019 14:52:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shinkuro-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Kp7uGEWEtnNhU8gwIs4dVE0BxyCeQVvH6EDEnNWUb1o=; b=x7BSkvKq0iHbzDL3lhUSHE1LnDmfstKXVgw5WwU3FmgV7HZkKkDjmql+AgStcJvGHS a99FQf95DDiGjJfZ3f7wOBDF/rc0bEJL1sGSdqwDYpm7pku/bvg6lXhf4ZbmYpXaQiHM w2dgD7mqQYf0PHrbmGWJwZoQLJfx/33w89QH8wF0IpUAjShqawAY7xmXg+aAkFqDIrxR Q6tAaqboq5j+2GLmvd0DZOeMg9IMRiZhAbNwZqy1zP8qc8v3sfl01N7ppx/lwsuHQZ1c Ss3X8N2mfuoD08wrGvg6h31ejNe7sxR+nrpEXAN/YVk0bvBipETJwadcZItRTT0x1OBL 8GkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Kp7uGEWEtnNhU8gwIs4dVE0BxyCeQVvH6EDEnNWUb1o=; b=UwjL57UnCmgTQ/CRYiOdCQ8G034WqMZpK9MQEwBJtRu3iTgpPgVwVdnWqigVZqQiCD LEX3rr/liGWf9kN526NRJ7J/rCYhlDbWLXutteR7mnMSLOGqyC+tYqrjA+z3Iyu7SC3h W0NUnkw2L6yyC2M6zMZQRR7oO66UZ5JpnHAbZKdRBeGFFjsW1YwGyN68MGf2Ej4og331 f+l68wOKTBxw8x7kaK9k5XVvZsUF1YhevMEHviiouTmhs97XLpzk5ZiC/P/1PpD5856h 20ZvSZAuu0ZP151Ihqx4HjQCy9aJo0C/hLvPe8iHDA8lFBNGqPcKkIXvczOaCrksOnLV QcIw==
X-Gm-Message-State: APjAAAW9Q+R0A+29AqX//uzfJkH9HqWQDHn26+jlyDbxF9sMga4Hbod8 htGnsGcWL9rB75Ezd8qxvcrq/9JNtTjC+9XfB1GbRg==
X-Google-Smtp-Source: APXvYqzS9p42xrAQhqtF4icgBmS2RCMIEb1LZg9hrWVdcvyBpqjBhlY4rDKD8YeBW6NeMMUh8Kv3QeFNcaucGBA8OAU=
X-Received: by 2002:a81:1f87:: with SMTP id f129mr12582006ywf.135.1562622771596; Mon, 08 Jul 2019 14:52:51 -0700 (PDT)
MIME-Version: 1.0
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <E45936AC-3CBF-4E09-8F1B-311EAA482BC1@pch.net>
In-Reply-To: <E45936AC-3CBF-4E09-8F1B-311EAA482BC1@pch.net>
From: Steve Crocker <steve@shinkuro.com>
Date: Mon, 08 Jul 2019 17:52:40 -0400
Message-ID: <CABf5zvLqpBPtEykOi5p4GvOEvLV=61KmcAEQ6w4VgFrw8nZ41Q@mail.gmail.com>
To: Bill Woodcock <woody@pch.net>, John Bambenek <jcb=40bambenekconsulting.com@dmarc.ietf.org>
Cc: dnsop <dnsop@ietf.org>, "Stephen D. Crocker" <steve@shinkuro.com>
Content-Type: multipart/alternative; boundary="000000000000382d07058d3277f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/q-9bPDgfWW5E4IWW3owNdEct9SM>
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: Mon, 08 Jul 2019 21:53:07 -0000

John and Bill,

Let me offer a slightly different perspective.  The proposal would provide
a way for domain name owners to publish information that they want
published, and it would, of course, be publicly available.

The pre-GDPR whois system collected contact information from registrants
irrespective of whether the registrant would have chosen to provide it.
That's a fundamentally flawed structure, i.e. the incentives are misaligned.

I'm not immediately persuaded the proposed solution, i.e. allowing
registrants to publish what they want via DNS records, will result in a
large amount of incorrect data.  What's the motivation to publish wrong
information as opposed to simply not publishing anything?  On the other
hand, it doesn't address the main issue under consideration these days, a
differentiated access system.  Thus, in my view, the proposal would provide
a solution to the easiest portion of the problem space and would not
address any of the deeper issues.

Steve


On Mon, Jul 8, 2019 at 5:45 PM Bill Woodcock <woody@pch.net> wrote:

>
>
> > On Jul 8, 2019, at 2:38 PM, John Bambenek <jcb=
> 40bambenekconsulting.com@dmarc.ietf.org> wrote:
> >
> > All-
> >
> > In response to ICANN essentially removing most of the fields in WHOIS
> for domain records, Richard Porter and myself created a draft of an
> implementation putting these records into DNS TXT records. It would require
> self-disclosure which mitigates the sticky issues of GDPR et al. Would love
> to get feedback.
>
> Good in principle, but the information in whois has always been, at least
> nominally, third-party vetted.  This would not be.  So my worry is that
> either it would get no uptake, or it would get filled with bogus
> information.  It’s a little hard for me to imagine it being widely used for
> valid information, though that would of course be the ideal outcome.
>
> So, no problem with this in principle, but I’d like to see some degree of
> consensus that user-asserted content is sufficient for people’s needs.
>
>                                 -Bill
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>