To:
<ietf-provreg@cafax.se>
From:
"Stuart Marsden" <Stuart.Marsden@poptel.net>
Date:
Mon, 24 Sep 2001 09:07:08 +0100
Importance:
Normal
In-Reply-To:
<3CD14E451751BD42BA48AAA50B07BAD6C5FA8B@vsvapostal3.prod.netsol.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: <check> Response Attribute
For a restricted domain (eg dot coop) you would have "no" for lack of registrant eligibility Stuart Marsden -----Original Message----- From: owner-ietf-provreg@cafax.se [mailto:owner-ietf-provreg@cafax.se] On Behalf Of Hollenbeck, Scott Sent: 23 September 2001 00:34 To: 'Patrick'; ietf-provreg@cafax.se Subject: RE: <check> Response Attribute > -----Original Message----- > From: Patrick [mailto:patrick@gandi.net] > Sent: Saturday, September 22, 2001 10:28 AM > To: ietf-provreg@cafax.se > Subject: Re: <check> Response Attribute > > > So the information about why it can not be registered is still > useful. I think Dan Manley suggested this as well. OK, if multiple people feel it would be helpful to provide both a yes/no response and some sort of rationale if the answer is "no", should we attempt to enumerate the reasons for "no" or should we consider free-form (aka server-defined, with some defined maximum length) text to describe the rationale? <Scott/>