Re: Transfering a domain

[Jeff Williams <jwkckid1@ix.netcom.com>]

David and all,

davidk@ISI.EDU wrote:
> 
> Rick,
> 
> > Rick H. Wesson writes :
> >
> > How will transfers of a domain from one regestry to another
> > take place? I expect it take the acknolagement from the regestry
> > holding the domain, the regestry the domain is being transfered to,
> > the end user requesting the domain transfer and the folks running
> > the CORE database be involved.
> >
> > Whom would an end user ask, if they are to ask CORE for the transfer
> > then I would expect that the folks that run the CORE database need
> > to charge an administrative fee much like the ARIN proposal for the
> > transfer of IP Networks. If speculation in new domain names is high,
> > then I would expect the load on the folks running the CORE db to be
> > high also.
> >
> > How should a transfer of ownership of a domain take place? How do you
> > make sure these transfers are authorized?
> 
> My light-weight proposal solves this rather elegantly:
> 
> Transfer of 'ownership of a registration' can be done secure and easily
> if the repository knows the public key of the end-user as well as the
> registrars. Any update should be accepted if it is (validly) signed by
> the end-user as well as by *any* of the registrars. The trick is now that
> the end-user doesn't need the cooperation of the old registrar if (s)he
> wants to change registrar which is definitely positive for the end-users
> in a world with competing registrars that might even not exist anymore
> when they go out of business.

  Using a shared key for all registries might be even a simpiler
solution
and provide for better security.  This could be also be done by adding
a special extension for this perpose to aall existing keys.  This is
already
being used in some non-related product implimentations.  (See IETF TLS
Doc).
> 
> David K.
> ---

Regards,
-- 
Jeffrey A. Williams
DIR. Internet Network Eng/SR. Java Development Eng.
Information Eng. Group. 
Phone :972-447-1878
E-Mail jwkckid1@ix.netcom.com