IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

Jim Reid <jim@rfc1035.com> Tue, 09 July 2019 14:47 UTC

Return-Path: <jim@rfc1035.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 9E80912016B for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 07:47:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 EzDeDQeX6mRJ for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 07:47:04 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95AD112018B for <dnsop@ietf.org>; Tue, 9 Jul 2019 07:47:04 -0700 (PDT)
Received: from wallace.rfc1035.com (hutch.rfc1035.com [195.54.233.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 28AAE24211C0; Tue, 9 Jul 2019 14:47:02 +0000 (UTC)
From: Jim Reid <jim@rfc1035.com>
Message-Id: <B8C5D846-324E-43FB-86F1-09B70239819E@rfc1035.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BF1ECA38-7BE5-4D22-B314-107ABAEF2422"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 09 Jul 2019 15:47:01 +0100
In-Reply-To: <FUkLTVMXAgJMiDybUjWJmf4VMxMskCZdtairxrSf2353@mailpile>
Cc: dnsop <dnsop@ietf.org>
To: Bjarni Rúnar Einarsson <bre@isnic.is>
References: <233E0AD8-97FE-466C-9B6C-D7A376031C3B@rfc1035.com> <FUkLTVMXAgJMiDybUjWJmf4VMxMskCZdtairxrSf2353@mailpile>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ioHn36ZBxhT-ZzGT_aOG96Cb6sE>
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:47:07 -0000


> On 9 Jul 2019, at 15:15, Bjarni Rúnar Einarsson <bre@isnic.is> wrote:
> 
> I think having a technical specification like this would be quite interesting from the point of view of automatically updates to existing Whois databases, without requiring the registrant directly (or indirectly) interact with complex APIs or provider-specific web interfaces.

Interesting in the sense that novichok is interesting? :-)

DNS and whois are very different protocols which get used and abused for very different things. I'm struggling to understand why they should be coupled like this or what problem(s) would get solved by doing that.

v2.23.0 | Report a Bug | By Email