An ISP that intends not to give services promised, can easily run a two line Perl script to capture customer's entered password and login name illegally and then change the password and information on that domain. A "bad" ISP can do this regardless if he has direct control over the domain or not. Your arguement fails here.
Farhad Sadeghi
Coolfred Internet Services
http://WWW.COOLFRED.NET
--- Tim Jung <tjung@igateway.net> wrote:
>Your not even taking into account the other side of the getting hosed. I
>register a domain with an RSP, he promises me the moon, and 10 hours of free
>web design, free domain registration, and all of this but reneges on the
>deal. I don't get 10 hours of web design, I get none, he still hasn't even
>setup my domain on his servers after 6 weeks. So I issue a charge back and
>move my domain to another hosting company. Now you telling me since I picked
>the domain and it is my company name with a ".com" tacked on the end that he
>gets my company's domain since he reneged on the deal and didn't give me
>what I was promised and wasted 6 weeks of my time? I think a free domain
>registration is worth 6 weeks of my company's wasted time no problem, and
>I'm sure not going to pay for something I never got, web hosting.
>
>So how do you handle the above? Who gets the domain? What if I even have a
>trademark on the name, acme-brooms-and-sticks.com(tm), what then?
>
>See it isn't so simple.
>
>Tim Jung
>System Admin
>Internet Gateway Inc.
>tjung@igateway.net
>
>----- Original Message -----
>From: "Coolfred Internet Services" <coolfred@coolfred.org>
>To: <eric@brouhaha.com>; <discuss-list@opensrs.org>
>Sent: Friday, March 03, 2000 9:11 PM
>Subject: Re: New Ideas for OpenSRS (or wish list) - Reseller Access
>
>
>>
>>
>> --- Eric Smith <20000303030705.F321E80B9@sitemail.everyone.net> wrote:
>> >Coolfred Internet Services <coolfred@coolfred.org> wrote:
>> >> It is rediculous to say this is "the risk" you must accept and this is
>like
>> >> "any other business". If a guy doesn't pay for his hosting account, I
>simply
>> >> lock his account. But to recover, say $1000, you would have to sell a
>100
>> >> domains for $20 to recover this loss.
>> >
>> >It's not the least bit ridiculous. All normal businesses have to deal
>with
>> >some amount of sales being fraudulent and uncollectable. There's no
>reason to
>> >expect that a domain registration business wouldn't have the same
>problem.
>> >
>> >If you want to avoid it, only accept checks and money orders, and do not
>> >register the domain(s) until you've confirmed with the bank that the
>> >funds have cleared. At that point there is no way for the remitter to
>> >call them back. Of course, you're going to have a hard time finding many
>> >customers if you do business this way.
>> >
>> >> OpenSRS admins should seriously reconsider this policy.
>> >
>> >What do you want OpenSRS to do about it? They're certainly not going to
>> >assume the liability or risk for your business dealings with your
>> >customer. That *would* be ridiculous.
>>
>> "What do you want OpenSRS to do about it?" :
>> I don't "expect" them to do anything. All the discussions here are meant
>to be constructive, not to bash OpenSRS or anyone else. That would be like
>shooting yourself in the foot. What I "hope" they would do, is give full
>control to resellers so then:
>> A) I can give better service to legit customers
>> B) I can give quicker service to legit customers
>> C) I can present our company as a competent service provider in domain
>registry and not just as a mark-up middleman
>> D) I can take back domains from unpaid customers, be it fraud or simply a
>customer not paying the bills (just as I do with their accounts)
>> E) I can give back the domains AFTER the customer has paid the bills (just
>as I do with their accounts)
>> F) Take over and sell any domains which were registered through fraudulent
>means to recover losses (just as I do for custom orders not paid for)
>> G) Give my customers less head-ache when they lose or forget their
>passwords or change emails or both.
>>
>> IMHO each and all of the above are reasons enough to go shead and give
>resellers more power. At the same time I accept that there needs to be some
>monitoring involved such as logging of activities to catch "bad" resellers.
>In such a case I believe the punishment should be as severe as immediate
>termination of all access as a reseller, and loss of all remaining RCUs and
>loss of control of all previously resold domains.
>>
>> Now someone mentioned "what if" the domain is worth 2 million dollars and
>the bad-reseller does not care about all that. Well I think a company whose
>just domain name is worth 2 million dollars would be competent enough to sue
>the bad-reseller AND recover all their losses. Additionally noone is saying
>they WOULD get away with it. Obviously if the reseller is found guilty, the
>domain will be returned by OpenSRS to the legit owner.
>>
>> Now all this arguement is about the fact that we are assuming that this is
>all too much work even if one bad reseller hijacks a domain. Well in my
>opinion the total work involved in settling issues with customer service,
>lost passwords, changed emails, etc. etc. will be more time consuming,
>specially for those of us who plan on selling 20 or 30 domains a day at some
>point.
>>
>> Obviously each and all resellers have their own biased opinion about this
>depending on which scenario is better for them. But can we get some feedback
>on this issue from OpenSRS guys please? Chuck? Scott? Anyone? What is really
>holding you back from giving resellers more power to administer the domains
>and have control over them?
>>
>>
>> Farhad Sadeghi
>> Coolfred Internet Services
>> http://www.coolfred.net
>>
>>
>> _____________________________________________________________
>> Email Powered by Everyone.net
_____________________________________________________________
Get your Free Email address at http://freemail.coolfred.org brought to you by http://www.coolfred.net
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:24 EDT