Re: [DNSOP] Proposal: Whois over DNS

John Bambenek <jcb@bambenekconsulting.com> Tue, 09 July 2019 16:05 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 0328F12064D for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 09:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level:
X-Spam-Status: No, score=-4.298 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 PwMdQiPeXBj2 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 09:05:32 -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 ECD861206E9 for <dnsop@ietf.org>; Tue, 9 Jul 2019 09:05:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bambenekconsulting.com; s=default; h=Content-Type:In-Reply-To:MIME-Version: Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-Transfer-Encoding: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=SXf2lVIg32hXGm1TOZOvxCGlzlib+/qHQY4FrhC5Bjs=; b=ZKmdRa+IGq/G8uqJGrxVSGp0G z+r5obKqgJDRm5Mq/a0K9MGQQQqNPoLgWNmVFE7Lh5GF6I0HIWWnE4dLFUWl5tgR/FI54l0hmIG0U LHgED7RRAD8Qs2hMpn1NeZyy269Kd+0Ef7SP0xjd5Bcc5bhUGD4SuiKKCsQglC/6Grg+E=;
Received: from [216.169.1.210] (port=10269 helo=jcb.local) by chicago.bambenekconsulting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <jcb@bambenekconsulting.com>) id 1hkscT-0001y9-SM; Tue, 09 Jul 2019 12:05:29 -0400
To: Ted Lemon <mellon@fugue.com>
Cc: dnsop@ietf.org
References: <1CA7BF1B-DF50-443B-9219-55259835FE23@bambenekconsulting.com> <233E0AD8-97FE-466C-9B6C-D7A376031C3B@rfc1035.com> <93244821-6C22-457F-BA06-CF43CA9FD12B@bambenekconsulting.com> <F45666C7-181A-4853-897E-40D5C0EA972B@fugue.com> <37daa562-c8a0-ec11-8a3f-ffebfb464d16@bambenekconsulting.com> <C4390F20-F2CE-45F7-A3DD-243313FB0E39@fugue.com> <884b1e64-7ffb-a793-c15e-480f765a0044@bambenekconsulting.com> <E34E80E5-6995-4F2C-989C-E82984C0690E@fugue.com>
From: John Bambenek <jcb@bambenekconsulting.com>
Openpgp: preference=signencrypt
Message-ID: <a008b238-d603-4b98-f7f5-be6622bc575f@bambenekconsulting.com>
Date: Tue, 09 Jul 2019 11:05:29 -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: <E34E80E5-6995-4F2C-989C-E82984C0690E@fugue.com>
Content-Type: multipart/alternative; boundary="------------DD30CBFB080D2E2C2A76AEE7"
Content-Language: en-US
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/9LB9F3GbUGYGx9M-SpYXWXvk_DM>
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 16:05:34 -0000

On 7/9/19 11:00 AM, Ted Lemon wrote:
> On Jul 9, 2019, at 11:41 AM, John Bambenek
> <jcb=40bambenekconsulting.com@dmarc.ietf.org
> <mailto:jcb=40bambenekconsulting.com@dmarc.ietf.org>> wrote:
>> You assume I'm going to create a huge database, I am not. I would
>> envision doing something like if you send me email, try to connect,
>> etc, there is a DNS query for this information, much like there are
>> queries for DBLs, SPF et al, and score it in real time.
>>
>> Or if doing abuse reporting, just programmatically look who an email
>> and then email whatever is given (assuming syntactically valid).
>>
>
> John, the DNS is the huge public database to which I am referring.
>  You don’t operate it.  You’re just proposing to require me to publish
> my private information in it in order to do business with you.
>
I'm proposing a standard to publish certain information should you wish
to. There is nothing in this document to indicate anything is required.
In theory, I as a network operator could require some information in
order to allow you access to my network, that is the sole power I have
and this proposal doesn't change that.