Re: <check> Response Attribute

[Patrick <patrick@gandi.net>]

On Fri, Sep 21, 2001 at 05:10:47PM -0400, Mike Lampson took time to write:
> Maybe it's too late for this, but what us Registrars need to know is whether
> the name is available for registration, not if it exists.  If a name cannot
> be registered, I don't really care if it can't be registered because it
> already exists or because it is reserved.

Registrars maybe not, but clients sure.
As Registrar I would like to be able to tell my customer that if this
domain can not be registered it is for a reason, being reserverd for
example (ie. you will never be able to get that one, please change
your mind), or just being registered by someone else previously (in
that case we can tell the client to see if the current owner wish to
sell).

So the information about why it can not be registered is still
useful.

For .NAME for example they are Defensive Registrations.
It would be great, when registering a domain name that fall under a
Defensive Registration to have back the answer : no, domain name not
available *because* such and such Defensive Registration.

In short the reason seems helpful to me, and should be included.
Client code (Registrars) will use it or not like they wish, but if
the Server (Registry) can send it, why not do it.

Patrick Mevzek
Gandi.