CINXE.COM

<!DOCTYPE html> <html lang="en" dir="ltr" prefix="content: http://purl.org/rss/1.0/modules/content/ dc: http://purl.org/dc/terms/ foaf: http://xmlns.com/foaf/0.1/ og: http://ogp.me/ns# rdfs: http://www.w3.org/2000/01/rdf-schema# schema: http://schema.org/ sioc: http://rdfs.org/sioc/ns# sioct: http://rdfs.org/sioc/types# skos: http://www.w3.org/2004/02/skos/core# xsd: http://www.w3.org/2001/XMLSchema# " class="no-js adaptivetheme"> <head> <meta charset="utf-8" /> <script>var _paq = _paq || [];(function(){var u=(("https:" == document.location.protocol) ? "https://matomo.apc.org/" : "http://matomo.apc.org/");_paq.push(["setSiteId", "1"]);_paq.push(["setTrackerUrl", u+"matomo.php"]);_paq.push(["setDoNotTrack", 1]);_paq.push(["disableCookies"]);if (!window.matomo_search_results_active) {_paq.push(["trackPageView"]);}_paq.push(["setIgnoreClasses", ["no-tracking","colorbox"]]);_paq.push(["enableLinkTracking"]);var d=document,g=d.createElement("script"),s=d.getElementsByTagName("script")[0];g.type="text/javascript";g.defer=true;g.async=true;g.src=u+"matomo.js";s.parentNode.insertBefore(g,s);})();</script> <meta name="Generator" content="Drupal 9 (https://www.drupal.org)" /> <meta name="MobileOptimized" content="width" /> <meta name="HandheldFriendly" content="true" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <link rel="icon" href="/themes/giswatch/favicon.ico" type="image/vnd.microsoft.icon" /> <link rel="alternate" hreflang="en" href="https://www.giswatch.org/institutional-overview/civil-society-participation/internet-corporation-assigned-names-and-numbers-i" /> <link rel="canonical" href="https://www.giswatch.org/institutional-overview/civil-society-participation/internet-corporation-assigned-names-and-numbers-i" /> <link rel="shortlink" href="https://www.giswatch.org/node/271" /> <link rel="dns-prefetch" href="//cdnjs.cloudflare.com"><title>Internet Corporation for Assigned Names and Numbers (ICANN) | Global Information Society Watch</title> <link rel="stylesheet" media="all" href="/sites/default/files/css/css_l1kfOkMfFMl1DxMxy-1xjW7fQBwj3KH4vQrFNmasBPY.css" /> <link rel="stylesheet" media="all" href="/sites/default/files/css/css_uHz9qKwGEkDPe8qqN1UnAiZ8o4HIjfT6furYAzhqVzU.css" /> <script src="/core/assets/vendor/modernizr/modernizr.min.js?v=3.11.7"></script> <script src="/core/misc/modernizr-additional-tests.js?v=3.11.7"></script> </head><body class="layout-type--page-layout user-logged-out path-not-frontpage path-node path-institutional-overview-2007-focus-participation-internet-corporation-assigned-names-and-numbers-ican page-node-type--institutional-overview theme-name--giswatch"> <a href="#block-giswatch-content" class="visually-hidden focusable skip-link">Skip to main content</a> <div class="dialog-off-canvas-main-canvas" data-off-canvas-main-canvas> <div class="page js-layout"> <div data-at-row="leaderboard" class="l-leaderboard l-row"> <div class="l-pr page__row pr-leaderboard" id="leaderboard"> <div class="l-rw regions container pr-leaderboard__rw arc--1 hr--1" data-at-regions=""> <div data-at-region="1" data-at-block-count="1" class="l-r region pr-leaderboard__leaderboard" id="rid-leaderboard"><div class="language-switcher-language-url l-bl block block-config-provider--language block-plugin-id--language-block-language-interface" id="block-languageswitcher-2"> <div class="block__inner"> <div class="block__content"><ul class="links"><li hreflang="en" data-drupal-link-system-path="node/271" class="en is-active"><span class="en__link-wrapper"><a href="/institutional-overview/civil-society-participation/internet-corporation-assigned-names-and-numbers-i" class="en__link is-active" hreflang="en" data-drupal-link-system-path="node/271">English</a></span></li><li hreflang="ar" data-drupal-link-system-path="node/271" class="ar"><span class="ar__link-wrapper"><a href="/ar/node/271" class="ar__link" hreflang="ar" data-drupal-link-system-path="node/271">Arabic</a></span></li><li hreflang="bs" data-drupal-link-system-path="node/271" class="bs"><span class="bs__link-wrapper"><a href="/bcsm/node/271" class="bs__link" hreflang="bs" data-drupal-link-system-path="node/271">Bos/Cro/Ser/Mne</a></span></li><li hreflang="bg" data-drupal-link-system-path="node/271" class="bg"><span class="bg__link-wrapper"><a href="/bg/node/271" class="bg__link" hreflang="bg" data-drupal-link-system-path="node/271">Bulgarian</a></span></li><li hreflang="ca" data-drupal-link-system-path="node/271" class="ca"><span class="ca__link-wrapper"><a href="/ca/node/271" class="ca__link" hreflang="ca" data-drupal-link-system-path="node/271">Catalan</a></span></li><li hreflang="fr" data-drupal-link-system-path="node/271" class="fr"><span class="fr__link-wrapper"><a href="/fr/node/271" class="fr__link" hreflang="fr" data-drupal-link-system-path="node/271">French</a></span></li><li hreflang="hi" data-drupal-link-system-path="node/271" class="hi"><span class="hi__link-wrapper"><a href="/hi/node/271" class="hi__link" hreflang="hi" data-drupal-link-system-path="node/271">Hindi</a></span></li><li hreflang="hu" data-drupal-link-system-path="node/271" class="hu"><span class="hu__link-wrapper"><a href="/hu/node/271" class="hu__link" hreflang="hu" data-drupal-link-system-path="node/271">Hungarian</a></span></li><li hreflang="ja" data-drupal-link-system-path="node/271" class="ja"><span class="ja__link-wrapper"><a href="/ja/node/271" class="ja__link" hreflang="ja" data-drupal-link-system-path="node/271">Japanese</a></span></li><li hreflang="pt-br" data-drupal-link-system-path="node/271" class="pt-br"><span class="pt-br__link-wrapper"><a href="/pt-br/node/271" class="pt-br__link" hreflang="pt-br" data-drupal-link-system-path="node/271">Portuguese, Brazil</a></span></li><li hreflang="ro" data-drupal-link-system-path="node/271" class="ro"><span class="ro__link-wrapper"><a href="/ro/node/271" class="ro__link" hreflang="ro" data-drupal-link-system-path="node/271">Romanian</a></span></li><li hreflang="ru" data-drupal-link-system-path="node/271" class="ru"><span class="ru__link-wrapper"><a href="/ru/node/271" class="ru__link" hreflang="ru" data-drupal-link-system-path="node/271">Russian</a></span></li><li hreflang="es" data-drupal-link-system-path="node/271" class="es"><span class="es__link-wrapper"><a href="/es/node/271" class="es__link" hreflang="es" data-drupal-link-system-path="node/271">Spanish</a></span></li><li hreflang="tl" data-drupal-link-system-path="node/271" class="tl"><span class="tl__link-wrapper"><a href="/tl/node/271" class="tl__link" hreflang="tl" data-drupal-link-system-path="node/271">Tagalog</a></span></li></ul></div></div> </div> <div class="search-block-form l-bl block block-search block-config-provider--search block-plugin-id--search-form-block" data-drupal-selector="search-block-form" id="block-giswatch-search" role="search" aria-labelledby="block-giswatch-search-menu"> <div class="block__inner block-search__inner"> <h2 class="visually-hidden block__title block-search__title" id="block-giswatch-search-menu"><span>Search</span></h2> <div class="block__content block-search__content"><form action="/search/node" method="get" id="search-block-form" accept-charset="UTF-8" class="search-block-form__form"> <div class="js-form-item form-item js-form-type-search form-type-search js-form-item-keys form-item-keys form-no-label"> <label for="edit-keys" class="visually-hidden">Search</label> <input title="Enter the terms you wish to search for." data-drupal-selector="edit-keys" type="search" id="edit-keys" name="keys" value="" size="" maxlength="128" class="form-search" /> </div> <div data-drupal-selector="edit-actions" class="form-actions element-container-wrapper js-form-wrapper form-wrapper" id="edit-actions"><input class="search-form__submit button js-form-submit form-submit" data-drupal-selector="edit-submit" type="submit" id="edit-submit" value="Search" /> </div> </form> </div></div> </div> </div> </div> </div> </div> <div data-at-row="header" class="l-header l-row"> <header class="l-pr page__row pr-header" role="banner" id="masthead"> <div class="l-rw regions container pr-header__rw arc--1 hr--1" data-at-regions=""> <div data-at-region="1" class="l-r region pr-header__header-first" id="rid-header-first"><div id="block-mission" class="l-bl block block-config-provider--block-content block-plugin-id--block-content-1451593a-eac7-48ec-8436-8a956283978f has-title block--type-basic block--view-mode-full" role="region" aria-labelledby="block-mission-title"> <div class="block__inner"> <h2 class="block__title" id="block-mission-title"><span>Global Information Society Watch</span></h2><div class="block__content"><div class="clearfix text-formatted field field-block-content--body field-formatter-text-default field-name-body field-type-text-with-summary field-label-hidden has-single"><div class="field__items"><div class="field__item"><div id="mission">Global Information Society Watch (GISWatch) is a collaborative community committed to building an open, inclusive and sustainable information society.<br /><span id="download-report"><a href="/the-reports">Download reports</a></span></div> </div></div> </div> </div></div> </div> </div> </div> </header> </div> <div data-at-row="navbar" class="l-navbar l-row"> <div class="l-pr page__row pr-navbar" id="navbar"> <div class="l-rw regions container pr-navbar__rw arc--1 hr--1" data-at-regions=""> <div data-at-region="1" class="l-r region pr-navbar__navbar" id="rid-navbar"><svg style="display:none;"> <symbol id="rm-toggle__icon--open" viewBox="0 0 1792 1792" preserveAspectRatio="xMinYMid meet"> <path class="rm-toggle__icon__path" d="M1664 1344v128q0 26-19 45t-45 19h-1408q-26 0-45-19t-19-45v-128q0-26 19-45t45-19h1408q26 0 45 19t19 45zm0-512v128q0 26-19 45t-45 19h-1408q-26 0-45-19t-19-45v-128q0-26 19-45t45-19h1408q26 0 45 19t19 45zm0-512v128q0 26-19 45t-45 19h-1408q-26 0-45-19t-19-45v-128q0-26 19-45t45-19h1408q26 0 45 19t19 45z"/> </symbol> <symbol id="rm-toggle__icon--close" viewBox="0 0 1792 1792" preserveAspectRatio="xMinYMid meet"> <path class="rm-toggle__icon__path" d="M1490 1322q0 40-28 68l-136 136q-28 28-68 28t-68-28l-294-294-294 294q-28 28-68 28t-68-28l-136-136q-28-28-28-68t28-68l294-294-294-294q-28-28-28-68t28-68l136-136q28-28 68-28t68 28l294 294 294-294q28-28 68-28t68 28l136 136q28 28 28 68t-28 68l-294 294 294 294q28 28 28 68z"/> </symbol> </svg> <nav aria-labelledby="block-giswatch-main-menu-menu" id="block-giswatch-main-menu" class="l-bl rm-block rm-config-provider--system rm-plugin-id--system-menu-block-main js-hide"> <div class="rm-block__inner"> <div class="rm-toggle"> <button class="rm-toggle__link un-button" role='button' aria-expanded="false"> <svg class="rm-toggle__icon"> <use id="rm-toggle__icon--use" xlink:href="#rm-toggle__icon--open"></use> </svg> <span class="rm-toggle__label" id="block-giswatch-main-menu-menu">Main menu</span> </button> </div><div class="rm-block__content" id="rm-content"> <span id="rm-accordion-trigger" class="hidden"> <button class="rm-accordion-trigger un-button" role='button' aria-expanded="false"> <svg class="rm-accordion-trigger__icon" viewBox="0 0 1792 1792" preserveAspectRatio="xMinYMid meet"><path d="M1600 736v192q0 40-28 68t-68 28h-416v416q0 40-28 68t-68 28h-192q-40 0-68-28t-28-68v-416h-416q-40 0-68-28t-28-68v-192q0-40 28-68t68-28h416v-416q0-40 28-68t68-28h192q40 0 68 28t28 68v416h416q40 0 68 28t28 68z"/></svg> <span class="visually-hidden">Toggle sub-menu</span> </button> </span> <ul class="menu odd menu-level-1 menu-name--main"> <li class="menu__item menu__item-title--home" id="menu-name--main__home"> <span class="menu__link--wrapper"> <a href="/" title="" class="menu__link" data-drupal-link-system-path="<front>">HOME</a> </span> </li> <li class="menu__item menu__item-title--about" id="menu-name--main__about"> <span class="menu__link--wrapper"> <a href="/about" class="menu__link" data-drupal-link-system-path="node/4">ABOUT</a> </span> </li> <li class="menu__item menu__item-title--news" id="menu-name--main__news"> <span class="menu__link--wrapper"> <a href="/press" class="menu__link" data-drupal-link-system-path="press">NEWS</a> </span> </li> <li class="menu__item menu__item-title--whos-watching" id="menu-name--main__whos-watching"> <span class="menu__link--wrapper"> <a href="/author-list" class="menu__link" data-drupal-link-system-path="author-list">WHO'S WATCHING?</a> </span> </li> <li class="menu__item menu__item-title--contact" id="menu-name--main__contact"> <span class="menu__link--wrapper"> <a href="/contact" class="menu__link" data-drupal-link-system-path="contact">CONTACT</a> </span> </li> <li class="menu__item menu__item-title--login" id="menu-name--main__login"> <span class="menu__link--wrapper"> <a href="/user/login" class="menu__link" data-drupal-link-system-path="user/login">LOGIN</a> </span> </li> <li class="menu__item menu__item-title--twitter" id="menu-name--main__twitter"> <span class="menu__link--wrapper"> <a href="https://twitter.com/apc_news" title="" class="menu__link">Twitter</a> </span> </li> <li class="menu__item menu__item-title--facebook" id="menu-name--main__facebook"> <span class="menu__link--wrapper"> <a href="https://www.facebook.com/apcnews" title="" class="menu__link">Facebook</a> </span> </li></ul> </div></div> </nav> </div> </div> </div> </div> <div data-at-row="main" class="l-main l-row"> <div class="l-pr page__row pr-main" id="main-content"> <div class="l-rw regions container pr-main__rw arc--1 hr--1" data-at-regions=""> <div data-at-region="1" data-at-block-count="3" class="l-r region pr-main__content" id="rid-content"><div data-drupal-messages-fallback class="hidden"></div><main id="block-giswatch-content" class="l-bl block block-main-content" role="main"> <article data-history-node-id="271" role="article" about="/institutional-overview/civil-society-participation/internet-corporation-assigned-names-and-numbers-i" class="node node--id-271 node--type-institutional-overview node--promoted node--view-mode-full"> <div class="node__container"> <header class="node__header"><h1 class="node__title"><span class="field field-name-title field-formatter-string field-type-string field-label-hidden">Internet Corporation for Assigned Names and Numbers (ICANN)</span> </h1></header> <div class="node__content"><div class="field field-node-taxonomy-vocabulary-4 field-entity-reference-type-taxonomy-term field-formatter-entity-reference-label field-name-taxonomy-vocabulary-4 field-type-entity-reference field-label-hidden"><div class="field__items"><div class="field__item field__item--_007---focus-on-participation"> <span class="field__item-wrapper"><a href="/year/2007-focus-participation" hreflang="en">2007 - Focus on Participation</a></span> </div></div> </div> <div class="field field-node--upload field-formatter-file-table field-name-upload field-type-file field-label-hidden has-single"><div class="field__items"><div class="field__item"><table data-striping="1" class="table cols-2"> <thead class="table__header"> <tr class="table__row"> <th class="table__cell table__header__cell">Attachment</th> <th class="table__cell table__header__cell">Size</th> </tr> </thead> <tbody class="table__body"> <tr class="table__row odd"> <td class="table__cell table__body__cell"><span class="file file--mime-application-pdf file--application-pdf"> <a href="/sites/default/files/gisw_icann_0.pdf" type="application/pdf" title="gisw_icann_0.pdf">gisw_icann_0.pdf</a></span> </td> <td class="table__cell table__body__cell">5.89 MB</td> </tr> </tbody> </table> </div></div> </div> <div class="field field-node-field-authors field-entity-reference-type-user field-formatter-entity-reference-label field-name-field-authors field-type-entity-reference field-label-inline clearfix"><h3 class="field__label">Authors</h3><div class="field__items"><div class="field__item field__item--jeanette-hofmann"> <span class="field__item-wrapper"><a href="/users/jhofmann" hreflang="en">Jeanette Hofmann</a></span> </div></div> </div> <div class="clearfix text-formatted field field-node--body field-formatter-text-default field-name-body field-type-text-with-summary field-label-hidden has-single"><div class="field__items"><div class="field__item"><h2>1. Introduction</h2> <h3>1.1 Objectives and main activities</h3> <p>ICANN is responsible, at the overall level, for the administration of three sets of unique identifier systems for the internet: domain names, numerical internet protocol (IP) addresses, and a third type that serves to identify so-called port and parameter numbers.</p> <p>The administration of the generic part of the domain name system (DNS) <sup><a name="_ftnref1" href="http://www.giswatch.org/gisw2007/node/3438#_ftn1" id="_ftnref1">[1]</a></sup> forms the core of ICANN's activities. Country code top-level domains (ccTLDs) are predominantly managed at the national level, while policies for the allocation of IP addresses are autonomously devised by the regional internet registries (RIRs). <sup><a name="_ftnref2" href="http://www.giswatch.org/gisw2007/node/3438#_ftn2" id="_ftnref2">[2]</a></sup></p> <p>At the time of ICANN's inception, the administration of the DNS was regarded as primarily technical. More recently, however, ICANN is seen as a regulatory body whose policies shape the market for the registration of domain names and set the conditions for creating new top-level domains (TLDs). <sup><a name="_ftnref3" href="http://www.giswatch.org/gisw2007/node/3438#_ftn3" id="_ftnref3">[3]</a></sup> Although technical and regulatory tasks may overlap, regulatory bodies require a different type of policy process and membership than do technical organisations.</p> <h3>1.2 Legal/constitutional composition</h3> <p>ICANN was founded in 1998 as a California-based not-for-profit corporation. Its mandate derives from two short-term contracts with the United States (US) government. The Internet Assigned Numbers Authority (IANA) <sup><a name="_ftnref4" href="http://www.giswatch.org/gisw2007/node/3438#_ftn4" id="_ftnref4">[4]</a></sup> oversees the global allocation of IP addresses, the root zone management of the DNS, and the assignment of technical protocol parameters used in various internet protocols; IANA can be likened to a global administrator of internet protocols. It is operated by ICANN under a contract with the US government, the "IANA contract" (NTIA, 2006). The other contract between the US government and ICANN is a memorandum of understanding (MoU) (NTIA, 1998) that specifies tasks for ICANN to accomplish as a precondition for the privatisation of internet names and numbers administration. Privatisation in this context means the transition of currently public responsibilities to a private, not-for-profit entity. Since 1997, the US government has claimed supervision authority over the management of the DNS and IP address allocation. At present it is unclear when and what part of its regulatory authority the US government intends to privatise.</p> <p>ICANN implements regulatory policies through contracts with the "rule takers", i.e. businesses providing services related to internet names or number spaces. While all registries for generic TLDs (gTLDs) and all large registrars have signed contracts, other organisations have been more hesitant. Independent actors such as the RIRs and root server <sup><a name="_ftnref5" href="http://www.giswatch.org/gisw2007/node/3438#_ftn5" id="_ftnref5">[5]</a></sup> operators, as well as many ccTLD registries, reject the idea of delegating regional authority to a central entity which is ultimately subject to California law and the authority of the US government. The root server operators, in particular, have so far refused to enter contractual agreements with ICANN. Others such as the RIRs were able to negotiate a memorandum of understanding that preserves substantial policy responsibility with the Number Resource Organisation (NRO), <sup><a name="_ftnref6" href="http://www.giswatch.org/gisw2007/node/3438#_ftn6" id="_ftnref6">[6]</a></sup> the organisation that represents the internet addressing community. <sup><a name="_ftnref7" href="http://www.giswatch.org/gisw2007/node/3438#_ftn7" id="_ftnref7">[7]</a></sup></p> <h3>1.3 Key members/participants and decision-making structures</h3> <p>The MoU between the US government and ICANN mandates a bottom-up policy process that involves all stakeholders in the management of the DNS and IP addresses, including users. Reflecting the widespread anti-state spirit on the net during the 1990s, which was even shared by parts of the Clinton administration (1993-2001), the public interest was to be represented by individual users. Governments – with the significant exception of the US government – would be involved only in an advisory capacity. Accordingly, ICANN's original bylaws stipulated that nearly half of the seats on the Board of Directors would be filled through a process to represent individual users. The other half would represent the emerging service industry surrounding the DNS and IP address allocation. Supporting organisations consisting of various stakeholder groups would be responsible for policy development. Individual users would form an At-Large Membership.</p> <p>In the course of an organisational reform in 2002, ICANN suspended the model of a balanced representation of the private sector and civil society. Individual users' representation on the Board is now reduced to a single non-voting liaison. The following chart describes the structure of ICANN and how the various entities are represented on the Board of Directors. The Board consists of fifteen voting members, eight of which are chosen by a Nominating Committee and six by the supporting organisations. The number of non-voting liaison members can vary. <sup><a name="_ftnref8" href="http://www.giswatch.org/gisw2007/node/3438#_ftn8" id="_ftnref8">[8]</a></sup></p> <h3>1.4 Relations with other international institutions and the multilateral system</h3> <p>ICANN is a corporation subject to California law and reports to the US government. There are no formal relations between ICANN and other international organisations. However, some intergovernmental bodies such as the International Telecommunication Union (ITU) and the World Intellectual Property Organisation (WIPO) participate in the Governmental Advisory Committee (GAC)<sup><a name="_ftnref9" href="http://www.giswatch.org/gisw2007/node/3438#_ftn9" id="_ftnref9">[9]</a></sup> of ICANN. The technical standard-setting bodies <sup><a name="_ftnref10" href="http://www.giswatch.org/gisw2007/node/3438#_ftn10" id="_ftnref10">[10]</a></sup> also appoint one liaison to the ICANN Board of Directors. As a consequence of its participation in the World Summit on the Information Society (WSIS), ICANN pays more attention to international organisations and actively supports their work where it touches upon ICANN's ambit. However, ICANN forms an important node in the network of organisations responsible for the development and coordination of the internet infrastructure, as the chart below shows.</p> <h3>1.5 Commitment to development</h3> <p>ICANN, together with its supporting organisations, is involved in national capacity-building regarding operational functions related to IP addresses and the DNS. Examples are assistance in the operation of ccTLD registries and the establishment of LACNIC and AfriNIC, the regional registries for allocating IP addresses in the African and Latin American and Caribbean regions respectively. <sup><a name="_ftnref11" href="http://www.giswatch.org/gisw2007/node/3438#_ftn11" id="_ftnref11">[11]</a></sup> ICANN has also established "regional presences" or liaisons in Africa, Asia, Latin America and the Middle East to strengthen its outreach and educational activities.</p> <h3>1.6 Commitment to gender equality</h3> <p>ICANN bylaws contain provisions for regional balance but not for gender balance. The term gender does not appear in its bylaws. However, due to the establishment of ICANN's Nominating Committee four years ago, the number of women in decision-making positions has increased.</p> <h3>1.7 Southern actors and civil society participation</h3> <p>Developing countries are underrepresented in all of ICANN's stakeholder groups. ICANN meetings do not take place at UN locations, which makes them expensive to attend for governments from developing countries. For civil society organisations, participation in international meetings is generally difficult to finance. ICANN has no budget for supporting participants from developing countries to attend its meetings. <sup><a name="_ftnref12" href="http://www.giswatch.org/gisw2007/node/3438#_ftn12" id="_ftnref12">[12]</a></sup> Lack of capacity and competence is another reason why developing countries may not participate in ICANN or attend meetings even when they take place in their regions. From a developing-country perspective, there might also be more pressing issues to attend to – such as access to the internet – than participating in ICANN.</p> <p>Civil society participates in ICANN through the At-Large Advisory Committee and the Non-Commercial User Constituency of the Generic Names Supporting Organisation. All in all, civil society participation in ICANN is rather low. Reasons for unsuccessful outreach efforts may have to do with the very specific and not easily comprehensible mission of ICANN, and the low interest of most users in the administration of the net's infrastructure, but also with the disfranchisement of individual users. Individuals have no votes in any of ICANN's decision-making bodies. They can achieve policy goals in ICANN only indirectly through the Nominating Committee or through lobbying other constituencies and supporting organisations.</p> <h2>2. Role and responsibilities in ICTs</h2> <h3>2.1 General orientation and responsibilities towards ICT policies and actions</h3> <p>ICANN’s communication services are based on addressing systems that carry out two crucial functions. First, they provide users or their communication devices with a unique identification; second, they provide information about the location of communication devices. The allocation of such identifiers requires global coordination to ensure that addresses are assigned only once and also in an efficient manner. The internet has two such identifier systems: IP addresses and domain names. ICANN is responsible for the overall coordination of these identifier systems. The term “coordination” refers to the fact that the actual assignment of numbers and the delegation of names is carried out by registries which are linked to ICANN through contracts.</p> <p>ICANN’s mission specifies three types of coordination related to internet names and number spaces. ICANN:</p> <ul><li>Coordinates the allocation and assignment of the three sets of unique identifiers for the internet, which are: <ul><li>a. domain names (forming a system referred to as the DNS);</li> <li>b. internet protocol (IP) addresses and autonomous system (AS) numbers; and</li> <li>c. protocol port and parameter numbers.</li> </ul></li> <li>Coordinates the operation and evolution of the DNS root name server system.</li> <li>Coordinates policy development reasonably and appropriately related to these technical functions (ICANN, 2006a).</li> </ul><p>ICANN's responsibilities and orientation in the overall field of ICT policies were defined in the late 1990s and thus reflect a specific period in the evolution of the internet following the privatisation of the backbone, the central network that linked all the parts of the internet together, and its opening to the general public in the mid 1990s. <sup><a name="_ftnref13" href="http://www.giswatch.org/gisw2007/node/3438#_ftn13" id="_ftnref13">[13]</a></sup></p> <p>The engineers who developed the DNS conceived domain names as arbitrary strings of characters without any direct relationship to names or marks in the real world. Domain names were meant to be "NOT natural language expressions" as Vint Cerf (2006) emphasised again at the first Internet Governance Forum in Athens in 2006. As Jon Postel (1994) put it in a memo that explains the DNS: "Concerns about 'rights' and 'ownership' of domains are inappropriate. It is appropriate to be concerned about 'responsibilities' and 'service' to the community." However, with the growth of the World Wide Web in 1992, domain names became very popular and quickly turned into tradable goods. Equivalents to famous names and protected marks in the name space became subject to escalating speculation and property rights conflicts. An informal market for domain names was emerging in the second half of the 1990s but there was no authority nor any rules to govern this new trade. The founding of ICANN in 1998 was the response to this lack of regulation.</p> <p>The MoU specified the following tasks for ICANN to accomplish in collaboration with the US government:</p> <ul><li>Develop policies for the allocation of internet addresses (IP numbers) and the assignment of other technical parameters</li> <li>Develop a plan for the introduction of competition in domain name registration services including an accrediting system for registrars</li> <li>Develop standards for the operation of generic TLDs</li> <li>Develop policies for the operation of root servers</li> <li>Develop a consensual mechanism for the delegation of new TLDs</li> <li>Establish a uniform procedure for the resolution of property rights conflicts over domain names</li> <li>Develop a review process that allows members of the internet community to appeal decisions by ICANN</li> <li>Develop a process for affected parties to participate in the formulation of policies regarding the technical management of the internet</li> <li>Develop membership mechanisms that "foster accountability to and representation of the global and functional diversity of the internet and its users" (NTIA, 1998).</li> </ul><p>Competition, "private bottom-up coordination" and international representation were some of the founding principles issued by the US government that have shaped ICANN's coordination tasks.</p> <p>Throughout its founding years, ICANN stressed the operational or technical nature of its functions. More recently, its policy-making activities have become so predominantly visible that they can no longer be denied. For at least the “generic” part of the DNS, ICANN has evolved into a regulatory agency with price-setting and service-related standards defining responsibilities. While the ccTLDs are typically administrated and regulated at the national level, ICANN sets contract-based policies for gTLDs such as ".com", ".org" or ".net". <sup><a name="_ftnref14" href="http://www.giswatch.org/gisw2007/node/3438#_ftn14" id="_ftnref14">[14]</a></sup></p> <p>However, ICANN’s self-governance approach differs in several respects from traditional regulatory mandates in the telecommunication area. Most importantly, ICANN is not independent of either its "regulatees" or its supervisory agency. The regulated organisations – registrars and registries – not only participate in ICANN's policy-setting efforts as members of ICANN's constituencies, they also contribute significantly to ICANN's budget. <sup><a name="_ftnref15" href="http://www.giswatch.org/gisw2007/node/3438#_ftn15" id="_ftnref15">[15]</a></sup> As a regulatory agency, ICANN is thus interwoven with and accountable to several actors with diverse or even antagonistic interests, the most influential of which are arguably the US government and the DNS service industry.</p> <h3>2.2. Specific responsibilities in relation to the WSIS</h3> <p>ICANN participated in the WSIS, though without any specific responsibilities. However, internet governance and the private self-regulatory approach that ICANN represents evolved into one of the major controversies in the first phase of the Summit. For this reason, ICANN attended the preparatory conferences, explaining its role, mission, guiding principles and organisational structure. ICANN also participated in the UN Working Group on Internet Governance and supported it financially. In its own ambit, ICANN launched a temporary working group on WSIS and organised several WSIS-related workshops at ICANN meetings.</p> <h2>3. Description and analysis of ICT activities</h2> <h3>3.1 WSIS-related activities since the Tunis Summit</h3> <p>ICANN's post-WSIS activities have focused on the Internet Governance Forum. ICANN has participated in and allocated money in its budget to financially support the Advisory Group that assisted the UN Secretary General in launching the first Forum meeting.<sup><a name="_ftnref16" href="http://www.giswatch.org/gisw2007/node/3438#_ftn16" id="_ftnref16">[16]</a></sup> ICANN also co-organised several workshops at the first Forum meeting, which dealt with building capacity for participation in internet coordination and with multilingualism on the internet.</p> <p>WSIS has clear repercussions for ICANN's further orientation. Its strategic plan for 2006 to 2009 reflects the outcome of WSIS both in terminology and concrete goals. It describes as future "challenges and opportunities" the development of appropriate structures and processes for a "post-WSIS ICANN" as well as "an appropriate role" for ICANN "in the broad group of international entities involved in internet functions" (ICANN, 2006c). As a result of WSIS, ICANN takes more notice of other international organisations related to information and communications technology (ICT) policies and may thus become more responsive to policy concerns outside its own mission. The same might be said of other organisations, so that regulatory competencies affecting the internet may in future interact on a more regular basis.</p> <p>On a concrete level, ICANN plans in the near future to:</p> <ul><li>Increase international participation in ICANN processes and offer translation into other languages</li> <li>Support regional capacity-building in the field of internet addressing and the DNS</li> <li>Improve and monitor ICANN's overall operational performance and that of its supporting organisations</li> <li>Audit its own openness, transparency and inclusiveness</li> <li>Deal in a systematic way with "end user issues" (complaint handling regarding registration of domain names)</li> <li>Pursue the deployment of internationalised domain names (also on the top level), and facilitate the introduction of new TLDs and a consensual WHOIS policy (see below).</li> </ul><h3>3.2 Other ICT-related activities</h3> <p>ICANN's regulatory activities centre on the provision of services particularly in the generic but also partly in the country-code domain name space. Examples of the regulation of existing services are the Uniform Dispute-Resolution Policy (UDRP) <sup><a name="_ftnref17" href="http://www.giswatch.org/gisw2007/node/3438#_ftn17" id="_ftnref17">[17]</a></sup> and the WHOIS policy. <sup><a name="_ftnref18" href="http://www.giswatch.org/gisw2007/node/3438#_ftn18" id="_ftnref18">[18]</a></sup></p> <p>The UDRP was introduced in 1999. It consists of an international online arbitration process for settling conflicting claims to domain names without resorting to national courts. The goal is to provide conflicting parties with a quick and low-cost resolution procedure. The scope of the UDRP is limited to domain names under gTLDs and a few ccTLDs. Furthermore, the UDRP only applies to claims made by trademark owners to domain names which have been registered and used in bad faith. Evaluations of the UDRP arbitration process (Froomkin, 2002; Geist, 2002) point out a systemic bias towards the complainants and thus a privileging of trademark-based claims over other rights.</p> <p>The WHOIS policy pertains to a database that contains contact information of domain name registrants. For several years ICANN has struggled to consensually define mandatory rules regarding essential registrant data elements that must be made publicly available by registrars. Intellectual property organisations and some public authorities wish unrestricted access to the WHOIS database. However, the publication of WHOIS information potentially conflicts with data protection laws, which vary widely across countries. A report by the London School of Economics (LSE) estimates that volunteers in ICANN have spent approximately 39,000 hours on this issue since the first task force was initiated in 2001 (LSE, 2006, p. 66).</p> <p>Examples of regulatory policies aimed at expanding or creating new markets are the delegation of new TLDs and the introduction of internationalised domain names (IDN). The 1998 MoU between the US government and ICANN already specified one of ICANN's tasks as the consideration of a process for the introduction of new gTLDs. In various pilots and trials that took place in 2000, 2004 and 2005, ICANN has to date delegated twelve new TLDs. However, there is still no established standard procedure for the future introduction of new gTLDs. The delegation of new TLDs has been a controversial issue for more than a decade, with some stakeholders arguing vigorously in favour of increasing the number of TLDs up to a technically feasible figure per year, and other stakeholders more or less against any additional TLDs. The supporting organisation for generic DNS issues in ICANN, the Generic Names Supporting Organisation (GNSO), <sup><a name="_ftnref19" href="http://www.giswatch.org/gisw2007/node/3438#_ftn19" id="_ftnref19">[19]</a></sup> has now completed another policy development process, which endorses the introduction of additional TLDs and recommends policy principles for their selection and allocation (GNSO, 2006).</p> <p>The DNS is based on the ASCII character set, which supports only Latin alphabet domain names. <sup><a name="_ftnref20" href="http://www.giswatch.org/gisw2007/node/3438#_ftn20" id="_ftnref20">[20]</a></sup> In order to enable international use of the DNS, the Internet Engineering Task Force (IETF) <sup><a name="_ftnref21" href="http://www.giswatch.org/gisw2007/node/3438#_ftn21" id="_ftnref21">[21]</a></sup> has developed a converting mechanism that allows for a translation of non-ASCII character domain names into ASCII-based names. Based on the technical specifications defined by the IETF (2003), ICANN devised guidelines for the use of those standards at the registry level. All operators of an ICANN-accredited TLD (i.e. .com, .net, .org, .info, .biz, etc.) are required to comply with those guidelines in order to obtain approval for the registration of internationalised domain names. Tests for introducing internationalised TLDs are expected to be completed by the end of 2007.</p> <h2>4. Stakeholder participation</h2> <h3>4.1. Key areas in which participation of civil society, Southern countries and women is an issue</h3> <p>Diversity in participation is especially important in the area of name space regulation. DNS policy issues such as the introduction of internationalised domain names (IDN) or decisions on data protection directly affect users' interests. Key decision-making bodies for DNS policy are currently the GNSO and the ICANN Board of Directors.</p> <p>Another relevant area is the evolving structure of ICANN itself. ICANN is a prime example of new forms of multi-stakeholder organisation, but also of the various problems inherent in these new types of consensus-building entities. As the continuous changes in ICANN's sub-structures and procedures show, the goal of fair representation and legitimate decision-making is very difficult to achieve once the traditional UN principle of "one state, one vote" is discarded as a model.</p> <h3>4.2 Actions taken to ensure effective participation of all stakeholders</h3> <p>A key element of ICANN's governance model is the principle of bottom-up consensus building.</p> <p>Stakeholders relevant to the field of DNS and IP address management are involved in ICANN through supporting organisations. The ICANN bylaws identify the roles and responsibilities of the three supporting organisations: the Address Supporting Organisation, Country Code Names Supporting Organisation (ccNSO) and GNSO. They are each responsible for policy development in their respective areas. The structure of the supporting organisations and their relationship with ICANN differ considerably. The GNSO, responsible for gTLDs, is the largest and has the most differentiated structure. As the following chart shows, the GNSO consists of six "constituencies", which should represent the diversity of interests involved in or affected by the management of the domain name space. As the chart also shows, ICANN's constituency structure over-represents business interests. The Non-Commercial Users Constituency is the only group in the GNSO Council that articulates civil society interests.</p> <p>As a result of ICANN's reform, a Policy Development Process (PDP) that covers issues in the purview of the GNSO and the ccNSO has been established. The PDP is part of the ICANN bylaws (Annex A and B) and specifies in detail the roles and responsibilities of the Board of Directors, the GNSO, the ccNSO and ICANN staff to ensure that decision-making processes go forward within a given time, but also that final decisions by the Board do indeed reflect the recommendations of the supporting organisations. In contrast to DNS policies, policies regarding the allocation of IP addresses are more or less autonomously developed by the Address Supporting Organisation.</p> <p>Civil society groups have two channels in ICANN to influence the policy process. The first channel is the At-Large Advisory Committee (ALAC), which represents self-organising Regional At-Large Organisations (RALOs). ALAC was originally designed for individual internet users. In future it might represent both organisations and individuals. The task of the At-Large Membership is to offer advice on ICANN's regulatory activities. Unlike the other stakeholder groups in ICANN, ALAC no longer has decision-making authority. <sup><a name="_ftnref22" href="http://www.giswatch.org/gisw2007/node/3438#_ftn22" id="_ftnref22">[22]</a></sup> It is represented on the Board, as well in the GNSO, through non-voting liaisons.</p> <p>The second channel of civil society participation is the Non-Commercial Users Constituency (NCUC), <sup><a name="_ftnref23" href="http://www.giswatch.org/gisw2007/node/3438#_ftn23" id="_ftnref23">[23]</a></sup> one of the six constituencies that together form the GNSO. NCUC constitutes a minority on the GNSO Council, the organisation’s decision-making body. The fact that the GNSO Council uses a weighted voting system, which favours the registrars and registries by giving their Council members two votes instead of one, further marginalises civil society perspectives in the GNSO.</p> <p>ICANN's bylaws (Article VI: Sections 3-5) include "diversity provisions" for international representation. To ensure diversity, ICANN's bylaws specify five geographic regions, <sup><a name="_ftnref24" href="http://www.giswatch.org/gisw2007/node/3438#_ftn24" id="_ftnref24">[24]</a></sup> all of which must be represented by at least one member of the Board, the various councils, and the Nominating Committee. There are no equivalent provisions to ensure gender diversity. For the At-Large Membership, geographic representation will be achieved through the five RALOs, which are intended to be umbrella entities for non-commercial organisations ("At-Large Structures") and individuals who take an interest and want to participate in ICANN. At present, all five RALOs are in the process of constituting themselves and negotiating a memorandum of understanding with ICANN. <sup><a name="_ftnref25" href="http://www.giswatch.org/gisw2007/node/3438#_ftn25" id="_ftnref25">[25]</a></sup></p> <p>After WSIS, ICANN has strengthened its efforts to internationalise participation. To facilitate multilingual communication, relevant documents are to be translated into other languages. There are also plans to offer simultaneous interpretation at ICANN meetings. In addition, ICANN has initiated outreach programmes designed to contribute to regional capacity-building in the area of DNS and IP address management and to increase participation from under-represented regions.</p> <p>Among the post-WSIS regional outreach activities are the newly established regional liaisons for each of ICANN's five world regions, the task of each being to form networks with and across all stakeholders, including national governments. The goal is to promote participation in ICANN but also to foster the emergence of regional DNS service industries and of user groups. In addition, ICANN created the position of a general manager for public participation to foster active participation by the various stakeholder groups.</p> <p>Until 2003, decision-making positions in ICANN were predominantly filled by the ICANN supporting organisations and their constituencies. In 2003, ICANN created a Nominating Committee, which selects eight members of ICANN's fifteen-member Board of Directors, as well as a "portion" of the GNSO and ccNSO Councils and the Interim ALAC. The purpose of the Nominating Committee is to broaden the existing mix of geography, culture, skills, experience, and perspective as derived from ICANN's supporting organisations. Due to the work of the Nominating Committee, the share of "ICANN outsiders" in decision-making positions has significantly increased and ICANN's Board and councils show a slightly increased participation of women, not least from developing countries. <sup><a name="_ftnref26" href="http://www.giswatch.org/gisw2007/node/3438#_ftn26" id="_ftnref26">[26]</a></sup> Civil society has a strong voice in the Nominating Committee, with five of its members being selected by ALAC. Together with the representative of the Non-Commercial Users Constituency, civil society constitutes roughly a third of the voting members.</p> <h3>4.3. Effectiveness of efforts to increase stakeholder participation</h3> <p>ICANN's diversity provisions do ensure a degree of regional variety in decision-making positions. Its travel reimbursement policy for Board members and Nominating Committee appointees enables participation from developing countries and from civil society organisations. However, on the level of general participation without decision-making responsibility, both regional and sectoral diversity is much more limited. The majority of attendees at ICANN meetings are from OECD countries and related to the internet industry. ICANN does offer all stakeholders opportunities to participate, but the actual influence on the policy process varies significantly among the different groups. In particular, individuals and non-commercial internet users lack an effective voice in policy matters.</p> <p>Fair representation and balance of interests is an issue especially in ICANN's most important supporting organisation, the GNSO. The representativeness, transparency and effectiveness of GNSO operations have recently been subject to an extensive evaluation conducted by the LSE. The LSE review comes to the conclusion that the current GNSO structure reflects a "snapshot of the interest groupings most active on generic names issues in the founding stages of ICANN in the late 1990s" (LSE, 2006, p. 423). Its constituency structure lacks the flexibility required to incorporate new stakeholders, and the individual constituencies are not easy for newcomers to find and to join. The report also notes that the majority of constituencies suffer from low participation and a lack of representativeness. Of the altogether 231 members of the GNSO, only a small fraction regularly participate. This means that policy recommendations on vital issues such as the conditions of use of domain names in gTLDs are developed by quite a small number of people.</p> <p>The review recommends among many other things:</p> <ul><li>Establishing a more flexible structure that is open and attractive to new stakeholder groups by reducing the number of GNSO constituencies from six to three (registration, business, and civil society including the now separate At-Large Membership).</li> <li>The creation of a primary, fee-based membership in ICANN so that it becomes actually possible to join the organisation and choose a constituency according to individual preferences.</li> <li>The strengthening of incentives for reaching consensus across the various interest groups through abolishing weighted voting and raising the threshold for consensus on the GNSO Council from 66% to 75%.</li> </ul><p>While a restructuring of the GNSO into three groups could well be a step forward to overcoming the antagonistic constellation in the GNSO, it bears the risk of codifying once again the minority position of civil society. By the same token, a membership fee might discriminate non-commercial users, particularly from developing countries. It is thus important that any new consensus-fostering mechanism gives adequate weight to civil society groups so that all views and interests are reflected in policy recommendations.</p> <p>The WSIS Declaration calls for a multilateral, transparent and democratic management of the internet, with the full involvement of governments, the private sector, civil society and international organisations. The WSIS documents offer no further specification, however, about what is meant by "democratic management of the internet". ICANN has never described its processes as democratic, choosing instead to speak of "bottom-up consensus". Considering that democracy is still primarily a national form of organisation, some core elements of which cannot easily be implemented in transnational environments, it seems understandable that ICANN avoids this term. However, the implementation of and, even more so, the compliance with bottom-up decision-making processes turn out to be fairly ambitious goals, too. ICANN's policy decisions over the past years reveal several examples where the Board of Directors acted despite a lack of consensus in the GNSO or other parts of its constituency. <sup><a name="_ftnref27" href="http://www.giswatch.org/gisw2007/node/3438#_ftn27" id="_ftnref27">[27]</a></sup> However, violations of constitutional decision-making procedures eventually undermine the legitimacy of an organisation. Another problem concerns the unequal distribution of power among ICANN's stakeholder groups. A full involvement of civil society in ICANN would require a restructuring of its bottom-up consensus-building process.</p> <h2>5. Conclusions and recommendations</h2> <h3>5.1 General conclusions</h3> <p>ICANN is one of the prominent examples of multi-stakeholder coordination or "self-governance" in ICT. Eight years after its inception, a number of insights can be drawn from this new type of regulation.</p> <p>Firstly, self-governance does not mean that governments disappear. Even if the US government lives up to its promise and eventually privatises DNS regulation, government(s) will still keep some control over the policy outcome. Private agencies cannot step outside the "shadow of hierarchy". They must comply with national laws, but they may also have to cope with political pressure, as ICANN had to in the battle over "triple X", the proposed TLD that would have created a virtual "red light district" on the internet. Despite political pressure that brought the contract negotiations to a halt in May 2006, in January 2007 ICANN published a new draft contract. <sup><a name="_ftnref28" href="http://www.giswatch.org/gisw2007/node/3438#_ftn28" id="_ftnref28">[28]</a></sup></p> <p>The current public-private arrangement is problematic for two reasons. The first concerns the US government’s unilateral control over the DNS infrastructure and ICANN's activities. From a normative point of view, unilateral control over vital internet infrastructure resources is without a doubt less legitimate than an intergovernmental regime. However, as debates throughout the WSIS have shown, it is unclear how political responsibility for a global infrastructure can be distributed in a more equitable manner without resorting to the UN system. The much criticised unilateral control over the DNS may thus persist because governments cannot agree on an alternative and more legitimate solution.</p> <p>A second problem pertains to accountability. Multi-stakeholder arrangements under public supervision tend to blur the responsibility for policy decisions. Again, ".xxx" provides a good example. If the division of labour between the government and the private agency is not clear-cut, it is difficult for affected parties to determine who can be held accountable for policies. On the other hand, there are limits to the capacity of self-regulation. In the event of a privatisation of ICANN, it will be vital to install reliable checks and balances to minimise the risk of abuses of regulatory authority.</p> <p>A weak point of private multi-stakeholder organisations concerns issues of membership and representation. While national and international organisations aggregate opinions and interests by means of representation, ICANN has been struggling for years to develop its own approach to inclusiveness and fair representation. The most controversial issue has been the role of individual users. No doubt, ICANN intends to be inclusive and does recognise the legitimacy that derives from openness and broad participation. But ICANN equally fears negative consequences from weak organisational boundaries such as "capture" or manipulation and a loss of control over the process of policy development.</p> <p>Thus ICANN still has an ambivalent stance on civil society participation. This is demonstrated by the disenfranchisement of the At-Large Membership after 2002 on the one hand and the substantial organisational and financial support for the newly founded ALAC on the other. ICANN supports the development of a complex civil society structure in ICANN but at the same time denies civil society direct influence on the policy process. Like other multi-stakeholder organisations, ICANN faces the challenge of balancing potentially conflicting values such as inclusiveness, consensus-orientation and effectiveness without having at their disposal the means and procedures of governmental institutions.</p> <p>Compared to national or intergovernmental organisations, ICANN is a remarkably open and transparent organisation. Debates about controversial issues such as the WHOIS database can be observed on the internet. The meetings of most councils and task forces are open, and recordings or minutes are released on the internet. Even the ICANN Board of Directors has made efforts to become more transparent. Detailed minutes of Board meetings are published on the internet, and in the case of critical decisions, the individual votes of Board members are now published. Some directors even offer personal explanations for their votes.</p> <p>Thanks to this high degree of transparency, the pros and cons of policy options in question are easier to understand and observers have the opportunity to develop informed opinions. What is more, transparency enables some degree of public control over the organisation's performance. ICANN's actions are closely monitored by a number of news services and blogs on the internet. Controversial policy decisions thus need to be justified. Because it enables public deliberation and some degree of accountability, transparency is at present regarded as a major source of legitimacy for private governance bodies. However, transparency can also turn into a source of de-legitimation. In the case of ICANN, transparency has led to a strong public awareness of its shortcomings.</p> <h3>5.2 Conclusions on performance in relation to ICT role and responsibilities</h3> <p>In 1998, when the first MoU between the US government and ICANN was agreed upon, the general expectation was that ICANN would accomplish its tasks within two years. However, the road towards privatisation of DNS management has turned out to be more difficult to navigate than expected. While some of the tasks were indeed implemented quickly, others are still on ICANN's “to-do list”. In September 2006, the US government therefore amended the MoU for a seventh time. <sup><a name="_ftnref29" href="http://www.giswatch.org/gisw2007/node/3438#_ftn29" id="_ftnref29">[29]</a></sup></p> <p>In 1999, ICANN introduced competition for the registration of domain names under gTLDs, established the Uniform Dispute Resolution Policy to deal with the "cybersquatting" of domain names of well-known organisations or products, and developed a participatory structure for the internet industry (supporting organisations). In 2000, ICANN approved several new TLDs and began setting standards for the operation of gTLDs. But since then, ICANN has failed to develop a general rules-based mechanism for the delegation of new TLDs. ICANN has also failed to create a membership organisation that fosters "accountability to and representation of" the diversity of internet users.</p> <p>ICANN's self-governance structure proved able to create a new market for registration services, but it lacks the power to act against vested interests in this market and its own organisation. There is as yet only marginal competition between TLDs, and the existing registries have successfully delayed the creation of a process for the regular introduction of TLDs.</p> <p>ICANN's overall acceptance depends on its problem-solving capacity, its inclusiveness and its ability to adequately reflect in its policy decisions the existing diversity of opinions. However, ICANN operates under severe restrictions, and the room for altering its structure and performance may therefore be limited. The self-governance approach implies that policies need the consent of the "rule takers". In some cases, this leads to non-transparent decision-making processes and biased results at the expense of users' interests. <sup><a name="_ftnref30" href="http://www.giswatch.org/gisw2007/node/3438#_ftn30" id="_ftnref30">[30]</a></sup></p> <p>ICANN's current structure privileges the interests of one industry sector over the interests of users and future businesses. The privatisation of DNS regulation would require as a minimum a more balanced representation, a more efficient policy development process and stronger mechanisms of accountability.</p> <h3>5.3 Conclusions on the adequacy of modalities and practices of participation</h3> <p>Under ICANN’s current structure, voting or decision-making rights are unequally distributed. Some stakeholder groups such as the individual users but also governments (though by their own choice) lack voting rights. Constituencies that have contractual relationships with ICANN (registries and registrars) have more votes than those that do not. The method of differentiating political influence and allocating voting rights according to a stakeholder’s share of the budget or similar criteria violates basic democratic principles and thus weakens the legitimacy of ICANN. All stakeholders participating in the policy-making process should be granted voting rights, and power asymmetries between constituencies should be avoided. Equal participation rights for individual users, as originally intended, would create an incentive for broader participation by civil society.</p> <h4>5.3.1 Concrete recommendations for improving the modalities of participation</h4> <ul><li>Non-commercial and individual user-related bodies in ICANN (NCUC, ALAC) should be merged into one civil society membership organisation. Regional chapters should be encouraged but not made mandatory. Hierarchical layers in the civil society body, both regional or functional, should be avoided.</li> </ul><ul><li>The GNSO should be restructured along the lines of the recommendations of the GNSO evaluation. However, incentives for consensus-building across the GNSO constituencies must include civil society as a third stakeholder.</li> </ul><ul><li>The ICANN Board and ICANN management must ensure that policy recommendations made by supporting organisations and councils are followed when explicitly required under the bylaws. In general, the ICANN Board and staff should respond more seriously to the public comments it invites on its policy proposals.</li> </ul><ul><li>In order to become more inclusive and attract new people across all regions and stakeholder groups, ICANN should produce policy briefs on relevant but complex and controversial issues that explain to newcomers the problem at hand and the various solutions under discussion. This would also be helpful for new members of the Board and councils.</li> </ul><h3>5.4 Specific recommendations for improving performance</h3> <p>ICANN is still an emerging organisation, as is reflected in the regular modifications of its bylaws. In order to increase trust in the organisation's processes, it is vital to establish an equivalent to the rule of law. ICANN's formal rules and principles need to become more self-binding so that the organisation's decisions will be more predictable and participating stakeholders can rely on the organisation's actions. Another crucial component of the rule of law is a non-discriminatory and effective means to appeal against potential violations of the bylaws.</p> <p>A possible and desirable side effect of a stronger "constitutionalisation" of ICANN would be a change in the balance of power between ICANN staff and the constituencies and councils working on a voluntary basis.</p> <p>ICANN's decisions on the delegation of new TLDs, the renewal of contracts for TLDs, and its accreditation policies for registrars have allocation effects. So far, ICANN's policies indirectly favour a small number of mostly US-based registry businesses and large, globally-acting registrars, none of which are located in developing countries. Regional effects of accreditation policies or the selection of new TLDs should play a more important role in ICANN's decisions. <sup><a name="_ftnref31" href="http://www.giswatch.org/gisw2007/node/3438#_ftn31" id="_ftnref31">[31]</a></sup></p> <h2>References</h2> <p>Cerf, V. (2006). “Governance of the Internet: The Tasks Ahead“. <em>Opening Remarks at Internet Governance Forum</em> [online]. Athens, Greece, 30 October - 2 November 2006. Available from: < <a href="http://www.icann.org/announcements/announcement-1-30oct06.htm" target="_new">www.icann.org</a>>.</p> <p>Froomkin, M. (2002). “ICANN’S Uniform Dispute Resolution Policy – Causes and (Partial) Curses”. <em>Brooklyn Law Review </em>[online], 67(3), pp.605-718. Available from: < <a href="http://personal.law.miami.edu/%7Efroomkin/articles/udrp.pdf%5D" target="_new">personal.law.miami.edu</a>>.</p> <p>Geist, M. (2002). “An examination of the allegations of systematic unfairness in the ICAVV UDRP”. <em>Brooklyn Journal of international law </em>[online], 27, pp.902-938. Available from: < <a href="http://www.michaelgeist.ca/content/blogcategory/70/192/10/10/" target="_new">www.michaelgeist.ca</a>>.</p> <p>GNSO (2006). <em>Draft Final Report of the Generic Names Supporting Organisation’s</em></p> <p><em>Policy Development Process</em> [online]. Available from: < <a href="http://gnso.icann.org/drafts/GNSO-PDP-Dec05-FR-14Nov06.pdf" target="_new">gnso.icann.org</a>>.</p> <p>ICANN (2006a) “ICANN Strategic Plan July 2007 – June 2010” [online]. Available from: < <a href="http://www.icann.org/strategic-plan/draft_stratplan_2007_2010_clean_final.pdf" target="_new">www.icann.org</a>>.</p> <p>ICANN (2006b). “Proposed Budget: fiscal year 2006-2007” [online]. Available from: < <a href="http://icann.org/announcements/proposed-budget-2006-07-cln.pdf" target="_new">icann.org</a>>.</p> <p>ICANN (2006c). “ICANN Strategic Planning Process for the July 2007 - June 2010 Strategic Plan“ [online]. Available from: < <a href="http://www.icann.org/announcements/announcement-13sep06.htm" target="_new">www.icann.org</a>>.</p> <p>IETF (2003). “Internationalized Domain Name (idn)“ [online]. Available from: < <a href="http://www.ietf.org/html.charters/OLD/idn-charter.html" target="_new">www.ietf.org</a>>.</p> <p>LSE (2006). “A Review of the Generic Names Supporting Organisation (GNSO)” [online]. Available from: < <a href="http://www.icann.org/announcements/gnso-review-report-sep06.pdf" target="_new">www.icann.org</a>>.</p> <p>Mueller, M. (2002). <em>Ruling the Root. Internet Governance and the Taming of Cyberspace</em>. Cambridge: MIT Press.</p> <p>NTIA (US. National Telecommunications and Information Administration) (1998). <em>Memorandum of Understanding Between the Department of Commerce and the Internet Corporation for Assigned Names and Numbers (ICANN)</em> [online]. Available from: < <a href="http://www.ntia.doc.gov/ntiahome/domainname/icann-memorandum.htm" target="_new">www.ntia.doc.gov</a>>.</p> <p>NTIA (2006). <em>IANA Contract</em> [online]. Available from: < <a href="http://www.ntia.doc.gov/ntiahome/domainname/iana/ianacontract_081406.pdf" target="_new">www.ntia.doc.gov</a>>.</p> <p>Peake, A. (2004). <em>Internet governance and the World Summit on the Information Society (WSIS) </em>[online]. Prepared for the Association for Progressive Communications (APC). Available from: < <a href="http://rights.apc.org/documents/governance.pdf" target="_new">rights.apc.org</a>>.</p> <p>Postel, J. (1994). “Domain Name System Structure and Delegation” [online]. Information Sciences Institute, University of Southern California. Available from: < <a href="http://www.isi.edu/in-notes/rfc1591.txt" target="_new">www.isi.edu</a>>.</p> <footer><p>Notes: <br /> This report was originally published as part of a larger compilation: “Global Information Society watch 2007: Participation ” which can be downloaded from <a href="https://www.giswatch.org/en/2007">https://www.giswatch.org/en/2007</a> <br /> Published by APC and ITem <br /> 2007 <br /><b>Creative Commons Attribution 4.0 International (CC BY 4.0) </b> <br /><a href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</a> <br /> Some rights reserved. <br /> ISBN: 92-95049-34-9 <br /> APC-200705-CIPP-R-EN-P-0034</p> </footer></div></div> </div> <div class="field field-node-taxonomy-vocabulary-2 field-entity-reference-type-taxonomy-term field-formatter-entity-reference-label field-name-taxonomy-vocabulary-2 field-type-entity-reference field-label-above"><h3 class="field__label">Themes</h3><div class="field__items"><div class="field__item field__item--civil-society-participation"> <span class="field__item-wrapper"><a href="/themes/civil-society-participation" hreflang="en">Civil society participation</a></span> </div></div> </div> <section class="field field-node--comment-node-institutional-ove field-formatter-comment-default field-name-comment-node-institutional-ove field-type-comment field-label-hidden display-mode-threaded comment-bundle-comment-node-institutional-ove comment-wrapper"> <a name="comments"></a></section> </div></div> </article> </main> </div> </div> </div> </div> <div data-at-row="footer" class="l-footer l-row"> <footer class="l-pr page__row pr-footer" role="contentinfo" id="footer"> <div class="l-rw regions container pr-footer__rw arc--1 hr--1" data-at-regions=""> <div data-at-region="1" class="l-r region pr-footer__footer" id="rid-footer"><div id="block-footeren" class="l-bl block block-config-provider--block-content block-plugin-id--block-content-48e94994-c6ce-4dc2-b88b-33cac52f8cb6 block--type-basic block--view-mode-full"> <div class="block__inner"> <div class="block__content"><div class="clearfix text-formatted field field-block-content--body field-formatter-text-default field-name-body field-type-text-with-summary field-label-hidden has-single"><div class="field__items"><div class="field__item"><div id="nav"> <ul class="primary-links footer-links"><li><a href="/contact">Contact us</a></li> <li class="last"><a href="/en/privacy-policy">Privacy Policy</a></li> </ul></div> <div id="footer-logos"><a href="https://www.apc.org" target="_blank" rel="noopener noreferrer"><img src="/sites/default/files/images/apclogo-small.jpg" caption="false" width="119" height="67" /></a><a href="https://www.sida.se/English/" target="_blank" rel="noopener noreferrer"><img src="/sites/default/files/images/logosida.png" caption="false" width="121" height="67" /></a></div> <div id="footer-text"> <p>Association for Progressive Communications (<a href="https://www.apc.org" target="_blank" rel="noopener noreferrer">APC</a>), Swedish International Development Cooperation Agency (<a href="https://www.sida.se/English/">Sida</a>)<br />Unless otherwise stated, material on this site is licenced under <a href="https://creativecommons.org/licenses/by/4.0/%0A" target="_blank" rel="noopener noreferrer">Creative Commons</a><br />The views expressed on this site are those of the individual authors and not necessarily the views of APC or Sida</p> </div> </div></div> </div> </div></div> </div> </div> </div> </footer> </div> <div data-at-row="attribution" class="l-attribution l-row"><div class="l-pr attribution"><div class="l-rw"><a href="//drupal.org/project/at_theme" class="attribution__link" target="_blank">Design by Adaptive Theme</a></div></div></div> </div> </div> <script type="application/json" data-drupal-selector="drupal-settings-json">{"path":{"baseUrl":"\/","scriptPath":null,"pathPrefix":"","currentPath":"node\/271","currentPathIsAdmin":false,"isFront":false,"currentLanguage":"en"},"pluralDelimiter":"\u0003","suppressDeprecationErrors":true,"ajaxPageState":{"theme":"giswatch","libraries":"at_core\/at.accordion,at_core\/at.breakpoints,at_core\/at.responsivemenus,at_core\/at.settings,collapsiblock\/core,giswatch\/base,giswatch\/book,giswatch\/ckeditor,giswatch\/color,giswatch\/comment,giswatch\/contact,giswatch\/custom_css,giswatch\/custom_css_file,giswatch\/fontfaceobserver,giswatch\/giswatch.layout.page,giswatch\/jquery_ui,giswatch\/language,giswatch\/responsive_menus,giswatch\/responsive_menus_accordion,giswatch\/responsive_menus_dropmenu,giswatch\/responsive_menus_slidedown,giswatch\/search,giswatch\/taxonomy,matomo\/matomo,system\/base"},"matomo":{"disableCookies":true,"trackMailto":true},"collapsiblock":{"active_pages":false,"slide_type":1,"slide_speed":200},"giswatch":{"at_responsivemenus":{"bp":"all and (min-width: 60.0625em)","default":"ms-slidedown","responsive":"ms-dropmenu","acd":{"acd_load":true,"acd_default":true,"acd_responsive":false,"acd_both":false}},"at_breakpoints":{"at_core_simple_wide":{"breakpoint":"wide","mediaquery":"all and (min-width: 60.0625em)"},"at_core_simple_tablet-isolate":{"breakpoint":"tablet-isolate","mediaquery":"all and (min-width: 45.0625em) and (max-width: 60em)"},"at_core_simple_mobile":{"breakpoint":"mobile","mediaquery":"all and (max-width: 45em)"}}},"ajaxTrustedUrl":{"\/search\/node":true},"user":{"uid":0,"permissionsHash":"00d5a2f3438a31ad0f165b1e86e49f99467c8649a9e9192d66e463ef156c19ba"}}</script> <script src="/sites/default/files/js/js_9HJhIDXpoxp4fzHBM8e4v20aWTjdOBNEdbqZYC3rmu8.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/fontfaceobserver/2.0.8/fontfaceobserver.js"></script> <script src="/sites/default/files/js/js_Zb-KvjwD-Mx_jm4YzA9d9pcQQOzZWa_KvTF40k1vsGA.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/enquire.js/2.1.2/enquire.min.js"></script> <script src="/sites/default/files/js/js_OHfNmOlNIFKrftJLCFYrGcSEKZRP9Lf5kOEnnsr5t0g.js"></script> </body> </html>