Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt

Dave Piscitello <dave.piscitello@icann.org> Tue, 01 May 2012 12:07 UTC

Return-Path: <dave.piscitello@icann.org>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 219D621E80DA for <weirds@ietfa.amsl.com>; Tue, 1 May 2012 05:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5hfgN7+nsK6g for <weirds@ietfa.amsl.com>; Tue, 1 May 2012 05:07:57 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id 9E47921E80BB for <weirds@ietf.org>; Tue, 1 May 2012 05:07:57 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Tue, 1 May 2012 05:07:57 -0700
From: Dave Piscitello <dave.piscitello@icann.org>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Date: Tue, 01 May 2012 05:07:56 -0700
Thread-Topic: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt
Thread-Index: Ac0nkwuS268zY6xBS7W3FPXlTCLLrQ==
Message-ID: <6484877E-8586-4AE9-ADB3-FDC7F868A269@icann.org>
References: <831693C2CDA2E849A7D7A712B24E257F0D5F47A3@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F0D5F4898@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <265BE093-6BD1-4A5B-AEBB-C36178A0A8CF@hxr.us> <9452079D1A51524AA5749AD23E00392810782A@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E00392810782A@exch-mbx901.corp.cloudmark.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] I-D Action: draft-hollenbeck-dnrd-ap-query-00.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2012 12:07:58 -0000

On May 1, 2012, at 12:13 AM, Murray S. Kucherawy wrote:

>> 
>> Is it something the general public would be interested in? Or is it
>> something a domain industry person wants? If its the former, it is
>> probably a good idea. If it is the latter, then why aren't they using
>> EPP or whatever?
> 
> I would like to be able to, given a domain name, get back a unique identifier for the registrant (owner, for example), with some expectation that it's stable.  Then if some other domain name comes back showing the same registrant ID, I know the two are related.
> 
> Bonus if I can say "give me all records for which the owner's registrant ID is X", but I'm guessing that's a long shot.

This is a business decision or opportunity for anyone who manages registration data or accumulates a sufficiently large data set that it is "interesting" for some form of analysis. What makes this hard today is that you must write over a hundred parsers to do this - and certain Whois responders change their responses (ostensibly to defeat harvesting Whois).

> 
>> In general, the broad internet using community doesn't tend to remember
>> their own identifiers in registries. They only know the natural
>> identifiers, such as domain names or IP addresses. So a look up of
>> registrar's by ID is, in my opinion, a feature to make adopting the
>> protocol harder while not doing much benefit for the broader internet
>> public. But host lookups by IP addresses does seem like something an
>> internet user may want to trouble shoot problems.
> 
> I think you're right for human consumers of the data, but automated systems might have an actual use for it.

No "might" needed. There are actual use cases today. It's just much harder to do than it ought to be.