ICANN Correspondence

ICANN Correspondences ICANN Correspondences



  • Data Protection/Privacy Issues: ICANN61 Wrap-up and Next Steps
    on March 21, 2018 at 7:00 am

    I want to thank everyone from across the community who participated in discussions around the ICANN61 meeting on the European Union's General Data Protection Regulation (GDPR) and its impact on registration directory services, as well as ICANN's contracts. Your contributions have helped advance our work to come into compliance with the law. As I noted during ICANN61, we have provided representatives of the Article 29 Working Party with an initial approach to our plan of action, by sharing our "Interim Model for Compliance with ICANN Agreements and Policies in Relation to the European Union's General Data Protection Regulation, (or the "Cookbook") [PDF, 922 KB]. The Cookbook provides explanation and rationale for the developing plan of action. The Cookbook also highlighted and requests guidance on some of the key points of divergence within our community. We will continue to seek guidance on those points of divergence and we will add new information we have gained from the discussions in San Juan in next versions and in our communications with the data protection authorities (DPAs). At the end of March we anticipate having our next interaction with Article 29 representatives since sending them the proposed model. This next stage is critical to determine what appears in the public WHOIS, including what is collected, escrowed and transferred from registrants to registrars and registries. There are open questions about several elements in the Proposed Interim Model and it's important we determine what are the best ways to answer those in a final model. In presenting our plan of action, we want to ensure that access is not lost if an accreditation model is not implemented in time for the GDPR's 25 May 2018 enforcement deadline. We will also highlight again, the importance of additional time to implement our solution. We are very aware of the need for additional time beyond May 2018 to implement a compliance model by which accredited users with a legitimate purpose may gain access to non-public WHOIS data. Feedback may also allow further refinement of the accreditation model. We will share any information that we gain from our next meeting with you by posting it to our Data Protection/Privacy Issues correspondence page. I am grateful for the contribution and spirit of collaboration that I have seen within so many constituencies and stakeholder groups. As noted in my previous blog, ICANN org is committed to finding a single, unified solution for use by all parties. The full community's engagement in this public discussion will help ensure all viewpoints are reflected as we develop a plan of action and a final interim model. In addition, as I noted several times during ICANN61, you can also reach out directly to your DPAs, in particular where you can provide additional information relating to these points of divergence and the impact of not having a plan of action in place by the upcoming May deadlines. We urge those working in parallel on the accreditation model, as well as those working with our Global Domains Division on technical implementation and a timeline, to continue to share their work through the gdpr@icann.org address, and with each other, while heeding the advice that may come from relevant stakeholders. To ensure a unified WHOIS, it is important we work together as ICANN settles on a final model. We welcome all feedback on the Proposed Interim Model, the development of an implementation timeline, as well as the accreditation process. Please send your input to gdpr@icann.org and be sure to review comments received from others in the community here. This is a fast-moving topic, so be sure to follow our Data Protection/Privacy Issues page for the latest updates. […]

  • Chair's Blog: ICANN61 Meeting & Board Workshop
    on March 21, 2018 at 7:00 am

    I would be remiss if I didn't begin this blog by thanking the people of Puerto Rico for such a wonderful experience during ICANN61. The conference center was great, the hosts gracious and the island is recovering after hurricane Maria. I hope to visit Puerto Rico again soon. I would also like to thank the ICANN org staff for their quick work navigating the technical challenges that came with suspending Adobe Connect services during the meeting, and the ICANN community for their good spirits and understanding surrounding the inconveniences. Board Workshop Ahead of ICANN61, the Board held a three day workshop in San Juan on 9,10 & 11 March. The Board Committees met on the first day to take care of their regular business, and then the full Board met for two consecutive days. We held in-depth sessions about policy and advice on priority issues for ICANN61 in preparation for Constituency Day. As you can imagine, a large part of our workshop was taken up with discussions on the European Union's General Data Protection Regulation (GDPR). We also held sessions on Workstream 2 recommendations, the anticipated updates to the Internationalized Domain Name (IDN) Implementation Guidelines, which apply to the IDNs at the second level, the status of work on the Registration Data Services PDP, and on the proposed disbursement mechanisms considered by the Cross Community Working Group on Auction Proceeds. Finally, we reviewed several resolutions which were approved subsequently during the Board formal meeting at the end of ICANN61. Public Meeting Much like at ICANN60, a big focus during the meeting was on data protection and privacy rules, mainly GDPR. I'd like to thank the community for the thoughtful contributions, vibrant conversations and challenges raised during the meeting. I encourage continued participation and engagement as we address near and longer term GDPR compliance issues. Based upon all of your inputs, comments, and submissions, we will in the coming weeks be pursuing a single compliance approach and model. As we work towards this model, please continue to participate and provide your views. We need the community, all of you, to work together to iron out differences. It is important to have a model that has unified community support. Another major topic of conversation was ICANN's Draft FY19 Operating Plan and Budget. I appreciate very much the thoughtful ideas shared and the information exchanges between the community, ICANN org and the Board. It was a really productive conversation. There seemed to be general agreement that we can and should do our work more effectively, more timely and with the efficient utilization of ICANN's resources. The Board is cognizant of concerns around the proposed budget cuts to various community programs and request mechanisms, and considers the comment period, that just ended, to be valuable in ensuring the community has an opportunity to weigh in on priorities. In finalizing the FY19 Budget, all public comments will be taken into account. There were also discussions on the consultation paper on the replenishment of the ICANN Reserve Fund. As always, the Supporting Organizations (SO) and Advisory Committees (AC) made great strides in their work, including: The At-Large Community held sessions on its improvement planning and reviewed comments on several current policy and budget topics, and Regional At-Large Organizations (RALOs) held meetings and events, in particular for the North American and Latin American organizations. The ASO Address Council, with new leadership, held its annual meeting covering regional policy developments, the ASO organizational review and candidates for ICANN Board Seat 9; The Country Code Names Supporting Organization (ccNSO) made progress on the retirement of ccTLDs, and elected Council Chairs and Vice Chairs; The Government Advisory Committee (GAC) completed its Communiqué; The Generic Names Supporting Organization (GNSO) spent significant working group time advancing PDPs on New gTLD Subsequent Procedures, Right Protection Mechanism, and Next Generation Registration Directory Services, and reviewed its policy development work with a report expected soon; The Number Resource Organization (NRO) Chair provided an informative overview about the activities of the Regional Internet Registries at the opening session; The Root Server System Advisory Committee (RSSAC) discussed its Statement on Entries in DNS Root Sources; and The Security and Stability Advisory Committee (SSAC) reviewed the Names Collision and Analysis project and hosted a DNSSEC Workshop. The SO and AC Leaders also started planning for ICANN62, the Policy Forum, in Panama in June 2018. Finally, the Board held a full Board Meeting as we usually do. For more details on the workshop, including minutes from the public Board Meeting, please see the Board Page. The Board will hold its next workshop in May 2018 in Vancouver, Canada, ahead of the GDD Industry Summit, but I expect you will be hearing from me sooner. […]

  • Budget Discussions at ICANN61
    on March 20, 2018 at 7:00 am

    During ICANN61, a major topic of conversation was the FY19 draft Budget and Operating Plan. As you’ve heard from me, 80-85 percent of our budget is already committed to certain projects that are in our Bylaws, our contracts, our operations, and other fixed costs. This means that roughly 15-20 percent of the overall budget can be considered when we are looking at ways to decrease our spending. We must work together to determine the best allocation of the remaining funds, because this is your decision, not mine. One of the things I greatly appreciated about this meeting was the willingness of our community to look at things differently, to try to think outside the box, and to come up with unexpected ideas. For example, in Puerto Rico, we talked with the SO/AC leaders who make up the meeting planning group to explore the key drivers of cost and high-level considerations on how we might be able to make ICANN meetings more efficient and effective. Our next step is to supply a more detailed paper outlining options and recommendations for the group to consider. We also talked a lot about reviews during the meeting, which was a particularly interesting discussion. In the next fiscal year, we have nine reviews running in various stages including a new Accountability & Transparency Review (ATRT3), a continuation of the Registration Directory Services (RDS) Review, and, we expect, the Security, Stability and Resiliency Review 2 (SSR2). Many people are not happy with the high number of reviews because they do not have the time to participate, and raised concerns that for the ATRT3, the Work Stream 2 Accountability recommendations are still being finalized, and for the RDS Review, there is still significant work remaining to address the impacts of the General Data Protection Regulation (GDPR) on the WHOIS system. Delaying either of these reviews would save many hours of volunteer time. Additionally, and more broadly, addressing the timing of reviews, and approach, will contribute to discussing how to make future reviews more efficient and more relevant. Deferring a review that will be impacted by current Policy Development Processes or other outside factors, could have significant savings on productivity and cost. For example, deferring the ATRT3 Review alone would save $700,000 USD, thus impacting next year’s budget. There were also discussions on staggering or phasing implementation of reviews, changing how certain reviews are conducted (limiting travel, number of review team members, clarity on scope or prioritization of recommendations, etc.), or considering the timing of reviews differently, for example timing the start of the next review based on when the implementation of prior review recommendations is complete. Some of these proposals could require Bylaw changes. These ideas are not about getting around the responsibilities detailed in the Bylaws. I can speak for the org, but I am sure the community and Board would agree, we are committed and accountable to conducting the reviews detailed in the Bylaws, and will work with the community to make any necessary adjustments based on community input and agreement. I’ve heard many times now, from various members of the community, about the need to and benefit of coordinating the work plans of the Supporting Organizations, Advisory Committees, Board, and org. The aim would be to reduce the number of parallel tracks being worked on, leading to reduced workloads and increased efficiency in developing policies or community recommendations. This coordination could be organized by developing mechanisms to plan together during the development of the next strategic plan. The ideas stemming from these initial conversations, are just that – initial. It’s important to note that some of the ideas here are inconsistent with the Bylaws, so, if agreed, implementing these ideas may require Bylaw changes. I am beginning to look at what changes might be made to the cycle of reviews embedded in our Bylaws. I am working with my team to determine the best next steps on this, including holding another public comment period about any changes that might have an effect on either Bylaws or policies. I look forward to your comments on the proposal. Ultimately, it is your decision if you would like to accept any change of the Bylaws. I look forward to working together. It was good to see so many of you in Puerto Rico and I hope that you had safe travels home. Now, it’s back to work. […]

  • More Information on the Adobe Connect Issue
    on March 20, 2018 at 7:00 am

    In our last blog on this issue, we reported that our technical teams are testing various scenarios to determine the root cause of the technical issue affecting our use of Adobe Connect. We are investigating whether the issue was caused by the software, or ICANN's configuration, or both. We are continuing to collaborate with CoSo Cloud LLC, our Adobe Connect cloud service provider and, through them, with Adobe. We will continue to provide updates on this issue pursuant to our coordinated disclosure guidelines. This means we will work jointly with CoSo and the person who reported the issue on the investigation and on sharing information about this issue. Until we know more, ICANN's Adobe Connect services will remain offline. In the meantime, we will be rolling out alternative collaboration tools to the community soon, so stay tuned. […]

  • Update on ICANN61 Adobe Connect Issues
    on March 14, 2018 at 7:00 am

    I wanted to provide you with a brief update on the issue with our Adobe Connect services. The issue is one that could possibly lead to the disclosure of the information shared in an ICANN Adobe Connect room. We are still investigating the root cause of the issue. We have formulated different scenarios based on authentication, encryption, and software versions, which we are testing in a controlled fashion in attempt to replicate and understand the root cause of the issue. We are working directly with Adobe and with our cloud service provider to learn more. As a reminder, we continue to offer Livestream video, multilingual audio, and live scribe feeds in the main meeting rooms at ICANN61. We are also accommodating questions and comments via email. For now, the investigation continues and I’ll keep you updated as we learn more. […]

ICANN Announcements

ICANN Announcements ICANN Announcements

  • ICANN63 Fellowship Application Round Now Open
    on March 20, 2018 at 7:00 am

    LOS ANGELES – 20 March 2018 - The Internet Corporation for Assigned Names and Numbers (lCANN) is launching the application round for individuals interested in participating in the ICANN63 Public Meeting through the Fellowship Program. The meeting will take place from 20-26 October 2018 in Barcelona, Spain. The deadline to apply is 27 April 2018, 23:59 UTC. Successful candidates will be announced on 27 July 2018 on icann.org. ICANN Fellowship Program 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 create a more diverse and a broader base of knowledgeable constituents who can engage in the ICANN multistakeholder process and become the new voices of experience in their regions and on the global stage. Since its creation in 2007, the Fellowship Program has built a strong group of individuals who are actively participating in ICANN communities and in other Internet governance entities in the Internet ecosystem. Participation covers a range of activities: Writing articles and blogs Giving online or in-person public comments about bottom-up policy building Participating in Internet conferences and panel discussions Joining working groups Mentoring newcomers Assisting our regional leaders Becoming leaders themselves More information 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. […]

  • Nomination Period for ICANN Multistakeholder Ethos Award Extended
    on March 20, 2018 at 7:00 am

    Nominations Close 28 March 2018 Submit Nominations Via the Ethos Award Nomination Form ICANN is pleased to remind community members that the nomination period for ICANN's Multistakeholder Ethos Award has been extended until 28 March 2018. The ideal recipient(s) will have served in roles in multiple ICANN working groups or committees and collaborated with more than one Supporting Organization and/or Advisory Committee in a significant capacity. Candidates for the award will demonstrate at least five years of participation in the ICANN Community. Candidates will be evaluated by a panel of community members appointed by the Chairs of each Supporting Organizations and Advisory Committees using a merit-based point system evaluated against three criteria: Demonstrated ability to work across community lines with both familiar and unfamiliar ICANN Stakeholders with the aim of consensus building and collaboration that substantiate ICANN's multistakeholder model; Facilitator of dialogue and open discussion in a fair and collegial manner, through the spirit of collaboration as shown through empathy and demonstrating a sincere desire to engage with people from other backgrounds, cultures, and interests; and Demonstrated additional devotional factors exhibited by time spent supporting ICANN's multistakeholder model and its overall effectiveness through volunteer service via working groups or committees. Please submit your nominations via this Nomination Form including detailed information outlining why the nominee meets the award criteria. Any additional information in support of nominations and/or questions about the award process may be submitted via email at ethosaward2018@icann.org. Award recipient(s) will be announced in June 2018 at ICANN62 Panama City. For more insights on the award program, please consult the ICANN Community Wiki. Submit Nominations Via the Ethos Award Nomination Form […]

  • ICANN Community Onboarding Pilot Program Call for Nominations by SOs/ACs
    on March 19, 2018 at 7:00 am

    LOS ANGELES – 19 March 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) has issued a call for nominations from the Supporting Organizations (SOs) and Advisory Committees (ACs) for the Community Onboarding Pilot (COP) Program at ICANN62. The COP seeks to improve ICANN community newcomer engagement and retention rates through mentorship, knowledge, and experience sharing. Nominations are due no later than Monday, 16 April 2018, 23:59 UTC. Additional details can be found here. 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. […]

  • Request for Proposal: ICANN's Open Data Platform
    on March 12, 2018 at 7:00 am

    LOS ANGELES – 12 March 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) is soliciting proposals to identify a provider to supply an Open Data Platform in the form of Software as a Service (SaaS). The Open Data Platform will be used by ICANN to publish as much of its data as possible with open licensing and open API access. The objective of this project is to provide open data on a range of subjects in a reliable and machine-readable form to download and process. The Open Data Platform will be a source system used by those in the ICANN organization and ICANN community who wish to tell a story with data, or provide insights and analysis of data. However, such work is not expected to take place on the Open Data Platform itself. ICANN is seeking to identify a provider to develop this system based on ICANN's requirements, as well as to maintain the system, and develop additional enhancements. For an overview of the RFP including the timeline, please click here [PDF, 320 KB]. Indications of interest should be emailed to OpenDataPlatform-RFP@icann.org. Proposals should be electronically submitted by 23:59 UTC on 18 April 2018 using ICANN's sourcing tool. Access to the ICANN org sourcing tool may be requested via the same email above. 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. […]

  • Successful Candidates Announced for ICANN62 Fellowship
    on March 9, 2018 at 8:00 am

    LOS ANGELES – 9 March 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) organization is pleased to announce that 44 individuals from 34 countries have been selected to participate in ICANN's Fellowship program at the 62nd Public Meeting in Panama City. ICANN62 is scheduled for 24-28 June 2018. It is a Policy Forum, so only alumni of the Fellowship Program were eligible to apply. The selected candidates represent all sectors of society including; civil, government, ccTLD operations, academia, business community, technical, security, and end user groups. The Fellowship program seeks to create a broader and more diverse base of knowledgeable constituents with priority given to candidates currently living in underserved and underrepresented communities around the world, those who represent diversity of gender, sector, region, experience, expertise, and/or have established financial need. 79 Fellowship applications were received from the ICANN62 Fellowship application round. Click this link to see the list of selected candidates and learn more about the Fellowship program. Along with selected Alumni of the program, 15 newcomers have been selected from Latin America and Caribbean region to participate in ICANN62 within the framework of the Regional Newcomers Fellowship Pilot. Read more about the Regional Newcomers Fellowship Pilot here and click this link to see the list of selected candidates. 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. […]