Technical (was: security, authorization, definition, etc.)

[budi@alliance.globalnetlink.com]

What if we focus on one thing:

   Make sure the protocol only allows *one* entity to
   make changes in the database.

This one entity could be the registry, could be a
registrar, could be the registrant, what have you
depending on the (busines) model.
From the technical point of view, we don't really
care. As long as we can make sure that only *one*
entity can make changes, right.

At this stage we don't really care how it is implemented.
Maybe in a form or certificate, token, password,
or whatever. As long as it's secure.

-- budi
--
Homepage: <http://budi.insan.co.id>
my presentation materials, papers, scrapbook, ... and more
What's your "web.id"? Register your web.id @ http://www.idnic.net.id