Rodney said what I was going to, but I'll add this http://www.opensrs.org/ If you can stomache that, then I have more of the same. For the record, I've tried to get you guy's attention with this stuff over two years ago. Y'all strongly told me it was non-operational. But, when systems start failing, and it becomes an operational issue, it's way too late.
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of William Allen Simpson Sent: Sunday, February 20, 2000 12:51 PM To: Roeland M.J. Meyer Cc: nanog@merit.edu Subject: Re: whois broke again?
"Roeland M.J. Meyer" wrote:
Then I suggest that you do. I wouldn't sign the NDA, but you might.
What NDA? It's draft-hollenbeck-rrp-01.txt.
But this is irrelevant to the whois discussion.
With SRS, this is no longer possible as the whois data is already distributed among NSI's channel market, the Registrars. Each are independent entities. The only real target you have to fire at is the ICANN. GFL ... they're broke.
I think we must be talking at cross purposes. The domain whois data is located in whois servers, maintained by the NSI registry. It is updated by registrars.
The NSI registry whois seems to be falling down and cannot get up. We need a good system of distributed whois servers, just as we have a robust system of distributed DNS servers.
We've talked about this before. Rather than complaining about NSI, folk need to get off their duffs and make it happen.
I don't have the kind of bandwidth that we should have at the whois servers, so I cannnot offer space. All I can do is chearlead (and write code).
Are we lacking an incremental distribution protocol for whois?
What about rwhois? (RFC-2167 Informational)
What about whois++? (RFC-1913 & 1914 Proposed Standards)
WSimpson@UMich.edu Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32