To:
Christopher Ambler <cambler-ietf@iodesign.com>
Cc:
"Hollenbeck, Scott" <shollenbeck@verisign.com>, ietf-provreg@cafax.se
From:
George Belotsky <george@register.com>
Date:
Wed, 7 Mar 2001 15:25:24 -0500
Content-Disposition:
inline
In-Reply-To:
<022301c0a737$3c8a9990$1701a8c0@underslunky>; from cambler-ietf@iodesign.com on Wed, Mar 07, 2001 at 10:48:36AM -0800
Sender:
owner-ietf-provreg@cafax.se
User-Agent:
Mutt/1.2.5i
Subject:
Re: Unique handle generation
Maybe we can attach some other information along with the email
address to ensure uniqueness. A digest of the whole handle can then
be generated. At this point, you basically have a UUID. People can
use the plain text version of their handle (easy to remember), while
automated information exchanges can work with the digests directly.
.. and I hope this is not beef liver, or you may not even remember
your email in a few years :) ...
George.
On Wed, Mar 07, 2001 at 10:48:36AM -0800, Christopher Ambler wrote:
> I have been, and remain convinced that email address, with the
> ability to change it as necessary, is the way to go.
>
> Then again, I'm also fond of liver and onions.
>
> Christopher
>
> ----- Original Message -----
> From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
> To: "'George Belotsky'" <george@register.com>; <ietf-provreg@cafax.se>
> Sent: Wednesday, March 07, 2001 10:36 AM
> Subject: RE: Unique handle generation
>
>
> > George,
> >
> > In terms of placing interoperability in the hands of the user, I prefer the
> > idea of either letting them choose their own identifier (it it happens to be
> > unused by anyone else), or using an e-mail address. InterNIC-generated
> > handles (which sounds similar to what you've suggested below) haven't proven
> > to be very memorable or useful in other contexts.
> >
> > <Scott/>
> >
> > -----Original Message-----
> > From: George Belotsky [mailto:george@register.com]
> > Sent: Wednesday, March 07, 2001 11:54 AM
> > To: ietf-provreg@cafax.se
> > Subject: Unique handle generation
> >
> >
> > Since unique handle creation is still an open issue, could we not
> > borrow/adapt a UUID generating algorithm for making such handles?
> >
> > This eliminates the need to keep a centralized database of these
> > things. Anyone can have as many handles as they want, and use them as
> > they see fit. This places interoperability in the hands of the user;
> > if someone wants their information shared between systems, they will
> > continue to use the same handle.
> >
> > George.
> >
> >
> >
> > -----------------------------
> > George Belotsky
> > Senior Software Architect
> > Register.com, inc.
> > george@register.com
> > 212-798-9127 (phone)
> > 212-798-9876 (fax)
> >
>
--
-----------------------------
George Belotsky
Senior Software Architect
Register.com, inc.
george@register.com
212-798-9127 (phone)
212-798-9876 (fax)