Re: [DNSOP] Proposal: Whois over DNS

Paul Vixie <paul@redbarn.org> Tue, 09 July 2019 14:46 UTC

Return-Path: <paul@redbarn.org>
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 BDD9C120172 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 07:46: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_HELO_NONE=0.001, SPF_PASS=-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 63BfIrP2e82X for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 07:46:37 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65514120106 for <dnsop@ietf.org>; Tue, 9 Jul 2019 07:46:37 -0700 (PDT)
Received: from linux-9daj.localnet (vixp1.redbarn.org [24.104.150.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id C88A2892D3; Tue, 9 Jul 2019 14:46:36 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: dnsop@ietf.org
Cc: John Bambenek <jcb=40bambenekconsulting.com@dmarc.ietf.org>, Joe Abley <jabley@hopcount.ca>
Date: Tue, 09 Jul 2019 14:46:36 +0000
Message-ID: <3564488.2yaKDDZa9B@linux-9daj>
Organization: none
In-Reply-To: <0ece2408-a1ec-fa5f-f8d1-ff65572de1ed@bambenekconsulting.com>
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <EDE98437-E0B8-4B2E-8AA5-2F6B0079CE8B@hopcount.ca> <0ece2408-a1ec-fa5f-f8d1-ff65572de1ed@bambenekconsulting.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hIXQe-sx9oA8hpO7c4cGyxiKypI>
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 14:46:39 -0000

On Tuesday, 9 July 2019 14:36:50 UTC John Bambenek wrote:
> Below
> 
> ...

john, (all,) my own prior review of this proposal was effectively neutral but 
actually negative. dns does not permit the kind of rate limiting and logging 
needed by individual domain holders around their whois details unless they 
operate their own authority servers, which is rare these days.

i would prefer to see a SRV RR at _whois._tcp.$apex, and a separate service 
running on the designated server(s) to actually provide the whois information. 
i believe there's a JSON or similar encoding now, to make it machine readable.

i'd like to know who fetches my registration information, and how often. some 
friend with whom i exchange secondary name services will likely not thank me 
for asking to see their dnstap output, or to run my preferred DNS RRL config.

-- 
Paul