ICANN ICANN Email List Archives

[comments-rpm-requirements-06aug13]


<<< Chronological Index >>>    <<< Thread Index >>>

RPM comment agreeing with Verisign comment

  • To: comments-rpm-requirements-06aug13@xxxxxxxxx
  • Subject: RPM comment agreeing with Verisign comment
  • From: "Edwin Hayward" <ehayward@xxxxxxxxxxxxxxxxxxxxxx>
  • Date: Tue, 17 Sep 2013 12:48:36 +0100

IDN domains have had to compromise on the "bit after the .com" for 
over a decade for the simple reason that there were no IDN TLDs 
available.

Now that Verisign is proposing to rectify this anomaly by allowing 
owners of an IDN domain ending in .com (e.g. a Japanese-language IDN 
domain) to receive the exact match domain to their existing domain 
name in the native language equivalent of .com, this is a proposal to 
be lauded not opposed.

It makes no sense at all for two different entities to be given the 
rights to register:

keyphraseinalanguage.com
keyphraseinalanguage.[IDN-version-of-.com]

For example, we own .com and under Verisign's suggestion we could 
also own .which is the identical domain name except for the 
.com/IDNcom distinction.

To allow two different registrants to own such domain names is to 
invite mass confusion and destroy trust in the IDN .coms before they 
have a chance to establish themselves.

Edwin Hayward
Memorable Domains Ltd
-- 
Edwin Hayward - ehayward@xxxxxxxxxxxxxxxxxxxxxx
Memorable Domains Ltd
"The Generic Domain Name Specialists"
http://www.memorabledomains.co.uk/
Unit 57, 23 King Street, Cambridge CB1 1AH
Registered in England and Wales number 07161669
VAT Registration 996422380




<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy