[177193] in North American Network Operators' Group
Re: whois server features
daemon@ATHENA.MIT.EDU (shawn wilson)
Wed Jan 7 15:45:58 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <CAEZw2byyvD3cW+Jzc_6wSAnTV=R1O4mnaMqG3Q3mioSvq+PG5A@mail.gmail.com>
From: shawn wilson <ag4ve.us@gmail.com>
Date: Wed, 7 Jan 2015 15:45:30 -0500
To: anthony kasza <anthony.kasza@gmail.com>
Cc: North American Network Operators Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Wed, Jan 7, 2015 at 3:32 PM, anthony kasza <anthony.kasza@gmail.com> wrote:
> 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.
>
Yes, that's what I was looking at. And that REST API looks nice...
Though from what I read (admittedly not the whole doc yet) I didn't
see it defined what type of data is returned, nor what data should be
expected, which would leave me in the same place. If I'm only getting
a blob back (that would be, I guess, internationalized at this point)
I've still got to loop through with a regex expecting some type of
key/value thing and concatenate data after a line break to the last
value (probably removing spaces since they try to format it pretty).
