Jump to content

ICANN: Difference between revisions

From ICANNWiki
← Older editNewer edit →
VisualWikitext
Jessica (talk | contribs)
Bureaucrats, Check users, lookupuser, Administrators, translator
14,952 edits
Jessica (talk | contribs)
Bureaucrats, Check users, lookupuser, Administrators, translator
14,952 edits
Line 167: Line 167:


==Process==
==Process==
ICANN generates and relies on a multitude of policies and practices. Some of the policies, such as those that govern [[[DNS]] have to undergo a formal [[PDP]] and must culminate with [[ICANN Board]] approval. Other policies and practices have been developed through extensive dialogue to reflect the perspectives of various stakeholders in the ICANN community, but they have not gone through a PDP. Operational policies and General practices are examples of the latter.<ref>[https://www.icann.org/policy#what_is_policy What is Policy?]</ref>
ICANN generates and relies on a multitude of policies and practices. Some of the policies, such as those that govern [[DNS]],  undergo a formal [[PDP]] and must culminate in an [[ICANN Board]] approval. The processes through which ICANN functions are developed through extensive dialogue in an effort to reflect the perspectives of various stakeholders in the ICANN community, but they do not require a PDP. Operational policies and General practices are examples of the latter.<ref>[https://www.icann.org/policy#what_is_policy What is Policy?]</ref>
   
   
===Policy Development===
===Policy Development===
Line 175: Line 175:
===Governance===
===Governance===
: ''Main article: [[ICANN Governance]]''
: ''Main article: [[ICANN Governance]]''
Governance refers to the operational policies that define how ICANN operates as an organization. These policies are not subject to a policy development process (PDP) and tend to depend on community input through less formal means.
Governance refers to the operational policies that define how ICANN operates as an organization. These policies are not subject to PDPs and tend to depend on community input through less formal means.


===Meetings===
===Meetings===

Revision as of 18:49, 19 January 2021

ICANNWiki Partner
Type: Private, Non-Profit
Industry: Internet Protocol Management
Founded: September 1998
Headquarters: 12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536 USA
Employees: 140 employees
Revenue: $217 million (2015)
Website: icann.org
Blog: blog.icann.org
Facebook: icannorg
LinkedIn: ICANN
Twitter: @ICANN
Key People
Göran Marby, CEO and President

Cherine Chalaby, Chair of the Board
Jeff Moss VP and Chief Security Officer

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

While ICANN began in the U.S. government, it is now and continues to be, an international, community-driven organization independent of any one government.[2] ICANN's management of an interoperable Internet covers over 330 million domain names, the allocation of more than 4 billion network addresses, and the support of approximately 95 million DNS look-ups every day across 240 countries.[3][4][5]

ICANN collaborates with a variety of stakeholders including 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, during which the new ICANN Board members take their seats.[6]

History: The Beginning[edit | edit source]

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

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

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 that made clear that the agency intended to empower a non-profit entity to take control of the Internet and its DNS system.[9] The proposal drew criticism from some American lawmakers and other concerned individuals who saw the American-fostered Internet about to be handed over to the IAHC, a Swiss entity.[10] 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.[11] 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.

The Memorandum of Understanding[edit | edit source]

On November 25, 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 and create 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.[12] The original agreement was set with an expiration of September 30th, 2000.[1] The MoU has been amended several times.

ICANN's bottom-up focus and its periodic structural reviews lead to a 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".[13]

Registrar Accreditation Process[edit | edit source]

On February 8th, 1999, ICANN posted its Draft Guidelines for Registrar Accreditation for public commentary.[14] The guidelines were formed through consultation with the DOC and NSI, and further tailored after the session of public commentary.[15] 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.[16] The ICANN board accepted the revised Statement of Registrar Accreditation Policy at their March, 1999 meeting in Singapore.[17]

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.[18]

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

Further Developments[edit | edit source]

gTLD Expansion[edit | edit source]

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".[28]

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.[29]

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.[30]; they all went on to approval in 2005-2006, except for the controversial .xxx,[31] which went through a much more contentious and drawn out process but was still approved in March, 2011 at ICANN 40.[32]

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.[33] 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.[34]

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

Second Round of Applications[edit | edit source]

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.[36]

Physical Expansion[edit | edit source]

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..[37] The Sydney office went on to be closed in 2012.

In February 2013, former 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.[38][39] 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.[40]

As of 2017, ICANN has offices in Los Angeles, Singapore, Montevideo, and Brussels. It has engagement centers in Geneva, Beijing, Nairobi, and Washington, DC.[41]

Time Zone Database[edit | edit source]

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.[42]

IANA Functions Stewardship Transition[edit | edit source]

Main article: IANA Functions Stewardship Transition

In March 2014, NTIA released a statement saying that they are intent on transitioning their part of the IANA functions away from NTIA and to the global stakeholder community. [43] ICANN issued a press release supporting this shift. [44]

ICANN created a co-ordination group from nominations among 13 community stakeholder groups, totaling 27 individuals, which produced a draft transition document. On December 2, 2014, ICANN opened the public comment period on the draft transition document produced by the coordination group.[45]

A New Approach to Africa[edit | edit source]

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.[46] The initiative has received strong support from African Internet stakeholders, including former Board Member Katim Touray. In March 2013, 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[47]

UDRP[edit | edit source]

Main article: 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.[48]

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.[49] Some of the public comments can be found here.

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

Review and Transparency Development[edit | edit source]

Many of the other developments at ICANN have been accomplished through the introduction of review teams, such as the Committee on ICANN Evolution and Reform. The push for reform was also significantly aided by Stuart Lynn's "President's report: The Case for Reform,"[51] which was credited with starting the dialogue on reform and leading to the creation of a formal committee.[23]

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 more clearly defined ICANN's mission and core values 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.[52]

Organization & Structure[edit | edit source]

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.[53] 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.[54] ICANN's structure and process is outlined in the ICANN Bylaws.

Board of Directors[edit | edit source]

Main article: ICANN Board

ICANN is governed by a Board of Directors made up of 15 voting members,[55] and the President and CEO, who is also a voting member. The board is further aided by five non-voting liaisons.[56] 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.[57]

Ombudsman[edit | edit source]

Main article: Ombudsman

The Ombudsman's function is to act as an independent, impartial, and neutral informal dispute resolution officer for the ICANN community for those who want to lodge a complaint about ICANN staff, board, or supporting organizations. The office of the Ombudsman ensures that the members of the ICANN community are treated fairly and uses techniques such as mediation, shuttle diplomacy, and formal investigation if needed. The Ombudsman investigates issues without taking sides through an informal, flexible process. The current Ombudsman is Herb Waye.

GNSO[edit | edit source]

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.[58]

ccNSO[edit | edit source]

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.[59]

ASO[edit | edit source]

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.[60] Its members are appointed by the world's 5 Regional Internet Registries (RIRs), which manage and allocate IP addresses in their respective continental regions.[61][62]

GAC[edit | edit source]

Main article: GAC

The GAC is an advisory committee to ICANN, created under the ICANN ByLaws. It provides advice to ICANN on public policy aspects of ICANN’s responsibilities with regard to the Internet Domain Name System (DNS). The GAC is not a decision-making body. It advises ICANN on issues that are within ICANN’s scope. GAC advice has a particular status under the ICANN ByLaws. Its advice must be duly taken into account by the ICANN Board, and where the Board proposes actions inconsistent with GAC advice it must give reasons for doing so and attempt to reach a mutually acceptable solution. The GAC appoints a non-voting liaison to the ICANN Board. This is normally the GAC Chair.

ALAC[edit | edit source]

Main article: ALAC

The At-Large Advisory Committee (ALAC) is one of ICANN's Advisory Committees. The mission of ALAC is to function as an advocate for the interests of individual Internet users.

SSAC[edit | edit source]

Main article: SSAC

This committee was originally intended to expand and specialize the role of ICANN, and it received official recognition in 2002.[22]

RSSAC[edit | edit source]

Main article: RSSAC

Process[edit | edit source]

ICANN generates and relies on a multitude of policies and practices. Some of the policies, such as those that govern DNS, undergo a formal PDP and must culminate in an ICANN Board approval. The processes through which ICANN functions are developed through extensive dialogue in an effort to reflect the perspectives of various stakeholders in the ICANN community, but they do not require a PDP. Operational policies and General practices are examples of the latter.[63]

Policy Development[edit | edit source]

Main article: ICANN Policy Development

DNS Policies are developed through formal policy development processes (PDPs), as set forth by the Bylaws.

Governance[edit | edit source]

Main article: ICANN Governance

Governance refers to the operational policies that define how ICANN operates as an organization. These policies are not subject to PDPs and tend to depend on community input through less formal means.

Meetings[edit | edit source]

Main article: ICANN Meetings

ICANN holds meetings three times per year; one of these meetings serves as the organization's annual general 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.[6] The next meeting will be the 61st meeting in San Juan, Puerto Rico.[64] Meetings are designated as A, B, C, and each meeting has a varying length and purpose.

Accountability[edit | edit source]

Main article: ICANN Accountability

Reviews[edit | edit source]

Main article: ICANN Reviews

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 board's 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.[56]

Conflicts of Interest[edit | edit source]

ICANN adopted a Conflict of Interest policy in 2012.[65] The policy requires that all Board Members, as well as those in various other positions, 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,[66] Board members also may not join business with a new gTLD registry until 12 months after the registry's application has been voted on.[57] Prior to the policy, ICANN did not have a clear position. 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.[67]

ICANN's CEO, Rod Beckstrom had previously noted at the opening ceremony to ICANN 42, even before staff member 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. 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.[68]

Manwin Anti-Trust Lawsuit[edit | edit source]

Main article: sTLD

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.[69] 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."[70]

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.[71] ICANN's and ICM's motions to dismiss can be found here and here respectively.

Employ Media Arbitration[edit | edit source]

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.[72] [73] [74] [75] [76] [77] [78]

.JOBS Charter Compliance Coalition Criticism[edit | edit source]

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.[79]

Awards[edit | edit source]

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.[80][81]

References[edit | edit source]

  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. ↑ Stewardship of IANA Functions Transitions to Global Internet Community as Contract with U.S. Government Ends. Retrieved 20 Nov 2017.
  3. ↑ ICANN Strategic Plan June 2010 June 2013. ICANN.
  4. ↑ VERISIGN DOMAIN NAME INDUSTRY BRIEF: INTERNET GROWS TO 330.6 MILLION DOMAIN NAMES IN Q1 2017. Retrieved 20 Nov 2017.
  5. ↑ OpenDNS. Retrieved 20 Nov 2017.
  6. ↑ 6.0 6.1 ICANN About Meetings. ICANN.
  7. ↑ Improvement of Technical Management of Internet Names and Addresses; Proposed Rule. National Telecommunications & Information Administration. Published 1998 February 20.
  8. ↑ Statement of Policy on the Management of Internet Names and Addresses. National Telecommunications & Information Administration. Published 1998 June 5.
  9. ↑ ICANN White Paper. ICANN.
  10. ↑ The Green Paper vs. The White Paper. ICANN. Published 1999 October 18.
  11. ↑ How do the NTIA White Paper and the ICANN By-Laws Impact Membership?. Harvard Law. Published 1999 January 19.
  12. ↑ Congressional Hearing.Published 1999 July.
  13. ↑ "ICANN 2.0 Meet the New Boss"
  14. ↑ ref name="accreditation"
  15. ↑ Press Release: ICANN Releases Draft Accreditation Guidelines. Mail Archive. Published 1999 February 8.
  16. ↑ ICANN Public Meeting Details. Harvard Law.
  17. ↑ ref name="accreditation"
  18. ↑ Statement of Registrar Accreditation Policy
  19. ↑ ref name="accreditation"
  20. ↑ ICANN.org
  21. ↑ Regular Meeting of the Board Minutes. ICANN. Published 2001 September 10.
  22. ↑ 22.0 22.1 ICANN Meeting in Accra Preliminary Report. ICANN. Published 2002 March 14.
  23. ↑ 23.0 23.1 ICANN Meeting in Bucharest Preliminary Report]. ICANN. Published 2002 June 28.
  24. ↑ Fourth Annual Meeting of the Board Minutes. ICANN. Published 2002 December 15.
  25. ↑ Preliminary Report | Regular Meeting of the Board - Rio de Janeiro. ICANN. Published 2003 March 27.
  26. ↑ Resolutions Adopted at Rome ICANN Board Meeting | Regular Meeting of the Board, Rome, Italy. ICANN. Published 2004 March 6.
  27. ↑ AfriNIC Application for Recognition as Regional Internet Registry Public Comment Forum. ICANN. Published 2005 March 14.
  28. ↑ Memorandum of Understanding Between the U.S. Department of Commerce and the Internet Corporation for Assigned Names and Numbers. National Telecommunications & Information Administration.
  29. ↑ ICANN Board Resolutions in Carthage, Tunisia. ICANN. Published 2003 October 31.
  30. ↑ 2005 Board Meetings
  31. ↑ Information Page for Sponsored Top-Level Domains. ICANN.
  32. ↑ .XXX Registry Agreement. ICANN. Published 2011 March 31.
  33. ↑ About the New gTLD Program. ICANN.
  34. ↑ ICANN Confirms Possible New Applicant Guidebook. Domain Incite. Published 2012 January 4.
  35. ↑ ICANN Verisign and NTIA ready for 100 new gTLDs per Week. Domain Incite. Published 2012 November 8.
  36. ↑ Approved Board Resolutions | Special Meeting of the ICANN Board. ICANN. Published 2012 February 7.
  37. ↑ New gTLDs expand ICANN Domain Incite. Published 2011 September 21.
  38. ↑ ICANN LA To be Broken Up Begging Letters to Stop, Nigel.je Retrieved 25 Feb 2012
  39. ↑ ICANN to Set up Hubs in Singapore and Istanbul, DomainIncite.com Retrieved 25 Feb 2013
  40. ↑ ICANN CEO We Owe Asia a Big Apology, ZDnet.com Retrieved 25 Feb 2013
  41. ↑ ICANN Contact Page. Retrieved 22 Nov 2017.
  42. ↑ ICANN to Manage Time Zone Database. ICANN. Published 2011 October 14.
  43. ↑ NTIA announces intent to transition key domain name functions
  44. ↑ Press release, March 14 2014
  45. ↑ ICANN opens comment period for its move out of US control
  46. ↑ A New Approach to Africa. ICANN. Published 2012 August 10.
  47. ↑ Chehade Commits to Grow The Number of Number of Domain Registrars in Africa, DomainIncite.com Retrieved 8 Mar 2013
  48. ↑ Uniform Domain Name Dispute Resolution Policy. ICANN. Published 1999 September 29.
  49. ↑ Rules for Uniform Domain Name Dispute Resolution Policy]. ICANN. Published 1999 September 29.
  50. ↑ Overview of Domain Name Policy Development. Harvard Law.
  51. ↑ President's Report: ICANN – The Case for Reform. ICANN. Published 2002 February 24.
  52. ↑ Appendix A to Minutes ICANN Board Meeting in Shanghai. ICANN. Published 2002 October 31.
  53. ↑ ICANN Organizational Structure. Stanford University.
  54. ↑ Obama administration joins critics of U.S. nonprofit group that oversees Internet. The Washington Post. Published 2011 March 1.
  55. ↑ Board Review. ICANN.
  56. ↑ 56.0 56.1 ICANN Bylaws. ICANN.
  57. ↑ 57.0 57.1 ICANN Board awards itself $35,000, developing countries $138,000, and adds to confusion with secondary timestamp. dotnxt. Published 2011 December 13.
  58. ↑ Generic Names Supporting Organization. ICANN.
  59. ↑ About. Country Code Names Supporting Organisation.
  60. ↑ The Address Supporting Organization. ICANN.
  61. ↑ About APNIC. APNIC.
  62. ↑ Adress Council Members. ASO.
  63. ↑ What is Policy?
  64. ↑ Middle East Developments Cause Cancellation of ICANN Jordan Meeting. ICANN Blog. Published 2011 February 18.
  65. ↑ ICANN Conflict of Interest Policy. Retrieved 21 Nov 2017.
  66. ↑ ICANN Conflict of Interest Policy. ICANN. Published 2012 May 6.
  67. ↑ Calls to Fix Revolving Door. Domain Incite. Published 2011 June 26.
  68. ↑ ICANN to Hire Conflict of Interest Experts. Domain Incite. Published 2011 October 6.
  69. ↑ Owner of YouPorn.com Plans to File Suit Against ICM ICANN over XXX. The Domains. Published 2011 November 16.
  70. ↑ YouPorn Challenges New gTLDs with Review Demand. Domain Incite. Published 2011 November 17.
  71. ↑ ICANN: Antitrust Law Does Not Apply To Us. Domain Incite. Published 2012 January 21.
  72. ↑ ICANN threatens to shut down .jobs. Domain Incite. Published 2011 February 28.
  73. ↑ Employ Media Response to ICANN'S Notice of Breach. dotJobs. Published 2011 February 28.
  74. ↑ Registry avoids .jobs shut-down. Domain Incite. Published 2011 April 20.
  75. ↑ .Jobs Manager Seeks Arbitration by International Court
  76. ↑ War of Words Over Jobs Breach Claims. Domain Incite. Published 2011 May 3.
  77. ↑ ICANN’s Response to Employ Media’s Request for Arbitration. Google Docs.
  78. ↑ Arbitration: Employ Media vs. ICANN. ICANN. Published 2012 November 1.
  79. ↑ The case study that could kill ICANN. dotnxt. Published 2012 January 11.
  80. ↑ Informatics prize for ICANN - Salem Ali Prize panel. Kuna. Published 2012 May 1.
  81. ↑ ICANN Receives Arab World Award. ICANN. Published 2012 May 22.

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Country Code Names Supporting Organization. Develops and recommends to the Board global policies relating to country-code top-level domains (ICANN Bylaws).

Address Supporting Organization. Advises the Board with respect to policy issues relating to the operation, assignment, and management of Internet addresses (ICANN Bylaws).

Governmental Advisory Committee. Considers and provides advice on the activities of ICANN as they relate to concerns of governments, particularly matters where there may be an interaction between ICANN's policies and various laws and international agreements or where they may affect public policy issues (ICANN Bylaws).

At-Large Advisory Committee. Considers and provides advice on the activities of ICANN related to the interests of individual Internet users (ICANN Bylaws). Not to be confused with the Non-Commercial Stakeholder Group.

Security and Stability Advisory Committee. Advises the ICANN community and Board on matters relating to the security and integrity of the Internet's naming and address allocation systems (ICANN Bylaws).

Root Server System Advisory Committee. Advises the ICANN community and Board on matters relating to the operation, administration, security, and integrity of the Internet's Root Server System (ICANN Bylaws).

Retrieved from "https://icannwiki.org/index.php?title=ICANN&oldid=1299374"