ICANN

From ICANNWiki
Jump to: navigation, search
ICANNLogo.png
ICANNWiki Gold Sponsor
Type: Private, Non-Profit
Industry: Internet Protocol Management
Founded: 1998
Headquarters: 4676 Admiralty Way # 330,
Marina del Rey, CA, USA
Employees: 140 employees
Revenue: $72 million (2011)
Website: icann.org
Blog: blog.icann.org
Facebook: icannorg
LinkedIn: ICANN
Twitter: TwitterIcon.png@ICANN
Key People
Fadi Chehadé, CEO and President

Steve Crocker, Chair of the Board
Jeff Moss VP and Chief Security Officer

ICANN is an acronym for the Internet Corporation for Assigned Names and Numbers, a global multi-stakeholder organization that was created and empowered through actions by the U.S. government and its Department of Commerce.[1] It coordinates the Internet DNS, IP addresses and autonomous system numbers, which involves a continued management of these evolving systems and the protocols that underly them.

While ICANN has its roots in the U.S. government, it is now, and continues to strive to be, an international, community-driven organization. Their management of an interoperable Internet covers 180 million domain names, the allocation of more than 4 billion network addresses, and the support of approximately a trillion DNS look-ups everyday across 240 countries.[2]

ICANN collaborates with companies, individuals, and governments to ensure the continued success of the Internet. It holds meetings three times a year, switching the international location for each meeting; one of these serves as the annual general meeting when the new ICANN Board members take their seats.[3]

Organization & Structure

It is central to ICANN's mission that the organization itself is structured in a way that welcomes a variety of voices and seeks to represent the extremely diverse constituencies with continued interest in the Internet's development, from registries, to corporations, to individual Internet users. In relation to ICANN's structural development, there have been critics who have taken issue with its closed-door sessions, the role of the U.S. Department of Commerce, and other structural and procedural rules.[4] ICANN has been described as being in a contentious oversight situation; with some countries calling for all U.S. influence to be removed from the organization by subordinating it to the U.N.'s jurisdiction, or suggesting similar solutions.[5] ICANN's structure and process is outlined in the ICANN Bylaws.

Board of Directors

Main article: ICANN Board

ICANN is governed by a Board of Directors made up of 15 voting members,[6] and the President and CEO, who is also a voting member. The board is further aided by five non-voting liaisons.[7] From ICANN's inception to December 2011, being a board member was a voluntary position. At that time, the ICANN Board responded to mounting pressure regarding conflicts of interest and the notion that compensation would create a more professional and accountable body by awarding themselves a $35,000 annual salary.[8]

Current Board of Directors

The 15 current directors, and the current CEO, are listed below, along with the organization which nominated them and the length of their term:[9]

Current Non-Voting Liaisons

GNSO

Main article: GNSO

The Generic Names Supporting Organization (GNSO) brings together smaller stakeholder groups, which in turn bring together constituencies and other groups, together into one Supporting Organization to develop policies, form consensus, and make recommendations related to gTLDs to the ICANN Board.[10]

ccNSO

Main article: ccNSO

The Country Code Names Supporting Organization (ccNSO) is an advisory body within ICANN created by and for ccTLD managers, which are the entities that oversee a given nation's own Country Code Top Level Domain. The ccNSO is a consortium of working groups and the ccNSO Council, and it works in conjunction with other supporting organizations and bodies within ICANN. It was founded in 2003. It is a forum for global discussions and debates regarding issues related to ccTLDs.[11]

ASO

Main article: ASO

The Address Supporting Organization (ASO) is one of the supporting organizations that was formed, according to ICANN's bylaws, through community consensus in 1999. The main objective of the ASO is to review and develop Internet Protocol recommendations, address policy, and advise the ICANN Board.[12] Its members are appointed by the world's 5 Regional Internet Registries (RIRs), which manage and allocate IP addresses in their respective continental regions.[13][14]

Process

Meetings

Main article: ICANN Meetings

ICANN holds week-long meetings three times per year; one of these meetings serves as the organization's annual meeting, where new board directors take their appointed seats. These meetings are held in a different location each time, with each global region hosting a meeting before the regional cycle is started anew.[3] The next meeting will be the 41st meeting in Singapore. The 41st meeting was scheduled to be held in Amman, Jordan, before it was moved due to security concerns.[15] Singapore was then selected to host that meeting.[16]

Meetings officially begin on a Monday, though some supporting organizations meet prior to this, and run through Friday.

A fellowship program is in place to bring in individuals who have a desire or need to attend but do not have the financial backing to attend on their own.[17]

Review Processes

ICANN has mechanisms in place for any individual or entity to solicit a reappraisal of any board decision that affects them. The Board Governance Committee is in charge of reviewing all reconsideration requests, which are submitted electronically and must be responded to within 30 days. The boards actions are also reviewed by an Independent Review Panel, which has the power to call attention to discrepancies between the bylaws and actions taken by the board, and recommend that the board readdress certain issues. Furthermore, ICANN's structure and operations, including every supporting organization and committee, is also subject to occasional reviews.[7]

History: The Beginning

On July 1st, 1997, U.S. President Bill Clinton directed the Secretary of Commerce to privatize the management of the DNS, which had heretofore been managed by the Defense Advanced Research Projects Agency (DARPA), the National Science Foundation (NSF) and other U.S. research agencies.[18] The goal was to open the Internet to greater international participation, and to bolster it as a new medium of commercial competition and exchange.[1]

On July 2nd, the Department of Commerce requested public input regarding DNS administration and structure, policy input regarding new registrars and the creation of new TLDs, and concerns regarding trademarks. More than 1,500 pages of comments were received.[19]

In January 1998, an agency of the Department of Commerce (NTIA) issued what has become known as the "Green Paper." The document was a proposal which made clear that the agency intended to empower a non-profit entity to take control of the Internet and its DNS system.[20] The proposal drew criticism from some American lawmakers and other concerned individuals who saw the American-fostered Internet about to be handed over to a Swiss entity.[21] The revised "White Paper" addressed some of those concerns but still posited the need for an Internet organization which could respect and foster stability, competition, bottom-up coordination, and international representation, while also establishing appropriate protocol and administrative mechanisms.[22] The "White Paper" did not clarify all of the divisive issues but instead called for the proposed entity to utilize its self-governance to decide on the issues at hand itself.[21] The White Paper spurned the creation of the International Forum on the White Paper, which involved the creation and meeting of four globally regional forums, and brought together some 1,000 Internet stakeholders. The IFWP did not create any specific proposal in response to NTIA's White Paper, but it did create a valuable body of thought and laid the foundations for future Internet governance and multi-stakeholder conferences and organizations.[23]

The Memorandum of Understanding

On November 25th, 1998, The U.S. Department of Commerce and ICANN entered into a Memorandum of Understanding (MoU),[1] which officially recognized ICANN as the entity that would:

  1. Establish policy for and direct the allocation of IP number blocks;
  2. Oversee the operation of the authoritative root server system;
  3. Oversee the policy for determining the circumstances under which new TLDs would be added to the root system;
  4. Coordinate the assignment of other Internet technical parameters as needed to maintain universal connectivity on the Internet; and
  5. Oversee other activities necessary to coordinate the specified DNS management functions, as agreed by the Department of Commerce and ICANN.

Once again, these responsibilities would be undertaken and guided by the principles of stability, competition, private bottom-up coordination, and representation.[1] The agreement established ICANN as an entity that would encourage transparency in its dealings and would create ample room for appeals for any binding decisions it would make. The Department of Commerce later noted that it was comfortable ceding its control to ICANN, as it seemed like the best step towards true privatization while still binding the authority of the institution to the American policies found within the MoU.[24] The original agreement was set with an expiration of September 30th, 2000.[1] The MoU has been amended several times.

The First Three Supporting Organizations

The three original supporting organizations include: [25]

Initial Issues

ICANN was immediately faced with two pressing, opposing issues: the task of reigning in cybersquatting by creating policies necessary to protect recognized trademarks, and conversely the need to expand the number of entities accredited to function as registrars. Following the release of the White Paper, WIPO began its own research into how to protect trademarks and intellectual property within the changing DNS. A congressional hearing some 7 months after the empowerment of ICANN recognized the steps that the new entity had already taken to protect intellectual property, recognized the headway WIPO had made in creating further proposals, and called on intellectual property owners to become involved in ICANN.[24]

WIPO's report, submitted to ICANN at their 1999 meeting in Berlin, supported the Whois system, but also recommended that, should the Whois system fail to provide adequate contact information for the trademark holder to contact the domain name holder, the registrar should be obliged to rectify the situation by canceling the domain name holder's rights to the name. ICANN immediately took steps to develop the nascent Whois system.

The report also made recommendations regarding the process of accrediting new registrars, called for the creation of a concrete dispute resolution process for intellectual property issues within the DNS, and also recommended that the creation of any new gTLDs should proceed slowly and with caution. These recommendations precipitated ICANN's Accreditation Guidelines, the creation of the UDRP, and the continued debate over how and when to increase the number of gTLDs.[24]

Registrar Accreditation

A month before the MoU officially recognized ICANN, the Department of Commerce and NSI amended their cooperative agreement. The agreement had previously maintained the NSI as the only registrar for the .com, .org, and .net domains.[31] The three amendments to the agreement removed the exclusive rights of NSI; amendment 11 called for the creation of a Shared Registry System, whereby an unlimited number of competitive registrars would have access to one system managed by NSI.[32] Amendment 12 gave more time to NSI to complete important milestones in the liberalization of registry services; the final phase, which called for equal access to the SRS by all accredited registrars, was now given a deadline of about one year, October 25th, 1999.[33] Amendment 13 attached a $9 fee for each second level domain name registered, payable as $18 for new registrations and $9 per year on the anniversary of the original registration.[34]

On February 8th, 1999, ICANN posted its Draft Guidelines for Registrar Accreditation for public commentary.[31] The guidelines were formed through consultation with the DOC and NSI, and further tailored after the session of public commentary.[35] Some issues raised during the period of public commentary include: concerns regarding the inherent bureaucracy, inadequate protections for intellectual property, and the reasoning behind accrediting registrars before the DNSO was constituted.[36] The ICANN board accepted the revised Statement of Registrar Accreditation Policy at their March, 1999 meeting in Singapore.[31]

The initial policy called for registrars to provide secure access to the registry, be operationally capable of handling significant registration volume, maintain electronic transaction records, handle and provide prompt service to SLD requests, provide security, handle seamless transfers of customers who desire to switch registrars, employ an adequately sized staff, and have measures in place to protect the interests of their customers should the registrar fail. The registrar would also have to demonstrate that it had a sufficient liability insurance policy and store of liquid assets. A concern over creating and maintaining a valid registry service is evidenced in the requirement that information regarding each registrant of a SLD would have to be submitted by the registrar to NSI for inclusion in its registry. Providing a searchable Whois service was also required. Application fees for those applying to be included in the Phase 1 testbed cost $2,500, the general application fee was $1,000. Annual accreditation fees, amounting to $5,000, would also be assessed.[37]

The Registration Accreditation Agreement was unanimously amended by the ICANN board in May, 2009.[31]

The Testbed Period

Numerous technical problems plagued the testbed period of the SRS.[38] The aforementioned Amendment 12 established the testbed period as Phase 1 of the deployment of the SRS, and set a start date of April 26th, 1999, and an end date of June 25th, 1999.[33] Register.com finally became the first of the 5 competitive testbed registrars to successfully implement its interface with the SRS, which happened 6 weeks into the 2 month testbed period. The technical difficulties also extended to the deployment of the required Whois system.[38] Throughout the testbed period general applications for the later phases were being accepted.[31] The Department of Commerce and the NSI extended the testbed period about 4 times,[39] the final extension finally expired on November 5th, 1999.[40]

UDRP

On September 29th, 1999, ICANN posted the Uniform Domain Name Resolution Policy for public comments. The process aimed to address problems arising from cybersquatting and protect intellectual property rights. This process was not solely a concern or product of ICANN, given WIPO's earlier, and continued, effort on the UDRP. The policy asserts that it will transfer, delete, or asses other changes to any domain name held by a domainer which:

  1. Is identical or confusingly similar to a trademark or service mark in which the complainant has rights; and
  2. The domainer no rights or legitimate interests in respect of the domain name; and
  3. The domain name in question has been registered and is being used in bad faith.[41]

The same day, ICANN also issued the Rules for the UDRP, which set forth the procedure for filing and responding to complaints. This was also open for a period of public commentary.[42] Some of the public comments can be found here.

ICANN adopted the UDRP at its November, 1999, meeting in Los Angeles.[43]

History: ICANN 2.0

ICANN's bottom-up focus and its periodic structural reviews lead to revision of its bylaws and the introduction of new entities and policies. One such rush of changes happened in and around the year 2000, when the prospective changes and the discussions surrounding them spurned people to talk of "ICANN 2.0".[44]

The Introduction of the ALAC

One of the discussions and propositions which was involved in the debate surrounding "ICANN 2.0" was the introduction of a body which could represent individual Internet users.[25] This became known as the At-Large Committee, or ALAC, and while it was finally introduced through amendments to the bylaws in 2002, it had been a hot topic for debate for years.[45]

Other Committees

Many of the other new developments at ICANN were accomplished through the introduction of review teams; such as the Committee on ICANN Evolution and Reform. Other Committees intent on expanding and specializing the role of ICANN were also created, such as the Security Committee, which eventually became the Security and Stability Advisory Committee. Both of these committees were given official recognition in 2002.[46] The push for reform was also significantly aided by Stuart Lynn's "President's report: The Case for Reform,"[47] which they credited for starting the dialogue on reform and leading to the creation of the more formal committee.[48]

ICANN adopted a new set of by-laws, which were first laid out by the aforementioned Evolution and Reform Committee, before being revised in response to Public Forums. Those by-laws can be read here. The by-laws not only more clearly defined ICANN's mission and core values, but it also put in place and improved apparatuses for review and greater transparency. The Reconsideration Committee, Independent Review Panel, and the Ombudsman all were strengthened as a part of this move towards a more transparent organization that is able to defend its actions and decisions.[49]

Further Developments

gTLD Expansion

Main article: gTLD

The discussion of creating new Generic Top-Level Domains has been around since the inception of ICANN; there was no set number fixed, and the fact that the .com extension has long been the most widely used and recognizable top-level domain was encouraged by ICANN's slow policy development process. It was underwritten in the 2001 amendments to their MoU with the U.S. Department of Commerce that ICANN was to "collaborate on the design, development and testing of a plan for creating a process that will consider the possible expansion of the number of gTLDs".[56]

In 2000, a number of Working Groups that had been created the year before submitted reports on their take on the introduction of new TLDs; most notably, Working Group C called for a limited number of extensions to be introduced. The Board continued to move ahead with new TLD introduction, creating this application process. The task force that worked with the process helped .aero, .biz, .coop, .info, .museum, .name, and .pro all become recognized extensions in 2000.

At the October, 2003 meeting in Carthage, the Board passed its most significant resolution to date on fully opening the gTLD creation process. In it they recognized their obligation to develop new gTLDs in an effective, transparent, and stable manner, the overdue nature of a formal process for gTLD expansion, and the problems they faced when introducing the last round of extensions in 2000. Thus, they resolved to begin to dedicate significant resources to the issue and to establish a public forum in order to receive community input.[57]

In 2003, important new sTLDs began being proposed. While these domains are different from gTLDs in that they are sponsored by a given constituency, this can be seen as another way in which the wider community was pressing for a greater variety of domain space. Applications came from .asia, .xxx, .net, .cat, .mobi, .jobs, and .travel.[58]; they all went on to approval in 2005-2006, except for the controversial .xxx,[59] which went through a much more contentious and drawn out process but was still approved in March, 2011 at ICANN 40.[60]

Further Developments

New gTLD Program

Main article: New gTLD Program

After the results of the 2000 and 2003 expansions of new gTLDs, a 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.[61] The Board announced the possibility of a 9th version of the Guidebook in January 2012, but the industry speculated that there was little chance that the changes would be more than clarification, as opposed to new rules and policies.[62]

In November, 2012, ICANN, Verisign, and NTIA, all confirmed that they were prepared with enough resources to begin launching 100 new gTLDs per week.[63]

Physical Expansion

In September, 2011, the ICANN Board approved resolutions to secure new office space for the organization. It is possible they will negotiate for more space at their current location, or that they find a new space at their headquarters of Marina Del Rey. It was also decided to begin permanently leasing its office space in Brussels instead of continuing to rent their space month-to-month. Much of its expansion is related to the new gTLD program. At the time of the board's decision, ICANN staff numbered 124, with 21 open positions to be filled. The 2012 budget includes $2.1 million for office space acquisition and maintenance for its offices in Marina Del Rey, Brussels, Sydney, Paolo Alto, and Washington D.C..[64] The Sydney office went on to be closed in 2012.

In February 2013, CEO Fadi Chehadé announced that ICANN's office in L.A. would diminish in importance while two new "hubs" would be created to fill the gap and provide new means of outreach to ICANN's international constituents. The hubs are to be located in Singapore and Istanbul, and are to act with far more authority and purpose than a stand-alone office; it is clear that many senior staff from the L.A. office will be asked to move, and the CEO himself said he will be based in Singapore once that office is up and running.[65][66] The news was announced during Mr. Chehadé's first comprehensive tour of Asia, with trips to South Korea, China, Japan, and Singapore. He noted that ICANN needed to apologize to Asia, as it had long not been given the attention it deserved within the organization.[67]

Conflicts of Interest

ICANN has never had a clear conflicts on interest policy, or any regulations in place that would prevent its most important staff members and its directors from moving directly into employment within the industry. This is an issue given the fact that these people of power influence the decisions and market-power of ICANN, and thus they could help create programs and policies that they could then go on to financially benefit from. This notably came to a head in 2011, when a prominent staffer and the Chairman of the Board left ICANN for employment in the industry. Both were involved in developing ICANN's new gTLD program, and both went on the be employed in new gTLD related ventures.[68]

The Chairman of the board in question was Peter Dengate Thrush, who led the directors to the historic approval of a new gTLD program and timeline at ICANN 41 in Singapore. This was his final meeting as Chairman of the board due to the determined term limits. Mr. Thrush went on, weeks later, to become the Executive Chairman of Top Level Domain Holdings, the parent company of new gTLD registry and consultancy, Minds + Machines. He was the first chair to move directly into a high-paying, domain name industry job.[69]

Following Mr. Thrush's move to Minds + Machines, a number of outside organizations and ICANN stakeholders called for a concrete ethics policy to be set in place, these include: U.S. Senator Ron Wyden, the Association of National Advertisers, The European Commission, The U.S. Department of Commerce, the French government, and other IP and industry organizations.[70] ICANN's CEO, Rod Beckstrom had previously noted at the opening ceremony to ICANN 42, even before Peter Dengate Thrush moved on, that he was encouraged by the fact that the ICANN community was moving to fix the lack of clear ethics rules within the organization. AusRegistry's CEO, Adrian Kinderis, later noted the converse fact that without clear ethics policies he and his industry would continue to go after ICANN's most knowledgeable and prepared individuals for their own gain.[68]

Following these developments, ICANN announced it would hire outside ethics experts to review its policies and make recommendations. The decision was made during a September, 2011 meeting of the board governance committee.[71]

A new Conflict of Interest Policy was released on December 8th, 2011, effective immediately. The policy requires that all Board Members, as well as those in various other postions, disclose any and all potential conflicts of interest to the Board Governance Committee. They must then abstain from any ICANN activities related to the conflict of interest,[72] Board members also may not join business with a new gTLD registry until 12 months after the registry's application has been voted on.[8]

Time Zone Database

On October 14th, 2011, ICANN announced that it would take over the management of the Internet Time Zone Database, which contains the code and data that computer programs and operating systems rely on to determine a given location's correct time. It agreed to pick up this new responsibility after a request from IETF. Prior to this, the Time Zone Database was managed by a group of volunteers, namely its coordinator, Arthur David Olson at the US National Institutes of Health.[73]

Manwin Anti-Trust Lawsuit

Manwin, one of the most prominent adult content producers on the Internet, filed an Anti-Trust suit against both ICM Registry and ICANN over the creation and implementation of the .xxx sTLD. This legal action took place in November, 2011, well after the TLD's approval and just before its general availability.[74] It also filed an Independent Review Panel (IRP) Request with ICANN, making it only the second company ever to do so (the first being ICM Registry itself). Manwin felt that ICANN did not "adequately address issues including competition, consumer protection, malicious abuse and rights protection prior to approving the .xxx TLD."[75]

In January, 2012, ICANN and ICM both filed motions to dismiss the case. ICANN argued that since it is a not-for-profit organization and it is not engaged in "trade or commerce," the US anti-trust laws are not applicable; additionally, both ICM and ICANN argued that Manwin's filing was essentially complaining about the possible increase in competition. ICM cited that Manwin had approached the company earlier with a supposed mutually-beneficial agreement, in which Manwin would acquire various premium .xxx domains for free, in exchange for sharing the profits of these domains with ICM. When ICM turned down the agreement, Manwin Managing Partner Fabian Thylmann said that he would do whatever he could to stop .xxx.[76] ICANN's and ICM's motions to dismiss can be found here and here respectively.

In mid-February, Manwin, ICANN and ICM Registry announced that they were in talks and hoping to resolve some or all of the outstanding complaints. The motions to dismiss the case filed by ICANN and ICM were temporarily put on hold.[77] On February 17, the company amended its anti-trust lawsuit against ICANN and ICM Registy. According to Manwin's counsel Kevin E. Gaut, two related state law claims were dropped to avoid potential risks of trial delays.[78]

In August 2012, a mixed ruling by the Central District of California District Court accepted only 2 out of ICANN and ICM's 7 motions to dismiss. The court ruled that ICANN would be subject to anti-trust law, as ICM pays fees to them in order to be permitted to run the .xxx domain space, and that the trial would proceed with focus on the "defensive registrations" market.[79]

Employ Media Arbitration

Employ Media requested an arbitration proceeding to resolve the notice of breach on the .jobs registry agreement issued by ICANN on February 27, 2011 in connection with the universe.jobs website. The jobs board website was launched by Employ Media in partnership with the Direct Employers Association, which the registry operator allowed to register more than 40 thousand .jobs domain names used on the jobs board to advertise job opportunities for more than 5,000 leading companies in the United States. ICANN claimed that that universe.jobs appeared to be in competition with other companies offering the same service and Employ Media's actions violated its charter. ICANN directed the .jobs registry operator and the [[SHRM|Society for Human Resource Management (SHRM), the sponsoring organization, to resolve the issues mentioned in the notice of breach and to comply with its charter. ICANN threatened to terminate the .jobs registry agreement if the problems were not be resolved. Employ Media argued that the universe.jobs was launched in compliance with the Phase Allocation Program, which was approved by ICANN. Although the registry operator was disappointed with ICANN's actions Employ Media agreed to resolve the issue by invoking the cooperative agreement provisions in the registry agreement. During the cooperative negotiations, Employ Media agreed to stop registering non-company name domain names until May 6, 2011. However, the company abandoned the cooperative agreement proceedings when it learned that ICANN posted the information about their cooperative negotiations regarding the notice of breach. Employ Media also accused ICANN of "bad faith action." ICANN's legal counsel explained that the internet governing body is just performing its duty to maintain accountability and transparency. When ICANN responded to the Employ Media's arbitration request it reiterated its strong position the Employ Media violated its charter and its decision was appropriate. ICANN asked the court to deny the registry operator's request for relief. At present, both parties are still waiting for the the schedule of their arbitration proceedings from the International Chamber of Commerce (ICC) International Court of Arbitration.[80] [81] [82] [83] [84] [85] [86]

.JOBS Charter Compliance Coalition Criticism

One day before the implementation of the new gTLD program, the .JOBS Charter Compliance Coalition, sent a letter to ICANN detailing the internet governing body's failure to evaluate and investigate all comments and information submitted by entities against the request of the .jobs registry operator to change its charter. It pointed out that ICANN failed to acknowledge its mistake and overturn its decision when complaints and evidence were filed for reconsideration that Employ Media violated its charter. The coalition chairman stated that ICANN was inefficient in dealing with the arbitration proceedings to immediately resolve Employ Media's charter violation, and consequently the company continues to exploit the .jobs TLD and expand the universe.jobs website. Furthermore, it said that the internet community is concerned that ICANN's new gTLD program's multiple stakeholder protection mechanisms might end up mismanaged just like the .jobs TLD and ICANN's promises are "empty words." Moreover, Bell requested the ICANN Board to publicly disqualify Employ Media and its partner, the Direct Employers Association ,from the new gTLD expansion program because the registry operator has a "history of abuse." According to its Chairman, this is the only way for ICANN to regain a measure of regulatory authority.[87]

A New Approach to Africa

On August 10, 2012, ICANN, with the support of AfriNIC, announced an initiative to increase African participation in influence within ICANN. The initiative is the result of a meeting between Steve Crocker, Chairman of ICANN's Board of Directors, ICANN's CEO-Designate Fadi Chehadé, and Interim CEO Akram Atallah, with African community members at ICANN 44 in Prague, Czech Republic. Their goal is to develop a framework for ICANN's Africa strategy to be announced at ICANN 45 in Toronto, Canada. A working group was established, led by Nii Quaynor of Ghana, to contribute to the development of the strategy. The group is also to work with Tarek Kamel, Head of Governmental Affairs.[88] The initiative has received strong support from African Internet stakeholders, including former Board Member Katim Touray. In March 2013, CEO Fadi Chehadé, expressed his desire to raise the number of registrars in Africa from 5 to 25, via personal and business relations with the banking and insurance sectors that would allow the African companies to more easily meet some form of tailored ICANN accreditation. His hope is to accomplish this in just a few months, with something implemented around ICANN 47 in Durban, in July, 2013[89]

Senate Hearing on New gTLD Program

On December 8, 2012, the U.S. Senate Committee on Commerce, Science and Transportation conducted a full committee hearing to evaluate the value and effects of the new gTLD expansion program as well as ICANN's efforts in resolving the concerns raised by the Internet community. Witnesses present during the committee hearings included:[90]

Witnesses' Testimonies

Angela Williams represented the concerns of the members of ICANN's Not-for-Profit Operational Concerns Constituency (NPOC) during the Senate hearing. In her testimony, she raised budgetary, public confusion, and cybersquatting issues. According to her, the increased risk of public confusion compromises Internet security. She also noted that it would be more expensive for not-for-profit organizations to protect their brand names/trademarks against fraud, cybersquatting and trademark infringement. She also pointed out that not-for-profit-organizations cannot afford the amount of money needed to become a domain name registry to ensure brand protection. Williams encouraged ICANN to consider the concerns of the members of the NPOC. She also recommended that verified not-for-profit organizations be allowed to exempt their trademarks from any new TLD applicant at no cost or at a drastically reduced fee.[91]

During the hearing, Dan Jaffe testified that the new gTLD program is "bad for consumers, marketers and the entire online marketplace" and enumerated different reasons why it is necessary to the stop its implementation. According to him, there is no substantial evidence that the new gTLD program will promote competition, relieve the scarcity of domain name space and support differentiated services and new products. He also cited that the new gTLD program has a serious economic impact. Brand owners might be compelled to file for defensive registrations to protect their trademarks or intellectual property rights. There is a possibility of misappropriation of intellectual property rights, domain navigation dilution, increased risk of cybersquatting, reduced investments from intellectual property owners, and losses from failed TLDs. Jaffe supported his claims using the “Economic Considerations in the Expansion of Generic TopLevel Domain Names, Phase II Report: Case Studies,” a study commissioned by ICANN in December, 2010. In addition, he also emphasized that the new gTLD programs lacks consensus and ICANN failed to meet its "bottom-up, consensus driven approach to policy development." Furthermore, he pointed out that the application fee is too expensive and harmful for brand owners and he also raised the concerns regarding the organization's conflict of interest policies after Peter Dengate Thrush decided to join Minds + Machines as Executive Chairman immediately after his term as chairman of ICANN. Thrush strongly advocated approval of the new gTLD program.[92]

Esther Dyson testified that the new gTLD program is not necessary to promote innovation. She said, "The rationale is that there's a shortage of domain names... but actually, there's a shortage of space in people's heads." She recommended for ICANN to conduct further consultation regarding the program and make a broader public outreach. She concluded her testimony with the saying, "If it ain't broke, don't fix it!"[93]

As representative of the U.S. NTIA, Fiona Alexander informed the members of the Senate Committee that the agency is part of the Governmental Advisory Committee (GAC), which is actively involved in the policy development process within ICANN. She testified that the NTIA and its counterparts within the GAC provided consensus advice to ICANN during the policy development process for the new gTLD program for six years. She emphasized that the GAC developed a "scorecard" to address the different issues raised by governments, which include:

  • objection procedures for governments
  • procedures for the review of sensitive strings
  • root zone scaling
  • market and economic impacts
  • registry-registrar separation
  • protection of trademark rights and other intellectual property
  • consumer protection issues
  • post-delegation disputes with governments
  • use and protection of geographic names
  • legal recourse for applicants
  • opportunities for stakeholders from developing countries
  • law enforcement due diligence recommendations
  • early warning mechanism for applicants to identify if a proposed string would raise controversies or sensitivities

Ms. Alexander strongly emphasized NTIA's support of ICANN's multistakeholder model of internet governance and dedication to maintaining the open Internet to promote economic growth, innovation and the free flow of information, products and services online.[94]

Kurt Pritz testified to the Senate committee that the introduction of new gTLDs has been one of the mandates of the Internet governing body since its establishment. Pritz pointed out that the new gTLD program was developed through the multistakeholder process; global internet stakeholders including brand and trade mark owners, domain name registries, registrars, registrants, governments, law enforcement agencies, governments, not-for-profit organizations, etc. participated in the policy development and implementation program for new gTLDs. He also emphasized the provisions in the Applicant Guidebook regarding new trademark protections such as the Uniform Rapid Suspension (URS) and the Trademark Clearing House, measures to mitigate malicious conduct, create objection processes, maintain DNS Security (DNSSEC) and other relevant issues. He concluded his testimony by reiterating that the "ICANN community worked tirelessly to create the new gTLD program to promote competition and innovation..."[95] [96]

ICANN's Answers the Senate Committee

On Janury 25, 2012, Pritz answered the questions sent by members of the Senate Committee on Commerce, Science and Transportation regarding the new gTLD expansion program. The questions were asked by Senators Barbara Boxer, Maria Cantwell, Claire McCaskill, Olympia Snowe and Mark Warner on January 8. The questions of the legislators were centered on the following issues:[97]

  • Intellectual Property Rights- In order to avoid consumer confusion and or violations of intellectual property rights, Pritz explained that the new gTLD program has mandatory intellectual property rights protection mechanisms for both first and second level domain names. He also added that strict reviews will be implemented and it will reject the applications of entities with a history of cybersquatting. In addition, the public and the various constituencies of ICANN will have the opportunity to review and raise their concerns regarding the proposed new gTLD strings. Pritz also enumerated the four available objection processes, which include:
  1. String Confusion Objection- the proposed new gTLD is confusingly similar to an existing or to another applied for gTLD string.
  2. Legal Rights Objection- the gTLD string being applied for infringes the existing legal rights of the objector.
  3. Limited Public Interest Objection- the proposed new gTLD string contradicts the generally accepted legal norms of morality and public order that are recognized under the principles of international law.
  4. Community Objection- a significant number of the target community is opposed to the new gTLD string being applied for.

Any objections should be filed to one of the three independent dispute resolution providers approved by ICANN, including the International Centre for Dispute Resolution (string confusion objections), WIPO Arbitration and Mediation Center (legal rights objections), and the International Chamber of Commerce-International Center of Expertise (limited public interest and community objections). Moreover, Pritz also emphasized the appointment of an Independent Objector, whose responsibility will be to review applications on behalf of the public interest and to file an objection if necessary.

  • Sunrise Period- Pritz informed the members of the committee that a Sunrise Period is mandated for all approved new gTLDs. The Trademark Clearinghouse will serve as a central repository of trademark rights information to be authenticated, stored and disseminated. All trademark holders will have the chance to record all their nationally and multi-nationally registered word marks from all jurisdictions. All the authenticated trademark rights data in the Trademark Clearinghouse will be used to protect those related domains during the pre-launch of the Sunrise Period and the Trademark claims services.
  • DNS Security (DNSSEC)- Pritz confirmed that all new gTLD applicants are required to implement DNSSEC. He also informed them that 82% of existing TLD registries have already deployed DNSSEC to ensure the security and stability of the DNS.
  • Crackdown on Rogue Websites- The new gTLD program is designed to prevent illegal activities and to easily remove malicious conduct through increased accessibility of information by law enforcement agencies. A thick Whois data system will be implemented to allow faster search capabilities and to efficiently combat rogue websites. ICANN will also implement background checks on applicants and will review their history of bad faith or reckless disregard of anti-cybersquatting law.
  • Estimated Number of New gTLDs to be Created- Pritz explained that based on the Root Server Stability experts advise, ICANN is committed and limited to add 1,000 new gTLD to the root zone in one year.
  • Plans on Excess Revenue from new gTLDs- ICANN is committed to using any excess funds to promote its non-profit missions for the benefit of the Internet community, such as the creation of a registry continuity fund for the protection of registrants, or establishment of a security fund to expand the use of secure protocols, support standards development organizations and other projects in accordance with the internet governing body's security and stability mission. Prits also emphasized that ICANN's budget is utilized in a transparent manner. The use of excess funds are subject to community discussions and consultations.
  • Concerns Raised by ANA and other parties- Pritz explained that the new gTLD program was developed for more than six years with input from 10 or more experts and community working groups under the multistakeholder process. He pointed out that significant protection mechanisms were created to ensure protections for intellectual property rights, registry failures, etc. He also pointed out that all concerns raised by ANA and other parties were accepted, considered and responded to. He also reiterated that in the multistakeholder process not everyone will be satisfied with the result. He quoted NTIA Assitant Secretary Larry Strickling's statement that "it is critical to respect the process and the outcome reached".
  • Harm of Delaying the new gTLD program Implementation- According to Pritz, if the new gTLD program implementation were to be delayed it will upset the multistakeholder process, which was designed by the United States government to ensure the openness of the internet.
  • FCC Concern on Rapid Exponential Expansion of new gTLDs- According to Pritz, the approved new gTLDs will be introduced in a measured and limited manner. No new gTLD will be operational before 2013 and the introduction will be distributed over time.
  • Recommendations of Law Enforcement Agencies- Pritz emphasized that ICANN is actively working to address the 12 recommendations of law enforcement agencies. ICANN is negotiating with registrars to amend an strengthen the Registrar Accreditation Agreement (RAA) to meet the recommendations before 2013.
  • Registry Failure- One of the safeguards implemented by ICANN for the new gTLD program is the availability of an Emergency Back End Registry Provider in case of registry failure.
  • United Nations Model on Internet Governance and its Impact- Pritz emphasized that the ICANN multistakeholder model is not perfect but "it has shown to be a powerful, dynamic model that is capable of reaching consensus positions on extremely difficult issues. A UN model will push the stakeholders outside the government to an inconsequential role." He also reiterated the statements of Sec. Strickling and Ambassador David Gross that abandoning the multistakeholder model will cause negative impact to the Internet and its governance, and he said that an "internet constrained by an international treaty will stifle the innovators and entrepreneurs who are responsible for its awesome growth."
  • Internet Growth and DNS Expansion- Pritz affirmed that the internet and the DNS will continue to grow. ICANN is committed to carrying out its mandates- to promote competition in the DNS while protecting vital information as well as business and consumer interests.
  • Status of IPv6 Migration- Pritz explained that the IPv4 and IPv6 protocols will be running side by side for years to come. Over 7,500 IPv6 had been allocated to network operators around the globe by the end of September 2011.

In early November 2012, Chehadé invited a group of business, IP, and noncommercial users, along with registrar and registry stakeholder groups, to discuss Clearinghouse-related issues. Resolutions and decisions for ICANN include[98]:

  • Registration: How registration recording and verification are addressed
  1. Agreeing to map out trademark submission and verification components
  2. Developing a new system to offer timely and accurate information on new gTLD launches
  3. Implementing seminars between implementers and various users
  • Sunrise Management: How to use Sunrise data files and offer flexibility for rights holders
  1. Offering model in which Clearinghouse data can be provided securely to rights holders for early sunrise registration
  2. Giving details on the degree of "matching" between a Clearinghouse record and a domain name's Whois data.
  • Claims Management: How new gTLDs registries and registrars will facilitate Clearinghouse records during the registration process
  1. Agreeing to hybrid system of decentralized and centralized system for Trademark Claims
  2. Offering trademark claims service for at least first 60 days of general registration and all new gTLD registries must offer a minimum 30-day sunrise period
  3. Decided not to implement measures to address the potential mining of the Clearinghouse database for purposes not related to rights protection, on the basis that most controls would be ineffective

House of Representatives Hearing on new gTLD

On December 14, 2011, the U.S. House of Representatives Sub-Committee on Communications Technology-Committee on Energy and Commerce also conducted a similar hearing regarding the new gTLD program. Kurt Pritz and all the other individuals who testified in the Senate also served at witnesses at the House of Representatives who echoed the same views about the program. Joshua Bourne, President of The Coalition Against Domain Name Abuse (CADNA), Thomas Embrescia, CEO of Employ Media and Anjali Hansen, IP attorney at the Council of Better Business Bureaus joined the rest of the witnesses during the hearing.[99]

Testimony of Witnesses

Mr. Joshua Bourne expressed his concern over the program and suggested some recommendations including the availability of a second round of application ease the anxiety associated with the program, provide option to block trademarks, update the language of the Anti-Cybersquatting Protection Act (ACPA), reduce pricing for multiple gTLD applicants and to add conditions on the IANA contract.[100] The call for second round of application was also expressed by Josh and the attendees of the CADNA gTLD Conference on November 2011.[101]

In her testimony, Ms. Anjali Hansen expressed her concern regarding the level of abuses and fraud over the internet and the high costs of brand protection. She also pointed out the importance of a competitive, innovative and open internet and BBB is not requesting for excessive regulation of the Internet by governments but they encourage registries and registrars to implement application standards to help reduce costs to businesses and to restore consumer trust.[102]

Thomas Embrescia testified in support of the ICANN new gTLD program. During the hearing, he pointed out that the private sector has a strong demand for new TLDs and the new gTLD program promotes competition, innovation. Furthermore he emphasized that it would help create more jobs and opportunities.He encouraged the members of the Congress to support the program. [103]

ICANN's Answers to Sub-Committee Members' Inquiries

On January 5, 2012, Cong. Greg Walden, Chairman of the House Sub-Committee on Communications and Technology, sent a letter to ICANN requesting answers to some issues related to the new gTLD program including:[104]

ICANN explained that consensus was achieved through community-driven policy development processes wherein working teams composed of members of the different internet stakeholders developed reports and recommendations and the public were given the opportunity to comment. The public comments were considered when drafting the final report and recommendations, before they were submitted it to the appropriate organization within ICANN such as the GNSO Council, which would in turn present their findings to the ICANN Board. ICANN emphasized that the GNSO Council is composed of all internet stakeholders and voted 19-1 in favor of the new gTLD policy. The internet governing body also pointed out that ICANN's Advisory Committees (GAC, ALAC, SSAC, RSSAC etc.) were involved in the consensus development. ICANN reiterated the statement of Sec. Larry Strickling that the ICANN "multistakeholder does not guarantee that everyone will be satisfied with the outcome.But it is critical to preserving the model of Internet governance that has been so successful to date that all parties respect and work through the process and accept the outcome once a decision is reached..."

  • Rights Protection Mechanisms

Rights protection will be implemented in the first and second level domain names. The internet governing body mentioned the development of the Trademark Clearinghouse as one of the rights protection mechanisms and it is mandatory to all new TLDs.

  • Request for a Second Round of Application

ICANN stated that it is committed to conducting additional rounds of new gTLD applications and it is working on determining that schedule.

  • Transparency regarding Surplus Funds generated from the new gTLD applications

ICANN emphasized that it is committed to using the excess funds generated from the new gTLD applications to advance its missions in a transparent way, such as allocating funds to projects that are of interest to the greater Internet community.

  • Bilateral Negotiations with registrars about the twelve Law Enforcement Due Diligence Recommendations

ICANN confirmed that it is conducting negotiations with its accredited registrars regarding the 12 recommendations of the enforcement agencies. Updates to the negotiation are available here

  • Contingency Plan in case a registry operator goes out of business

ICANN told the Congress that an "Emergency Backend Registry Operator" (EBERO) is in place to take-over the operations if a failed registry to ensure that the interest of domain name registrants are protected.

ICANN explained that information regarding the new Applicant Support Program is available, which offers two types of financial assistance under ASP: a reduced application fee of $47,000 from $185,000, and a payment plan to deal with the whole $185,000 application fee. To qualify for financial assistance, entities must meet certain criteria. Financial Assistance applications will be evaluated by an independent Support Application Review Panel (SARP).

ICANN explained that the Trademark Clearinghouse is a database of registered trademarks and other types intellectual property rights, which will be used to provide protection during the "Sunrise" and "Trademark Claims" processes. ICANN notes that 60-days post launch operation of the Trademark Claims exceeds the final recommendation of the Special Trademark Issues (STI) team, which was involved in developing the service and suggested that no mandatory post-launch claims service is necessary.

  • Possibility of subsidizing the costs of Uniform Dispute Resolution Policy (UDRP) using surplus funds

ICANN clarified that no commitment has been made regarding the use of surplus funds and that the issue is a matter of continued community consultations. ICANN will consider the proposal to subsidize costs of disputes under the UDRP.

ICANN is dedicated to improving the access and accuracy of the Whois information; Thick Whois information requirements will be in place for all new gTLDs. Five studies regarding Whois services focusing on issues related to misuse, registrant identification, privacy and proxy services were conducted.

  • New gTLD Application Fee

ICANN provided a breakdown of the current $185,000 application fee, which includes development costs ($26,950 per application), applications processing and evaluation costs ($97,800 per application), costs for risk mitigation steps ($60,000 per applicant). Further breakdown of the cost is available here

  • Revenue from second level domain name registrations under new gTLDs

ICANN said that it did not evaluate any additional revenue that might be generated from defensive second level domain name registrations. Registries are required to pay ICANN with annual fees with fixed components.

  • Cost recovery model in assessing fees

The cost-neutral model was a direct response to the GNSO policy recommendation that application fees are designed to ensure that the implementation of the new gTLD program is self funding. Once the TLDs are operational, transaction based fees for registries and registrars will apply to domain registrations.

  • Loser pays system against cybersquatting

The new gTLD dispute resolution under the new gTLD program implements the loser pays system. The IRT did not recommend a full loser pays system for domain name disputes related to cybersquatting. The loser pays system has exceptions on filing fees for disputes and URS claims of less than 15 domain names. Claims for 26 or more names in a URS claims might be done on a loser-pays basis.

  • Auction process for multiple gTLD applicants

The auctions process in case of multiple gTLD applicants will be applied as a last resort. ICANN encourage applicants to work on developing a mutually-agreeable solution.

The new gTLD program offers heightened protection mechanisms against abuses, registry failure and other malicious conducts designed by intellectual property experts

  • Law Enforcement Community Recommendations

ICANN is actively working on the 12 recommendations of the law enforcement community and negotiating with registrars to amend the Registrar Accreditation Agreement (RAA), particularly the inclusion of a more improved and accurate Whois database.

  • Cost/Benefit Analysis used by ICANN before implementing the new gTLD program

Five economic studies were commissioned by ICANN to examine the anticipated benefits and costs of the new gTLD program.

Second Round of Application

On February 7, 2012, the ICANN Board approved the implementation of a second round and application window for the new gTLD program in response to the request of the global Internet community, particularly the members of CADNA. The board delegated the ICANN CEO to work with the Internet community to develop a work plan and the needed prerequisites to open the second round of application for new gTLDs.[105] [101]

Awards

In May, 2012, ICANN was recognized by The Board of Trustees of Sheikh Salem Al-Ali Al-Sabah Informatics Award with their 11th 'Informatics Medal'. The medal is given with appreciation for the organization's efforts at maintaining and strengthening the Internet's infrastructure. The Board also expressed gratitude for the role that ICANN has played in developing and deploying Arabic IDN's, which allow Arabic populations to surf the web without relying on foreign characters or domains. The award has been given out since 2007, and is given to institutions or public figures that are influential in the fields of Informatics and Internet Development. It was received on behalf of ICANN by the company's President and CEO, Rod Beckstrom.[106][107]

CEO Fadi Chehadé

Since first introducing himself to the ICANN Community at ICANN 44 in Prague, and assuming the CEO position ahead of ICANN 45 in Toronto, Mr. Chehadé has actively engaged and restructured the organization to better facilitate what he has determined are its core functions. This includes: Operational Excellence, Contract Compliance, International Outreach, and Transparency.[108]

Contractual Compliance

A major push by Mr. Chehadé was to improve contractual compliance at ICANN. He stressed in his introductory speech that his prior experience at IBM taught him the importance of writing and following through clearly on contracts. On his first day as CEO he promoted Maguy Serad, Senior Director of Contractual Compliance, to Vice President of Contractual Compliance, with her department reporting directly to the CEO.[108]

"Contractual Compliance Audit Program" was introduced in late 2012 as a 3 year plan to ensure all registries and registrars are following their contracts. The scope of the program is: Registrar and registry agreements, including the incorporated ICANN consensus policies; All ICANN-accredited registrars (2001 and 2009 RAAs); Existing TLD registries; New agreements entered into with a contracted party may be included; New gTLD registries (when available). The timeline is broken down so that over the three year period 1/3 of Registry and Registrar agreements from a complete list will be randomly selected and audited, continuing with the remainder until finished.[109]

In January, 2013, Verisign Senior Vice President Pat Kane sent ICANN a letter stating that it had no intentions submitting to an ICANN audit of its .net registry. Kane wrote, "Verisign has no contractual obligations under its .net Registry Agreement with ICANN to comply with the proposed audit. Absent such express contractual obligations, Verisign will not submit itself to an audit by or at the direction of ICANN of its books and records." A registry audit would entail a review of compliance with Whois, zone file access, data escrow, monthly reporting, and other policies outlined in the registry agreements.[110]

International Outreach & Engagement with Underrepresented Regions

Fadi Chehadé made expanding on previous CEO Rod Beckstrom's work on reaching out to the international world a major priority, which notably entailed requiring new staff hires to speak 2 languages and personal and staff tours to promote ICANN and its New gTLD Program. It seemed through the way he talked about the current level of outreach and engagement and the lack of results that he believed that previous efforts were not substantial enough. He noted in his first speech to an ICANN audience, at ICANN 44 in Prague before he took up the CEO position, that he had already met with the African and Latin American delegations and that they were "yearning" to be reached out, which would be a top priority.[111] The day that he assumed the position of CEO he also appointed Sally Costerton to lead Stakeholder Engagement and Tarek Kamel to act as Senior Adviser to Government Affairs. The promotion of Mr. Kamel, an Egyptian national, was the first time an individual from the developing world had been made an Executive of ICANN. Both these positions are based in ICANN's European Headquarters and report directly to the CEO.[112]

Weeks later, 4 Vice Presidents of Regional Stakeholder Engagement were announced. These positions report directly to Sally Costerton and were mostly internal promotions intended to raise the level of importance for global engagement. The Vice Presidents are: Pierre Dandjinou, Africa; Baher Esmat, Middle East; Veni Markovski, Russia, CIS and Eastern Europe; Savenaca Vocea, Australasia/Pacific Islands.[113]

In October, 2012, AFRINIC and ICANN signed an agreement to facilitate the deployment of anycast instances of L Root DNS server, operated by ICANN, in the African region. ICANN, as the operator of the L-Root Server, will work cooperatively with AFRINIC to identify candidate sites within the region of Africa that meet the criteria for the hosting of anycast instances of the L-Root server operated by ICANN. Part of AFRINIC's mission aims to increase the number of DNS root servers instances in the African region as well as its own DNS Anycast platform where AFRINIC hosts its own DNS services but also make it available at no cost for ccTLDs in the region.[114]

At ICANN 45 in Toronto, a 3 year plan, entitled "ICANN's New Approach to Africa", was unveiled and presented to the community for comment. The plan was created through a working group convened at the previous ICANN meeting, which involved input from much of the African delegation, AFRINIC, and other important contacts knowledgeable about the region.[115]

In February 2013, CEO Fadi Chehadé announced that ICANN's office in L.A. would diminish in importance while two new "hubs" would be created to fill the gap and provide new means of outreach to ICANN's international constituents. The hubs are to be located in Singapore and Istanbul, and are to act with far more authority and purpose than a stand-alone office; it is clear that many senior staff from the L.A. office will be asked to move, and the CEO himself said he will be based in Singapore once that office is up and running.[116][117] The news was announced during Mr. Chehadé's first comprehensive tour of Asia, with trips to South Korea, China, Japan, and Singapore. He noted that ICANN needed to apologize to Asia, as it had long not been given the attention it deserved within the organization.[118]

In March 2013, Mr. Chehadé continued on his global outreach tour and engaged Middle eastern stakeholders at the Arab Multi-Stakeholder Internet Governance meeting in Dubai. The meeting, hosted by the Telecommunications Regulatory Authority (TRA) of the United Arab Emirates, brought together representatives from several different Internet organizations. Fadi Chehadé noted that he hoped to have a more clear engagement strategy for the Arab World by May, and noted that this goal would only be possible if the many Arab stakeholders involved also came to the table.[119]

Implementation vs. Policy Development

While a longstanding issue within the ICANN community, the difference and use of implementation procedures and policy development began to reach a noticeable head throughout 2012 and into 2013. Strictly speaking, anything that is "ICANN Policy" needs to go through its various supporting organizations and be approved, while implementation refers to matters adopted by the ICANN Board regardless of any consultation to the rest of the community. ICANN is supposed to be driven by bottom-up, consensus policy development, and this often results in the organization making slow progress. Implementation procedures are necessary to accommodate the practical issues related to organizational effectiveness.[120]

Issues that have recently sparked debates over implementation vs. policy development:

  • Special protections were given to the Internaional Olympic Comittee and Red Cross/Red Crescent in 2012 with regards to their marks across all New gTLDs. This action was approved by the ICANN Board despite the fact that the GNSO was still debating the issue though still largely against the special protections.
  • In 2012, the registry agreements for .com and .net were renewed without requirements for a "thick" Whois, despite policy development that was working for such requirements.[121]
  • The current model of the Trademark Clearinghouse and Uniform Rapid Suspension System did not come from the policy that was drafted on trademark issues but rather special groups, including the Implementation Review Team.
  • Further trademark issues appear to be forthcoming via implementation and not policy development after closed-door meetings in late 2012 with business and IP interests within the community.[120] This is known as the "Strawman Solution".[122]

References

  1. 1.0 1.1 1.2 1.3 1.4 ICANN DOC MoU Memorandum of Understanding, Depart. of Commerce and ICANN. ICANN. Published 1999 December 31.
  2. ICANN Strategic Plan June 2010 June 2013. ICANN.
  3. 3.0 3.1 ICANN About Meetings. ICANN.
  4. ICANN Organizational Structure. Stanford University.
  5. Obama administration joins critics of U.S. nonprofit group that oversees Internet. The Washington Post. Published 2011 March 1.
  6. Board Review. ICANN.
  7. 7.0 7.1 ICANN Bylaws. ICANN.
  8. 8.0 8.1 ICANN Board awards itself $35,000, developing countries $138,000, and adds to confusion with secondary timestamp. dotnxt. Published 2011 December 13.
  9. Board of Directors. ICANN.
  10. Generic Names Supporting Organization. ICANN.
  11. About. Country Code Names Supporting Organisation.
  12. The Address Supporting Organization. ICANN.
  13. About APNIC. APNIC.
  14. Adress Council Members. ASO.
  15. Middle East Developments Cause Cancellation of ICANN Jordan Meeting. ICANN Blog. Published 2011 February 18.
  16. ICANN Confirms June Singapore Meeting. Goldstein Report. Published 2011 February 27.
  17. Fellowship Program. ICANN.
  18. Improvement of Technical Management of Internet Names and Addresses; Proposed Rule. National Telecommunications & Information Administration. Published 1998 February 20.
  19. Statement of Policy on the Management of Internet Names and Addresses. National Telecommunications & Information Administration. Published 1998 June 5.
  20. ICANN White Paper. ICANN.
  21. 21.0 21.1 The Green Paper vs. The White Paper. ICANN. Published 1999 October 18.
  22. How do the NTIA White Paper and the ICANN By-Laws Impact Membership?. Harvard Law. Published 1999 January 19.
  23. Letter from Boston Working Group to Ira Magaziner. National Telecommunications & Information Administration. Published 1998 September 28.
  24. 24.0 24.1 24.2 Congressional Hearing.Published 1999 July.
  25. 25.0 25.1 25.2 ICANN Profile, Structure and Personnel Review. Caslon Analytics.
  26. DNSO Background. ICANN.
  27. Resolution on DNSO Constituencies. ICANN.
  28. DNSO Website
  29. Appendix B to Minutes of Board Meeting. ICANN. Published 2002 December 12.
  30. 30.0 30.1 ICANN Bylaws As Amended and Restated. ICANN. Published 1999 October 29.
  31. 31.0 31.1 31.2 31.3 31.4 Registrar Accreditation: History of the Shared Registry System. ICANN.
  32. Amendment 11. National Telecommunications & Information Administration. Published 1998 October 7.
  33. 33.0 33.1 Amendment 12. National Telecommunications & Information Administration.
  34. Amendment 13. National Telecommunications & Information Administration.
  35. Press Release: ICANN Releases Draft Accreditation Guidelines. Mail Archive. Published 1999 February 8.
  36. ICANN Public Meeting Details. Harvard Law.
  37. Statement of Registrar Accreditation Policy
  38. 38.0 38.1 Registrar Competition Testbed and Accreditation Update #2. ICANN. Published 1999 June 14.
  39. http://cyber.law.harvard.edu/icann/pressingissues2000/briefingbook/milestones.html. Harvard Law.
  40. Fact Sheet on Tentative Agreements among ICANN, the U.S. Department of Commerce, and Network Solutions, Inc. ICANN.
  41. Uniform Domain Name Dispute Resolution Policy. ICANN. Published 1999 September 29.
  42. Rules for Uniform Domain Name Dispute Resolution Policy]. ICANN. Published 1999 September 29.
  43. Overview of Domain Name Policy Development. Harvard Law.
  44. "ICANN 2.0 Meet the New Boss"
  45. At-Large Advisory Committee (ALAC). ICANN.
  46. 46.0 46.1 ICANN Meeting in Accra Preliminary Report. ICANN. Published 2002 March 14.
  47. President's Report: ICANN – The Case for Reform. ICANN. Published 2002 February 24.
  48. 48.0 48.1 ICANN Meeting in Bucharest Preliminary Report]. ICANN. Published 2002 June 28.
  49. Appendix A to Minutes ICANN Board Meeting in Shanghai. ICANN. Published 2002 October 31.
  50. ICANN.org
  51. Regular Meeting of the Board Minutes. ICANN. Published 2001 September 10.
  52. Fourth Annual Meeting of the Board Minutes. ICANN. Published 2002 December 15.
  53. Preliminary Report | Regular Meeting of the Board - Rio de Janeiro. ICANN. Published 2003 March 27.
  54. Resolutions Adopted at Rome ICANN Board Meeting | Regular Meeting of the Board, Rome, Italy. ICANN. Published 2004 March 6.
  55. AfriNIC Application for Recognition as Regional Internet Registry Public Comment Forum. ICANN. Published 2005 March 14.
  56. Memorandum of Understanding Between the U.S. Department of Commerce and the Internet Corporation for Assigned Names and Numbers. National Telecommunications & Information Administration.
  57. ICANN Board Resolutions in Carthage, Tunisia. ICANN. Published 2003 October 31.
  58. 2005 Board Meetings
  59. Information Page for Sponsored Top-Level Domains. ICANN.
  60. .XXX Registry Agreement. ICANN. Published 2011 March 31.
  61. About the New gTLD Program. ICANN.
  62. ICANN Confirms Possible New Applicant Guidebook. Domain Incite. Published 2012 January 4.
  63. ICANN Verisign and NTIA ready for 100 new gTLDs per Week. Domain Incite. Published 2012 November 8.
  64. New gTLDs expand ICANN Domain Incite. Published 2011 September 21.
  65. ICANN LA To be Broken Up Begging Letters to Stop, Nigel.je Retrieved 25 Feb 2012
  66. ICANN to Set up Hubs in Singapore and Istanbul, DomainIncite.com Retrieved 25 Feb 2013
  67. ICANN CEo We Owe Asia a Big Apology, ZDnet.com Retrieved 25 Feb 2013
  68. 68.0 68.1 Calls to Fix Revolving Door. Domain Incite. Published 2011 June 26.
  69. Former ICANN Chair Joins M + M. Domain Incite. Published 2011 June 26.
  70. Would an ICANN ethics policy break the law. Domain Incite. Published 2011 October 3.
  71. ICANN to Hire Conflict of Interest Experts. Domain Incite. Published 2011 October 6.
  72. ICANN Conflict of Interest Policy. ICANN. Published 2012 May 6.
  73. ICANN to Manage Time Zone Database. ICANN. Published 2011 October 14.
  74. Owner of YouPorn.com Plans to File Suit Against ICM ICANN over XXX. The Domains. Published 2011 November 16.
  75. YouPorn Challenges New gTLDs with Review Demand. Domain Incite. Published 2011 November 17.
  76. ICANN: Antitrust Law Does Not Apply To Us. Domain Incite. Published 2012 January 21.
  77. ICM and YouPorn in AntiTrust Settlement Talks. Domain Incite. Published 2012 February 14.
  78. Manwin Amends Complaint Against ICM & ICANN & Drops 2 State Claims & Talks Of Settlement. The Domains. Published 2012 February 21.
  79. Court rules YouPorn can sue ICANN for alleged .xxx antitrust violations. Domain Incite. Published 2012 August 14.
  80. ICANN threatens to shut down .jobs. Domain Incite. Published 2011 February 28.
  81. Employ Media Response to ICANN'S Notice of Breach. dotJobs. Published 2011 February 28.
  82. Registry avoids .jobs shut-down. Domain Incite. Published 2011 April 20.
  83. .Jobs Manager Seeks Arbitration by International Court
  84. War of Words Over Jobs Breach Claims. Domain Incite. Published 2011 May 3.
  85. ICANN’s Response to Employ Media’s Request for Arbitration. Google Docs.
  86. Arbitration: Employ Media vs. ICANN. ICANN. Published 2012 November 1.
  87. The case study that could kill ICANN. dotnxt. Published 2012 January 11.
  88. A New Approach to Africa. ICANN. Published 2012 August 10.
  89. Chehade Commits to Grow The Number of Number of Domain Registrars in Africa, DomainIncite.com Retrieved 8 Mar 2013
  90. Hearings-ICANN's Expansion of Top Level Domains-Dec. 8, 2012. U.S. Senate. Published 2012 December 8.
  91. Testimony of Angela F. Williams, Senate Hearing, Dec. 8, 2012. U.S. Senate. Published 2012 December 8.
  92. Testimony of Daniel L. Jaffe, Hearing on ICANN’s Expansion of Top Level Domains, Dec. 8, 2012. U.S. Senate. Published 2012 December 8.
  93. Testimony of Esther Dyson, Hearing on ICANN's Expansion of Top Level Domains, Dec. 8, 2011. U.S. Senate. Published 2011 December 8.
  94. Testimony of Fiona M. Alexander, Hearing on ICANN’s Expansion of Top Level Domains, Dec. 8, 2011. U.S. Senate. Published 2011 December 8.
  95. Testimony of Kurt Pritz, Hearing on Expansion of Top Level Domain Names, Dec. 8, 2012
  96. Sen. Barbara Boxer to Kurt Pritz, Questions for the Record,ICANN’s Expansion of Top Level Domain Names, Dec. 8, 2011. U.S. Senate. Published 2011 December 8.
  97. Pritz to Boxer. Published 2012 January 25.
  98. Building a Secure and Reliable Trademark Clearinghouse. ICANN Blog. Published 2012 November 7. Retrieved 2012 November 13.
  99. United States: New gTLD Hearing, Round 2: A Critical House, But To What End?. Mondaq. Published 2011 December 22.
  100. Testimony of Josh Bourne-President, Coalition Against Domain Name Abuse. Committee on Energy & Commerce. Published 2011 December 14.
  101. 101.0 101.1 International - Call for ICANN to announce second round of gTLD applications. World Trademark Review. Published 2011 November 2.
  102. Testimony of Anjali K. Hansen-Intellectual Property Attorney, Council of Better Business Bureaus
  103. Testimony of Thomas Embrescia, CEO of Employ Media. Committee on Energy & Commerce. Published 2011 December 14.
  104. ICANN's Response to Cong. Greg Walden. ICANN. Published 2012 January 20.
  105. Approved Board Resolutions | Special Meeting of the ICANN Board. ICANN. Published 2012 February 7.
  106. Informatics prize for ICANN - Salem Ali Prize panel. Kuna. Published 2012 May 1.
  107. ICANN Receives Arab World Award. ICANN. Published 2012 May 22.
  108. 108.0 108.1 Video, ICANN 44 Speech, Youtube.comPosted 25 June 2012, Retrieved 11 January 2013
  109. Audits, ICANN.orgRetrieved 11 Jan 2013
  110. In Major Sub Verisign Refuses to Let ICANN Audit Net, DomainIncite.comPublished & retrieved 11 Jan 2012
  111. New ICANN CEO Fadi Chehade Impresses in Opening Session the Internet is the Greatest Public Gift, TheDomains.comPublished 25 June 2012, Retrieved 11 Jan 2013
  112. Announcement 19Oct12, ICANN.orgPublished 19 Oct 2012, Retrieved 11 Jan 2013
  113. Announcement 28Nov12, ICANN.orgPublished 28 Nov 2012, Retrieved 11 Jan 2013
  114. AFRINIC and ICANN to cooperate Further in Internet Development, AFRINIC.netPublished 18 Oct 2012, Retrieved 11 Jan 2013
  115. Initiative Unveiled to Increase ICANNs Presence in Africa, ThisDayLive.com Published 1 Nov 2012, Retrieved 11 Jan 2013
  116. ICANN LA To be Broken Up Begging Letters to Stop, Nigel.je Retrieved 25 Feb 2012
  117. ICANN to Set up Hubs in Singapore and Istanbul, DomainIncite.com Retrieved 25 Feb 2013
  118. ICANN CEo We Owe Asia a Big Apology, ZDnet.com Retrieved 25 Feb 2013
  119. PRWeb, Releases, PRWeb.com Retrieved & Published March 7 2013
  120. 120.0 120.1 Race Toward New, BNA.comPublished 17 Jan 2013, Retrieved 18 Jan
  121. Why Com Still Doesnt Have Thick Whois, DomainIncite.comPublished Aug 31 2012, Retrieve 18 Jan 2013
  122. TMCH Strawman, ICANN.org 30 Nov 2012, Retrieved 18 Jan 2013