Changes

Line 120: Line 120:  
: ''Main Article: [[New gTLD Program]]''
 
: ''Main Article: [[New gTLD Program]]''
 
After the results of the 2000 and 2003 expansion of new gTLDs, a [[PDP|Policy Development Process]] in connection with the introduction of new gTLDs was developed by the [[Generic Names Supporting Organization]] (GNSO), which lasted from 2005 until 2007. During this Policy Development Process, the GNSO conducted extensive and detailed consultations with all constituencies within the ICANN global internet community. In 2008, 19 Specific Policy Recommendations were adopted by the ICANN Board for the implementation of new gTLDs, which describe the specifics of allocation and the contractual conditions. ICANN involved the global internet community in an open, inclusive and transparent implementation process to comment, review and provide their input toward creating the Applicant Guidebook for New gTLDs. The protection of intellectual property, community interests, consumer protection, and DNS stability were addressed during the process. Different versions and multiple drafts of the Applicant Guidebook were released in 2008. By June 2011, the ICANN Board launched the New gTLD Program, at the same time approving the [[New gTLD Applicant Guidebook]].<ref>[http://newgtlds.icann.org/about/program About the New gTLD Program]</ref>
 
After the results of the 2000 and 2003 expansion of new gTLDs, a [[PDP|Policy Development Process]] in connection with the introduction of new gTLDs was developed by the [[Generic Names Supporting Organization]] (GNSO), which lasted from 2005 until 2007. During this Policy Development Process, the GNSO conducted extensive and detailed consultations with all constituencies within the ICANN global internet community. In 2008, 19 Specific Policy Recommendations were adopted by the ICANN Board for the implementation of new gTLDs, which describe the specifics of allocation and the contractual conditions. ICANN involved the global internet community in an open, inclusive and transparent implementation process to comment, review and provide their input toward creating the Applicant Guidebook for New gTLDs. The protection of intellectual property, community interests, consumer protection, and DNS stability were addressed during the process. Different versions and multiple drafts of the Applicant Guidebook were released in 2008. By June 2011, the ICANN Board launched the New gTLD Program, at the same time approving the [[New gTLD Applicant Guidebook]].<ref>[http://newgtlds.icann.org/about/program About the New gTLD Program]</ref>
 +
 +
===Closed Generic Strings===
 +
After ICANN published information on its 1,930 applications it was immediately noted that some companies had applied for a number of generic terms relevant to their business, writing in their applications that they intended to be the sole registrant for the TLD. There was no [[Brand TLD]] distinction in this round, though there were guesses that ICANN would create rules for such TLDs in any future round. Thus, the closed generic terms violated no rules as developed through the [[GNSO]] process and as included in the Applicant Guidebook. Some noted that this was in fact an intentional byproduct of the program that had been considered while others disagreed.<ref>User Summary, AM</ref>
 +
 +
The largest applicant for closed gTLDs is [[Amazon]], and many worried that their applications to control a large number of generic terms would result in them circumnavigating traditional navigation for shopping online and give them an unfair competitive advantage. Another notable portfolio client with multiple closed generics is [[L'Oréal]].<ref name="WTR">[http://www.worldtrademarkreview.com/daily/Detail.aspx?g=7be56061-2229-412c-8f71-55bc20932cd8&utm_source=buffer&buffer_share=c3e5d WorldTrademarkReview.com]</ref> In late 2012, Amazon and other companies that applied for closed-generic strings received a [[GAC]] Early Warning from GAC Chair, [[Heather Dryden]]. The early warning system is the work of an individual GAC member but signals that the larger GAC organization may later issue official advice recommending the rejection of the TLD application as-is by the [[ICANN Board]]. Those applicants that receive warnings are encouraged to work with the objecting representative. The German representative also raised issues with regards to closed generics.<ref>[http://www.name.com/blog/ntlds/2013/01/the-gtld-land-grab-controversy-google-amazon-and-the-gac-part-ii/ The gTLD Land Grab Controversy Google Amazon and the GAC Part II, Name.com] Pub 14 Jan 2013, Retrieved 6 Jan 2013</ref><ref>[https://gacweb.icann.org/display/gacweb/GAC+Early+Warnings GAC Early Warnings, GACweb.ICANN.org]</ref>
 +
 +
Following further questions ICANN's New gTLD Program Committee looked at the issue. Information on their January meeting that was released in February 2013 shows that they were unclear how to even define a closed generic, what are the common attributes, what an appropriate remediation strategy would be, and further note that there is no violation taking place between the applications and the Applicant Guidebook, and they therefore have no room to comment or change policy without further direction from a policy development process started in the [[GNSO]]. Still, they opened up a public comment period on February 5th, 2013, to ascertain opinions on what a closed generic is, and what are the criteria for which a proposed registry can operate a "closed" or "open" string.<ref>[http://www.icann.org/en/news/announcements/announcement-2-05feb13-en.htm Announcement, ICANN.org]5 February 2013</ref>
 +
 +
Objections to closed generics have come from [[Microsoft]], who notes the danger they pose to competition on the Internet, and an online petition started by Tom Gilles of NewgTLDsite.com.<ref name="WTR"></ref><ref>[http://www.thedomains.com/2013/02/06/microsoft-is-latest-to-come-out-against-closed-generic-new-gtlds-in-letter-to-icann/ Microsoft is Latest to Come Out Against Closed Generic New gTLDs in Letter to ICANN, TheDomains.com] Published and Retrieved 6 Feb 2013</ref>
    
==References==
 
==References==
 
{{reflist}}
 
{{reflist}}
 
[[Category: Glossary]]
 
[[Category: Glossary]]