Re: [DNSOP] Proposal: Whois over DNS

Patrick Mevzek <mevzek@uniregistry.com> Mon, 08 July 2019 21:53 UTC

Return-Path: <mevzek@uniregistry.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 32DFB120073 for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 14:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.336
X-Spam-Level: *
X-Spam-Status: No, score=1.336 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_NONE=-0.0001, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uniregistry.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 DNp_BX4SSyMb for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 14:53:02 -0700 (PDT)
Received: from a-mx.uniregistry.com (a.mx.uniregistry.net [64.96.177.8]) (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 DCD2612016E for <dnsop@ietf.org>; Mon, 8 Jul 2019 14:52:56 -0700 (PDT)
Abuse: Forward to abuse@uniregistry.com with full headers
X-Virus-Scanned: Content filter at a-mx.uniregistry.net
Powered-By: https://www.uniregistry.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uniregistry.com; s=bravo; t=1562622775; bh=C+vJmYyJgvg2LWLHgbBGVs04a260o5V825jmxbcdU7g=; h=Subject:To:References:From:Date:In-Reply-To; b=AmcZ3eoVlaPlgiRqPmQECLX30NcBgnliDJAwAprZh+P2DQputNQjk6uzR34tNsmSN eSLqC3XuXXE1ZCTZ3HglOw/h4Z/hVZugIlcIwnNYaM8mirgAwKhqYGOXYelWnQta6x GX+JRvpnMSj8ke3R+RbKdu7XWoKlJZbRROhVF+KwWCzx8whB44/r/s97lpcnHbMIx7 +AhbP/79ToqVJi1F46whnzIhNy8SxD31dZaIQs1NxlpPWHS7MxGC1wHHecwv/yw7Q9 t3kvSmN7ix1DBX/FASZmSf69GmgPG1EW206U7MkcawSn/wWOrgrWTr3xkAj9mbzR5P kppDf4bDS/gOQ==
Received: from PatrickM.local ([66.54.123.66]) (authenticated bits=0) by a-mx.uniregistry.com (8.15.2/8.15.2/Debian-8) with ESMTPSA id x68Lqrqa027472 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 8 Jul 2019 21:52:55 GMT
To: dnsop WG <dnsop@ietf.org>
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com>
From: Patrick Mevzek <mevzek@uniregistry.com>
Organization: Uniregistry
Message-ID: <3f3b0fcd-e09d-be29-7b85-ceb34a2e10f7@uniregistry.com>
Date: Mon, 08 Jul 2019 16:52:52 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/H9BHp8UQn7ViJ0_MSw_gLNVtYTM>
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 21:53:12 -0000




On 2019-07-08 16:38 -0500, John Bambenek 
<jcb=40bambenekconsulting.com@dmarc.ietf.org> wrote:
> In response to ICANN essentially removing most of the fields in WHOIS 
> for domain records, Richard Porter and myself created a draft of an 
> implementation putting these records into DNS TXT records.

Not all registered domains are published (no NS records), so what about 
those?

Also your proposal puts the onus of (valid) information publishing on 
the registrant of each domain, no more on the registrar or the registry, 
because
_whois.example.com is under the control of example.com and not under 
control of the registry under which example.com lives and neither its 
registrar as the DNS provider may not be the registrar.

So what did I not understand about who controls and where do the 
_whois.example.com RRs exist?

As for:
"This means that if a domain owner were compromised,
    someone else has contact information to get in touch with the true
    own to organize remediation."
It depends on how you define "domain owner were compromised".
This could as well mean "have access to registrar panel to configure 
this domain" which in turns means "being able to put whatever 
nameservers, and hence DNS records as one wishes". But you may be 
relying on the TTLs of old records?
(a point not discussed I think; would long TTLs be good for those records?).

Also, a similar idea was floated on the regext mailing list sometimes ago:
https://www.ietf.org/archive/id/draft-brown-whoami-02.txt
This was using well known URIs to publish whois data and the URI DNS RR.
-- 
Patrick Mevzek