.москва: Difference between revisions
Due to changes in the FAITID management, Key People section was edited to correctly reflect current structure. |
FAITID is a backend provider for .москва(.xn--80adxhks), using Flexireg platform (TM belongs to FAITID). |
||
(One intermediate revision by the same user not shown) | |||
Line 2: | Line 2: | ||
|logo = Moscow.JPG | |logo = Moscow.JPG | ||
|status = Delegated | |status = Delegated | ||
|manager = Foundation for Assistance | |manager = [[Foundation for Assistance for Internet Technologies and Infrastructure Development|FAITID]] | ||
|country = | |country = | ||
|language = Russian | |language = Russian | ||
|translation = moscow | |translation = moscow | ||
|stringcontention = No | |stringcontention = No | ||
|registryprovider = | |registryprovider = [[FAITID]] | ||
|registrations = | |registrations = | ||
|date = | |date = |
Latest revision as of 05:42, 1 November 2017
Status: | Delegated |
Language: | Russian |
Translates to: | moscow |
Manager: | FAITID |
Registry Provider: | FAITID |
Type: | IDN GeoTLD |
Punycode: | .xn--80adxhks |
More information: |
.москва (the Russian translation for .moscow) is a new IDN GeoTLD that was proposed in ICANN's new gTLD expansion program. The application for the .москва IDN TLD was submitted by the Foundation for Assistance for Internet Technologies and Infrastructure Development (FAITID), a non-profit organization established in 2011 to develop and implement initiatives to increase the use of the Internet in Russian communities and internationally.[1] Their application succeeded and was delegated to the Root Zone on 24 April 2014.[2]
The company is also applying for the English equivalent, .moscow.
The .moscow .москва Project[edit | edit source]
In 2010, The RU-CENTER, a Russian Registrar, initiated the .moscow .москва project and recommended the creation of a special Community Council to handle the applications for the proposed TLDs with ICANN. The center submitted its official proposal to develop the .moscow .москва TLDs to various government agencies in Moscow.[3]
One of the leading newspapers in Moscow, the Moskovskiy Komsomolets, launched a survey on its website to determine if the project was supported by its constituents from September 2 to October 1, 2010. The survey found that the proposals were supported by thousands of individuals and businesses, as well as government agencies in the city.[4] The Moscow Department of Culture and the Moscow Department of Support and Development of Small and Middle Entrepreneurship (DSDSME) supported the recommendation of the RU-CENTER to create a Community Council to supervise the application for the TLDs. In 2011, the Foundation for Assistance for Internet Technologies and Infrastructure Development (FAITD) was established and took-over the responsibilities to manage the .moscow .москва project.[5] [6]
FAITID promoted the .moscow .москва Project during the 2010 RIPE NCC Moscow Regional Meeting, [7] the ICANN 40 Meeting in San Francisco, [8] the ICANN 43 Meeting in Costa Rica, [9] and during various Internet events, conferences and international domain forum.[10]
Application to ICANN[edit | edit source]
FAITD selected Sedari, a TLD business management service provider to help prepare the application for the TLDs with ICANN. FAITID Board Member Dmitry Burkov expressed his confidence in the Sedari management and cited the company's knowledge and expertise in TLDs and ICANN procedures. He said, "Implementation of any TLD is a complicated project with many issues to resolve. That’s why we’ve chosen Sedari as our strategic international partner for .MOSCOW and .МОСКВА. Sedari management has the experience and industry knowledge on ICANN that makes us confident the company is familiar with all the procedures of the corporation, in particular related to new TLDs. Together with Sedari we’ll make the project for Moscow top-level domains successful giving Russian users more choice in the domain name space."[11]
On April 12, 2012, the foundation confirmed that its application for the .москва and .moscow TLDs had been submitted to ICANN and that it had paid the requisite $185,000 for each application. FAITID also said that the standard price for registration fee for every domain name will be set at 600 Roubles (20$).[12]
Supporters[edit | edit source]
As of May 2012, there are 17,666 supporters for the .moscow .москва project. Letters of endorsements were received from the following government agencies and officials in Moscow:[13]
- Moscow Department of Support and Development of Small and Middle Entrepreneurship
- Moscow Department of Culture
- Minister of Moscow Government Artyom Ermolaev
- Moscow Government
- Department of Information Technology of Moscow
- Coordination Center for TLD RU
- Russian Association for Electronic Communications
Contract Signed[edit | edit source]
On 19 December 2013 Foundation for Assistance for Internet Technologies and Infrastructure Development received a Registry Agreement signed by ICANN for .москва after passing all the required processes needed to become a Registry Operator for the string.[14]
Delegation and Availability[edit | edit source]
.москва was delegated to the Root Zone of the DNS on 24 April, 2014, completing the successful application for the string.[2]
References[edit | edit source]
- ↑ About TLDs .MOSCOW and .МОСКВА
- ↑ 2.0 2.1 Delegated Strings, ICANN.org Retrieved 30 May 2014
- ↑ RU-CENTER has announced the idea of TLDs .MOSCOW and .МОСКВА implementation
- ↑ A poll in the support of TLDs .MOSCOW and .МОСКВА started on the “Moskovskiy Komsomolets” website
- ↑ About TLDs .MOSCOW and .МОСКВА
- ↑ About the Foundation
- ↑ TLDs .MOSCOW and .МОСКВА were introduced during the RIPE NCC Moscow Regional Meeting 2010
- ↑ Moscow TLDs will be introduced on ICANN Meeting in San Francisco
- ↑ Final Consultations on Application for .MOSCOW and .МОСКВА Domains Held in Costa Rica
- ↑ .MOSCOW and .МОСКВА TLDs Have Been Presented at International Domain Forum in Bulgaria
- ↑ Sedari signs with dot Moscow bidders
- ↑ Application for .MOSCOW and .МОСКВА TLDs was Submitted to ICANN
- ↑ Official Documents
- ↑ Registry Agreements, ICANN.org Retrieved 30 Dec 2013