Re: [DNSOP] Proposal: Whois over DNS

John Bambenek <jcb@bambenekconsulting.com> Mon, 08 July 2019 22:23 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 DB594120323 for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 15:23:44 -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 HxKTpksri3SA for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 15:23:43 -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 E0D4012032B for <dnsop@ietf.org>; Mon, 8 Jul 2019 15:23:42 -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=uWnAbSb2Zsa6t08KgbO94AarH4zPldS+LeQQC8SDIbA=; b=RHaiJvifAFk5xBDktu+MPt3f/ CrqLd6MF+7uAodrQnktiyxMTrv5NwXhWWIBY3Xk7Xs0WVORdtd0v0C/Vok61hm7hlHuW2yr6IsHbe G8PBhvmb1lfD2ObUux6zuxJSU1GwZCbZAZ4ii3QIy7LzD+OYYDpaskobXAEIdSm7XRaHw=;
Received: from [216.169.1.210] (port=24326 helo=[192.168.11.116]) by chicago.bambenekconsulting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <jcb@bambenekconsulting.com>) id 1hkc2u-0004cG-K1; Mon, 08 Jul 2019 18:23:40 -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: <51595f52-74d7-dc43-4f91-042448e2cda9@uniregistry.com>
Date: Mon, 08 Jul 2019 17:23:40 -0500
Cc: dnsop WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CDEEFD1-CEA9-4693-8B4C-AEF29DC54E1D@bambenekconsulting.com>
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <3f3b0fcd-e09d-be29-7b85-ceb34a2e10f7@uniregistry.com> <9ED809E4-8121-4636-87D4-3A062FCC8C80@bambenekconsulting.com> <51595f52-74d7-dc43-4f91-042448e2cda9@uniregistry.com>
To: Patrick Mevzek <mevzek@uniregistry.com>
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/-uiAtx6__PLzVOaO75xmB4ugTFo>
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 22:23:54 -0000

If there is no auth NS there is no whois. Acceptable limitation. 

In short term, no incentives. My hope is to get consensus, make it an RFC, then start encouraging auditors and the like to flag on it. But yes, it needs some critical mass of adoption or its just another idea on paper. 

Reputation and contact-ability intersect in this use case in my mind. 

—
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 8, 2019, at 17:14, Patrick Mevzek <mevzek@uniregistry.com> wrote:

> On 2019-07-08 17:05 -0500, John Bambenek <jcb@bambenekconsulting.com> wrote:> For domains with no NS records? Who cares, they aren’t in actual use. (Or if they are something is broken or more likely malicious so block it).
> 
> They could be (in use), at some point. See past "fast flux" cases.
> 
> WHOIS was invented to be able to contact "someone" for any kind of problems, technical or administrative. A domain not having NS records may be a technical problem, or not, but if it is a problem who to contact if that information lives in the DNS itself?
> 
>> Yes, the onus is on domain owners (and that requires consensus and adoption which are not given but why its being brought up here).
> 
> So you are expecting registrants to abide by this, and then all DNS providers to update their web interface so that people will be able to enter those records? What incentives will they all have to do that?
> 
> I am probably less optimist than you.
> 
> But my understanding is that it seems you are trying to publish some data to derive some "reputation" based on it, instead of really data to be able to contact people. They are different goals probably.
> -- 
> Patrick Mevzek
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop