[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "Jordyn A. Buchanan" <jordyn@register.com>
Cc: Edward Lewis <lewis@tislabs.com>, ietf-provreg@cafax.se, jaap@sidn.nl
From: Edward Lewis <lewis@tislabs.com>
Date: Tue, 25 Sep 2001 16:41:45 -0400
In-Reply-To: <a05100c22b7d698ebe75e@[192.168.2.116]>
Sender: owner-ietf-provreg@cafax.se
Subject: RE: <check> Response Attribute

At 4:28 PM -0400 9/25/01, Jordyn A. Buchanan wrote:
>I agree with the approach outlined by Ed in general, but some thought
>should go into whether or not "Maybe" should be an answer along with
>"Yes" and "No.

I say this with two things in mind:
1) Don't let a chair decision be the reason for a mistake.
2) As I don't do day-to-day registration activities, I try to remain a referee.

What is the difference between "maybe" and "yes" with a qualifying
statement (recognizing that there is an impact to an implemetation)?  Or,
perhaps, "no" with a qualifier?  (E.g., the name is available for a cost of
10.000 Euros, but not for less.)

Is there an example of a registration process that uses "maybe" as a return
for a check command today, or a process that has "maybe" in its design?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                NAI Labs
Phone: +1 443-259-2352                      Email: lewis@tislabs.com

You fly too often when ... the airport taxi is on speed-dial.

Opinions expressed are property of my evil twin, not my employer.



Home | Date list | Subject list