Re: [DNSOP] Proposal: Whois over DNS

John Bambenek <jcb@bambenekconsulting.com> Tue, 09 July 2019 21:56 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 0C855120141 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 14:56:54 -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 b0YPPKcsXqYE for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 14:56:52 -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 090131200B3 for <dnsop@ietf.org>; Tue, 9 Jul 2019 14:56:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bambenekconsulting.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type: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=wRmnkbrmc9F7GoPLXP0lZZWShC7ard2jXhIq/vuyUtg=; b=j5yLdoDuDEW60qpFDIEcZuVos GXTZdfULYHsZcCoEDIQG5vdLkYK6i5xY3fLMMYxeDGV5ZsP8NeduGHbArXXsGigoHRgMYJj+5oBZf WsxKm9G6ox+Hs+718XjpinGbncRdDvTkIx+rhmQwUvvMCaiyyXgU/hUTgpioHZW9jlW/4=;
Received: from c-67-167-98-187.hsd1.il.comcast.net ([67.167.98.187]:53822 helo=[192.168.11.181]) by chicago.bambenekconsulting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <jcb@bambenekconsulting.com>) id 1hky6T-00025t-P2; Tue, 09 Jul 2019 17:56:49 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: John Bambenek <jcb@bambenekconsulting.com>
X-Mailer: iPhone Mail (16F203)
In-Reply-To: <3564488.2yaKDDZa9B@linux-9daj>
Date: Tue, 09 Jul 2019 16:56:49 -0500
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6ABF86DD-A4D6-459C-A790-B3406932C76E@bambenekconsulting.com>
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <EDE98437-E0B8-4B2E-8AA5-2F6B0079CE8B@hopcount.ca> <0ece2408-a1ec-fa5f-f8d1-ff65572de1ed@bambenekconsulting.com> <3564488.2yaKDDZa9B@linux-9daj>
To: Paul Vixie <paul@redbarn.org>
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/LLLY96TSqTy4Da9DuYfivnpX4wY>
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 21:56:54 -0000

How would having an SRV record and an entirely different (currently undeveloped) service help the situation?

If its a question of query logs, the consequence of putting any service (smtp, web, slack) in the hands of a third-party is they need to provide that (if you pay them) or you don’t get it. Why should this service be special in that regard?

—
John Bambenek

On July 1st, 2019, my DGA feeds are converting to a CC-BY-NC-SA 4.0 license which means commercial use will require a license. Contact sales@bambenekconsulting.com for details

On Jul 9, 2019, at 09:46, Paul Vixie <paul@redbarn.org> wrote:

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