ICANN Blog

ICANN Blog ICANN Blog

  • Final Proposed FY19 Operating Plan and Budget
    on May 21, 2018 at 7:00 am

    Today, we published the final proposed FY19 Operating Plan and Budget and submitted it to the ICANN Board for consideration at the meeting on 30 May 2018. This is an important step in the process to ensure transparency so that you – and the rest of the ICANN community – can see what exactly is sent to the Board before it is adopted. I want to thank you for your comments and productive discussions on the budget. I was very pleased that we received over 185 comments through the public comment process, in addition to the many productive discussions we had, especially during ICANN61. As a result of your feedback and comments, we've made a few suggested changes to the budget. The Fellowship Program received an increase from 30 to 45 seats per meeting, based on your feedback. In addition, the ICANN organization will be seeking community feedback on the entire Fellowship Program in the next few months. We heard your concerns about the reduced Community Regional Outreach Program (CROP) funding, and as a result, its funding for outreach is reinstated at $50,000. We will also be progressively decreasing funding for the ICANN Wiki from $66,000 in FY19 to a commitment of $33,000 for FY20, based on your comments. In addition, budget was reallocated for the General Data Protection Regulation (GDPR), and data protection and privacy in FY19, as it is prudent planning to anticipate increased expenses next year. This year was the first time we merged the Additional Budget Request process with the Operating Plan and Budget process. In Document 2 [PDF, 621 KB] on page 26 you can see what additional budget items were approved. We are also holding a webinar on 24 May at 14:00 UTC, where you can learn more about these changes and ask questions. Here is the link to join: https://participate.icann.org/finance/. I encourage you to read the Executive Summary in Document 1 [PDF, 305 KB]. Thank you again for contributing your comments and feedback. It is a testament to the multistakeholder model in action. […]

  • Chair's Blog: Approving the Temporary Specification for gTLD Registration Data and Next Steps
    on May 17, 2018 at 7:00 am

    The ICANN Board's approval today of the proposed "Temporary Specification for gTLD Registration Data" is an important step towards bringing ICANN and its contracted parties into compliance with the European Union's General Data Protection Regulation (GDPR). The Board took this action so that ICANN and its contracted parties may remain in compliance with both existing contractual requirements and community-developed policies as they relate to WHOIS. The adoption of this Temporary Specification is a major and historic milestone as we work toward identifying a permanent solution. The ICANN org and community have been closely working together to develop this interim model ahead of the GDPR's 25 May 2018 enforcement deadline, and the Board believes that this is the right path to take. WHOIS is an important system, and preserving it allows it to continue to act as a key tool in the ongoing fight against cybercrime, malicious actors, intellectual property infringement, and more. This Temporary Specification, which is based on the Proposed Interim Compliance Model [PDF, 922 KB], aims to prevent fragmentation of WHOIS and ensure that WHOIS continues to be available, to the greatest extent possible. ICANN's role in providing the technical coordination of the globally distributed WHOIS system is a unique matter, including the public interest nature of WHOIS. In my previous post, I provided the background into how the Board reorganized its Vancouver Workshop to dedicate a significant amount of time, and effort to review and discuss the proposed Temporary Specification, This extra time was also an important opportunity for us to have ICANN org answer our questions and discuss the potential risks that could accompany either no action or adoption of a proposed Temporary Specification. Above all, ICANN's mission, as laid out in the bylaws, is to preserve the Internet's system of unique identifiers. We believe that this Temporary Specification strikes the right balance between upholding that mission and bringing the org and its contracted parties into compliance with this law. As with the requirements of a temporary policy, if still needed, the Board will reconvene in 90 days to reaffirm its adoption. Until that time, I encourage you to submit your thoughts to gdpr@icann.org. And I invite you to visit the dedicated Data Protection/Privacy page to follow the latest updates. Finally, I want to thank the community, ICANN org and the Board for their hard work over the past year in getting us to this place. While I recognize there are important elements remaining to be finalized, the adoption of this Temporary Specification today is a first step, and it sets us on the right path to maintaining WHOIS in the public interest, while complying with GDPR. […]

  • Please Comment on the Timing of Reviews
    on May 16, 2018 at 7:00 am

    The topic of reviews has been an ongoing one over the years. As we went into ICANN61, and during ICANN61, we held many discussions on the budget and priorities for ICANN, as we are working to find ways to operate more efficiently and effectively, while considering the availability of the community and our resources. One theme that continued to arise during those discussions was community member concerns and observations regarding the number of concurrent reviews in the context of volunteer and resource strain – for example, currently, there are eleven reviews running at the same time. Based on those discussions, we opened two Public Comment periods to provide transparency and get input on a range of available options, and to understand which options – or new suggestions - the community would support to alleviate the existing strain on volunteer and ICANN resources as it pertains to reviews, without diminishing ICANN's accountability. To build on feedback from the community, we have developed initial short and long-term options to provide more reasonable scheduling of ICANN reviews that aim to help meet ICANN's accountability and transparency obligations in a more practical and sustainable manner. We are inviting public comment on the short-term and long-term options. After Public Comment closes, we will analyze the comments that were received and coordinate with the Organizational Effectiveness Committee of the Board (OEC) to identify whether there is agreement in the community and if so, recommendations to the Board on the paths forward. The short-term options involve the third Accountability and Transparency Review (ATRT3) and the second Registration Directory Service Review (RDS-WHOIS2). The options for ATRT3 range from maintaining status quo, to moving forward with some aspects of the review (such as a focus only on the evaluation of prior review recommendations), to deferring the start of ATRT3 for approximately one year. The options for RDS-WHOIS2 similarly range from keeping the status quo by continuing the review work under way, to limiting the work to the evaluation of prior review recommendations only, to pausing the work. We recognize the extensive work and progress the RDS-WHOIS2 Review Team has accomplished so far and thank the Review Team for their efforts, and encourage the team to participate in this Public Comment. ICANN organization will of course continue our full commitment and support with both RDS-WHOIS2 and ATRT3 as planned. Should the public comment process and input indicate community agreement for another approach, that will then be implemented together with the community. To find the list of the short-term options along with advantages, disadvantages, please click here [PDF, 140 KB]. Please share your public comment on short-term options by 6 July 2018. The long-term options aim to provide scheduling flexibility with appropriate checks and balances by the community and the Board. These options are based on several principles, including: aiming for no more than three to four reviews per year, recognizing limited community resources, ensuring adequate funding for reviews, and ensuring efficiency and effectiveness of the reviews. Long-term options include: staggering of the reviews adding new timing criteria providing scheduling flexibility to the timing of reviews outlined in the Bylaws. To find the list of the long-term options, along with advantages, disadvantages, and potential Bylaws implications, please click here [PDF, 116 KB]. Please share your public comment on the principles that would inform long-term options by 20 July 2018. If you would like to invite us to present options and hold a Q&A with your constituency via a remote call, please contact us: reviews@icann.org. Webinar Details & How to Attend Two webinars will also be held to help the ICANN Community understand the proposals and provide additional opportunity for Q&A. Webinar 1: 07 June 2018: 5:00-6:00 UTC [local time] Webinar 2: 07 June 2018:17:00-18:00 UTC [local time] To participate, please request a calendar invitation by sending your email request to mssi-secretariat@icann.org and indicate which webinar you will join. I encourage you to please help ICANN improve the challenging timing of reviews by providing your input, including if you have other suggestions. Also by sharing this call to action with your fellow community members to encourage their input. Thank you for your time, participation, and support. […]

  • مدونة رئيس مجلس الإدارة: ملخص لورشة عمل مجلس الإدارة في فانكوفر
    on May 14, 2018 at 7:00 am

    خلال عطلة نهاية الأسبوع اجتمع مجلس إدارةICANNفي الفترة 11-13 مايو في فانكوفر بكندا. وعقدنا ثلاث جلسات عامة واجتماعًا عامًا لمجلس الإدارة، وآمل أن تتمكنوا من الانضمام إلى بعض منها. في صباح اليوم الأول من ورشة العمل، يوم الجمعة، بدأنا بالاجتماع مع الرؤساء المشاركينللجنة الاستشارية لنظام خادم الجذر(RSSAC) لنفهم بصورة أفضل عملهم، القضايا التي يستشرفونها وأولوياتهم. قضينا بعد ذلك معظم اليوم في الجلسات لمناقشة نهجنا في التخطيط الاستراتيجي، التوقعات والاتجاهات الاستراتيجية الطويلة الأجل، كجزء من الحوار لنضع مع المجتمع التكرار التالي لخطةICANN الاستراتيجية الخمسية الجديدة للفترة 2021-2025. قدم يوران ماربي، رئيس والمدير التنفيذي،ICANN، إلى مجلس الإدارة تحديثًا موجزًا بشأن التوقيت المتوقع للبند المؤقت المقترح لبيانات التسجيل لنطاقاتgTLD. وكما قد تكونوا قد قرأتم فيمدونة المشاركةالخاصة به في هذا الموضوع، فنحن، كمجلس إدارة، دعمنا توصيته بإصدار الوثيقة إلى المجتمع ومجلس الإدارة في نفس الوقت مساء 11 أيار (مايو). ومن أجل أن نخصص الاهتمام المناسب لمراجعة البند المؤقت المقترح، قمنا بإعادة تنظيم ورشة العمل لاستيعاب مراجعة شاملة ومناقشة خلال عطلة نهاية الأسبوع.  لقد كان من الأهمية القصوى بالنسبة لي، ولمجلس الإدارة بأكمله، أن يكون لدينا الوقت الكافي لاستيعاب هذه الوثيقة ومناقشتها. لذلك قررنا عقد الجلسات العامة المخطط لها، لكن تمت إعادة جدولة الجلسات الأخرى.  كما قررنا أن ندفع وقت بدئنا صباح السبت إلى الساعة 10:00 صباحًا حتى يتاح لنا الوقت لقراءة الوثيقة وتحديد الأسئلة والتعليقات. يوم السبت اجتمعنا وبدأنا مناقشاتنا، وكل عضو من أعضاء مجلس الإدارة طرح الأسئلة وقدم الأفكار إلى نظر فريق مؤسسةICANN. تم تجميع المناقشات بصورة عامة في المجموعات التالية: كيف يُسهِّل البند المؤقت المقترح الامتثال للقواعد العامة لحماية البيانات GDPR الإرشاد بشأن معالجة أو إدخال تفسير المصطلحات الناشئة عن GDPR إمكانية استخدام عناوين البريد الإلكتروني الشائعة مجهولة الهوية عبر التسجيلات حقوق الوصول / آليات الاعتماد قضايا مهمة لعمل المجتمع الإضافي، مثل العمل المستمر لوضع نموذج الاعتماد الحاجة العامة لبند مؤقت احتياجات ICANN لإنفاذ الامتثال القدرة على تحديث البند المؤقت إذا لزم الأمر كانت مناقشتنا مفصَّلة، أثيرت قضايا صعبة، وكانت مناقشتنا قوية. واستغرقنا الوقت بقدر ما نحتاج لمراجعة البند المؤقت المقترح، وفي نهاية اليوم وضعنا خطة لمواصلة المناقشة يوم الأحد. عقدنا أيضا جلستين علنيتين يوم السبت، واحدة بقيادة أكرم عطا الله، بشأن مكتب مقاصة العلامات التجارية فيما يتعلق بمناقشة مستمرة مع مجموعة أصحاب المصلحة للسجلات، وأخرى، بقيادة مارتن بوتيرمان، بشأن بطاقة نتائج اللجنة الاستشارية الحكوميةGAC، رداً على القضايا التي أثارتهاGACفي بيانها الرسمي في سان خوان. صباح يوم الأحد، استأنفنا الاجتماع، وضعنا جدول أعمالنا لهذا اليوم، وبدأنا مناقشة خطة المراجعات لوثيقة البند المؤقت المقترح. واستؤنفت المناقشات الكاملة والحوار، طُرحت الأسئلة وحدثت المداولات بطريقة منفتحة وبنّاءة للغاية.  أردنا التأكد من أن جميع أسئلتنا قد تم تناولها وأن هناك خطة لمواصلة إدخال التغييرات التي تعكس القضايا التي أثارناها. تستطيعون رؤية التغييرات الناتجة في البند المؤقت المنقح التي أصدرتها مؤسسةICANNهنا[PDF, 152 KB]. ثم قمنا بنقل اتجاهنا لمناقشة العملية الأوسع حول إمكانية اعتماد البند المؤقت المقترح. لقد تأملنا وناقشنا ما إذا كان لدينا، كمجلس إدارة، الوقت الكافي لإكمال محادثتنا بشأن بند مؤقت مقترح منذ صدوره يوم الجمعة 11 أيار (مايو). وكان قرارنا بشأن هذه النقطة "بالرفض". لقد حققنا تقدماً كبيرا بقضاء ما يقرب من 16 ساعة في ورشة عمل مجلس الإدارة بشأن هذا الموضوع المهم، لكننا قررنا معًا تأجيل تصويتنا على اعتماد البند المؤقت المقترح. وسوف يتيح هذا لنا الفرصة لتعزيز مناقشتنا، ولنشارك مع المجتمع البند المؤقت المنقح الذي يعكس توضيحاتنا. بعد ذلك، وكما هو مخطط، قاد مارتن بوتيرمان جلسة علنية بشأن التقدم المحرز في ضوء الأولويات التشغيلية لمجلس الإدارة للسنة المالية 2018، مع التركيز على العمل الذي تم إنجازه بشأن الأهداف منذ أن دوَّنت بشأن أولوياتناهنا. ناقشنا بعد ذلك مسارا للمضي قدماً، إذا كان يجب اعتماد البند المؤقت المقترح. وتضمن ذلك محادثة حول بدء تشاور مجلس الإدارة وGACالرسمي وعملية وضع سياسات جديدة لتحقيق توصيات بشأن نموذج نهائي، وكذلك القدرة على إدخال تغييرات مؤقتة على البند المؤقت إذا كانت ضرورية حتى يتوفر النموذج النهائي. وكمجموعة، ناقشنا بعد ذلك أفكارًا حول المخاطر المحتملة التي قد تصاحب إما عدم اتخاذ إجراء أو اعتماد البند المؤقت المقترح. كما ناقشنا أفضل طريقة لإبقاء المجتمع على علم بالتقدم المحرز والعملية المؤدية إلى القرار النهائي الذي سنتخذه. وإحدى نتائج تلك المحادثة هي مستوى التفصيل المقدم في هذه المدونة. واتفقنا أيضا مع مؤسسةICANNلعقدندوة مجتمعية عبر الويبفي 15 أيار (مايو)، من 09:15 إلى 10:30 بتوقيت المحيط الهادئ الصيفي (16:15-17:30 بالتوقيت العالمي المنسق) لمناقشة هذا الموضوع. في نهاية اليوم، في تمام الساعة 17:00 بالتوقيت المحلي، عقد مجلس الإدارة اجتماعًا كاملاً لمجلس الإدارة كما نجتمع عادةً. أصدر مجلس الإدارة قرارًا يشير إلى أننا بصدد اتخاذ قرار بشأن اعتماد البند المؤقت في 17 أيار (مايو) 2018 أو حول ذلك التاريخ. وكما هو موضح في القرار، يعتزم مجلس الإدارة استخدام هذا الوقت الإضافي للتأكيد على أن التعديلات المناسبة أُدخلت على البند المؤقت قبل اعتماده. وللحصول على مزيد من المعلومات حول ورشة العمل، بما في ذلك محضر اجتماع مجلس الإدارة العام، برجاء الاطلاع علىصفحة مجلس الإدارة. أقدِّر مستوى الوقت، التفاصيل، المناقشة والنظر الذي قدمه مجلس الإدارة لهذا الموضوع – كانت ورشة عمل بنّاءة للغاية. وكان هذا ممكنا فقط بسبب العمل الشاق الذي قامت به مجتمعICANN ومؤسسةICANNفي الوصول بنا إلى هذه المرحلة، ولهذا أشكركم. […]

  • Chair’s Blog: A Wrap-Up of the Vancouver Board Workshop
    on May 14, 2018 at 7:00 am

    Over the weekend the ICANN Board met on 11-13 May in Vancouver, Canada. We held three public sessions and a public Board meeting, and I hope you were able to join some. In the morning of the first day of the workshop, Friday, we began by meeting with the Root Server Security Advisory Committee (RSSAC) Co-Chairs to get a better understanding of their work, what issues they see coming down the road and their priorities. We then spent most of the day in sessions discussing our approach to strategic planning, long-term strategic outlook and trends, as part of the dialogue for the development with the community of the next iteration of ICANN's new Five-Year Strategic Plan for the period 2021-2025. Göran Marby, President & CEO, ICANN, gave the Board a brief update on the anticipated timing of a proposed Temporary Specification for gTLD Registration Data. As you may have read in his blog post on this topic, we, as a Board, supported his recommendation to release the document to the community and the Board at the same time the evening of May 11th. In order for us to devote the proper attention to reviewing a proposed Temporary Specification, we reorganized the workshop to accommodate a thorough review and discussion over the weekend. It was of the utmost importance to me, and the entire Board, that we have the time to digest, discuss and debate this document. We decided, therefore, to hold our planned public sessions, but the other sessions were rescheduled.  We also decided to push our start time on Saturday morning to 10:00 am so that we had time to read the document and identify questions and comments. On Saturday we came together and started our discussions, with each Board member asking questions of, and raising points for, consideration to the ICANN org team. The discussions were broadly grouped into the following buckets: How the proposed Temporary Specification facilitates compliance with GDPR Guidance on addressing or incorporating interpretation of terms arising out of the GDPR Potential for use of common anonymized email addresses across registrations Access rights/accreditation mechanisms Important issues for further community action, such as continued work to develop an accreditation model The general need for a Temporary Specification ICANN's compliance enforcement needs The ability to update the Temporary Specification if needed Our discussion was detailed, challenging issues were raised, and our debate was robust. We took as much time as we needed to review the proposed Temporary Specification, and at the end of the day we had framed a plan for continuing the discussion on Sunday. We also held two public sessions on Saturday, one led by Akram Atallah, on the Trademark Clearinghouse regarding an ongoing discussion with the Registries Stakeholder Group, and another, led by Maarten Botterman, on the GAC scorecard, in response to the issues raised by the GAC in their San Juan Communique. On Sunday morning, we reconvened, set our agenda for the day, and began by discussing the plan for revisions to the proposed Temporary Specification document. Full discussions and debate resumed, questioning and deliberating occurred in a very open and a constructive manner.  We wanted to ensure that all of our questions had been addressed and that there was a plan for continued incorporation of changes that reflected the issues we raised. You will be able to see the resulting changes in the revised Temporary Specification released by ICANN org here [PDF, 152 KB]. We then shifted gears to discuss the broader process around the potential adoption of a proposed Temporary Specification. We reflected and discussed if we, as a Board, had sufficient time to complete our conversation on a proposed Temporary Specification since its release on Friday 11 of May. On this point we decided "no". We had made strides by spending close to 16 hours of the Board workshop on this important topic, but we decided together to postpone our vote on adoption of a proposed Temporary Specification. This will allow us the opportunity to further our discussion, and to share with the community the revised proposed Temporary Specification reflecting our clarifications. Then, as planned, Maarten Botterman led a public session on the progress made against the Board's operational priorities for FY18, highlighting the work that's been done on goals since I blogged about our priorities here. We then discussed a path forward, if a proposed Temporary Specification is to be adopted. This included conversation on initiating a formal Board/GAC consultation and a new Policy Development Process to achieve recommendations on an ultimate model, as well as the ability to make interim changes to a Temporary Specification should they be necessary until the ultimate model is available. As a group, we then discussed ideas about potential risks that could accompany either no action or adoption of a proposed Temporary Specification. We also discussed the best way to keep the community apprised of the progress and the process leading to the eventual decision we will take. One of the results of that conversation is the level of detail provided in this blog. We have also agreed with ICANN org to convene a community webinar on 15 May, from 09:15 to10:30 Pacific Daylight Time (16:15-17:30 UTC) to discuss this topic. At the end of the day, at 17:00 local time, the Board held a full Board Meeting as we usually do. The Board passed a resolution noting our intent to take a decision on the adoption of a Temporary Specification on or about 17 May 2018. As indicated in the resolution, the Board intends to use this additional time to confirm that appropriate modifications are incorporated into the Temporary Specification prior to adoption. For more details on the workshop, including minutes from the public Board Meeting, please see the Board Page. I appreciate the level of time, detail, discussion and consideration that the Board has given to this topic – it was a very instructive workshop. This was only possible because of the hard work of the ICANN community and ICANN org in getting us to this place, and for that, I thank you. […]

ICANN Announcements

ICANN Announcements ICANN Announcements

  • Proposed FY19 Operating Plan and Budget for ICANN Board Adoption Published
    on May 21, 2018 at 7:00 am

    LOS ANGELES – 21 May 2018 – Today, the Internet Corporation of Assigned Names and Numbers (ICANN) published the proposed FY19 Operating Plan and Budget, and Five-Year Operating Plan update, after the review of public comments. In addition, the ICANN organization and Board Finance Committee have approved the Staff Report of Public Comments, which was originally published on 24 April 2018. As indicated in the Staff Report, several changes were approved for incorporation into the proposed documents. The revised documents are posted here, and on the Planning page, with a summary of changes, to ensure visibility and transparency of the final documents sent to the ICANN Board for consideration in its meeting on 30 May 2018. The ICANN org will host a webinar on 24 May at 14:00 UTC where community members can ask questions and learn more about the changes made to the budget. A recording of the webinar will be posted to the community wiki. This year, the Additional Budget Requests were streamlined into the Operating Plan and Budget process. Please see Document 2 [PDF, 621 KB], page 26 to find out what Additional Budget Requests have been approved. 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 Approves Temporary Specification for gTLD Registration Data
    on May 17, 2018 at 7:00 am

    LOS ANGELES – 17 May 2018 – The Board of Directors of the Internet Corporation for Assigned Names and Numbers (ICANN) today approved the proposed "Temporary Specification for gTLD Registration Data." The full text of the Board's resolution is available here. The Board took this action to establish temporary requirements for how ICANN and its contracted parties will continue to comply with existing ICANN contractual requirements and with community-developed policies as they relate to WHOIS, while also complying with the European Union's General Data Protection Regulation (GDPR). "The ICANN Board's approval today of the proposed Temporary Specification for gTLD Registration Data is an important step towards bringing ICANN and its contracted parties into compliance with GDPR," said Cherine Chalaby, ICANN Board Chair. "While there are elements remaining to be finalized, the adoption of this Temporary Specification sets us on the right path to maintaining WHOIS in the public interest, while complying with GDPR before its 25 May enforcement deadline." The Board spent significant time during its Vancouver Workshop reviewing and discussing the proposed Temporary Specification, clearing most of their planned schedule to allow for more time to consider the most appropriate path forward. The ICANN organization has closely worked with stakeholders and the ICANN community to discuss and develop the Temporary Specification, and has maintained an ongoing dialogue with the Article 29 Working Party (WP29) to solicit its feedback and input. "The Proposed Interim Compliance Model is the product of significant collaboration between the org and the community," said Göran Marby, ICANN President and CEO. "With the Temporary Specification now approved by the Board, we can continue working together to identify a permanent solution." The Board's resolution also initiated a community-led policy development process to consider the development and adoption of a consensus policy based on the issues outlined within the Temporary Specification. The Temporary Specification, which reflects ICANN's Proposed Interim Compliance Model [PDF, 922 KB], aims to ensure the continued availability of the WHOIS system to the greatest extent possible while maintaining the security and stability of the Internet's system of unique identifiers, as outlined in its mission and bylaws. Preserving the WHOIS system is critical to the stability and security of the Internet, which allows for the easy identification and mitigation of bad actors, cybercriminals, intellectual property infringement, and other malicious activity online. The Temporary Specification provides a single, unified interim model that ensures a common framework for registration data directory services. It allows registrars and registries, also referred to as ICANN's contracted parties, to continue with the robust collection of registration data from both natural and legal persons, as well as technical information, in connection with a domain name registration. The Temporary Specification only replaces certain provisions in the Registry Agreements and Registrar Accreditation Agreements, as well as policies. All other current obligations remain in force. ICANN's contracted parties would be required to apply the model outlined in the Temporary Specification when processing personal data linked to the European Economic Area (EEA). If impracticable for a contracted party to limit their application of the requirements strictly to the EEA, they may apply the requirements to registrations on a global basis. To ensure compliance with the GDPR, access to personal data will be restricted to layered/tiered access, where only users with a legitimate purpose can request access to non-public data through registrars and registry operators. Until a unified access model is in place, registries and registrars will have to determine which requests are permissible under the law. Alternatively, users may contact either the registrant or listed administrative and technical contacts through an anonymized email or web form available via the registered name's registrar. Registrants may opt to have their full contact information made publicly available. This Temporary Specification has been adopted under the procedure for Temporary Policies outlined in the Registry Agreement and Registrar Accreditation Agreement. Fifteen Board members voted to approve its adoption, representing a unanimous approval among Board members present and meeting the contractual requirement for the Board passing a temporary specification. The Board must reaffirm its temporary adoption every 90 days, and may continue to do so for no more than one year. The ICANN Board, in its resolution adopting the Temporary Specification, has also deferred formal action on certain pieces of advice the Government Advisory Committee (GAC) provided in its San Juan Communiqué. This decision was made at the GAC's request, which was detailed in a letter [PDF, 525 KB] to the Board. The Board will consider if any further action is needed after additional discussion with the GAC. For more information and to follow the latest updates, please visit the dedicated Data Protection/Privacy issues page. 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. […]

  • NextGen@ICANN Application Round for ICANN63 Is Now Open
    on May 15, 2018 at 7:00 am

    LOS ANGELES – 15 May 2018 – Today, The Internet Corporation for Assigned Names and Numbers (ICANN) launched the application round for those interested in participating at the ICANN63 meeting in Barcelona through the NextGen@ICANN Program. This Meeting will take place from 20–26 October 2018. The application round will remain open until 22 June 2018. Successful candidates will be announced on the ICANN website on 30 July 2018. For more information, click 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. […]

  • ICANN Announces DENIC eG as New ICANN-Designated Agent to Support Registrar Data Escrow Services
    on May 15, 2018 at 7:00 am

    LOS ANGELES – 15 May 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) today announced it has entered into an agreement with DENIC eG as an ICANN-designated agent to support Registrar Data Escrow (RDE) services on the ICANN organization's behalf. DENIC eG is a not-for-profit cooperative headquartered in Frankfurt, Germany and is the operator of the ccTLD .DE. ICANN org selected DENIC through a competitive Request for Proposal initiated in August 2017, following requests from the registrar community to expand the RDE program, in part to meet regional challenges such as the European Union's General Data Protection Regulation. Background The Registrar Data Escrow program is intended to protect registrants in the event of registrar failure or termination of a Registrar Accreditation Agreement (RAA). Ensuring the successful transfer of a domain name sponsorship aligns with the ICANN org's objective to support a healthy, stable, and resilient unique identifier ecosystem and is consistent with its Mission and Bylaws (Section 1.1) that states, "ICANN coordinates the allocation and assignment of names in the root zone of the Domain Name System (DNS) and coordinates the development and implementation of policies concerning the registration of second-level domain names in generic top-level domains (gTLDs)." The 2013 Registrar Accreditation Agreement requires registrars to deposit a copy of gTLD registration data with either the ICANN org or with an ICANN-approved RDE agent at its own expense. Since 2007, Iron Mountain has acted as the sole ICANN-designated RDE agent, which has accepted and processed the registrar escrow deposits on behalf of ICANN org. DENIC eG is the second ICANN-designated RDE agent available to registrars. Registrars may also utilize Third Party Providers approved by both ICANN and the registrar; for more information on the Registrar Data Escrow Program and other Third Party Providers see: https://www.icann.org/resources/pages/registrar-data-escrow-2015-12-01-en. […]

  • ICANN and PTI Publish U.S. Tax Returns for FY17
    on May 15, 2018 at 7:00 am

    LOS ANGELES – 15 May 2018 – Today, the Internet Corporation for Assigned Names and Numbers (ICANN) and Public Technical Identifiers (PTI) published their U.S. tax returns (Form 990) for the fiscal year ending 30 June 2017. This is the first time that the recently created PTI has been required to file Form 990. View Form 990 for ICANN for FY17 [PDF, 385 KB]. View Form 990 for PTI for FY17 [PDF, 321 KB]. ICANN and PTI filed Form 990 for the fiscal year ending 30 June 2017 with the Internal Revenue Service (IRS) on 14 May 2018, in compliance with the extended due date of 15 May 2018. Form 990 is the U.S. return for organizations exempt from income taxes under section 501(c) of the Internal Revenue Code. The publication of ICANN’s and PTI’s financial information is part of an ongoing commitment to accountability and transparency. The community is invited to review ICANN's and PTI’s tax returns and to make comments or ask questions. Please contact us at: controller@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. […]