Jump to content

.ком: Difference between revisions

From ICANNWiki
← Older edit
VisualWikitext
No edit summary
No edit summary
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{TLD|
{{TLD|
|logo  =  
|logo  =  
|status = Proposed
|status = Delegated
|country  =  
|country  =  
|language = Russian
|language = Russian
Line 16: Line 16:
}}
}}


'''.ком''' is an [[IDN]] [[gTLD]] being proposed in [[ICANN]]'s [[New gTLD Program]]. The applicant is [[Verisign]].<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref>
'''.ком''' is an [[IDN]] [[gTLD]] delegated in [[ICANN]]'s [[New gTLD Program]]. [[Verisign]] manages the TLD and is its [[Registry]]. The proposed application succeeded and was delegated to the [[Root Zone]] on 28 July, 2015.<ref name="delegation">[http://newgtlds.icann.org/en/program-status/delegated-strings Delegated String, ICANN.org] Retrieved 30 Jul 2015</ref>
.<ref>[http://newgtlds.icann.org/en/program-status/application-results/strings-1200utc-13jun12-en Reveal Day 13 June 2012 – New gTLD Applied-For Strings]</ref>
===IDN Transliterations of .com & .net===
===IDN Transliterations of .com & .net===
Verisign's [[Pat Kane]] noted in January 2012 that the company was planning on applying for "about 12" new gTLDs, and noted that most of these were going to be [[IDN]] transliterations of [[.com]].<ref>[http://seekingalpha.com/article/322517-verisign-management-discusses-q4-2011-results-earnings-call-transcript?part=qanda 2011 Results Earnings Call Transcript], SeekingAlpha.com. Published 26 January 2012.</ref> Expected languages included Japanese, Korean, Chinese, Cyrillic, Arabic, and Hebrew.<ref>[http://domainnamewire.com/2012/01/26/verisign-plans-to-apply-for-about-12-new-top-level-domain-names/ Verisign Plans to Apply for About 12 New Top Level Domain Names], DomainNameWire.com. Published 26 January 2012.</ref><ref>[http://domainincite.com/verisign-to-apply-for-a-dozen-new-gtlds/ Verisign to Apply for a Dozen New gTLDs], DomainIncite.com. Published 27 January 2012.</ref>
Verisign's [[Pat Kane]] noted in January 2012 that the company was planning on applying for "about 12" new gTLDs, and noted that most of these were going to be [[IDN]] transliterations of [[.com]].<ref>[http://seekingalpha.com/article/322517-verisign-management-discusses-q4-2011-results-earnings-call-transcript?part=qanda 2011 Results Earnings Call Transcript], SeekingAlpha.com. Published 26 January 2012.</ref> Expected languages included Japanese, Korean, Chinese, Cyrillic, Arabic, and Hebrew.<ref>[http://domainnamewire.com/2012/01/26/verisign-plans-to-apply-for-about-12-new-top-level-domain-names/ Verisign Plans to Apply for About 12 New Top Level Domain Names], DomainNameWire.com. Published 26 January 2012.</ref><ref>[http://domainincite.com/verisign-to-apply-for-a-dozen-new-gtlds/ Verisign to Apply for a Dozen New gTLDs], DomainIncite.com. Published 27 January 2012.</ref>
Line 23: Line 24:


In the end, the languages chosen for transliterations are: Thai, Deva, Korean (Hang), Chinese (Hant/Traditional & Hans/Simplified), Hebrew, Russian, Arabic, Japanese. The two non-IDN applications by the company are for [[.comsec]] and [[.verisign]].
In the end, the languages chosen for transliterations are: Thai, Deva, Korean (Hang), Chinese (Hant/Traditional & Hans/Simplified), Hebrew, Russian, Arabic, Japanese. The two non-IDN applications by the company are for [[.comsec]] and [[.verisign]].
In July 2013, Verisign's [[Pat Kane]] outlined in an article<ref>[http://blogs.verisigninc.com/blog/entry/update_on_verisign_s_idn Update on Versigns IDNs Versigininc.com] Retrieved 4 Oct 2013</ref> the company's plans for allowing existing registrants of second-level [[IDN]] domain names to secure the matching domain under Verisign's new [[IDN]] gTLDs. For example, if you're the registrant of the Hebrew word for "website" that is registered as a second-level domain under [[.com]], you will have the rights to that second-level name under the gTLD "[[.קוֹם|קוֹם.]]" but you will not have the rights under the Hebrew transliteration of ".net" if it existed.<ref>[http://domainincite.com/13702-verisign-lays-out-buy-once-idn-gtld-plans Verisign lays out buy once IDN gTLD plans, Domain Incite] Retrieved 4 Oct 2013</ref>
===Application===
===Application===
Excerpted from response to question #18 in TLD application:
Excerpted from response to question #18 in TLD application:
Line 31: Line 35:


The initial target audience for CYRILLIC_TRANSLITERATION_OF_.COM is the registrants of the more than 30,000 Cyrillic IDN second-level addresses in .com. These registrants will have the opportunity to register their IDN.com addresses as IDN. CYRILLIC_TRANSLITERATION_OF_.COM addresses."<ref>[http://gtldresult.icann.org/application-result/applicationstatus Application Download from gTLDresult.ICANN.org]Retrieved 16 Jan 2013</ref>
The initial target audience for CYRILLIC_TRANSLITERATION_OF_.COM is the registrants of the more than 30,000 Cyrillic IDN second-level addresses in .com. These registrants will have the opportunity to register their IDN.com addresses as IDN. CYRILLIC_TRANSLITERATION_OF_.COM addresses."<ref>[http://gtldresult.icann.org/application-result/applicationstatus Application Download from gTLDresult.ICANN.org]Retrieved 16 Jan 2013</ref>
==Objection==
An official Legal Rights Objection was filed by Regtime Ltd.; Legato Ltd. against the applicant.<ref>[http://www.wipo.int/amc/en/domains/lro/cases/ LRO Cases, WIPO.int]</ref>
A Legal Rights Objection, as defined by the ICANN approved mediator, [[WIPO]], is when, "third parties may file a formal objection to an application on several grounds, including, for trademark owners and Intergovernmental Organizations (IGOs) [..] When such an objection is filed, an independent panel (comprised of one or three experts) will determine whether the applicant’s potential use of the applied-for gTLD would be likely to infringe [..] the objector’s existing trademark, or IGO name or acronym."<ref>[http://www.wipo.int/amc/en/domains/lro/ LRO, WIPO.int] Retrieved 25 March 2013</ref>
==References==
==References==
{{reflist}}
{{reflist}}
Line 36: Line 44:
[[Category:TLD]]
[[Category:TLD]]
[[Category:Technology New gTLDs|ком]]
[[Category:Technology New gTLDs|ком]]
__NOTOC__

Latest revision as of 21:55, 30 July 2015

Status: Delegated
Language: Russian
Translates to: Transliteration of "com"
Manager: Verisign
Registry Provider: Verisign
Type: IDN gTLD
Category: Technology
More information:

.ком is an IDN gTLD delegated in ICANN's New gTLD Program. Verisign manages the TLD and is its Registry. The proposed application succeeded and was delegated to the Root Zone on 28 July, 2015.[1] .[2]

IDN Transliterations of .com & .net[edit | edit source]

Verisign's Pat Kane noted in January 2012 that the company was planning on applying for "about 12" new gTLDs, and noted that most of these were going to be IDN transliterations of .com.[3] Expected languages included Japanese, Korean, Chinese, Cyrillic, Arabic, and Hebrew.[4][5]

During its first quarter earnings report, on April 26, 2012, it was confirmed that Verisign would be applying for 14 new gTLDs, 12 of which are foreign language transliterations of .com and .net.

In the end, the languages chosen for transliterations are: Thai, Deva, Korean (Hang), Chinese (Hant/Traditional & Hans/Simplified), Hebrew, Russian, Arabic, Japanese. The two non-IDN applications by the company are for .comsec and .verisign.

In July 2013, Verisign's Pat Kane outlined in an article[6] the company's plans for allowing existing registrants of second-level IDN domain names to secure the matching domain under Verisign's new IDN gTLDs. For example, if you're the registrant of the Hebrew word for "website" that is registered as a second-level domain under .com, you will have the rights to that second-level name under the gTLD "קוֹם." but you will not have the rights under the Hebrew transliteration of ".net" if it existed.[7]

Application[edit | edit source]

Excerpted from response to question #18 in TLD application:

"As of this writing, more than 800,000 internationalized second-level domain names are registered in .com, including more than 30,000 in Cyrillic. The CYRILLIC_TRANSLITERATION_OF_.COM gTLD, along with the other proposed IDN transliterations of .com, provide an immediate benefit to registrants of those names by giving them the opportunity to register IDN second-level domain names as “IDN.IDN” domain names. That is, registrants can use their preferred script in both the second-level domain name and the gTLD name. Doing so improves these domain names’ functionality and accessibility to speakers of non-Latin-based languages.

[..]

The initial target audience for CYRILLIC_TRANSLITERATION_OF_.COM is the registrants of the more than 30,000 Cyrillic IDN second-level addresses in .com. These registrants will have the opportunity to register their IDN.com addresses as IDN. CYRILLIC_TRANSLITERATION_OF_.COM addresses."[8]

Objection[edit | edit source]

An official Legal Rights Objection was filed by Regtime Ltd.; Legato Ltd. against the applicant.[9]

A Legal Rights Objection, as defined by the ICANN approved mediator, WIPO, is when, "third parties may file a formal objection to an application on several grounds, including, for trademark owners and Intergovernmental Organizations (IGOs) [..] When such an objection is filed, an independent panel (comprised of one or three experts) will determine whether the applicant’s potential use of the applied-for gTLD would be likely to infringe [..] the objector’s existing trademark, or IGO name or acronym."[10]

References[edit | edit source]

Retrieved from "https://icannwiki.org/index.php?title=.ком&oldid=103210"