Eric,
I'm asking the question primarily from the registrar perspective. As in,
does it make sense to give registrars the option of providing a service to
their customers that will block any transfer request from another registrar?
I'm leaning towards "yes", leaving the decision to use such a service (which
could of course be undone or removed if needed) up to whomever might find it
valuable.
Scott Hollenbeck
Network Solutions, Inc. Registry
-----Original Message-----
From: Eric Schaetzlein [mailto:eric@schlund.de]
Sent: Wednesday, September 06, 2000 3:49 PM
To: Hollenbeck, Scott
Cc: 'NSI RRP Mailing List'
Subject: Re: [NSI-RRP] Prohibiting Transfer
Hi Scott,
I think you can do both things in both ways -
a) blocking fraudulent transfers of V.I.P. domains with auto-NACKs or LOCKs
b) delay/block legitimate transfers with auto-NACKS or LOCKs
But clearly LOCKs are handled at the registry level and therefore are a
stronger means
for a) as well as b)
So the question would be: let the registrars do the work or the registry?
Eric
On 2000/09/06, Hollenbeck, Scott wrote:
> There's been a recent discussion among some of the NSI Registry's
registrar
> customers about using a domain status indicator to block domain transfer
> requests. Does anyone here feel strongly one way or another about the
idea
> of having a status indicator that means that everything is OK with the
> domain, but transfer requests will be automatically rejected?
>
> Some registrars claim that such a feature will help "lock down" a domain
> from fraudulent transfer requests. On the other hand, others claim that
it
> could be used to delay or block legitimate transfer requests. Should
there
> be a GRRP requirement to provide a feature that will automatically reject
> transfers?
---------
See http://www.nsiregistry.com/maillist/rrp/
for message archives and subscription management information.
This archive was generated by hypermail 2b29 : Wed Sep 06 2000 - 20:04:55 EDT