[177188] in North American Network Operators' Group
Re: whois server features
daemon@ATHENA.MIT.EDU (shawn wilson)
Wed Jan 7 14:48:16 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <EFD3482D-69F4-4F8B-B42E-0D7AD86411BA@pch.net>
From: shawn wilson <ag4ve.us@gmail.com>
Date: Wed, 7 Jan 2015 14:47:47 -0500
To: Bill Woodcock <woody@pch.net>
Cc: North American Network Operators Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Wed, Jan 7, 2015 at 1:53 PM, Bill Woodcock <woody@pch.net> wrote:
>
>> On Jan 7, 2015, at 10:38 AM, shawn wilson <ag4ve.us@gmail.com> wrote:
>>
>> Is there a list of NIC (and other popular whois server) features (what
>> can be searched on) and what data they provide (and what title they
>> give it)?
>
> Heh, heh, heh. There are just about as many whois output formats as ther=
e are back-end data-stores. Note that I say =E2=80=9Cdata-stores=E2=80=9D =
rather than databases. Some of them aren=E2=80=99t. So when you say =E2=
=80=9Ctitle=E2=80=9D I assume you=E2=80=99re referring to half of a key-val=
ue pair. A concept some large whois sources don=E2=80=99t have.
>
Yes, I'm referring to mapping between key names.
> So, you=E2=80=99re not running into a poorly-documented mystery, you=E2=
=80=99ve run afoul of one of the rotten armpits of the shub-Internet.
>
So there's no consensus between NICs for the information they should
have in whois and what search mechanisms they should provide? I guess
what you're saying is that whois is just a protocol definition and
nothing else?
