[177201] in North American Network Operators' Group
Re: whois server features
daemon@ATHENA.MIT.EDU (George Michaelson)
Wed Jan 7 21:13:23 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <516C1E31-E0EC-4900-A00E-66A74B32FF34@virtualized.org>
Date: Thu, 8 Jan 2015 12:11:24 +1000
From: George Michaelson <ggm@algebras.org>
To: David Conrad <drc@virtualized.org>
Cc: North American Network Operators Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
CRISP is dead. RDAP is real. If people need to script, then RDAP is
workable JSON and for once, has converged on sensible stuff in both names
and numbers.
the whois "problem" is a formalism owned by ICANN, but as DRC pointed out
the WHOIS solution is dispersed.
RPSL lies to one side btw. I wish it was a defined RDAP type. It may be
work-in-progress but thats not clear.
On Thu, Jan 8, 2015 at 11:38 AM, David Conrad <drc@virtualized.org> wrote:
> Hi,
>
> > Scripting languages have modules that can parse many registrar whois
> > formats. However, most are incomplete due to the plurality of output
> > formats as stated above. I, and i suspect many others, wouls *love* to
> see
> > a more concrete key value format drafted and enforced by ICANN.
>
> ICANN can only 'enforce' stuff on the contracted parties, namely the
> gTLDs. And, in fact, they do so in contractual agreements (if you want the
> gory details, see Specification 4 of
> http://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.htm
> for registries and
> https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#whois
> for registrars).
>
> ICANN can't 'enforce' anything on the ccTLDs or RIRs.
>
> Regards,
> -drc
>
>
