Hello William,
Not what I meant. Sorry if I wasn't clear.
Imagine a customer who gets confused / misled and renews somewhere other
than where He/She registered a domain? Does the RSP who registered the
domain originally continue to provide parking, DNS, email forwarding if
those services are provided as part of the ongoing renewal fees at the
RSP?
No.
Is the customer suprised when His/Her site drops off the net and email
is broken after renewing at a "rougue" RSP?
Yup.
This is about the customer's perception of the fairness / complexity of
the whole process, and our ability to "protect" our customers from what
is clearly a hole in this system.
I would rather see an easy to use RSP transfer mechanism, not this
"renew anywhere" approach.
Ken
http://pacificdomains.net
> Hello Ken,
>
> Tuesday, January 02, 2001, 8:19:45 PM, Ken wrote:
>
> > Scott,
>
> > Thanks for clearing that up.
> > On to the next question:
>
> > Does the "sponsoring RSP" in effect take this domain from the previous
> > RSP? They clearly take the profit. Do they provide the DNS? The parking?
> > The Support? No.
>
> > We have value added services (parking, DNS + more) that are included
> > with registration, and this will seriously complicate things on our end.
> > This will be difficult for many customers to understand. We certainly
> > never intended to provide these services on an ongoing basis without the
> > recurring income from renewals.
>
> Those services should not be dependent upon the OpenSRS data. You
> should have seperate services management interfaces for those
> services, that are outside of the OpenSRS interface.
>
> The only exception to that rule should be if you developed your own
> clients and control access to the authentication data in that way, as
> you noted. Any RSP who is depending on the OpenSRS authentication and
> client code to also control things like DNS or other services has
> already made a huge mistake.
>
> --
> Best regards,
> William mailto:[EMAIL PROTECTED]
>
>
--
Ken <[EMAIL PROTECTED]>
