[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

whois server features

Subject: whois server features
From: rubensk at gmail.com (Rubens Kuhl)
Date: Wed, 7 Jan 2015 17:55:48 -0200
In-reply-to: <CAH_OBicKFtrSCzTUZHU_Z5oP8kEpELoH+64ouwvr-Df1jqFRhg@mail.gmail.com>
References: <CAH_OBidrQiAP++Tjuz_4goKMcSxo+yJ4fMyR=jpAYSY0+F96_w@mail.gmail.com> <CAH_OBie503gHHjDrBM_Jdwj1fNVOJSL6DEGQe3zxBxMHVv8vnQ@mail.gmail.com> <[email protected]> <CAH_OBicKFtrSCzTUZHU_Z5oP8kEpELoH+64ouwvr-Df1jqFRhg@mail.gmail.com>

>
> > So, youâ??re not running into a poorly-documented mystery, youâ??ve 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?
>

Might not even qualify for "protocol definition", and RFC 3912 ACKs this:

https://tools.ietf.org/html/rfc3912


Rubens

References:
- Fwd: whois server features
  - From: ag4ve.us at gmail.com (shawn wilson)
- whois server features
  - From: woody at pch.net (Bill Woodcock)
- whois server features
  - From: ag4ve.us at gmail.com (shawn wilson)

Prev by Date: whois server features
Next by Date: whois server features
Previous by thread: whois server features
Next by thread: whois server features
Index(es):
- Date
- Thread