AW: Definition of Registry

["Herbert Vitzthum" <herbert@vitzthum.at>]

Peter,

if the RRP is only for NSI or maybe some new gTLDs fine. If not understand
and accept ccTLD Voice and nearly common way of doeing.

Best Regards

Herbert

> -----Ursprüngliche Nachricht-----
> Von: owner-ietf-provreg@cafax.se [mailto:owner-ietf-provreg@cafax.se]Im
> Auftrag von Peter Mott
> Gesendet: Donnerstag, 04. Jänner 2001 22:15
> An: Jaap Akkerhuis; Hollenbeck, Scott
> Cc: Alf.Hansen@uninett.no; ietf-provreg@cafax.se
> Betreff: RE: Definition of Registry
>
>
> >     OK, how about changing the definition from this:
> >
> >     "Registry: An entity that provides back-end domain name registration
> >     services to registrars, managing a central repository of
> > information
>
> Whats broke here is the notion that a registry provides a domain name
> registration service.  In a competitive model, the registry should only do
> these things:-
>
> *	Provide registrars with access to a shared database
> *	Publish zone files
>
> At no time does the registry register names.  Registration is a task
> completed by the registrar as part of executing a contract it has with the
> registrant.
>
> The registry should not have any interest in the business of domain name
> registration.  Just the business of ensuring accredited registrars can.
>
> My thinking is that the registry exists to complete the tasks
> which cant be
> shared due to the hierarchical nature of the system.  But those
> tasks alone.
>
> The moment you have the registry taking on other tasks, you introduce
> compexity and duplication of responsibility.
>
> Regards
>
> Peter Mott
> Chief Enthusiast
> 2day.com
> -/-