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


To: Edward Lewis <lewis@tislabs.com>
cc: ietf-provreg@cafax.se, jaap@tislabs.com, brunner@nic-naa.net
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Date: Wed, 26 Sep 2001 14:02:48 -0400
In-Reply-To: Your message of "Tue, 25 Sep 2001 10:30:03 EDT." <v03130301b7d642cdd5bf@[199.171.39.21]>
Sender: owner-ietf-provreg@cafax.se
Subject: Re: <check> Response Attribute

Ed,

What does "exist" and "not exist" actually mean in this context?

If the registry used a good [1] random number generator and modulo 2
arithmatic to generate the {0,1} return value of a boolean <check>,
or always returned the value {0}, or always returned the value {1},
regardless of the operands, could a registry detect which algorithm
{random, always false, always true} was used?

I probably misunderstand what registrars do, and why, but if <check>
discloses some externally visible state(s), how is it externalized
from the registry, and how is it visible? Alternatively, is <check>
simply a means of expressing a protocol-visible consequence of the
application of a query or particularly a transform command upon an
object?

Next, what datatype is appropriate for the "reason why" portion of the
new <check> return?

Eric

[1] http://search.ietf.org/internet-drafts/draft-eastlake-randomness2-02.txt


Home | Date list | Subject list