IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

Bill Woodcock <woody@pch.net> Mon, 08 July 2019 22:09 UTC

Return-Path: <woody@pch.net>
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 4C76712026D for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 15:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 01r1vdKGa5el for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 15:09:36 -0700 (PDT)
Received: from mail.pch.net (keriomail.pch.net [206.220.231.84]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 236F4120077 for <dnsop@ietf.org>; Mon, 8 Jul 2019 15:09:36 -0700 (PDT)
X-Footer: cGNoLm5ldA==
Received: from [10.19.48.53] ([69.166.14.2]) (authenticated user woody@pch.net) by mail.pch.net (Kerio Connect 9.2.7 patch 3) with ESMTPSA (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256 bits)); Mon, 8 Jul 2019 15:09:33 -0700
From: Bill Woodcock <woody@pch.net>
Message-Id: <F04D4226-BC48-48AF-A583-729C9AFA8382@pch.net>
Content-Type: multipart/signed; boundary="Apple-Mail=_44CB3505-6AC0-4355-8394-F55AF7DD5069"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 08 Jul 2019 15:09:26 -0700
In-Reply-To: <CABf5zvLqpBPtEykOi5p4GvOEvLV=61KmcAEQ6w4VgFrw8nZ41Q@mail.gmail.com>
Cc: John Bambenek <jcb=40bambenekconsulting.com@dmarc.ietf.org>, dnsop <dnsop@ietf.org>
To: Steve Crocker <steve@shinkuro.com>
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <E45936AC-3CBF-4E09-8F1B-311EAA482BC1@pch.net> <CABf5zvLqpBPtEykOi5p4GvOEvLV=61KmcAEQ6w4VgFrw8nZ41Q@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/K6ZK3hp-b7M60h-2ijAlKwLcpA4>
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 22:09:50 -0000


> On Jul 8, 2019, at 2:52 PM, Steve Crocker <steve@shinkuro.com> wrote:
> 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?

A few years ago, we’d have said the same thing about signatures on PGP public keys, right?

The problem is that as the number of people connected to the Internet grows, the likelihood that there will be at least one person prone to graffiti, that is, vandalizing an unprotected system simply for the purpose of vandalism, not out of any other motivation, approaches one.

> 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.

Yes, I think that’s true.  But it doesn’t necessarily militate against moving this forward.  If it solves some problems for some people, and doesn’t hurt anyone else, that’s sufficient.

                                -Bill

v2.23.0 | Report a Bug | By Email