To:
michaelm@netsol.com
Cc:
george@register.com (George Belotsky), william.tan@i-dns.net (William Tan), bmanning@isi.edu (Bill Manning), ietf-provreg@cafax.se
From:
Bill Manning <bmanning@isi.edu>
Date:
Mon, 12 Mar 2001 14:00:02 -0800 (PST)
In-Reply-To:
<20010312164610.M2702@bailey.dscga.com> from "Michael Mealling" at Mar 12, 2001 04:46:10 PM
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: Unique handle generation
% e75ad859-83db-4225-a564-120f2fd0d5a9@RIPE % % or more generally: % <objectid>@<administrative ID> % % This is what you use in 99% of the cases in the protocol. Both % sides are globally unique so you can be sure that if RIPE % no longer has the thing it will still have the same name of % e75ad859-83db-4225-a564-120f2fd0d5a9 no matter where it moved % to. The RIPE service could even give you a referal to where it % thinks it got moved to.... % % Now, if you want to build an adjunct service to find an object id without % an administative ID then that's a slower, more exhaustive search. % But it could be done because it would be an atypical query and thus % one that could be done as a low priority process... % % Now that I think about it I guess this was Bill's point just repackaged.. % % -MM BING-BING-BING.... And Ricks point as well. e75ad859-83db-4225 is just icky.... :) -bill