<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [registrars] DRAFT Standard form for use by losing registrars after a transfer is initiated
- To: "Larry Erlich" <erlich@xxxxxxxxxxxxxxxxxx>
- Subject: RE: [registrars] DRAFT Standard form for use by losing registrars after a transfer is initiated
- From: "Bruce Tonkin" <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 4 Sep 2003 13:09:18 +1000
- Cc: <registrars@xxxxxxxx>
- Sender: owner-registrars@xxxxxxxxxxxxxx
- Thread-index: AcNyLcZl7zuNKw0NQMq1G/uzxhBdugAYzFyg
- Thread-topic: [registrars] DRAFT Standard form for use by losing registrars after a transfer is initiated
Hello Larry,
>
> If "must include" then gaming can still be done
> simply by adding other language to the message
> that includes the information specified.
The intent is that additional (often misleading) information cannot be
included in the standardised message. Registrars are free to send
separate messages that contain any material they want, assuming they are
compliant with local trade practices laws.
>
> It would probably be a good idea to
> add some text stating what it means
> to "change registrar" exactly and what
> the function of a registrar is. Customers often
> don't know what role
> the registrar plays.
Please suggest some succinct wording.
> I have seen multiple
> cases of customers who are convinced by their
> web hosting company that they need to switch
> registrar in order to get hosting.
Yes - I have come across this problem too.
A separate issue is probably producing a consumer guide to purchasing
domain names.
I am planning to have a go at producing one for use in Australia (on a
voluntary basis), with input from other registrars.
By far the most preferable approach is for industry to agree on best
practice approaches. It is only when there is market failure (partly
due to the design of the registry transfer business processes that allow
a losing registrar to deny a customers right to transfer) that
regulation should be required. I believe that the registrars
constituency did attempt to resolve the issue internally but that
failed, and domain name users have demanded a change (just look at the
complaints received by ICANN and registrars on this issue).
Regards,
Bruce
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|