ICANN Correspondence

ICANN Blog

ICANN Blog ICANN Blog

  • GNSO Council Launches EPDP on the Temporary Specification for gTLD Registration Data
    on July 19, 2018 at 7:00 am

    It is an honor to announce that the Generic Names Supporting Organization (GNSO) Council has just officially launched an Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. During our July Council meeting held today at 12:00UTC, the GNSO Council passed the Initiation Request [PDF, 390 KB] of the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data and adopted the EPDP Team Charter [PDF, 523 KB]. Both documents are the product of several months of preparatory work on the part of the Council, acting as the Charter and Initiation Request Drafting Team. This important milestone marks the official commencement of the GNSO's very first Expedited PDP. As the name suggests, an EPDP is a Policy Development Process in which the early steps of Preliminary Issue Report and Final Issue Report (and associated public comment periods) are eliminated to fast-track policy development in cases of urgency. The GNSO Council has agreed that the EPDP is the most appropriate response to the ICANN Board's adoption of the proposed Temporary Specification for gTLD Registration Data. It facilitates meeting the unique time constraints presented by the Temporary Specification, as described in detail in the Background Information section below. Since the Board's adoption of the Temporary Specification on 17 May 2018, the GNSO Council, as Bylaws-mandated manager of the policy development process, has been working hard in preparation for the launch of this EPDP. During an extraordinary meeting on 12 June 2018, the GNSO Council agreed to form a Drafting Team, consisting of Council leadership and interested Council members. Over the next several weeks, including many face-to-face hours at ICANN62 in Panama and many hours of teleconferences in the weeks following ICANN62, the Drafting Team worked tirelessly to reach an agreement on challenging issues such as membership criteria, composition, leadership, and scope of the policy development effort. Incremental changes identified through the PDP 3.0 – a key 2018 initiative of the GNSO Council aimed at improving the effectiveness and efficiency of the PDP – have informed and guided the Charter drafting process. Ultimately, the EPDP Charter is a testament to the true commitment and diligence of the Drafting Team and GNSO Council. It is also with great pleasure that we announce the appointment of Kurt Pritz as the Chair of the EPDP. Following rigorous evaluation of the applications received for the role of Chair of the EPDP, a selection panel unanimously recommended Kurt Pritz for this important position. The GNSO Council has agreed that he possesses the unique skill set needed to lead this EPDP. The GNSO Council has also put out a Call for Volunteers for the EPDP Team; it is expected that the Team will be formed and hold its first meeting during the week of 30 July 2018. This is an achievement that all in the GNSO and the wider ICANN community can be immensely proud of. This milestone could not have been achieved without the dedication, principled compromise, and remarkable efforts of the Drafting Team and GNSO Council members, working in collaboration with their Stakeholder Groups and Constituencies. While the EPDP has put the GNSO in unfamiliar territory, the heartening amount of work accomplished in such a short period has laid the groundwork for the EPDP's success. Please join me in celebrating the GNSO Council's achievement, and the demonstration of Councilors' ability to work together in the true spirit of the multistakeholder model. We welcome the ICANN community to follow the important work of the EPDP. To learn how to participate as a non-member, you may read our announcement today on icann.org. Background Information On 17 May 2018, the ICANN Board adopted the proposed Temporary Specification for gTLD Registration Data. This was an interim measure to bring existing WHOIS obligations in line with requirements of the European Union's General Data Protection Regulation. This has, in turn, triggered the obligation of the GNSO Council to undertake a policy development process to confirm, or not, the Temporary Specification as a Consensus Policy. The EPDP must be completed within 12 months of the implementation effective date (25 May 2018) of the Temporary Specification. […]

  • Minimal User Impact Expected From Root Zone Key Signing Key (KSK) Rollover
    on July 18, 2018 at 7:00 am

    The ICANN organization believes that an update of the Domain Name System Security Extensions (DNSSEC) trust anchor for the global Domain Name System (DNS) on 11 October 2018 will affect only a very small number of DNS users. The decision to roll the root zone Key Signing Key (KSK) is being made after a significant outreach effort and careful consideration of all available data. Since the DNS root zone was originally signed in 2010, the DNSSEC Practice and Policy Statement1 has set the expectation that the root zone KSK will change. Fortunately, most validating resolvers that observe a new root zone KSK should be able to configure it as a new trust anchor automatically using "Automated Updates of DNS Security (DNSSEC) Trust Anchors," defined in RFC50112. A resolver operator can also update their trust anchor configuration manually if they have become aware that the root KSK is changing based on ICANN's various outreach efforts. There is no standardized or deterministic way to actively measure that a validating resolver has the correct set of trust anchors configured. The best method currently available is "Signaling Trust Anchor Knowledge in DNS Security Extensions" (documented in RFC 81453) that was published in April 2017. In that protocol, validators emit a DNS query that contains the DNSKEY key IDs of configured trust anchors in the query name. These queries can be passively observed in traffic at the root servers. In September 2017, there were a handful of resolvers using this protocol and the announcements of trust anchors showed a higher percentage of misconfigured trust anchors than initially anticipated. However, the signal observed at the time was not well understood and, as a result, the ICANN org decided to postpone the root zone KSK roll to better understand the signal with the help of the technical community. Further research by the ICANN org's Office of the CTO (OCTO) team and others revealed concerns with the quality of the RFC 8145 data. For example, a DNS query reporting trust anchor information that is sent to a forwarder is treated the same as any other query and will be sent to a root server regardless if the forwarder is validating or not. In one case, a popular DNS resolver implementation signaled the trust anchor even though the resolver was not configured to validate and thus would not have the new trust anchor. This implementation decision was reversed in a subsequent release of the software. In another case, a well-known DNS resolver library signaled the trust anchor but did not have a method to automatically update its trust anchor configuration. As a result, a single deployment of a popular single-user VPN implementation using that DNS resolver library would emit the old trust anchor signal from different source addresses over time. Wes Hardaker at the University of Southern California Information Sciences Institute discovered this behavior and the vendor using the library was informed and updated their software. This change has significantly reduced the number of sources reporting the old trust anchor.4 However, the RFC 8145 data reports only resolvers; it does not provide an indication of the number of end users dependent upon those resolvers. To understand the size of the population of users behind validating resolvers, the Regional Internet Registry for the Asia Pacific region (APNIC) used a measurement system that utilizes Google's advertising network to query the DNS. Analyzing the intersection of ICANN's trust anchor signaling sources with their own resolver sources and then extrapolating, APNIC calculated that only 0.05 percent of Internet users would be negatively affected by the root KSK roll.5 Looking forward, the ICANN org will soon reach out to the 1,000 Internet Service Providers (ISPs) with the most active resolver traffic that suggests DNSSEC validation has been enabled in order to ensure they aware that the root KSK roll will occur on 11 October 2018. Those ISPs will also be surveyed on their preparation plans for the rollover, which may cause those resolver operators to become more aware of the KSK rollover. Since the first announcement of the development of plans to roll the trust anchor in 2015, the ICANN org has maintained an outreach campaign that has (to date) included nearly 100 speaking engagements at international, regional, and national conferences, and more than 150 news stories in the technical press. The ICANN org has also published nine blog articles related to the trust anchor rollover and continues to reach out to the ISPs that have validating resolvers in their networks but which, from RFC 8145 data, do not appear to have the new trust anchor configured. As a result of these efforts and the data we have been able to collect, the ICANN org has increased confidence that the root KSK rollover planned for 11 October 2018 will have the potential to affect only a tiny fraction of DNS users. 1 https://www.iana.org/dnssec/icann-dps.txt 2 https://datatracker.ietf.org/doc/rfc5011/ 3 https://datatracker.ietf.org/doc/rfc8145/ 4 http://root-trust-anchor-reports.research.icann.org/ 5 http://www.potaroo.net/ispcol/2018-04/ksk.pdf [PDF, 184 KB […]

  • A Review of Our FY18 Middle East Journey
    on July 18, 2018 at 7:00 am

    The year was filled with accomplishments as well as challenges for ICANN in the Middle East. As we build upon our accomplishments and learn from the challenges, we take this opportunity to present a report on our regional activities. But before doing so, we'd like to thank each of our community members in the Middle East for their tireless efforts and collaboration, leading us to where we are now, with a bright future of ICANN activities in the region. The report is built upon ICANN's Middle East Global Stakeholder Engagement (GSE) team activities in FY18, with a focus on building capacity and raising awareness around ICANN and the wider Internet ecosystem. The report highlights include: Regional participation rates at ICANN Public Meetings Regional events, webinars, and workshops Academic engagements Regional studies Community feedback The report also includes ICANN regional community member and participant surveys to assess the efficiency of our efforts in the region. Among them is a survey on ICANN's FY18 Middle East Engagement. To see the results of this survey, click here [PDF, 111 KB]. You can review the full report here [PDF, 878 KB], and contact us at meac.swg@icann.org for feedback or questions. […]

  • Enforcing the Temporary Specification
    on July 16, 2018 at 7:00 am

    In May, the ICANN Board adopted the Temporary Specification for gTLD Registration Data, modifying our agreements with registries and registrars to comply with the European Union's General Data Protection Regulation (GDPR). Since then, ICANN Contractual Compliance has received a number of questions regarding how we would enforce these new provisions. The purpose of this blog is to describe our approach to enforcing the Temporary Specification, explain how to file complaints about potential violations of the new provisions, and share information on some of the issues we have seen so far. As noted at the Global Domains Division (GDD) Industry Summit in May and at the ICANN62 Policy Forum in June, ICANN Contractual Compliance is enforcing the requirements of the Temporary Specification as of 25 May 2018, as it does any other ICANN agreement or policy requirement. This is done through the Contractual Compliance function, which employs the same approach and process for all enforcement areas. Details regarding this approach and process can be found here. All contracted parties are advised to review the Temporary Specification carefully. Many of the requirements apply even if the registry or registrar is not in the European Union and has no registrations from the European Economic Area. Enforcement of the Temporary Specification applies to all ICANN contracted parties. For a high level review of the Temporary Specification, ICANN also published and regularly updates a Frequently Asked Questions document. One recurring concern we have received is how ICANN Contractual Compliance will obtain non-public registration data that is required to process a complaint. Among the complaints received to date, ICANN Contractual Compliance has received two alleging denial of access to non-public registration data for legitimate purposes. Most of the other complaints received concern the availability of data published in WHOIS. For registrars, some of the registration data issues include: Over-redacting public registration data, e.g.: All contact fields are redacted when only some should be; Missing Administrative/Technical email field and/or value; Missing Registrant Organization/State/Province/Country field and/or value; and Redacting privacy/proxy information Non-compliant redacted fields e.g., missing anonymized email and/or webform to contact Registrant/Admin/Tech contact or using non-compliant values in the field for ex. "00000" Registrar appears to be using registry WHOIS data causing endless loop of referral from registry to registrar data Transfer requests being denied due to non-functional anonymized email address for registrant Some of the registry issues include: Missing required Registrant/Admin/Tech Email (requirement for registries) Required Registrant/Admin/Tech Email message in legal disclaimer only Not providing full registration data to the Uniform Rapid Suspension System (URS) provider Registry providing thick Bulk Registration Data Access (BRDA) files to ICANN instead of thin data We have also received a number of questions regarding the process for filing complaints alleging noncompliance with the Temporary Specification. As many have observed, there is not a "Temporary Specification" complaint form. To file a complaint about potential violations of the Temporary Specification or any other part of the agreements, please use the most relevant form published on the ICANN.org compliance page. ICANN Contractual Compliance will process complaints regardless of the form used. I hope this information is helpful. If you have any other questions or concerns regarding enforcement of the Temporary Specification, please let us know by emailing either the Contractual Compliance department at compliance@icann.org or me at Jamie.hedlund@icann.org. […]

  • Data Protection/Privacy Update: Additional Guidance from the European Data Protection Board
    on July 13, 2018 at 7:00 am

    The ICANN community has been engaged in focused discussion and engagement about the impact of the European Union's General Data Protection Regulation (GDPR) on the WHOIS system over the past year. During this time, ICANN org worked with the community to develop an interim approach for how ICANN and gTLD registries and registrars could continue to comply with ICANN agreements in relation to the GDPR. This interim solution was adopted by the ICANN Board in May 2018 as the Temporary Specification for gTLD Registration Data. The community continued discussions during ICANN's recent meeting in Panama (ICANN62), which included discussions about initiating policy development work for a long-term solution, as well as a possible unified approach to allow continued access to full WHOIS data to third-parties with a legitimate interest. You can find key updates, documents, legal analyses, guidance from European data protection authorities, and inputs from the community about this topic on our Data Protection/Privacy Issues webpage. An important letter [PDF, 764 KB] of note, was received by ICANN on 5 July 2018, from the European Data Protection Board (EDPB) which provided additional guidance that may help significantly to advance the ICANN community's discussion on this important issue. We are very grateful to the EDPB for its guidance and willingness to engage with ICANN.  We are carefully evaluating the additional guidance concerning our compliance with the GDPR, as it relates to publication and access to personal data which is processed in the context of ICANN's coordination of the WHOIS through its contracts with its 2,500 domain name registries and registrars. This blog will address what we are looking at from the letter and why we think the guidance is so important. Below I will highlight some of the key points in the letter and share our initial thinking about possible options for incorporating this guidance into WHOIS in the coming weeks and months. The EDPB's letter provides answers to some of the open questions from ICANN and the ICANN community relating to ICANN's approach in the Temporary Specification. A good example, on a specific open question concerning registrations of legal persons and whether such registrations are impacted by the GDPR, the EDPB advises that it "considers that personal data identifying individual employees (or third parties) acting on behalf of the registrant should not be made publically available by default in the context of WHOIS. If, on the other hand, the registrant provides generic contact email information (e.g. admin@domain.com), the EDPB does not consider that the publication of such data in the context of WHOIS would be unlawful…." Second, the EDPB's letter provides important guidance to advance recent community discussions about a unified access model for how legitimate users of WHOIS data could continue to have access to non-public data. The EDPB notes that non-public WHOIS data could be made available to third parties "provided that appropriate safeguards are in place to ensure that the disclosure is proportionate and limited to that which is necessary and the other requirements of the GDPR are met…." The EDPB confirms its expectation of ICANN developing "a WHOIS model which will enable legitimate uses by relevant stakeholders, such as law enforcement…" This is a strong indicator that we will receive additional inputs were the community to continue its work and come together to identify a method providing access to non-public WHOIS data consistent with the law. The EDPB letter provides helpful insight into transparency requirements that should be part of a model, including appropriate logging of data requests, as well helpful suggestions in the event ICANN is considering a model that uses codes of conduct and accreditation as the approach to providing access to the data. Third, the EDPB highlights some areas where ICANN may provide additional clarity about GDPR compliance as it relates to the global WHOIS system. The areas identified by the EDPB relate to ICANN's purposes for processing gTLD registration data, data collection, as well as the appropriate period for retaining personal data.  Last, the EDPB letter makes reference to ICANN's ongoing legal proceedings in Germany against the registrar EPAG, with specific references to the clarifications ICANN provided in its court filings concerning administrative and technical contact details that are collected as part of a WHOIS record. Because of this reference, earlier this week, ICANN submitted the EDPB's letter to the court for its consideration. A copy of this submission will be published on our Litigation Documents webpage. We are carefully considering the guidance provided by the EDPB to inform the ICANN Board whether clarifications, changes or implementation adjustments may be needed to the Temporary Specification adopted on 17 May 2018. We also are evaluating this guidance as it relates to the Framework Elements for a Unified Access Model, possible contractual compliance actions against contracted parties, as well as the ongoing legal proceedings in Germany where ICANN asked the Regional Court in Bonn for assistance in interpreting the GDPR in order to protect the data collected in WHOIS. We would encourage the community to read the full of the EDPB letter, share your thoughts and continue to participate in discussions we will have over the coming months. We also hope that the EDPB's guidance will be a helpful input to the important policy work being conducted in the expedited policy development process that is being initiated by the GNSO Council. We look forward to continuing to work with you, and we are hopeful that we can continue the progress of the collective ICANN community on these important issues. We will continue to keep the community apprised of developments, and please also see our Data Protection/Privacy and provide any input through gdpr@icann.org. […]

ICANN Announcements

ICANN Announcements ICANN Announcements

  • ICANN Request to Preserve WHOIS Data Referred to German Appeal Court
    on July 19, 2018 at 7:00 am

    LOS ANGELES – 19 July 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) was informed yesterday that the Regional Court in Bonn, Germany, has decided to refer to the Higher Regional Court in Cologne, Germany, the injunction proceedings ICANN initiated against EPAG, a Germany-based, ICANN-accredited registrar that is part of the Tucows Group. ICANN filed the injunction proceedings seeking assistance in interpreting the European Union's General Data Protection Regulation (GDPR) in order to protect the data collected in WHOIS. In its initial ruling, the Regional Court determined that it would not issue an injunction against EPAG. ICANN appealed this decision. Upon receipt of the appeal, the Regional Court exercised its option to re-evaluate its decision instead of immediately forwarding the matter to the Higher Regional Court to address the appeal. In referring the matter to the Higher Regional Court in Cologne, the Regional Court did not change its original determination not to issue an injunction against EPAG. The Regional Court also rejected the alternative claims submitted by EPAG in recent court filings. Notably, the Regional Court issued this second ruling without consideration of the additional court filings submitted earlier this week by ICANN and ICANN's Intellectual Property Constituency. Those filings will be part of the record to be transferred to the Higher Regional Court for the appeal. ICANN will continue to pursue this matter as part of its public interest role in coordinating a decentralized global WHOIS for the generic top-level domain system. ICANN awaits further direction from the Higher Regional Court on next steps, which could include referring the matter to the European Court of Justice, issuing a decision based upon the papers already submitted, requesting additional briefings or scheduling a hearing with the parties. Background: On 25 May 2018, ICANN filed the injunction proceedings against EPAG. ICANN asked the Court for assistance in interpreting the GDPR in an effort to protect the data collected in WHOIS. ICANN sought a court ruling to ensure the continued collection of all WHOIS data. The intent was to assure that all such data remains available to parties that demonstrate a legitimate purpose to access it, and to seek clarification that under the GDPR, ICANN may continue to require such collection. ICANN filed the proceedings because EPAG had informed ICANN that as of 25 May 2018, it would no longer collect administrative and technical contact information when it sells new domain name registrations. EPAG believes collection of that particular data would violate the GDPR. ICANN's contract with EPAG requires that information to be collected. EPAG is one of over 2,500 registrars and registries that help ICANN maintain the global information resource of the WHOIS system. ICANN is not seeking to have its contracted parties violate the law. Put simply, EPAG's position spotlights a disagreement with ICANN and others as to how the GDPR should be interpreted. On 30 May 2018, the Regional Court determined that it would not issue an injunction against EPAG. In rejecting the injunctive relief, the Court ruled that it would not require EPAG to collect the administrative and technical data for new registrations. However, the Court did not indicate in its ruling that collecting such data would be a violation of the GDPR. Rather, the Court said that the collection of the domain name registrant data should suffice in order to safeguard against misuse in connection with the domain name (such as criminal activity, infringement, or security problems). The Court reasoned that because it is possible for a registrant to provide the same data elements for the registrant as for the administrative and technical contacts, ICANN did not demonstrate that it is necessary to collect additional data elements for those contacts. The Court also noted that a registrant could consent and provide administrative and technical contact data at its discretion. On 13 June 2018, ICANN appealed the Regional Court's ruling to the Higher Regional Court of Cologne, Germany, and again asked for an injunction that would require EPAG to reinstate the collection of all WHOIS data required under EPAG's Registrar Accreditation Agreement with ICANN. In addition to the court proceedings, ICANN is continuing to pursue ongoing discussions with the European Commission and the European Data Protection Board to gain further clarification of the GDPR as it relates to the integrity of WHOIS services. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. […]

  • How to Get Involved: Launch of the EPDP on the Temporary Specification for gTLD Registration Data
    on July 19, 2018 at 7:00 am

    LOS ANGELES – 19 July 2018 – Today, the Generic Names Supporting Organization (GNSO) Council initiated the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Read the GNSO Chair Heather Forrest's blog for more details. Unlike other GNSO PDP efforts, which are open for anyone to join, the GNSO Council has decided to limit the membership composition of this EPDP. This decision is primarily based on the need to complete the work in a relatively short timeframe and to resource the effort responsibly. As such, GNSO Stakeholder Groups, the Governmental Advisory Committee (GAC), the Country Code Supporting Organization (ccNSO), the At-Large Advisory Committee (ALAC), the Security and Stability Advisory Committee (SSAC), and the Root Server System Advisory Committee (RSSAC) have each been invited to appoint up to a set number of members and alternates, as outlined in the EPDP Team Charter [PDF, 523 KB]. In addition, the ICANN Board and ICANN Org have been invited to assign a limited number of liaisons to this effort. However, that does not mean that members of the ICANN community cannot be involved if they are not appointed members, alternates or liaisons. One can follow the deliberations of the EPDP Team by signing up as a mailing list observer, follow the meetings via real-time audio cast, and check the recordings and transcripts accessible to the public. Furthermore, the Charter dictates that the EPDP Team should make provisions as part of its work plan to provide regular updates to the ICANN community and others interested, for example, through newsletters and webinars. Moreover, the EPDP Team is required to reach out at an early stage to GNSO Stakeholder Groups and Constituencies as well as other ICANN Supporting Organizations and Advisory Committees to request input. Last but not least, everyone will be invited to comment on the EPDP Team Initial Report once it is published for public comment. Per the EPDP procedures, the EPDP Team is expected to carefully consider and analyze all input received through the public comment forum. Further details on how to get involved are included hereunder. The GNSO Council hope that the ICANN community will make use of these opportunities to closely follow the EPDP Team deliberations! Mailing List Observers One can become an observer of the EPDP Team mailing list on a read-only basis. Sign up here: https://goo.gl/forms/iZg5JWHOnERsoEMI2. The names of mailing list observers will also be published on the EPDP wiki space. Conference Call Audio Cast While participation on EPDP Team conference calls is restricted to appointed members and liaisons only, non-members are able to listen in real-time via an audio cast. The audio cast will begin streaming a few minutes before the start of each conference call: Listen in via a web browser: http://stream.icann.org:8000/stream01 Listen in via an application (such as iTunes): http://stream.icann.org:8000/stream01.m3u Check the EPDP Team conference calls on the GNSO Master Calendar. Recordings, Transcripts & Materials All EPDP Team conference calls will be recorded and transcribed. Recordings, transcripts as well as any notes and action items will be made available on the GNSO Master Calendar. In addition, all EPDP related materials, including recordings, transcripts, background documents, and team output, can be found on the EPDP wiki space. Frequently Asked Questions ICANN Org has gathered questions received on the EPDP and will continue adding questions to the live Frequently Asked Questions document as they are received. About EPDP On 17 May 2018, the ICANN Board adopted the proposed Temporary Specification for gTLD Registration Data. This is an interim measure to bring existing WHOIS obligations in line with requirements of the European Union's General Data Protection Regulation. This also triggered the GNSO Council to undertake a policy development process to confirm, or not, the Temporary Specification as a Consensus Policy within 12 months of its implementation effective date (25 May 2018). The GNSO Council agreed that an EPDP provides the best opportunity to meet this timing requirement. To determine the proposed path forward, a Drafting Team was formed, consisting of Council leadership and interested Council members. The Drafting Team developed an Initiation Request [PDF, 390 KB] for an EPDP and a proposed EPDP Team Charter. During its meeting on Thursday, 19 July 2018, the GNSO Council passed the motion to initiate the EPDP and to adopt the EPDP Team Charter [PDF, 523 KB]. For further information, please email gnso-secs@icann.org. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. […]

  • 2018 Nominating Committee Update on Candidate Selections
    on July 17, 2018 at 7:00 am

    LOS ANGELES – 17 July 2018 – The 2018 Nominating Committee (NomCom) is pleased to announce that the selection of all 2018 open ICANN leadership positions was finalized by the Committee at ICANN62 in Panama City, Panama. The selections for the three ICANN Board positions were decided unanimously. The ICANN organization has sent out communications to the successful candidates and any alternates, as well as to those who made it to the final round but were not selected this year. The NomCom plans to make a public announcement of the successful candidates in August 2018. The 2018 NomCom would like to thank the Board, Advisory Committees, Supporting Organizations, stakeholder groups, and constituencies for their support with outreach and recruitment, as well as their assistance in outlining requested criteria for the open positions. The NomCom encourages the ICANN community to continue its assistance in recruiting candidates for the 2019 NomCom. For more information on the 2018 NomCom, including timeline and work phases, please visit https://www.icann.org/nomcom2018. […]

  • Successful Candidates Announced for ICANN63 Fellowship
    on July 16, 2018 at 7:00 am

    LOS ANGELES – 16 July 2018 - The Internet Corporation for Assigned Names and Numbers (ICANN) organization is pleased to announce the 45 individuals from 39 countries that have been selected to participate in the ICANN Fellowship Program at ICANN63 Annual General in Barcelona, Spain, from 20-25 October 2018. The successful candidates represent all sectors of society including, civil, government, ccTLD operations, academia, business community, technical, security, and end user groups. The Fellowship Program seeks out individuals who are interested in, or already engaged in, the various aspects of ICANN's work in policy building, the operation of the Domain Name System, and the security and stability of the global Internet. The goal of the program is to help create a broader and more diverse base of knowledgeable constituents. Priority is given to candidates currently living in underserved and underrepresented communities around the world, representing diversity of gender, sector, region, experience, expertise, and financial need. The ICANN org received a total of 471 applications for the ICANN63 Fellowship Program. Click this link to see the list of selected candidates and to learn more about the Fellowship Program. About ICANN ICANN’s mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. […]

  • ICANN Board of Directors Submits Comments Regarding NTIA's Notice of Inquiry on International Internet Policy Priorities
    on July 13, 2018 at 7:00 am

    LOS ANGELES – 13 July 2018 – The Board of Directors of the Internet Corporation for Assigned Names and Numbers (ICANN) submitted comments [PDF, 320 KB] today in response to the United States Department of Commerce National Telecommunications and Information Administration (NTIA) Notice of Inquiry (NOI) on International Internet Policy Priorities. In its comments, ICANN's Board of Directors highlighted the success of the multistakeholder model and enhancements made to the organization's accountability mechanisms during the IANA stewardship transition. The comments also pointed to the high customer satisfaction levels delivered by the operator of the Internet Assigned Numbers Authority (IANA) functions, Public Technical Identifiers (PTI). For more information about the NTIA's NOI, please visit https://www.ntia.doc.gov/federal-register-notice/2018/notice-inquiry-international-internet-policy-priorities. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. […]