IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

Paul Vixie <paul@redbarn.org> Wed, 10 July 2019 00:13 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 112DB12027C for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 17:13:29 -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, 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 d838jmxL5mwC for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 17:13:27 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5031A1202BF for <dnsop@ietf.org>; Tue, 9 Jul 2019 17:13:27 -0700 (PDT)
Received: from linux-9daj.localnet (50-255-33-26-static.hfc.comcastbusiness.net [50.255.33.26]) (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 33FB8892D3; Wed, 10 Jul 2019 00:13:27 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: dnsop@ietf.org
Cc: John Bambenek <jcb=40bambenekconsulting.com@dmarc.ietf.org>
Date: Wed, 10 Jul 2019 00:13:26 +0000
Message-ID: <2274465.ZR2O4vXfpM@linux-9daj>
Organization: none
In-Reply-To: <6ABF86DD-A4D6-459C-A790-B3406932C76E@bambenekconsulting.com>
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <3564488.2yaKDDZa9B@linux-9daj> <6ABF86DD-A4D6-459C-A790-B3406932C76E@bambenekconsulting.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/NXFgFKlDyF7g7VA6qUQJjjJnGzs>
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: Wed, 10 Jul 2019 00:13:33 -0000

On Tuesday, 9 July 2019 21:56:49 UTC John Bambenek wrote:
> How would having an SRV record and an entirely different (currently
> undeveloped) service help the situation?

whois and rdap servers are a dime a dozen. i can run one for all of my 
domains, and put it behind a rate limiter to make life harder for scrapers.

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

it contains my PII.

-- 
Paul

v2.23.0 | Report a Bug | By Email