At 06:10 PM 12/19/01 -0500, [EMAIL PROTECTED] wrote:
>Scott/Chuck?
>
>Domain Lock as standard?
>sounds good to me.
Going to try and get this early in the new year (first 35-75 days). Here is
my current thinking - let me know what you think:
- reseller has ability to set this through RWI
- on for all sponsored names (may be issues with this - requires
registry overhead)
- on for a specific name
- on for a "selected by search (including registrant contact
info)" subset
- off only one name at a time
- Reseller has ability to set this through the API:
- on for a specific name
- off only one name at a time
Further:
- reseller can globally set switch in RWI that allows control of the
setting through manage
- if on, allows new manage functionality to toggle within normal profile rules
Let me know how this sounds to you -
>Do any other registrars offer domain lock at no charge?
I have heard some do, but I do not really know. I only use OSRS.. :)
FWIW, the logic (or lack of it) behind delaying the release of this feature
was largely my fault... I got it stuck in my head that there was value in
this, and that we should somehow charge, or provide a premium service that
allows good security options. It just annoyed me that just giving it to
registrants was leaving money on the table, and that it offered only
marginally better security than what they have today. My thinking has
evolved, and I know beleive:
- resellers can add the value (provide more robust security options) and
manage the risk as they fit - this makes sense as you have the customer
relationship, and therefore naturally have lots of natural levers to do this
- the value here is clear - however, it is not something that we can bother
to charge for as a premium service - not only would running a service be
challenging, but the billing component would likely cost as much as much to
develop as the service might generate in revenue
Regards,
sA
sA
