RE: <check> Response Attribute

[Chris Cowherd <chris.cowherd@enom.com>]

I would say that "reserved" domain names are not available.

-----Original Message-----
From: Eric Brunner-Williams in Portland Maine
[mailto:brunner@nic-naa.net]
Sent: Fri, September 21, 2001 8:17 AM
To: Hollenbeck, Scott
Cc: 'ietf-provreg@cafax.se'; brunner@nic-naa.net
Subject: Re: <check> Response Attribute 


Scott,

You propose to restrict the type of <check> from an enumerated extensible
set (token) to a enumerated inextensible (boolean) set.

How do you propose we handle requirements for "reserved" domain names?

Eric

> The <check> command response currently returns an element attribute to
note
> if an object exists.  The value space of this attribute is really boolean,
> but the current schema uses a "+" to note "exists" and a "-" to note
> "doesn't exist".  I'd like to propose a simplification for the sake of
> consistency with other boolean attributes, changing the type of the
> attribute to "boolean", an XML Schema data type.  This would mean that the
> acceptable values become "1" and "true" for "exists" , and "0" and "false"
> for "doesn't exist".