[177198] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: whois server features

daemon@ATHENA.MIT.EDU (anthony kasza)
Wed Jan 7 20:17:17 2015

X-Original-To: nanog@nanog.org
In-Reply-To: <CAGFn2k2jXeciPoRWDQXbtPueMveQaxK2r7SkDkLyHbVuuz3RnQ@mail.gmail.com>
Date: Wed, 7 Jan 2015 12:32:49 -0800
From: anthony kasza <anthony.kasza@gmail.com>
To: Rubens Kuhl <rubensk@gmail.com>
Cc: North American Network Operators Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

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.

-AK
On Jan 7, 2015 12:26 PM, "Rubens Kuhl" <rubensk@gmail.com> wrote:

> > This is not the response I was looking for (and reading the RFC makes
> > me feel even worse).
> >
> > Is there a better mechanism for querying NICs for host/owner information?
> >
>
> There will be, one day. And the start (although not the whole journey) will
> be when this I-D follows the standard path all the way to STD:
> http://tools.ietf.org/html/draft-ietf-weirds-rdap-query-18.html
>
>
> Rubens
>

home help back first fref pref prev next nref lref last post