IETF Logo Mail Archive

Re: [DNSOP] Proposal: Whois over DNS

John Bambenek <jcb@bambenekconsulting.com> Tue, 09 July 2019 15:09 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 4D276120106 for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:09:49 -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 f6dJv97y5XFy for <dnsop@ietfa.amsl.com>; Tue, 9 Jul 2019 08:09:47 -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 31F341203FC for <dnsop@ietf.org>; Tue, 9 Jul 2019 08:09:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bambenekconsulting.com; s=default; h=Content-Transfer-Encoding:Content-Type :In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject: 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=NZFXU+vlrNXCzkh8eEz/F+JV1UTPtRX0XADZiQl8OFM=; b=mFe9SL8AIv7+dNiLL/5LlZnuXo IEFQrcqc/BYViMyHoSlW+Q1xikRNKwLrV8K9xoy/v9f4q+PnE2MGwMuYzX4ccONG1xOo473MaxpHa i9cixhhbh+z9Ptf9s7acF0WoERZErFPLJFcyAr6lPI7SL/ittemr8iLftWrFkD6fI5sE=;
Received: from [216.169.1.210] (port=31516 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 1hkrkT-0000hS-Sa; Tue, 09 Jul 2019 11:09:41 -0400
To: Joe Abley <jabley@hopcount.ca>
Cc: Jim Reid <jim@rfc1035.com>, 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> <EDE98437-E0B8-4B2E-8AA5-2F6B0079CE8B@hopcount.ca> <0ece2408-a1ec-fa5f-f8d1-ff65572de1ed@bambenekconsulting.com> <B520D17D-F258-41C3-97DD-3CE5C3A8E952@hopcount.ca>
From: John Bambenek <jcb@bambenekconsulting.com>
Openpgp: preference=signencrypt
Message-ID: <954b934f-17cb-afeb-75ca-d37b1bb668ae@bambenekconsulting.com>
Date: Tue, 09 Jul 2019 10:09:41 -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: <B520D17D-F258-41C3-97DD-3CE5C3A8E952@hopcount.ca>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
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/DVGdQVRjrMgv3jWUbcclcTIFT5M>
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 15:09:49 -0000

Below

On 7/9/19 10:07 AM, Joe Abley wrote:
> Hi John,
>
> On 9 Jul 2019, at 10:36, John Bambenek <jcb@bambenekconsulting.com> wrote:
>
>> If the proposal is to create a standard by which to put contact
>> information into DNS records, what venue would you suggest?
> I think that the protocol aspects of this are the least difficult ones. If this is fundamentally the data governance issue that I think it is, I think it would make a lot more sense to align exactly with what is happening in RDAP, treating self-publication as a new profile and DNS as a possible transport. If there's data to publish, thinking about transport afterwards seems far more sensible than inventing a transport and hoping that the data will follow.
No more data governance than there is already in publishing records in
DNS today.
>
> RDAP profiles are not being discussed in the IETF. I think this is a feature.
>
>>> I also agree that without any widespread incentive to implement, test and maintain, the data is going to be noisy and sparse to the point where it's useless for any practical use anyway.
>> You could say the same for SPF.
> There's an operational incentive to publish SPF records: the need for recipients to accept legitimate mail that is being sent. I don't know what the operational incentive is to publish "whois" data in zone files.
Once a critical mass of adoption happens, then a similar incentive...
the need for recipients to accept legitimate mail, for one.
>
>
> Joe

v2.23.0 | Report a Bug | By Email