RE: Unique handle generation

["Paul George" <pgeorge@saraf.com>]

Perhaps remove the second part of #4?  Why add auxilary info to the handle?
It would then be serving two purposes. So it would read:

>4. An object handle MUST contain information that unambiguously identifies
>the object.

But then is it duplicating #2.(2. An object handle MUST be globally unique.)

The alternative would be:

4. An object handle MUST contain information that unambiguously identifies
both the object and the object's administrative repository at time of
creation.


Paul George
SARAF Software Solutions
(703)538-5666 x234


-----Original Message-----
From: Hollenbeck, Scott [mailto:shollenbeck@verisign.com]
Sent: Monday, March 12, 2001 7:37 AM
To: 'Paul George'; ietf-provreg@cafax.se
Subject: RE: Unique handle generation


Right now I'm working with the assumption that the administrative repository
won't change, but maybe that's not a good assumption.  For example, gTLD
registry operators may change over time.  Changing the handle upon such a
repository change would be counter to other requirements, but not changing
it might be confusing.

Perhaps this requirement should be reworded -- suggestions?

<Scott/>

>-----Original Message-----
>From: Paul George [mailto:pgeorge@saraf.com]
>Sent: Monday, March 12, 2001 7:08 AM
>To: ietf-provreg@cafax.se
>Subject: RE: Unique handle generation
>
>
>4. An object handle MUST contain information that
>unambiguously identifies
>both the object and the object's administrative repository.
>
>Is there a possibility that the object's administrative
>repository could
>change?  If so, then that attribute should not be a part of
>the handle. This
>is because that part of the handle would then only indicate
>the admin that
>originated the handle, not the current administrator.