Changes

Jump to navigation Jump to search
766 bytes removed ,  2 months ago
m
Line 23: Line 23:  
[[Jeff Moss]] VP and Chief Security Officer <br>
 
[[Jeff Moss]] VP and Chief Security Officer <br>
 
}}
 
}}
'''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 [[DOC|Department of Commerce]].<ref name="icann-mou">[http://www.icann.org/en/general/icann-mou-25nov98.htm ICANN DOC MoU Memorandum of Understanding, Depart. of Commerce and ICANN]. ICANN. Published 1999 December 31.</ref> It coordinates the Internet [[DNS]], [[IP]] addresses and [[ASN|autonomous system numbers]], which involves a continued management of these evolving systems and the protocols that underlie them.
+
'''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 [[DOC|Department of Commerce]].<ref name="icann-mou">[http://www.icann.org/en/general/icann-mou-25nov98.htm ICANN DOC MoU Memorandum of Understanding, Depart. of Commerce and ICANN]. ICANN. Published 1999 December 31.</ref> It coordinates the Internet [[DNS]], [[IP]] addresses, and [[ASN|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.<ref>[https://www.icann.org/news/announcement-2016-10-01-en Stewardship of <abbr>IANA</abbr> Functions Transitions to Global Internet Community as Contract with U.S. Government Ends]. Retrieved 20 Nov 2017. </ref> Their 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 everyday across 240 countries.<ref>[http://www.icann.org/en/about/planning/strategic/strategic-plan-2010-2013-19feb10-en.pdf ICANN Strategic Plan June 2010 June 2013]. ICANN.</ref><ref>[https://blog.verisign.com/domain-names/verisign-domain-name-industry-brief-internet-grows-to-330-6-million-domain-names-in-q1-2017/ VERISIGN DOMAIN NAME INDUSTRY BRIEF: INTERNET GROWS TO 330.6 MILLION DOMAIN NAMES IN Q1 2017]. Retrieved 20 Nov 2017.</ref><ref>[https://system.opendns.com/ OpenDNS]. Retrieved 20 Nov 2017.</ref>
+
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.<ref>[https://www.icann.org/news/announcement-2016-10-01-en Stewardship of <abbr>IANA</abbr> Functions Transitions to Global Internet Community as Contract with U.S. Government Ends]. Retrieved 20 Nov 2017. </ref> 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.<ref>[http://www.icann.org/en/about/planning/strategic/strategic-plan-2010-2013-19feb10-en.pdf ICANN Strategic Plan June 2010 June 2013]. ICANN.</ref><ref>[https://blog.verisign.com/domain-names/verisign-domain-name-industry-brief-internet-grows-to-330-6-million-domain-names-in-q1-2017/ VERISIGN DOMAIN NAME INDUSTRY BRIEF: INTERNET GROWS TO 330.6 MILLION DOMAIN NAMES IN Q1 2017]. Retrieved 20 Nov 2017.</ref><ref>[https://system.opendns.com/ OpenDNS]. Retrieved 20 Nov 2017.</ref>
   −
ICANN collaborates with a variety of stakeholders including companies, individuals, and governments to ensure the continued success of the Internet. It holds [[ICANN Meetings|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.<ref name="meetings">[http://meetings.icann.org/about ICANN About Meetings]. ICANN.</ref>
+
ICANN collaborates with a variety of stakeholders including companies, individuals, and governments to ensure the continued success of the Internet. It holds [[ICANN Meetings|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.<ref name="meetings">[http://meetings.icann.org/about ICANN About Meetings]. ICANN.</ref>
    
==History: The Beginning==
 
==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 been managed by the Defense Advanced Research Projects Agency ([[DARPA]]), the National Science Foundation ([[NSF]]) and other U.S. research agencies.<ref>[http://www.ntia.doc.gov/ntiahome/domainname/022098fedreg.htm Improvement of Technical Management of Internet Names and Addresses; Proposed Rule]. National Telecommunications & Information Administration. Published 1998 February 20.</ref> The goal was to open the Internet to greater international participation, and to bolster it as a new medium of commercial competition and exchange.<ref name="icann-mou"></ref>
+
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.<ref>[http://www.ntia.doc.gov/ntiahome/domainname/022098fedreg.htm Improvement of Technical Management of Internet Names and Addresses; Proposed Rule]. National Telecommunications & Information Administration. Published 1998 February 20.</ref> The goals were to open the Internet to greater international participation and bolster it as a new medium of commercial competition and exchange.<ref name="icann-mou"></ref>
   −
On July 2nd, the [[DOC|Department of Commerce]] requested public input regarding [[DNS]] administration and structure, policy input regarding new registrars, the creation of new [[TLD]]s, and concerns regarding trademarks. More than 1,500 pages of comments were received.<ref>[http://www.ntia.doc.gov/ntiahome/domainname/6_5_98dns.htm Statement of Policy on the Management of Internet Names and Addresses]. National Telecommunications & Information Administration. Published 1998 June 5.</ref>
+
On July 2, the [[DOC|Department of Commerce]] requested public input regarding [[DNS]] administration and structure, policy input regarding new registrars, the creation of new [[TLD]]s, and concerns regarding trademarks. More than 1,500 pages of comments were received.<ref>[http://www.ntia.doc.gov/ntiahome/domainname/6_5_98dns.htm Statement of Policy on the Management of Internet Names and Addresses]. National Telecommunications & Information Administration. Published 1998 June 5.</ref>
   −
In January 1998, an agency of the [[DOC|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.<ref>[http://www.icann.org/en/general/white-paper-05jun98.htm ICANN White Paper]. ICANN.</ref> 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.<ref name="greenwhite">[http://www.icann.org/en/comments-mail/icann-current/msg00800.html The Green Paper vs. The White Paper]. ICANN. Published 1999 October 18.</ref> 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.<ref>[http://cyber.law.harvard.edu/rcs/principles.html How do the NTIA White Paper and the ICANN By-Laws Impact Membership?]. Harvard Law. Published 1999 January 19.</ref> 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.
+
In January 1998, an agency of the [[DOC|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.<ref>[http://www.icann.org/en/general/white-paper-05jun98.htm ICANN White Paper]. ICANN.</ref> 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.<ref name="greenwhite">[http://www.icann.org/en/comments-mail/icann-current/msg00800.html The Green Paper vs. The White Paper]. ICANN. Published 1999 October 18.</ref> 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.<ref>[http://cyber.law.harvard.edu/rcs/principles.html How do the NTIA White Paper and the ICANN By-Laws Impact Membership?]. Harvard Law. Published 1999 January 19.</ref> 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===
 
===The Memorandum of Understanding===
On November 25th, 1998, The U.S. [[DOC|Department of Commerce]] and ICANN entered into a Memorandum of Understanding ([[MoU]]),<ref name="icann-mou"></ref> which officially recognized ICANN as the entity that would:
+
On November 25, 1998, The U.S. [[DOC|Department of Commerce]] and ICANN entered into a Memorandum of Understanding ([[MoU]]),<ref name="icann-mou"></ref> which officially recognized ICANN as the entity that would:
    
# Establish policy for and direct the allocation of IP number blocks;  
 
# Establish policy for and direct the allocation of IP number blocks;  
Line 47: Line 47:  
Once again, these responsibilities would be undertaken and guided by the principles of stability, competition, private bottom-up coordination, and representation.<ref name="icann-mou"></ref> 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]].<ref name="congress">[http://commdocs.house.gov/committees/judiciary/hju63594.000/hju63594_0f.htm Congressional Hearing].Published 1999 July.</ref> The original agreement was set with an expiration of September 30th, 2000.<ref name="icann-mou"></ref> The [[MoU]] has been amended several times.
 
Once again, these responsibilities would be undertaken and guided by the principles of stability, competition, private bottom-up coordination, and representation.<ref name="icann-mou"></ref> 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]].<ref name="congress">[http://commdocs.house.gov/committees/judiciary/hju63594.000/hju63594_0f.htm Congressional Hearing].Published 1999 July.</ref> The original agreement was set with an expiration of September 30th, 2000.<ref name="icann-mou"></ref> The [[MoU]] has been amended several times.
   −
ICANN's bottom-up focus and its periodic structural reviews lead to revision of its [[ICANN Bylaws|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".<ref>[http://llr.lls.edu/volumes/v36-issue3/froomkin.pdf "ICANN 2.0 Meet the New Boss"]</ref>
+
ICANN's bottom-up focus and its periodic structural reviews lead to a revision of its [[ICANN Bylaws|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".<ref>[http://llr.lls.edu/volumes/v36-issue3/froomkin.pdf "ICANN 2.0 Meet the New Boss"]</ref>
    
====Registrar Accreditation Process====
 
====Registrar Accreditation Process====
Line 72: Line 72:  
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 [http://www.icann.org/en/tlds/application-process-03aug00.htm 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.
 
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 [http://www.icann.org/en/tlds/application-process-03aug00.htm 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, [[ICANN Board|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.<ref>[http://www.icann.org/en/announcements/advisory-31oct03.htm ICANN Board Resolutions in Carthage, Tunisia]. ICANN. Published 2003 October 31.</ref>
+
At the October 2003 meeting in Carthage, [[ICANN Board|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.<ref>[http://www.icann.org/en/announcements/advisory-31oct03.htm ICANN Board Resolutions in Carthage, Tunisia]. ICANN. Published 2003 October 31.</ref>
    
In 2003, important new [[sTLD]]s began being proposed. While these domains are different from [[gTLD]]s 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]].<ref>[http://www.icann.org/en/minutes/index-2005.html 2005 Board Meetings]</ref>; they all went on to approval in 2005-2006, except for the controversial [[.xxx]],<ref>[http://www.icann.org/en/tlds/stld-apps-19mar04/ Information Page for Sponsored Top-Level Domains]. ICANN.</ref> which went through a much more contentious and drawn out process but was still approved in March, 2011 at [[ICANN 40]].<ref>[http://www.icann.org/en/tlds/agreements/xxx/ .XXX Registry Agreement]. ICANN. Published 2011 March 31.</ref>
 
In 2003, important new [[sTLD]]s began being proposed. While these domains are different from [[gTLD]]s 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]].<ref>[http://www.icann.org/en/minutes/index-2005.html 2005 Board Meetings]</ref>; they all went on to approval in 2005-2006, except for the controversial [[.xxx]],<ref>[http://www.icann.org/en/tlds/stld-apps-19mar04/ Information Page for Sponsored Top-Level Domains]. ICANN.</ref> which went through a much more contentious and drawn out process but was still approved in March, 2011 at [[ICANN 40]].<ref>[http://www.icann.org/en/tlds/agreements/xxx/ .XXX Registry Agreement]. ICANN. Published 2011 March 31.</ref>
Line 79: Line 79:  
After the results of the 2000 and 2003 expansions of new gTLDs, a [[PDP|Policy Development Process]] in connection with the introduction of new gTLDs was developed by the [[Generic Names Supporting Organization]] (GNSO), which lasted from 2005 until 2007. During this Policy Development Process, the GNSO conducted extensive and detailed consultations with all constituencies within the ICANN global internet community. In 2008, 19 Specific Policy Recommendations were adopted by the ICANN Board for the implementation of new gTLDs, which describe the specifics of allocation and the contractual conditions. ICANN involved the global internet community in an open, inclusive and transparent implementation process to comment, review and provide their input toward creating the Applicant Guidebook for New gTLDs. The protection of intellectual property, community interests, consumer protection, and DNS stability were addressed during the process. Different versions and multiple drafts of the Applicant Guidebook were released in 2008. By June 2011, the ICANN Board launched the New gTLD Program, at the same time approving the [https://newgtlds.icann.org/en/applicants/agb New gTLD Applicant Guidebook].<ref>[http://newgtlds.icann.org/about/program About the New gTLD Program]. ICANN.</ref> 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.<ref>[http://domainincite.com/icann-confirms-possible-new-applicant-guidebook/ ICANN Confirms Possible New Applicant Guidebook]. Domain Incite. Published 2012 January 4.</ref>
 
After the results of the 2000 and 2003 expansions of new gTLDs, a [[PDP|Policy Development Process]] in connection with the introduction of new gTLDs was developed by the [[Generic Names Supporting Organization]] (GNSO), which lasted from 2005 until 2007. During this Policy Development Process, the GNSO conducted extensive and detailed consultations with all constituencies within the ICANN global internet community. In 2008, 19 Specific Policy Recommendations were adopted by the ICANN Board for the implementation of new gTLDs, which describe the specifics of allocation and the contractual conditions. ICANN involved the global internet community in an open, inclusive and transparent implementation process to comment, review and provide their input toward creating the Applicant Guidebook for New gTLDs. The protection of intellectual property, community interests, consumer protection, and DNS stability were addressed during the process. Different versions and multiple drafts of the Applicant Guidebook were released in 2008. By June 2011, the ICANN Board launched the New gTLD Program, at the same time approving the [https://newgtlds.icann.org/en/applicants/agb New gTLD Applicant Guidebook].<ref>[http://newgtlds.icann.org/about/program About the New gTLD Program]. ICANN.</ref> 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.<ref>[http://domainincite.com/icann-confirms-possible-new-applicant-guidebook/ ICANN Confirms Possible New Applicant Guidebook]. Domain Incite. Published 2012 January 4.</ref>
   −
In November, 2012, ICANN, [[Verisign]], and [[NTIA]], all confirmed that they were prepared with enough resources to begin launching 100 new gTLDs per week.<ref>[http://domainincite.com/10961-icann-verisign-and-ntia-ready-for-100-new-gtlds-per-week ICANN Verisign and NTIA ready for 100 new gTLDs per Week]. Domain Incite. Published 2012 November 8.</ref>
+
In November 2012, ICANN, [[Verisign]], and [[NTIA]] all confirmed that they were prepared with enough resources to begin launching 100 new gTLDs per week.<ref>[http://domainincite.com/10961-icann-verisign-and-ntia-ready-for-100-new-gtlds-per-week ICANN Verisign and NTIA ready for 100 new gTLDs per Week]. Domain Incite. Published 2012 November 8.</ref>
    
* [http://www.icann.org/en/about/financials/investment-policy-new-gtld Investment Policy re: New gTLDs, Adopted Dec. 2012]
 
* [http://www.icann.org/en/about/financials/investment-policy-new-gtld Investment Policy re: New gTLDs, Adopted Dec. 2012]
Line 87: Line 87:     
====Physical Expansion====
 
====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..<ref>[http://domainincite.com/as-new-gtlds-loom-icann-expands/ New gTLDs expand ICANN] Domain Incite. Published 2011 September 21.</ref> The Sydney office went on to be closed in 2012.
+
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..<ref>[http://domainincite.com/as-new-gtlds-loom-icann-expands/ New gTLDs expand ICANN] Domain Incite. Published 2011 September 21.</ref> 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.<ref>[http://nigel.je/2013/02/icann-la-to-be-broken-up-begging-letters-to-stop/ ICANN LA To be Broken Up Begging Letters to Stop, Nigel.je] Retrieved 25 Feb 2012</ref><ref>[http://domainincite.com/11967-icann-to-set-up-hubs-in-singapore-and-istanbul ICANN to Set up Hubs in Singapore and Istanbul, DomainIncite.com] Retrieved 25 Feb 2013</ref> 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.<ref>[http://www.zdnet.com/sg/icann-ceo-we-owe-asia-a-big-apology-7000011762/ ICANN CEO We Owe Asia a Big Apology, ZDnet.com] Retrieved 25 Feb 2013</ref>
+
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.<ref>[http://nigel.je/2013/02/icann-la-to-be-broken-up-begging-letters-to-stop/ ICANN LA To be Broken Up Begging Letters to Stop, Nigel.je] Retrieved 25 Feb 2012</ref><ref>[http://domainincite.com/11967-icann-to-set-up-hubs-in-singapore-and-istanbul ICANN to Set up Hubs in Singapore and Istanbul, DomainIncite.com] Retrieved 25 Feb 2013</ref> 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.<ref>[http://www.zdnet.com/sg/icann-ceo-we-owe-asia-a-big-apology-7000011762/ ICANN CEO We Owe Asia a Big Apology, ZDnet.com] Retrieved 25 Feb 2013</ref>
    
As of 2017, ICANN has offices in Los Angeles, Singapore, Montevideo, and Brussels. It has engagement centers in Geneva, Beijing, Nairobi, and Washington, DC.<ref>[https://forms.icann.org/en/contact ICANN Contact Page]. Retrieved 22 Nov 2017.</ref>
 
As of 2017, ICANN has offices in Los Angeles, Singapore, Montevideo, and Brussels. It has engagement centers in Geneva, Beijing, Nairobi, and Washington, DC.<ref>[https://forms.icann.org/en/contact ICANN Contact Page]. Retrieved 22 Nov 2017.</ref>
Line 101: Line 101:  
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. <ref>[http://www.ntia.doc.gov/press-release/2014/ntia-announces-intent-transition-key-internet-domain-name-functions NTIA announces intent to transition key domain name functions]</ref> ICANN issued a press release supporting this shift. <ref>[https://www.icann.org/resources/press-material/release-2014-03-14-en Press release, March 14 2014]</ref>
 
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. <ref>[http://www.ntia.doc.gov/press-release/2014/ntia-announces-intent-transition-key-internet-domain-name-functions NTIA announces intent to transition key domain name functions]</ref> ICANN issued a press release supporting this shift. <ref>[https://www.icann.org/resources/press-material/release-2014-03-14-en Press release, March 14 2014]</ref>
   −
ICANN created a co-ordination group from nominations among 13 community stakeholder groups, totaling 27 individuals, which produced a draft transition document. On December 2nd 2014, ICANN opened the public comment period on the draft transition document produced by the coordination group.<ref>[http://www.thedomains.com/2014/12/02/icann-opens-comment-period-for-its-move-out-of-us-control-deadline-is-december-22nd/ ICANN opens comment period for its move out of US control]</ref>
+
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.<ref>[http://www.thedomains.com/2014/12/02/icann-opens-comment-period-for-its-move-out-of-us-control-deadline-is-december-22nd/ ICANN opens comment period for its move out of US control]</ref>
    
====A New Approach to Africa====
 
====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 [[WG|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.<ref>[http://www.icann.org/en/news/announcements/announcement-10aug12-en.htm A New Approach to Africa]. ICANN. Published 2012 August 10.</ref> 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<ref>[http://domainincite.com/12181-chehade-commits-to-grow-the-number-of-domain-registrars-in-africa Chehade Commits to Grow The Number of Number of Domain Registrars in Africa, DomainIncite.com] Retrieved 8 Mar 2013</ref>
+
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 [[WG|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.<ref>[http://www.icann.org/en/news/announcements/announcement-10aug12-en.htm A New Approach to Africa]. ICANN. Published 2012 August 10.</ref> 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<ref>[http://domainincite.com/12181-chehade-commits-to-grow-the-number-of-domain-registrars-in-africa Chehade Commits to Grow The Number of Number of Domain Registrars in Africa, DomainIncite.com] Retrieved 8 Mar 2013</ref>
    
====UDRP====
 
====UDRP====
Line 117: Line 117:  
The same day, ICANN also issued the [http://www.icann.org/en/udrp/udrp-rules-29sept99.htm 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.<ref>[http://www.icann.org/en/udrp/udrp-rules-29sept99.htm Rules for Uniform Domain Name Dispute Resolution Policy]]. ICANN. Published 1999 September 29.</ref> Some of the public comments can be found [http://www.icann.org/en/comments-mail/comment-udrp/current/maillist.html here].
 
The same day, ICANN also issued the [http://www.icann.org/en/udrp/udrp-rules-29sept99.htm 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.<ref>[http://www.icann.org/en/udrp/udrp-rules-29sept99.htm Rules for Uniform Domain Name Dispute Resolution Policy]]. ICANN. Published 1999 September 29.</ref> Some of the public comments can be found [http://www.icann.org/en/comments-mail/comment-udrp/current/maillist.html here].
   −
ICANN adopted the [[UDRP]] at its November, 1999, meeting in Los Angeles.<ref>[http://cyber.law.harvard.edu/udrp/overview.html Overview of Domain Name Policy Development]. Harvard Law.</ref>
+
ICANN adopted the [[UDRP]] at its November 1999 meeting in Los Angeles.<ref>[http://cyber.law.harvard.edu/udrp/overview.html Overview of Domain Name Policy Development]. Harvard Law.</ref>
   −
==Organization & Structure==
+
====Review and Transparency Development====
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 [[Registry|registries]], to [[:Category:Companies|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 [[DOC| U.S. Department of Commerce]], and other structural and procedural rules.<ref>[http://sunburn.stanford.edu/~eroberts/courses/cs181/projects/the-domain-name-system/icannorg.html ICANN Organizational Structure]. Stanford University.</ref> 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.<ref>[http://www.washingtonpost.com/wp-dyn/content/article/2011/02/28/AR2011022803719.html?hpid=topnews Obama administration joins critics of U.S. nonprofit group that oversees Internet]. The Washington Post. Published 2011 March 1.</ref> ICANN's structure and process is outlined in the [[ICANN Bylaws]].
+
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,"<ref>[http://www.icann.org/en/general/lynn-reform-proposal-24feb02.htm President's Report: ICANN – The Case for Reform]. ICANN. Published 2002 February 24.</ref> which was credited with starting the dialogue on reform and leading to the creation of a formal committee.<ref name="bucharest">[http://www.icann.org/en/minutes/prelim-report-28jun02.htm#EvolutionandReform ICANN Meeting in Bucharest Preliminary Report]]. ICANN. Published 2002 June 28.</ref>
   −
===Board of Directors===
+
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 [http://www.icann.org/en/minutes/minutes-appa-31oct02.htm here]. The by-laws more clearly defined ICANN's mission and core values and improved apparatuses for review and greater transparency. The [[Reconsideration Committee]], [[IRP|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.<ref>[http://www.icann.org/en/minutes/minutes-appa-31oct02.htm Appendix A to Minutes ICANN Board Meeting in Shanghai]. ICANN. Published 2002 October 31.</ref>
: ''Main article: [[ICANN Board]]
  −
ICANN is governed by a [[ICANN Board|Board of Directors]] made up of 15 voting members,<ref>[http://www.icann.org/en/reviews/board/ Board Review]. ICANN.</ref> and the President and CEO, who is also a voting member. The board is further aided by five non-voting liaisons.<ref name="bylaws">[http://www.icann.org/en/general/bylaws.htm ICANN Bylaws]. ICANN.</ref> 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.<ref name="dotnxt">[http://news.dot-nxt.com/2011/12/13/icann-board-dec-minutes ICANN Board awards itself $35,000, developing countries $138,000, and adds to confusion with secondary timestamp]. dotnxt. Published 2011 December 13.</ref>
     −
====Current Board of Directors====
+
==ICANN Organizational Issues==
The 19 current directors and the current CEO, are listed below, along with the organization which nominated them and the length of their term:<ref>[http://www.icann.org/en/general/board.html Board of Directors].</ref>
+
:''See [[ICANN Bodies]] for a list of the key players in ICANN's [[Multistakeholder Model]].''
* [[Göran Marby]], '''President and CEO'''
  −
* [[Maarten Botterman]] ('''Chair'''), selected by the [[NomCom]], December 2016 - [[Annual Meeting|AGM]] 2022
  −
* [[León Sánchez]], ('''Vice-Chair)''' selected by the [[ALAC]], June 2017 - [[Annual Meeting|AGM]] 2023
  −
* [[Becky Burr]], selected by the [[GNSO]], November 2016 – [[Annual Meeting|AGM]] 2022
  −
* [[Ron da Silva]], selected by the [[ASO]], October 2015 - [[Annual Meeting|AGM]] 2021
  −
* [[Sarah Deutsch]], selected by [[NomCom]], November 2017 – AGM 2023
  −
* [[Avri Doria]], selected by [[NomCom]], November 2017 – AGM 2023
  −
* [[Lito Ibarra|Rafael Lito Ibarra]], selected by the [[NomCom]], Oct. 2015 - [[Annual Meeting|AGM]] 2021
  −
* [[Akinori Maemura]], selected by the [[ASO]], November 2016 - [[Annual Meeting|AGM]] 2022
  −
* [[Matthew Shears]], selected by [[Generic Names Supporting Organization|GNSO]], November 2017 – AGM 2020
  −
* [[Danko Jevtovic]], selected by [[NomCom]], October 2018 - [[AGM]] 2021
  −
* [[Mandla Msimang]], selected by [[NomCom]], November 2019 - [[AGM]] 2022
     −
====Current Non-Voting Liaisons====
+
It is central to ICANN's mission that the organization is structured in a way that welcomes a variety of voices and seeks to represent diverse constituencies with continued interest in the Internet's development, from [[Registry|registries]], to [[:Category:Companies|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 [[DOC|U.S. Department of Commerce]], and other structural and procedural rules.<ref>[http://sunburn.stanford.edu/~eroberts/courses/cs181/projects/the-domain-name-system/icannorg.html ICANN Organizational Structure]. Stanford University.</ref> 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.<ref>[http://www.washingtonpost.com/wp-dyn/content/article/2011/02/28/AR2011022803719.html?hpid=topnews Obama administration joins critics of U.S. nonprofit group that oversees Internet]. The Washington Post. Published 2011 March 1.</ref> ICANN's structure and process are outlined in the [[ICANN Bylaws]].
* [[Kaveh Ranjbar]], [[RSSAC]] liaison
+
 
* [[Merike Käo]], [[SSAC]] liaison
+
===Board of Directors===
* [[Harald Alvestrand]], [[IETF]] liaison
+
: ''Main article: [[ICANN Board]]''
* [[Manal Ismail]], [[GAC]] liaison
+
ICANN is governed by a [[ICANN Board|Board of Directors]] made up of 16 voting members (including ICANN's CEO) and four non-voting liaisons.<ref name="bylaws">[http://www.icann.org/en/general/bylaws.htm ICANN Bylaws]. ICANN.</ref> 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.<ref name="dotnxt">[http://news.dot-nxt.com/2011/12/13/icann-board-dec-minutes ICANN Board awards itself $35,000, developing countries $138,000, and adds to confusion with secondary timestamp]. dotnxt. Published 2011 December 13.</ref>
    
===Ombudsman===
 
===Ombudsman===
 
: ''Main article: [[Ombudsman]]''
 
: ''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]].
+
The [[Ombudsman]] is required to offer independent, impartial, and neutral informal dispute resolution for those who want to lodge a complaint about ICANN staff, board, or supporting organizations. The independence of this office has been called into question, as the person in this role is hired and fired by the ICANN Board and reports to the ICANN Chair. The length of tenure has also been debated.
    
===GNSO===
 
===GNSO===
 
: ''Main article: [[GNSO]]''
 
: ''Main article: [[GNSO]]''
 
+
The [[Generic Names Supporting Organization]] (GNSO) brings together representatives of constituencies concerning [[gTLD]]s.<ref>[http://gnso.icann.org/ Generic Names Supporting Organization]</ref> As such, it has received criticism on its policy development process. Namely, [[Working Group]] dynamics and how the GNSO determines that it has reached [[consensus]] have proved particularly problematic.
The [[Generic Names Supporting Organization]] (GNSO) brings together smaller stakeholder groups, which in turn bring together constituencies and other groups,  together into one [[SO|Supporting Organization]] to develop policies, form consensus, and make recommendations related to [[gTLD]]s to the [[ICANN Board]].<ref>[http://gnso.icann.org/ Generic Names Supporting Organization]. ICANN.</ref>
      
===ccNSO===
 
===ccNSO===
 
: ''Main article: [[ccNSO]]''
 
: ''Main article: [[ccNSO]]''
 
+
The [[Country Code Names Supporting Organization]] (ccNSO) was created by and for [[ccTLD]] managers, which are the entities that oversee a given nation's own Country Code Top Level Domain.<ref>[http://ccnso.icann.org/about About].</ref> The main issues it faces are a shortage of candidates and a lack of transparency and accountability in its [[PDP]].
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.<ref>[http://ccnso.icann.org/about About]. Country Code Names Supporting Organisation.</ref>
      
===ASO===
 
===ASO===
 
: ''Main article: [[ASO]]''
 
: ''Main article: [[ASO]]''
 
+
The [[Address Supporting Organization]] (ASO) reviews and develop [[IP|Internet Protocol]] recommendations.<ref>[http://aso.icann.org/ The Address Supporting Organization]</ref> It has been criticized for lacking a single, authoritative description of the process for global numbering policies and a lack of transparency on the difference between the roles of the [[ASO]] and the [[NRO]], which is a non-ICANN body that strongly overlaps with the 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 [[IP|Internet Protocol]] recommendations, address policy, and advise the [[ICANN Board]].<ref>[http://aso.icann.org/ The Address Supporting Organization]. ICANN.</ref> Its members are appointed by the world's 5 [[RIR|Regional Internet Registries]] (RIRs), which manage and allocate IP addresses in their respective continental regions.<ref>[http://www.apnic.net/about-APNIC About APNIC]. APNIC.</ref><ref>[http://aso.icann.org/people/address-council/address-council-members/ Adress Council Members]. ASO.</ref>
      
===GAC===
 
===GAC===
 
: ''Main article: [[GAC]]
 
: ''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.
+
The GAC advises the ICANN Board on how governments will react to potential policies. The GAC has come under fire for seemingly allow the governments they represent a veto power over ICANN decisions.<ref>[https://cdt.org/insights/icann-must-follow-its-own-rules/ ICANN Must follow its own rules. CDT]</ref>
    
===ALAC===
 
===ALAC===
 
: ''Main article: [[ALAC]]
 
: ''Main article: [[ALAC]]
The At-Large Advisory Committee (ALAC) is one of [[ICANN]]'s [[AC|Advisory Committees]]. The mission of ALAC is to function as an advocate for the interests of individual Internet users.
+
The At-Large Advisory Committee (ALAC) advocates for the interests of individual Internet users. ALAC was recently criticized for spending too much time on process and administrative issues, too little on policy advice, which was also considered of low quality. ALAC is also struggling with an uneven distribution of power.<ref>[https://www.icann.org/en/system/files/files/atlarge-review-final-02may17-en.pdf 2017 At-Large Review]</ref>
   −
===Other Committees===
+
===SSAC===
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 [[SSAC|Security and Stability Advisory Committee]]. Both of these committees were given official recognition in 2002.<ref name="accra">[http://www.icann.org/en/minutes/prelim-report-14mar02.htm#EvolutionandReformCommittee ICANN Meeting in Accra Preliminary Report]. ICANN. Published 2002 March 14.</ref> The push for reform was also significantly aided by [[Stuart Lynn]]'s "President's report: The Case for Reform,"<ref>[http://www.icann.org/en/general/lynn-reform-proposal-24feb02.htm President's Report: ICANN – The Case for Reform]. ICANN. Published 2002 February 24.</ref> which they credited for starting the dialogue on reform and leading to the creation of the more formal committee.<ref name="bucharest">[http://www.icann.org/en/minutes/prelim-report-28jun02.htm#EvolutionandReform ICANN Meeting in Bucharest Preliminary Report]]. ICANN. Published 2002 June 28.</ref>
+
:''Main article: [[SSAC]]''
 +
SSAC was originally intended to expand and specialize the role of ICANN, and it received official recognition in 2002.<ref name="accra">[http://www.icann.org/en/minutes/prelim-report-14mar02.htm#EvolutionandReformCommittee ICANN Meeting in Accra Preliminary Report]. ICANN. Published 2002 March 14.</ref> SSAC as a body and its individual members have been criticized for their lack of communication and engagement with other ICANN bodies.<ref>[https://www.icann.org/en/system/files/files/ssac-review-final-17dec18-en.pdf 2018 SSAC Review]</ref>
   −
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 [http://www.icann.org/en/minutes/minutes-appa-31oct02.htm 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]], [[IRP|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.<ref>[http://www.icann.org/en/minutes/minutes-appa-31oct02.htm Appendix A to Minutes ICANN Board Meeting in Shanghai]. ICANN. Published 2002 October 31.</ref>
+
===RSSAC===
 +
:''Main article: [[RSSAC]]''
 +
RSSAC advises ICANN on the operation, administration, security, and integrity of the Internet's Root Server System. It has come under fire for offering minimal, reactionary input rather than offering regular updates and being distrustful of non-RSO stakeholders.<ref>[https://www.icann.org/en/system/files/files/rssac-review-final-02jul18-en.pdf 2018 RSSAC Review]</ref>
    
==Process==
 
==Process==
 +
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===
 +
: ''Main article: [[PDP|ICANN Policy Development]]''
 +
DNS Policies are developed through formal policy development processes (PDPs), as set forth by the Bylaws.
 +
 +
===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 PDPs and tend to depend on community input through less formal means.
 +
 
===Meetings===
 
===Meetings===
 
: ''Main article: [[ICANN Meetings]]''
 
: ''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.<ref name="meetings"></ref> The next meeting will be the 61st meeting in San Juan, Puerto Rico. <ref>[http://blog.icann.org/2011/02/middle-east-developments-interfere-with-icann-41-jordan-meeting/ Middle East Developments Cause Cancellation of ICANN Jordan Meeting]. ICANN Blog. Published 2011 February 18.</ref> Meetings are designated as A, B, C and each meeting has a varying length and purpose.
+
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.<ref name="meetings"></ref> The next meeting will be the 61st meeting in San Juan, Puerto Rico.<ref>[http://blog.icann.org/2011/02/middle-east-developments-interfere-with-icann-41-jordan-meeting/ Middle East Developments Cause Cancellation of ICANN Jordan Meeting]. ICANN Blog. Published 2011 February 18.</ref> Meetings are designated as A, B, C, and each meeting has a varying length and purpose.
===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 [[IRP|Independent Review Panel]], which has the power to call attention to discrepancies between the [[ICANN Bylaws|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.<ref name="bylaws"></ref>
+
===Accountability===
 +
: ''Main article: [[ICANN Accountability]]''
 +
 
 +
===Reviews===
 +
: ''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 [[IRP|Independent Review Panel]], which has the power to call attention to discrepancies between the [[ICANN Bylaws|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.<ref name="bylaws"></ref>
    
==Conflicts of Interest==
 
==Conflicts of Interest==
Line 216: Line 217:  
[[Category: Organizations]]
 
[[Category: Organizations]]
 
[[Category: Sponsor]]
 
[[Category: Sponsor]]
[[Category:Articles with Chinese]]
  −
[[Category: Articles with Spanish]]
 
Bureaucrats, Check users, lookupuser, Administrators, translator
4,076

edits

Navigation menu