Re: Registrar and registry backend processes.

2005-01-21 Thread Edward Lewis
At 10:32 AM +0100 1/21/05, Stephane Bortzmeyer wrote: Remember that the whois protocol is a mess. May be IRIS will fix that. For those concerned with IRIS, please take time to review the documents listed at the bottom of this page: http://www.ietf.org/html.charters/crisp-charter.html RFCs 3981

Re: Registrar and registry backend processes.

2005-01-21 Thread Stephane Bortzmeyer
On Tue, Jan 18, 2005 at 05:08:18AM +0100, Lionel Elie Mamane <[EMAIL PROTECTED]> wrote a message of 61 lines which said: > Further, these options are not documented anywhere, In the man page of GNU whois :-) When querying \fIwhois.denic.de\fP for domain names, the program will automatically

Re: Registrar and registry backend processes.

2005-01-18 Thread Eric Brunner-Williams in Portland Maine
> For what it is worth, some consider the .de whois server broken; see > below. Let's note that the new RFC (3912) doesn't mention the "help > methodology" anymore. In the high stakes game of registry redelegation, with .org as a data point and the new gTLD competition (winners: [info,biz,name,

Re: Registrar and registry backend processes.

2005-01-18 Thread Elmar K. Bins
Hi William, > > And some call this not broken but necessary. I can explain off-list, > > if you like. > > Why off-list? Just tell that you want to support multi-lingual domain names. There are a couple more reasons, and I'm not sure it's NANOG business ;-) > I believe he meant that URL should

Re: Registrar and registry backend processes.

2005-01-18 Thread william(at)elan.net
On Tue, 18 Jan 2005, Elmar K. Bins wrote: > > > eight million registered .de domain names, has also indicated that > > > it is planning to bid. > > > > For what it is worth, some consider the .de whois server broken; see > > below. Let's note that the new RFC (3912) doesn't mention the "help >

Re: Registrar and registry backend processes.

2005-01-18 Thread Elmar K. Bins
[EMAIL PROTECTED] (Lionel Elie Mamane) wrote: > >> $ telnet whois.denic.de whois > >> Trying 81.91.162.7... > >> Connected to whois.denic.de. > >> Escape character is '^]'. > >> ? > >> domain: ? > >> status: invalid > > > Which is defined in what RfC? > > RFC 954, which has recently (

Re: Registrar and registry backend processes.

2005-01-18 Thread Lionel Elie Mamane
On Tue, Jan 18, 2005 at 10:03:31AM +0100, Elmar K. Bins wrote: > [EMAIL PROTECTED] (Lionel Elie Mamane) wrote: >>> A nonprofit firm in Frankfurt, Denic eG, which manages Germany's >>> eight million registered .de domain names, has also indicated that >>> it is planning to bid. >> For what it is

Re: Registrar and registry backend processes.

2005-01-18 Thread Elmar K. Bins
[EMAIL PROTECTED] (Lionel Elie Mamane) wrote: > > A nonprofit firm in Frankfurt, Denic eG, which manages Germany's > > eight million registered .de domain names, has also indicated that > > it is planning to bid. > > For what it is worth, some consider the .de whois server broken; see > below. L

Re: Registrar and registry backend processes.

2005-01-17 Thread Lionel Elie Mamane
On Mon, Jan 17, 2005 at 06:16:25PM -0800, [EMAIL PROTECTED] wrote: > P.S. > can anyone comment on the reputations of the .net registry > administration contenders (no need to comment on verisign)? > A nonprofit firm in Frankfurt, Denic eG, which manages Germany's > eight million registered .de d

Re: Registrar and registry backend processes.

2005-01-17 Thread davidb
[second posting attempt, apologies if the first identical post ever arrives] On Mon, 17 Jan 2005 15:47:50 -0700, Michael Loftis <[EMAIL PROTECTED]> wrote: >It's clearly broken, and needs to be put up for >public review by 'the powers that be' so that it can >be fixed. What's happening now fee

Registrar and registry backend processes.

2005-01-17 Thread Michael Loftis
I think, briefly, that we need to force Verisign and the registrars to be FAR more public about the backend process for WHOIS data and for the TLD zone data. Especially with .com, .net, and probably .org, and this latest failure of 'the system' and the obvious lack of information on 'the system