June 2018 - council - lists.icann.org

Notes from GNSO Council - ICANN Board meeting to discuss next steps following the Board's adoption of the temporary specification for gTLD Registration Data
by Marika Konings June 9, 2018

June 9, 2018

Dear All, Please find below the notes from today’s GNSO Council – ICANN Board meeting to discuss next steps following the Board’s adoption of the temporary specification for gTLD Registration Data. Note that the recording and transcript of the meeting will be circulated shortly. These high-level notes are designed to help the Council navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. Best regards, Marika ================== Board-GNSO Council Call Next steps following Board adoption of Temporary Specification 5 June 2018 Questions have been divided into three categories: * Scope * Timing * Participation This is unchartered territory so a degree of flexibility of all involved will be required. Nevertheless, the Council is the manager of the PDP and as such, the Board expects the Council to take on this role and has no intention to interfere. Aim to answer as many questions as possible today and for those for which it is not possible to provide an answer, identify who and when an answer can be provided. Number of questions overlap, including in the questions between the Council and the Board, so not every question may need an answer as it may already get answered in response to another question. (4) What is the intent of the EPDP? Is it simply to confirm the Temporary Specification, or something more? What room is there in scoping to anticipate that the EPDP may conclude that the Temporary Specification cannot be confirmed “as is”, and make changes in order to achieve consensus policy? * Key is flexibility, need to work collegially and flexible. Not set things in stone - deal with issues and problems as they arise. In the Board's view there is room for various outcomes: confirming temporary specification; developing a different approach from what is established in the temporary specification; addressing additional issues that are not specifically identified in the temporary specification but for example, the annex. Is for the GNSO Council to manage, but Board stands ready to assist as needed. Any outcome will obviously need to comply with the law. * 12 month deadline needs to inform the scoping. Need to understand whether some of the additional items called out in the annex could be dealt with differently. (5) The Temporary Specification reasoning for including WHOIS as a security and stability issue is based on the new ICANN Bylaws; at time of contract signing, that wasn’t the case. Doesn’t that open a possible avenue to challenge it altogether? Wouldn’t phasing the EPDP allowing a quick Consensus Policy made of uncontroversial parts of the Temp Spec increase the assurances that this wouldn’t hamper ICANN Org’s compliance ability? * Response to this question needs to be further discussed. (6) What happens should the Board decide to either modify the Temporary Specification or completely replace the temporary specification by a new one at a later point in time? Does this change the scope of the ongoing EPDP (note: Council does not intend to run multiple EPDPs simultaneously), and if so, how is the EPDP expected to deal with such changes while it may be half way through its process? * Need to be flexible. If there is an amendment to the temporary spec, the circumstances need to be considered. An amendment in month 1 may be dealt with differently compared to one in month 11. Similarly the type of amendment - minor or substantial. It may also be possible that a new temporary spec is triggered on a certain issue that in theory would trigger a new PDP, although it might be possible to fold this into the existing PDP. Flexibility is key, need timely communication to ensure that the appropriate approach can be considered factoring in all circumstances. Board does not want to use the temporary specification approach unless absolutely necessary, for example when guidance is received from DPAs that certain elements would need to be changed. * Need some boundaries around how changes are dealt with as that may provide some needed clarity, especially to (E)PDP Team in case changes occur. The more that can be reached agreement on in the early stages, the better. Ensure common understanding of possible scenarios. * Consider parking lot approach to park issues that need to be dealt with, but which may not be urgent. (9) Does ICANN have/will ICANN develop a list of policies and contractual clauses that are impacted by the temporary specification (beyond what is currently identified in the Annex)? This would help with scoping the work. * ICANN Org is in the process of preparing a list which should be ready for sharing shortly. Once published, all input is welcome. ICANN Org to follow up with the Council on the expected timing within 24 hours. If possible, would be helpful to have this document prior to the upcoming Council meeting (12 June). (8) The Temporary Specification covers a number of additional policies that go beyond the requirements of the RA and RAA as they relate to Registration Data Directory Services. How does the Board believe the GNSO Council should handle these areas of overlap? * How does the GNSO currently deal with this? In unchartered territory here as we are working of a temporary specification, that is normally not the scenario in a normal PDP. For example, the temp spec refers to SLAs for RDS services - that would normally be an implementation matter, not a policy matter. Need to consider this question further. (10) What happens if the GNSO is not able to reach consensus at the end of the 1 year period? (see also Timing) * Board to explore other ways forward. Absent another way forward there are things that automatically occur at the end of the 12 month period - temp spec would no longer be in force. Review throughout the 12 month period how things are going, would allow Board to explore alternative ways forward which could potentially buy more time. The longer it takes, the greater the likelihood is that decisions are taken outside of ICANN. If community wants to be in control, needs to work in a timely manner. (11) How does the Board expect the EPDP to follow and/or to incorporate ICANN´s ongoing legal strategy and the decisions of EU country courts? (12) As evidenced by the recent legal action involving EPAG, there are parties who believe aspects of the Temporary Specification as written are not compliant with the GDPR. How does the Board think the GNSO Council should approach this matter when structuring and scoping the PDP? * Ongoing court cases may have an impact on issues, but the (E)PDP Team is not expected to deliberate on these issues unless these are reflected in the temporary specification. (4) Does the initial 90-day (and maximum one-year) period - and thus the maximum timeline for the GNSO’s policy work - commence on 17 May (date of Board resolution) or 25 May (effective date of the temporary specification)? We note that the operative language from the RAA/RA specifies that “In establishing any Temporary Policy, the Board shall state the period of time for which the Temporary Policy is adopted and shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws”, and the Board resolution is clear that the specification is effective beginning on 25 May. This could be interpreted to mean that the one-year clock starts from the effective date of the specification rather than Board action via resolution, which is a difference of 8 days. * 25 May 2018 is the starting point, so 1 year period would end on 24 May 2019. Up to the Council to decide when to start, but regardless, process has to complete by 24 May 2019. (5) What happens should the Board decide to either modify the temporary specification or completely replace the temporary specification by a new one at a later point in time? Does the amended temporary specification become a new temporary specification, effectively re-starting the clock on the Temp Spec and the ongoing EPDP? If changes to the Temporary Specification as it is today are certain to occur, and the amended temporary specification becomes a new temporary specification, why not delay starting the ePDP (assuming clock re-starts)? Note Council’s intention is not running multiple EPDP, but rather revising scope of the one ongoing EPDP. * Will depend on facts and circumstances. Board wants to continue to consult, could include appointing a liaison to the (E)PDP Team, small Board caucus to liaise with the Council, etc. Board wants to help without seeking to impose views. * Need the ability for instant consultation noting the possible moving parts and the need to be flexible. What does "consult" mean? Council weighing in on decision-making? More looking from the perspective of the Council being able to consult with the Board as needed. Board would talk to different parties and factor in input - if a particular way or structure is preferred, this can be discussed. (1) Participation of the GAC: How will the EPDP take into account GAC advice? Should the Board facilitate a session between the GNSO and the GAC on this issue, and when? * Would be good to discuss with GAC what is possible and feasible. Need to open up channels of discussion, recognising that the GNSO is in charge and leading. (6) How is the re-confirmation process expected to occur as the temporary policy is only valid for 90 day intervals? * Board will hold meetings at 90 day intervals and review prior to each meeting whether there is any new guidance that may require changes, followed by renewal of temporary specification for another 90 days. Changes may need to happen outside of that cycle. (7) Has the Board considered what actions it may take in the event that, at the end of the one-year period, the Temporary Specification is not confirmed as a Consensus Policy and no other Consensus Policy has been developed to replace it? * See previous response to similar question. ======== If more discussion is helpful, Board is willing and available. Need to determine which questions need to be followed up on and timeline for those. Develop task list as a result. Could include request for further calls. Council holding extraordinary meeting on 12 June to further discuss next steps. Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

4 3

GNSO2 Review Working Group Progress & Implementation Status Report
by Julie Hedlund June 8, 2018

June 8, 2018

Dear GNSO Council members, On behalf of the GNSO Review Working Group (WG) please find the attached GNSO Review Progress & Implementation Status Report and slides for the update to the GNSO Council at ICANN62. The GNSO Review WG requests 15 minutes on the agenda of the GNSO Council meeting at ICANN62 on Wednesday, 27 June for this brief update by the GNSO Review WG Chair, Jen Wolfe. As you may know, the GNSO Review WG is executing and overseeing the implementation of the GNSO Review 2 (GNSO2) recommendations. This Report is a required periodic update to the GNSO Council and the Operational Effectiveness Committee (OEC) of the ICANN Board of Directors. The Working Group was initiated on 15 March 2017 and has been meeting bi-weekly. The original suggested timeline for implementation has been adjusted to reflect the fact that the Implementation Plan was not adopted by the ICANN Board until 03 February 2017, and to reflect the Working Group’s progress, but the overall goal for the implementation of all recommendations is unchanged. The Working Group expects to complete the implementation of all of the recommendations within the original timeline, not later than September 2018. This is the second Program & Implementation Status Report provided to the GNSO Council and the OEC. The first Report was submitted to the GNSO Council and the OEC in November 2017 at ICANN60. Please note that due to the deadline for documents to be considered at ICANN62, the OEC has requested that the Report be submitted to them by Friday, 08 June, and staff has submitted it accordingly. Kind regards, Julie Julie Hedlund, Policy Director

1 0

Final Proposed Agenda GNSO Council Meeting - 12 June 2018 at 12:00 UTC
by Nathalie Peregrine June 7, 2018

June 7, 2018

Dear all, Please below find the updated final proposed agenda for the extraordinary GNSO Council Meeting on 12 June 2018 at 12:00 UTC. Draft proposed agenda 12 June 2018 – Extraordinary GNSO Council Meeting Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/AygFBQ This agenda was established according to the GNSO Operating Procedures<https://gnso.icann.org/en/council/op-procedures-30jan18-en.pdf> v3.3, updated on 30 January 2018 For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 12:00 UTC: https://tinyurl.com/yb9ydjth [tinyurl.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__tinyurl.com_yb9ydjth&d…> 05:00 Los Angeles; 08:00 Washington; 13:00 London; 17:00 Islamabad; 21:00 Tokyo; 22:00 Hobart GNSO Council Meeting Audio Cast Listen in browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Listen in application such as iTunes: http://stream.icann.org:8000/stream01.m3u[stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Opening Remarks Item 2. COUNCIL DISCUSSION – Next steps following adoption of ICANN Board Temporary Specification (115 minutes) On 11 May 2018, ICANN released the Temporary Specification<https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#con…> on gTLD Registration Data, which served as the main agenda topic for the subsequent Board Workshop in Vancouver. This proposed Temporary Specification provides an interim solution until the community completes a policy development process on the temporary specification which is expected to complete within a one year period. On 14 May 2018, ICANN released a revised Temporary Specification<https://www.icann.org/en/system/files/files/proposed-gtld-registration-data…> and scheduled a webinar on 15 May 2018 to discuss the topic. The Board passed a resolution<https://www.icann.org/resources/board-material/resolutions-2018-05-13-en>, noting their intent to adopt the Temporary Specification on or around 17 May 2018. On 17 May 2017, the ICANN Board approved<https://www.icann.org/resources/board-material/resolutions-2018-05-17-en> the proposed Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en>, which establishes temporary requirements for how ICANN and its Contracted Parties will comply with both ICANN contractual requirements and the European Union’s General Data Protection Regulation (GDPR). On 21 May 2018, the Council and SG/C chairs met to discuss possible next steps for the ICANN Board adoption of the Temporary Specification. On its 24 May 2018 meeting, the Council discussed possible next steps following ICANN Board adoption of the Temporary Specification. On 5 June 2018, the Council met with the ICANN Board to discuss a set of questions the Council developed, as well as overall next steps. Subsequently, Council leadership and staff developed a Mindmap<https://gnso.icann.org/sites/default/files/file/field-file-attach/temporary…> to help understand the elements around a potential Expedited Policy Development Process, such as timing, team composition, and planning for ICANN62 Here, the Council will continue its discussion from its 24 May 2018 meeting to discuss and plan for its next steps to begin work on the policy development process related to the Temporary Specification. 7.1 – Update (Council Leadership) 7.2 – Council discussion 7.3 – Next steps Item 3: ANY OTHER BUSINESS (0 minutes) ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-proced… References for Coordinated Universal Time of 12:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 05:00 San José, Costa Rica (CST) UTC-6 06:00 New York/Washington DC, USA (EDT) UTC-4 08:00 Buenos Aires, Argentina (ART) UTC-3 09:00 Rio de Janeiro, Brazil (BRST) UTC-3 09::00 London, United Kingdom (GMT) UTC+1 013:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 13:00 Paris, France (CEST) UTC+2 14:00 Islamabad, Pakistan (PKT) UTC+5 17:00 Singapore (SGT) UTC+8 20:00 Tokyo, Japan (JST) UTC+9 21:00 Sydney/Hobart, Australia (AEDT) UTC+10 22:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 28 of October 2018, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 4 of November 2018 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and : https://tinyurl.com/yb9ydjth

1 0

Fwd: [soac-chairs] Update for SO/AC Chairs: Second Security, Stability, and Resiliency (SSR2) Review -- Next Steps
by Heather Forrest June 7, 2018

June 7, 2018

Dear Council colleagues, Below, an update from ICANN Org on SSR2. If you have any questions, I'll be happy to channel them to Larisa. Best wishes, Heather ---------- Forwarded message ---------- From: Larisa B. Gurnick <larisa.gurnick(a)icann.org> Date: Wed, Jun 6, 2018 at 7:12 AM Subject: [soac-chairs] Update for SO/AC Chairs: Second Security, Stability, and Resiliency (SSR2) Review -- Next Steps To: "soac-chairs(a)icann.org" <soac-chairs(a)icann.org> Cc: SSR2 <ssr2-review(a)icann.org>, Theresa Swinehart < theresa.swinehart(a)icann.org>, David Olive <david.olive(a)icann.org> Dear SO/AC Chairs, We are pleased to inform you that the ICANN organization has engaged an external professional to facilitate the transition process and help the SSR2 review team in restarting and moving forward with its work. The SSR2 Review Team members have been notified of the appointment of the facilitator and efforts undertaken to support their work, confirming the official restart of the SSR2. After reviewing facilitator profiles and guidance from SO/AC chairs, ICANN organization has identified Phil Khoury, Cameron. Ralph. Khoury Consulting Services <http://crkhoury.com.au/>, to assist the review team in relaunching its activities. Phil Khoury’s 15 years of experience facilitating discussions, his solid understanding of the ICANN multistakeholder model, and consensus building expertise, distinguished him as an appropriate resource to address the scope and focus areas you have identified. Based on your 13 March note <https://www.icann.org/en/system/files/correspondence/soac-to-koubaa-13mar18…>, we understand that you would like to share the results of the survey you conducted after ICANN60 with the facilitator, to inform preparatory work leading up to the facilitated face-to-face meeting. Phil Khoury will reach out to you to receive the relevant material. He will also contact each of the SSR2 members to get their input in preparation for the next steps and proposed Review team’s upcoming face-to-face meeting. We are planning the meeting at ICANN’s office in Belgium or another identified location, in coordination with the review team, aiming for a time that can accommodate the majority of review team members. Thank you again for your dedication and collaboration in ensuring the success of this review. Best regards, Larisa *Larisa B. Gurnick* Vice President Multistakeholder Strategy and Strategic Initiatives ICANN larisa.gurnick(a)icann.org Skype: larisa.gurnick 1-310-383-8995 _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org https://mm.icann.org/mailman/listinfo/soac-chairs

4 3

ICANN62: GNSO Sessions How to Get Organized and Remote Participation Details
by Nathalie Peregrine June 6, 2018

June 6, 2018

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings’ team has put together an updated ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN62 Meeting Schedule<https://62.schedule.icann.org/> GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ> Step 1 – Create a profile and your personalized ICANN62 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you’ve added all your chosen meetings to “My Schedule” go to Export. 1. Importing creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. 2. Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. * For Outlook calendars: http://support.pathable.com/knowledgebase/articles/81449-moving-your-schedu…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> * For Google calendars: http://support.pathable.com/knowledgebase/articles/1313-moving-your-schedul…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> Step 3 All Adobe Connect rooms (which can be found on the session information on the Meeting Schedule<https://62.schedule.icann.org/> and on the GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ>) will provide audio streaming only Adobe Connect room microphones will not be enabled. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the GNSO Remote Participation wiki page<https://community.icann.org/x/6QQFBQ> for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Step 4 Please download the mobile app by searching for “ICANN62” in your app stores. Nathalie Peregrine and Terri Agnew will be onsite in Panama to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<applewebdata://FB60497E-61D8-4FE9-BF9C-EB238191E416/gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

New gTLD Subsequent Procedures PDP WG newsletter - June 2018
by Emily Barabas June 6, 2018

June 6, 2018

Dear all, On behalf of the leadership team of the New gTLD Subsequent Procedures PDP Working Group, I am writing to share the latest edition of the Working Group newsletter: http://go.icann.org/SubPro [go.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__go.icann.org_SubPro&d=D…>. Please feel free to share this newsletter with individuals and groups who may be interested in the Working Group’s activities. An archive of previous editions of the newsletter is available on the WG wiki [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pa…> and on the GNSO website [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_news…>. Kind regards, Emily Emily Barabas | Senior Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

ICANN62 GNSO Policy Briefing Available for Download
by Ariel Liang June 6, 2018

June 6, 2018

Dear All, On behalf of the GNSO Team, I am happy to report that the GNSO Policy Briefing for ICANN62 is now available for download at http://go.icann.org/gnsobriefing If you prefer to download individual sections, you can do so by visiting this page<http://go.icann.org/policybriefing>. The policy briefing is intended to facilitate your preparation for ICANN62 – if you have any comments and/or suggestions on how we can further facilitate your preparation, let me know. Please feel free to share the link with your respective groups and anyone else that may be interested. If you have a twitter account, you may also retweet this post to help spread the word: https://twitter.com/ICANN_GNSO/status/1004338899634868225 Happy reading! Best Regards, Ariel Ariel Xinyue Liang Policy Analyst | Washington, DC Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

GNSO Council Abstention Notification Form [#275]
by ICANN June 6, 2018

June 6, 2018

1 0

FW: ICANN Contracted Parties e-Briefing - June 2018
by Marika Konings June 5, 2018

June 5, 2018

For your information. [cid:image001.jpg@01D3FC1D.ED5973B0] 4 June 2018 Greetings, The ICANN Global Domains Division (GDD) Services & Engagement team would like to highlight some recent, more notable, community-impacting activities and projects below. We are preparing for the ICANN62 Policy Forum<https://meetings.icann.org/en/panamacity62> in Panama City, Panama and look forward to your participation. New & Noteworthy Temporary Specification for gTLD Registration Data The General Data Protection Regulation (GDPR) was adopted by the European Union (EU) in April 2016 and took full effect on 25 May 2018. On 17 May 2018, ICANN published the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en> (Temporary Specification). This Temporary Specification establishes temporary requirements to allow ICANN and gTLD registry operators and registrars to continue to comply with existing ICANN contractual requirements and community-developed policies in light of the GDPR. The Temporary Specification applies to all of ICANN’s contracted parties and is now in effect as of 25 May 2018. GDPR and Temporary Specification Webinar To offer further guidance and to learn how your organization may be affected by the Temporary Specification, we have scheduled a one-hour, interactive webinar on 6 June 2018. This will be a live webinar, held in English with live interpretation in Arabic, Chinese, French, Russian, and Spanish, and we encourage you to email your questions ahead of time to globalsupport(a)icann.org<mailto:globalsupport@icann.org> with “GDD Temp Spec Webinar” in the email’s subject line. A recording of the webinar will be posted as soon as possible on icann.org<http://icann.org>. Webinar Details & How to Attend Date: 6 June 2018 Time: 16:00 - 17:00 UTC (click here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=NSp+Roadmap+for+R…> to view time zone converter) Join via Adobe Connect meeting here<https://participate.icann.org/tempspec06june2018> View dial-in information here<https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=8021705257&num=1-605-…> Participant Code: 802 170 5257 Contracted Parties Encouraged to Prepare for RDAP As indicated in Section 1 of Appendix A<https://www.icann.org/resources/pages/gtld-registration-data-specs-en/#appe…> of the Temporary Specification for gTLD Registration Data<https://www.icann.org/resources/pages/gtld-registration-data-specs-en> (Temporary Specification), the ICANN organization intends to invoke the requirements in the registry and registrar agreements for implementation of the Registration Data Access Protocol<https://www.icann.org/rdap> (RDAP) service. Currently, several contracted parties are participating in an RDAP pilot program<https://www.icann.org/news/announcement-2017-09-05-en> to gain operational experience with RDAP and to define the appropriate operating profile(s) for the service. This pilot program is available to all community members. ICANN urges all registries and registrars to begin preparing to operate an RDAP service as the technical development of the service may take several months. Please see the RDAP page<https://www.icann.org/rdap> for more information. Privacy Policy Notification to Contracted Parties On Friday, 25 May 2018, the ICANN org updated its privacy policies and certain website terms of service to provide greater transparency, promote simplification, and align with recent changes in privacy laws applicable to ICANN org under the GDPR. To learn more, please visit https://www.icann.org/privacy. 2018 GDD Industry Summit The fourth annual Global Domains Division Industry Summit<https://www.icann.org/gddsummit> was held in Richmond, British Columbia, Canada, from 14-17 May. Over 400 stakeholders attended from 32 countries. The primary purpose of the summit is to provide a forum for ICANN’s contracted parties to discuss issues of mutual interest and importance, share best practices, and meet one-on-one with members of the ICANN org. This year, a multiple track format was added with one track dedicated to technical operations. The ICANN org is currently scouting an appropriate location in the Asia-Pacific region for the 2019 summit. In 2020, the GDD Industry Summit will be held in Europe. Domain Name Marketplace Indicators ICANN org concluded its assessment of the draft V1.0 indicator schema, jointly developed with the project Advisory Panel, for all vendor proposals received. The project was awarded to ZookNIC, Inc<http://www.zooknic.com/>. In April, the project team presented its proposed design approach and methodology to the Advisory Panel. The schema evaluation effort will conclude by the end of August 2018. Upon completion of the evaluation, ICANN org intends to procure the external data sources necessary to finalize the V1.0 Indicators for publication prior to the end of the calendar year. Final Proposed Draft Version 4.0 of the IDN Guidelines Now Published The Internationalized Domain Name (IDN) Implementation Guidelines<https://www.icann.org/resources/pages/implementation-guidelines-2012-02-25-…> relate to IDN registration policies and practices and are designed to minimize the risk of cybersquatting and consumer confusion. Once approved by the ICANN Board, these guidelines are contractually binding for most gTLD registries and registrars offering IDN registrations. After multiple public consultations and review of current IDN Guidelines version 3.0<https://www.icann.org/resources/pages/idn-guidelines-2011-09-02-en>, the IDN Guidelines Working Group<https://community.icann.org/display/IDN/IDN+Implementation+Guidelines> has published<https://www.icann.org/news/announcement-2018-05-10-en> the updated Final Proposed Draft version 4.0<https://www.icann.org/en/system/files/files/idn-guidelines-10may18-en.pdf> of the IDN Guidelines. This draft is pending approval from the ICANN Board of Directors. After approval, version 4.0 of the guidelines will become applicable to the relevant registries and registrars. Contracted Parties Satisfaction Survey In April 2018, the annual contracted parties satisfaction survey concluded. The objective of this survey was to understand and track feedback on the GDD’s work with contracted parties on an annual basis, based on the following dimensions: integrity, dependability, competence, commitment, and satisfaction. The published results<https://www.icann.org/resources/pages/metrics-gdd-2015-01-30-en> include a slide presentation with aggregated answers to each of the 12 survey questions and an executive summary. Naming Services Portal Terms of Use On 11 May 2018, changes to the Naming Services portal’s Terms of Use were deployed. Users who have not yet activated their accounts received an activation email. Please activate your account as soon as possible. For additional information regarding the features and functionality of the portal, please visit the Registry Resources<https://www.icann.org/resources/pages/registry-resources-2017-09-22-en> or Naming Services portal for Registrars<https://www.icann.org/resources/pages/nsp-registrars-2018-03-26-en> pages on icann.org<http://icann.org>. These pages include webinar recordings, user guides, and additional resources. Please email globalsupport(a)icann.org<mailto:globalsupport@icann.org> or contact your engagement manager with any questions. ICANN to Publish Semi-Annual Report on WHOIS Accuracy In mid-June, the ICANN org will publish the Phase 2 Cycle 6 WHOIS Accuracy Reporting System (ARS) Report. This report is a follow-up to previous ARS reports which have been published semi-annually since December 2015 and explores the syntax and operability accuracy of WHOIS records in gTLDs in light of the requirements of the 2009 and 2013 Registrar Accreditation Agreements (RAAs). It also examines the leading types of nonconformance, trends, and comparisons of WHOIS accuracy across gTLD types, ICANN regions, and RAA versions. Additional information about the project is available at whois.icann.org/whoisars<http://whois.icann.org/whoisars>. ICANN Finance Department to Annually Publish Tax Residency Certificate Effective this year and annually thereafter, the ICANN org will publish<https://www.icann.org/resources/pages/payments-2012-02-25-en>: (1) the lCANN certification letter stating it is a tax resident of United States; and (2) Form 6166 - U.S. Tax Residency Certification for the relevant year. We expect the certificates from the U.S. Internal Revenue Service will be published annually by ICANN org in the month of March. Tax residency forms for the years 2016, 2017 and 2018 are available on the ICANN Billing and Payments page<https://www.icann.org/resources/pages/payments-2012-02-25-en>. If you have questions, please submit a general inquiry case via the Naming Service portal or email globalsupport(a)icann.org<mailto:globalsupport@icann.org>. The 2018 Contractual Compliance Quarter One Performance Report In March 2018, the ICANN org published a blog<https://www.icann.org/resources/pages/compliance-reports-2018> on Enhancing Transparency in Contractual Compliance. As described in the report and blog<https://www.icann.org/resources/pages/compliance-reports-2018>, Contractual Compliance completed its work on enhanced metrics and performance reports<https://features.icann.org/compliance>. Contractual Compliance team members will be attending the ICANN62 Policy Forum and available for a limited number of one-on-one sessions with contracted parties, which can be requested by emailing compliance(a)icann.org<mailto:compliance@icann.org>. Policy Implementation Updates Protection of IGO and INGO Identifiers for All gTLDs On 16 January 2018, the Implementation of the Protection of IGO and INGO Identifiers for all gTLDs Policy was published<https://www.icann.org/resources/pages/igo-ingo-protection-policy-2018-01-16…>. Contracted parties have until 1 August 2018 to complete implementation of the new requirements for specified names of IGOs, the International Olympic Committee (IOC), and the Red Cross/Red Crescent Movement (RCRC). For INGOs, the implementation period will be 12 months from the release of the INGO Claims Systems Specification, which is currently under development. Thick WHOIS Transition Consensus Policy On 13 May 2018, the ICANN Board passed a Resolution<https://www.icann.org/resources/board-material/resolutions-2018-05-13-en#1.e> to defer contractual compliance enforcement of the Thick WHOIS transition policy in consideration of the European Union's General Data Protection Regulation (GDPR). ICANN Contractual Compliance will defer enforcing the following milestones until the dates listed below: • 30 November 2018: The registry operator must begin accepting Thick WHOIS data from registrars for existing registrations in .COM, .NET and .JOBS. • By 30 April 2019: All registrars must send Thick WHOIS data to the registry operator for all new registrations in .COM, .NET and .JOBS. • By 31 January 2020: All registrars are required to complete the transition to Thick WHOIS data for all registrations in .COM, .NET and .JOBS. For more information, please refer to the published Thick WHOIS Transition Policy available here<https://www.icann.org/resources/pages/thick-whois-transition-policy-2017-02…>. Privacy/Proxy Service Provider Accreditation Program ICANN org continues to work with the volunteer Implementation Review Team (IRT) on implementing the generic names supporting organization’s (GNSO) recommendations for a proxy/privacy service provider accreditation<https://www.icann.org/resources/pages/ppsai-2016-08-18-en> program. The ICANN org received a request from the RrSG on 4 May 2018<https://www.icann.org/en/system/files/correspondence/bunton-to-atallah-04ma…> to pause the IRT’s work, and a communication opposing this from the Coalition for Online Accountability<https://www.icann.org/en/system/files/correspondence/marks-metalitz-to-atal…> on 10 May 2018. These requests are currently under consideration. Registrars Naming Services Portal – Registrar ICANN recently launched the Naming Services portal for Registrars, an application built to streamline the way registrars conduct business with the ICANN org. This recent launch is a step towards in making the Naming Services portal the primary system of record and replacing legacy systems. As part of this release, all registrar primary contacts now have access to the portal with the ability to view the compliance tickets for the relevant IANA IDs. The ICANN org is continuing to work with a registrar portal planning group to gather input on the future feature enhancements to the portal. Webinar Announcement: Naming Services Portal Roadmap ICANN org will hold a webinar scheduled on 13 June 2018 to discuss the Naming Service portal for registrars, its current capabilities, and the roadmap for future releases. Participants have an opportunity to provide feedback and ask questions directly from the product team. A recording of the webinar will be made available following the session. Webinar Details & How to Attend Date: 13 June 2018 Time: 14:00 - 15:00 UTC (click here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=NSp+Roadmap+for+R…> to view time zone converter) Join Via Adobe Connect<https://participate.icann.org/nspwebinar/> Via Dial-In Information<https://www.myrcplus.com/cnums.asp?bwebid=8369444&ppc=2897077927&num=1-605-…> Participant Code: 289 707 7927 2013 Registrar Accreditation Agreement (RAA) Renewal The initial set of early adopters that executed the 2013 RAA are nearing the auto-renewal process. The steps for the RAA auto-renewal process are detailed here<https://www.icann.org/resources/pages/renewing-2013-07-08-en>. Registrars who meet the criteria will have their agreements auto-renewed for a new five-year term of accreditation. Additional ICANN-designated Registrar Data Escrow Agent ICANN org announced<https://www.icann.org/news/announcement-3-2018-05-15-en> DENIC eG as an additional ICANN-designated Registrar Data Escrow Agent. Registrars wishing to change their escrow agent should follow the Registrar Data Escrow Agent Change<https://www.icann.org/resources/pages/registrar-data-escrow-agent-change-20…> process. Registries New Registry Resources Available on icann.org<http://icann.org> One of the Registry Services & Engagement team’s goals in the coming year is to review and update the registry resources<https://www.icann.org/resources/pages/registry-resources-2017-09-22-en> available on icann.org<http://icann.org>. We recently published the GDD Handbook<https://www.icann.org/en/system/files/files/gdd-ops-handbook-registry-opera…>, and the Registry Billing Frequently Asked Questions<https://www.icann.org/en/system/files/files/registry-operator-billing-faqs-…>. If you have feedback or suggestions regarding registry resources, please submit a general inquiry via the Naming Services portal or email globalsupport(a)icann.org<mailto:globalsupport@icann.org>. Procedure for Community gTLD Change Requests The ICANN org and the Community gTLD Change Request Working Group discussed updates to the draft procedure based on the comments received during Public Comment<https://www.icann.org/public-comments/community-gtld-change-procedure-2018-…> and finalized an updated version available here<https://www.icann.org/resources/pages/community-gtld-change-requests-proced…>. The ICANN org is preparing to offer this service for community gTLD registry operators with an expected launch date in July 2018. Registry Service and Evaluation Policy (RSEP) Process Improvements Representatives from the Registries Stakeholder Group (RySG) and ICANN org are reviewing the RSEP submission and review process. The objective is to find ways to improve timelines from the initial RSEP request through ICANN approval while providing more clarity to registries in each stage of the process. Following a review of proposed updates to the operational process at the GDD Industry Summit in Richmond, British Columbia, the RySG will provide feedback to staff, and this will be discussed in more detail at ICANN62. We hope this information provides you with additional insight and transparency into our ongoing activities and look forward to your feedback. Best Regards, Cyrus Namazi Vice President, Domain Name Services & Industry Engagement ICANN Global Domains Division [cid:image001.jpg@01D3FC23.2C1C3F60]

1 0

MP3, Adobe Connect recording and chat transcript/ GNSO Council with the ICANN Board meeting to discuss next steps following the adoption of ICANN Board of the temporary specification on Tuesday 5 June 2018 at 13:00 UTC.
by Terri Agnew June 5, 2018

June 5, 2018

Dear GNSO Council, Please find below the MP3, Adobe Connect recording and chat of the GNSO Council with the ICANN Board meeting to discuss next steps following the adoption of ICANN Board of the temporary specification held on Tuesday 5 June 2018 at 13:00 UTC. MP3: <https://audio.icann.org/gnso/gnso-council-icann-board-05jun18-en.mp3> https://audio.icann.org/gnso/gnso-council-icann-board-05jun18-en.mp3 Adobe Connect Recording URL: <https://participate.icann.org/p6ai9gt1qeg/> https://participate.icann.org/p6ai9gt1qeg/ Adobe Connect chat at: <https://gnso.icann.org/en/meetings/transcript-chat-council-icann-board-05ju…> https://gnso.icann.org/en/meetings/transcript-chat-council-icann-board-05ju… All on page: <https://gnso.icann.org/en/group-activities/calendar> https://gnso.icann.org/en/group-activities/calendar Thank you. Happy listening and reading! With kind regards, Terri --- Terri Agnew Operations Support - GNSO Lead Administrator Internet Corporation for Assigned Names and Numbers (ICANN) Email: <mailto:terri.agnew@icann.org> terri.agnew(a)icann.org Skype ID: terri.agnew.icann Find out more about the GNSO by taking our interactive courses and visiting the <https://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy…> GNSO Newcomer pages Follow @GNSO on Twitter: <https://twitter.com/ICANN_GNSO> https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: <https://www.facebook.com/icanngnso/> https://www.facebook.com/icanngnso/ <http://gnso.icann.org/en/> http://gnso.icann.org/en/

1 0