To:
<budi@alliance.globalnetlink.com>, <ietf-provreg@cafax.se>
From:
"Peter Mott" <peter@2day.com>
Date:
Sat, 6 Jan 2001 22:32:11 +1300
Importance:
Normal
In-reply-to:
<200101052239.QAA09535@alliance.globalnetlink.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
RE: Definition of Registry
> Peter, > I still think that the user/registrant/registered entity > is the one that has the power to change the data in > the registry. (Through some kind of certificate.) > > However, she can delegate the right to a registrar. > ie. a registrar can change the data, on behalf of her. > It is easy to transfer authority/delegation from one > registrar to another registrar if she wishes. > Just revoke the certifiate and issue an new one. > > Maybe something like this? > > Registry > | > +--------+-----------+ ... > | | | > User/ registrar registrar > Registrant | | > +--+---+ > | | > User/ > Registrant Above is based on a technical/data management perspective. It does not address business relationship, contract or liability issues. For example, if the registry sells domain name registration services directly to registrants, then it is competing with its registrar customers. It also means the registry has to charge a domain name registration fee of some sort to the registrant directly, potentially managing thousands of accounts and all the time taking its focus away from its core business - that of providing a register that records domain name registration contracts executed by registrars. There are several others that make it less than desirable as well, but I wont go into them here. My preferred model sees the registry charging each accredited registrar a monthly fee that represents their share of the cost of providing the registry service. The registry should not charge registrars fees that relate to specific domain names. This is where I think the ICANN gTLD model and the NSIregistry modus operandi could be improved to reduce complexity and cost. Anyway, I suspect this thread is now off topic. Most people here want to build a protocol based on a technical view, not one that takes into account business relationships and legal contracts. Regards Peter Mott Chief Enthusiast 2day.com -/-