Re: Transfering a domain

["Rick H. Wesson" <wessorh@ar.com>]

Vince,

If the contact information is distributed then its distributed to a regestry,
hince ownership. This will need to be transfered in the CORE db to point to
the correct Registry that hold the contact info. If all the contact information
was in the CORE repository then there would only need logical seporation of
responsibility, unless any registry could update *ANY contact information.

I asked about flat rate fees, the consept seemed to bounce. If the costs
to run the CORE repository increase in relation to increases in domain
allocation then at some point CORE breaks, unless costs are related to
each allocation, as is the case with ARIN.

-Rick


On Jan 8,  6:24pm, Vince Wolodkin wrote:
> Subject: Re: Transfering a domain
> Under the shared model I have continually espoused, no registry would
> hold ownership of a domain, there would be no need for transfers.  I
> didn't see a billing model in place in the draft.
>
> Why do you assume flat fees rather that per action charges?  Did I miss
> something in the draft?
>
> Vince
>
> Rick H. Wesson wrote:
> >
> > 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?
> >
> > Thanks,
> >
> > -Rick
> >
> > --
> > Rick H. Wesson
>-- End of excerpt from Vince Wolodkin



-- 
Rick H. Wesson