[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: <ietf-provreg@cafax.se>
CC: <ietf-whois@imc.org>
From: budi@alliance.globalnetlink.com
Date: Fri, 26 Jan 2001 06:22:39 +0700
In-reply-to: <003701c086f6$46260ef0$32272dd4@jamessonyvaio>
Sender: owner-ietf-provreg@cafax.se
Subject: Re: Merging RRP and Whois


> And IMHO, there is no technical reason to forbid a registrant to access
> the registry directly, should certain policy or technical reqirement
> needs it. I am not saying the registry SHOULD (or MUST) do this, but
> that they MAY.

Agree. Why can't we simplify the requirement, ie. the
system (protocol/implementation) should only allow
*one* entity to access (read/write/update) to a record?
This *one* entity could be registrar, reseller, registrant,
registry, whatever. As long it is *one* entity.
(That way it can accomodate any business model.)


-- 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

Home | Date list | Subject list