IDN Forums - Internationalized Domain Names  
Home | Advertise on idnforums | Premium Membership

Go Back   IDN Forums - Internationalized Domain Names > IDN Discussions > General Discussion

General Discussion Feel free to talk about anything and everything in this board.

LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 18th January 2013, 12:09 PM
555 555 is offline
ком.ком コム.コム
Join Date: Jan 2006
Posts: 4,141
iTrader: (33)
Rep Power: 1708
555 has disabled reputation
GAC Early Warnings just got a whole lot more important

If i understand it correctly then this is what RD was hoping to see in order to insure registrant's rights to existing gTLD's IDN.IDN/Other variants when applicable. Problem is it is not clear to me if this only applies to the strings receiving the GAC early warnings or to all applicants.

"This is a bit of a big deal. It refers to Question 18 in the new gTLD application, which was introduced late at the request of the GAC and covers the “mission/purpose” of the applied-for gTLD.

Answers to Question 18 are not scored as part of the new gTLD evaluation, and many applicants took it as an invitation to waffle about how awesome they plan to be.

Now it seems possible they they could be held to that waffle.

Crocker told Dryden (with my emphasis):

The New gTLD Program does not currently provide a mechanism to adopt binding contractual terms incorporating applicant statements and commitment and plans set forth within new gTLD applications or arising from early warning discussions between applicants and governments. To address concerns raised by the GAC as well as other stakeholders, staff are developing possible mechanisms for consideration by the Board New gTLD Committee. That Committee will discuss the staff proposals during the upcoming Board Workshop, 31 Janaury – 2 February.

In other words, early next month we could see some new mechanisms for converting Question 18 blah into enforceable contractual commitments that new gTLD registries will have to abide be."


Question 18 is the part the applicant has to explain how/what they plan for the "New" gTLD

The not so short answer to question 18 from the .орг application (.org):


18(a). Describe the mission/purpose of your proposed gTLD.

The mission⁄purpose of the IDN gTLD is to offer the Eastern European language community (Bosnian, Bulgarian, Belarusian, Macedonian, Russian, Serbian, and Ukrainian) a gTLD that is an in-language and localized translation of .ORG, and to promote the mainstream adoption of Internationalized Domain Names (IDNs).

PIR wishes to extend its stewardship of .ORG to other language communities, providing a consistent end-user experience across the IDN equivalents. PIR’s deployment of an IDN, as a mainstream and proven registry operator, will serve as an important boost to promote the adoption of IDNs, and will signal to application developers to support IDNs, which in turn leads to a better user experience and usability of IDNs.

History and Way Forward

While the content of a website can appear in any language, domain names have generally been limited to the characters used in English. Since the majority of the world speaks a language other than English, this can present a significant barrier to Internet access for many cultures.

PIR has taken the first step in supporting Non-English languages through the introduction of IDNs at the second level for .ORG. These .ORG second level IDNs include Danish, German, Hungarian, Icelandic, Korean (Hangul), Latvian, Lithuanian, Polish, Spanish, Swedish, Cyrillic, and Chinese IDN.

These second-level IDNs, where the name (left of the dot) is in a Non-English language and the gTLD (right of the dot) remains in English, have been available for a number of years but only offer a partial solution for the language communities. Some languages, like Arabic, are written from right to left. IDNs at the second level are not very useful for the communities that use these languages because users would need to change both the type direction and script in the middle of entering a domain name. With this IDN gTLD application, we wish to provide a complete in-language domain name recognized as related to .ORG and a more elegant experience for the Internet user.
Public Interest Registry (PIR) manages .ORG, an unrestricted gTLD – the domain which has served the public interest for more than 25 years.
The Cyrillic IDN gTLD will be a valuable part of ICANN’s expansion consistent with guidance defined in Section 9.3 of the Affirmation of Commitments (AoC). Specifically, the Cyrillic IDN gTLD will promote the goals of the new gTLD round and the AoC reflected in the following ways:
• A stable launch of a new gTLD that provides registrants a clear choice with a relevant domain;
• Internet users trusting in the authenticity of an in-language IDN gTLD representing similar values of .ORG; and
• An active community involvement in the IDN gTLD, such as through PIR’s .ORG Advisory Council.

The Cyrillic IDN gTLD, administered in a trusted and responsible manner by PIR, will give organizations across this language community a unique, relevant, respected place on the Internet.

18(b). How do you expect that your proposed gTLD will benefit registrants, Internet users, and others?

The Cyrillic IDN gTLD will benefit registrants, Internet users, and others as described below in response sections 18b(i-v).

18b(i) The Cyrillic IDN gTLD’s area of specialty is in providing registrants a local language domain name for greater inclusiveness of Internet users. A goal of the Cyrillic IDN gTLD is to carry forward the reputation of .ORG as being trustworthy, well-intentioned, valuable information, and reliable. These are the top five brand attributes of .ORG, as indicated in PIR’s annual brand research conducted in 2008-2011. PIR will operate the IDN gTLD registry in the same exemplary manner as it does for .ORG in order to carry forward the environment conducive to such positive brand recognition.

18b(ii) The Cyrillic IDN gTLD will advance the goals of competition, differentiation and innovation in a number a ways. Creating a language-unique IDN gTLD for organizations will advance competition among TLDs that currently offer domain service to community organizations.

Community organizations use .ORG today, as well as a wide selection of TLDs, ccTLDs, sTLDs. A uniquely identifiable IDN gTLD for organizations will provide the same differentiation that organizations can achieve today with .ORG, but within their own language. This distinction also benefits Internet users who are searching for language specific organizations on the Internet.

18b(iii) With each IDN gTLD that is launched, the Internet takes a big step forward in becoming truly global. English might be a popular language in the world, but there are many people who donʹt use it, or who use other languages together with it. With IDNs, the Internet will reach many more people, who previously were either completely offline, or who used the Internet only in a limited way. The Cyrillic IDN gTLD will make the Internet more user-friendly for this language community. Internet users will now be able to write a domain name or an URL exactly the way it is supposed to be written - i.e. without substituting the special symbols in Latin-based languages, or without transcribing non-Latin languages into English.

PIR’s Abuse Prevention and Mitigation policies (summarized in response to Evaluation Question #18b(iv) and detailed in response to Evaluation Question #28) will strive to make this Cyrillic IDN gTLD a safer and more trustworthy environment for Internet users. The policies combat fraudulent activity and abusive practices prevalent in other top-level domains.

18b(iv) To achieve the above goals and assure that the Cyrillic IDN gTLD domain names are allocated in an appropriate manner, PIR has developed a set of IDN Registration Policies and corresponding compliance and enforcement mechanisms.
The policies are built to match the need of the IDN registrants, based on experience from the .ORG gTLD management since 2003; and to ensure a higher security level for domain names than what currently is considered standard global requirements for gTLDs today.

IDN Registration Policies

The registration policies in support of the goals are described in the following summary and are detailed later in this section.
• Registrant Eligibility Requirements – there are no eligibility restrictions for the IDN domain names, in order to serve a variety of community organizations and remain consistent with the unrestricted use of .ORG.
• Content and Use Restriction Policy – ensures that IDN domain names are not used for illegal or fraudulent purposes or activities.
• Compliance Functions – ensures ongoing compliance of the Abuse Prevention and Mitigation and the Content and Use Restriction Policy.
• Name Selection Policy – ensures that initially only Cyrillic IDN scripts for domain names are registered.
• Reserved Name Policy – names⁄types of domain names will initially be reserved from registration under the Cyrillic IDN.
• Registry Name Policy – names⁄types of domain names will be held from general availability, these will be used in support of the registry.

The following policies support the IDN goals and are detailed in subsequent Evaluation Questions of the application dedicated to such policies, as noted below.

• Abuse Prevention and Mitigation – includes the Anti-Abuse Policy which addresses the identification and prompt action taken on malicious use of domain names. Detailed descriptions of the policies can be found in response to Evaluation Question #28.
• Rights Protection Mechanisms – to protect intellectual property holders under the Trademark Clearinghouse, Uniform Dispute Resolution Policy (UDRP), Uniform Rapid Suspension (URS), Post-Delegation Dispute Resolution Policy (PDDRP), in addition to the Sunrise services and policies that can be found in response to Evaluation Question #29.

PIR will review all policies and processes on an annual basis with involvement from the PIR’s .ORG Advisory Council.

Specific Policy Details

Content and Use Restriction Policy: Abusive use of the IDN domain names will not be tolerated by PIR. The following use and content limitations apply:
• Any illegal or fraudulent usage of the IDN domain name is not allowed, including but not limited to phishing and pharming attacks, distribution of malware, and distribution of adult content.
• Registration and use of a domain name in violation of Rights Protection Mechanisms is not allowed.

Violations of any of the IDN Registration Policies may be grounds for loss of registration, pursuant to the enforcement mechanism discussed below.

Compliance Functions: While disputes will be managed directly by the dispute resolution providers, PIR will to conduct random compliance efforts across all the IDN Registration Policies. Periodically PIR will conduct through compliance staff a sample of IDN registrations to verify compliance with the name and use policy.

If a registrant is found to not be in compliance the registrant will be notified that the domain will be placed on registry lock and that if the issue is not cured the domain will be terminated.

As part of the compliance function PIR will also incorporate its existing expertise, obtained through its management of .ORG, to monitor and take action on any abusive behavior occurring on IDN domain names.

Name Selection Policy: At the time of launch, domain names (to the left of the dot) will be restricted to the same Cyrillic script used to the right of the dot only. As market demands, additional scripts to the left of the dot will be considered for domain name registration.

Reserved Names Policy: The IDN domain name that a registrant wishes to register must fulfill certain name policy criteria. The following names⁄types of domain names will initially be reserved from registration under the Cyrillic IDN:
• All single- and two-character second-level domain names;
• Domains of an inappropriate nature, pursuant to a list defined by PIR and its .ORG Advisory Council;
• Names provided by ICANN as required reserved names;
• A list of generic names defined by PIR and its .ORG Advisory Council. Such names will be released in a specific RFP process.

Registry Name Policy: The following names⁄types of domain names will be held from general availability, these will be used in support of the registry.
• Names to support registry operations, e.g., registry.IDN

Compliance and Enforcement Mechanisms
PIR will take measures to enforce the policies of the IDN gTLD. These measures are addressed via our audit process (described below) and through our defined dispute resolution processes.

A violation of the IDN Registration Policies will be enforced on a case-by-case, fact specific basis, under the process set forth below:
1. Any alleged violation of the Rights Protection Mechanisms shall be enforced under the provisions contained in each of them.

Disputes resulting out of violations of the IDN Registration Policies will be resolved through the Compliance Functions and the Rights Protection Mechanisms. The Rights Protection Mechanisms (Trademark Clearinghouse, UDRP, PDDRP, and the Sunrise services and policies) will be made applicable by the ICANN-Accredited Registrarsʹ registration agreements with registrants. Proceedings under the Rights Protection Mechanisms will be conducted in accordance with the policies and procedures that will be included in an appendix to the Registry Agreement. As set forth in the Compliance Functions, registry operator will review on a random basis, monitor, and verify that any particular domain name is being used in compliance with the Rights Protection Mechanisms processes.

18b(v) PIR will manage the Cyrillic IDN gTLD in accordance with best practices and specific policies around privacy and data protection, as it does for nearly 10 million .ORG registrations today. Specific protections of the WHOIS administered by the registry backend service provider can be found in Evaluation Question #26, and details on our privacy policies in Evaluation Question #28.

Pursuant to its mission, PIR has been conducting outreach since its management of the .ORG domain began in 2003. Ongoing outreach and communications ensures that we meet the projected benefits as described and established in response to #18b(i-v). The Cyrillic IDN language community is large and global in reach. As such, coordinated efforts and international outreach and communication are necessary to drive awareness of the benefits of the IDN for language-unique identification, differentiation, and innovation.

In 2008, PIR conducted focus group meetings in Moscow, Russia to understand the needs of the community and the receptiveness to Internationalized Domain names. The community stated a strong preference to a full IDN experience (an IDN top-level domain) and indicated that an IDN top level domain would lead to mainstream adoption of IDNs.

In 2011, PIR launched a second level Cyrillic IDN (Cyrillic domain name prefix using the “.ORG” top level domain). This implementation gave PIR experience with the language and script table, and allowed us to confirm the Internet user preference for an IDN top-level domain; both provided excellent feedback from the language community to pursue this Cyrillic IDN top level domain.

Based on PIR’s long-term successful management of .ORG and its outreach, it will ensure the secure and stable operation as well as market adoption of the IDN gTLD.

18(c). What operating rules will you adopt to eliminate or minimize social costs?

PIR’s long-standing track record speaks to its core mission to serve the public interest, and thereby minimizing social costs,(e.g. as has been done through PIR’s implementation of anti-abuse policies, the rollout of DNSSEC and active participation in public interest events, and more.) PIR will launch and manage the Cyrillic IDN gTLD in a responsible manner. Our global outreach in preparation of this application provided direct guidance on the specific needs of the community, concerns on policies, procedures for registration and pricing. This knowledge is reflected in this application.

Minimizing negative social costs and consequences on registrants and consumers:
A goal of this name space is to keep impacts and burden to the community nominal, and focus on the positive benefits of having a language-unique IDN domain name. PIR is confident our IDN gTLD domain name registration service, pricing, and related policies do not place burdens on the community, but rather, will support their goals for language uniqueness, differentiation, and innovation.

18c(i) In general, following the initial Sunrise registration processes, registrations will be processed on a first-come, first-served basis. For registrants that were not able to register the name they preferred, and believe such name has been awarded in error to another entity, PIR has developed the Sunrise Dispute Resolution Policy explained in Evaluation Question #29.

18c(ii) PIR will from time-to-time offer discount⁄rebate programs for registrations through its distribution channel.

18c(iii) PIR will offer terms of up to 10 years for domain name registrations. Depending on the needs of registrants and only after consultation with ICANN, PIR may consider offering longer-term contracts. At this time, PIR will not offer permanent contracts.

Depending on the cost of doing business and other economic factors, PIR may from time-to-time increase the wholesale price in accordance with the provisions of Section 2.10 of the new gTLD Registry Agreement.
ロレックス.com رولكس.com Ролекс.com Порше.com 路易威登.com 必胜宅急送.com 香港迪士尼乐园.com Hermè Nestlé.com

Last edited by 555; 18th January 2013 at 12:15 PM..
Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

All times are GMT. The time now is 09:20 AM.

Site Sponsors
Your ad here
buy t-shirt
מחיר הזהב

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.3.0
Copyright 2005

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54