May 2017 - Gnso-newgtld-wg - lists.icann.org

Recordings, Attendance & AC Chat from New gTLD Subsequent Procedures Working Group call on Tuesday, 30 May 2017 at 15:00 UTC
by Terri Agnew 30 May '17

30 May '17

Dear All, Please find the attendance of the call attached to this email and the MP3 and Adobe Connect recording below for the New gTLD Subsequent Procedures Working Group call held on Monday, 30 May 2017 at 15:00 UTC. Attendance of the calls is also posted on the agenda wiki page: https://community.icann.org/x/CtTRAw MP3: <https://audio.icann.org/gnso/gnso-new-gtld-subsequent-30may17-en.mp3> https://audio.icann.org/gnso/gnso-new-gtld-subsequent-30may17-en.mp3 Adobe Connect Recording: <https://participate.icann.org/p21dituonyc/?OWASP_CSRFTOKEN=1d0b66cd3929354d 21560731d101913a0a7092f23edd328723cd77441b3653ca> https://participate.icann.org/p21dituonyc/ The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar ** Please let me know if your name has been left off the list ** Mailing list archives: <http://mm.icann.org/pipermail/gnso-newgtld-wg/> http://mm.icann.org/pipermail/gnso-newgtld-wg/ Thank you. Kind regards, Terri ------------------------------- Adobe Connect chat transcript for Tuesday, 30 May 2017 Terri Agnew:Dear All, Welcome to the New gTLD Subsequent Procedures WG call Tuesday, 30 May 2017 at 15:00 UTC Terri Agnew:agenda wiki page: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_C tTRAw <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_ CtTRAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpC IgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9Z M&s=7tRYX2_ejPjCUmLNQ85geMm4b8yoPiXnlBhSoxrmOZc&e> &d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXh FzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=7t RYX2_ejPjCUmLNQ85geMm4b8yoPiXnlBhSoxrmOZc&e= Vanda Scartezini:hi everyone Dietmar Lenden - Valideus Ltd:good jeff Vanda Scartezini:i am hear you very well! Jonathan Robinson:@Michael. Thank-you. So, work in progress for now. Emily Barabas:Jonathan, meeting notes from the discussion on VI are here: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_F tTRAw <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_ FtTRAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpC IgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9Z M&s=YpPf4hT7FKf6MvdJRSgI0w_6lXP5rg1hdNfCLJ_q7WE&e> &d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXh FzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=Yp Pf4hT7FKf6MvdJRSgI0w_6lXP5rg1hdNfCLJ_q7WE&e= Jonathan Robinson:@Jeff. Thank-you for furhter clarification. Informative. Michael Flemming:Thank you, Jeff! Bruna Santos:yes Dietmar Lenden - Valideus Ltd:SAC95 on emojis Dietmar Lenden - Valideus Ltd:Lin: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system _files_files_sac-2D095-2Den.pdf <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste m_files_files_sac-2D095-2Den.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJ ms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZl eORKf2eU-3jv623xrpDUQEjJ9ZM&s=riTNvPmPV9og3OXsfVFxUflHS41ABDTB08takSRthl0&e> &d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXh FzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=ri TNvPmPV9og3OXsfVFxUflHS41ABDTB08takSRthl0&e= Terri Agnew:reminder, recordings can be found on the GNSO Calendar: https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_group -2Dactivities_calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou p-2Dactivities_calendar&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5 cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU- 3jv623xrpDUQEjJ9ZM&s=Kf4o3YeBUU8B_bp4fzliNi4veqihcoFp-JGmrVfiD0Y&e> &d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXh FzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=Kf 4o3YeBUU8B_bp4fzliNi4veqihcoFp-JGmrVfiD0Y&e= Emily Barabas:and meeting notes from the session with Patrik are here: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_K dTRAw <https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_ KdTRAw&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpC IgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9Z M&s=pamhkJ8wbe7cxBSuN7t0NncuQ4po7tGPFoKVwSsVBr8&e> &d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXh FzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=pa mhkJ8wbe7cxBSuN7t0NncuQ4po7tGPFoKVwSsVBr8&e= Cheryl Langdon-Orr (CLO):thx staff :-) Jannik Skou Thomsen Trampedach:so no more public comments round? No CC3? Or will the last final consolidated recommendations have to go through a Public Comment? Steve Chan:CC2 Public Comment page here: https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2D comments_cc2-2Dnew-2Dgtld-2Dsubsequent-2Dprocedures-2D2017-2D03-2D22-2Den <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2 Dcomments_cc2-2Dnew-2Dgtld-2Dsubsequent-2Dprocedures-2D2017-2D03-2D22-2Den&d =DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFz L7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=ZD_K hSXkR7XPvcN3QfDmsFQjPa_GWQUqgGMtrbaMGpI&e> &d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXh FzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=ZD _KhSXkR7XPvcN3QfDmsFQjPa_GWQUqgGMtrbaMGpI&e= Ken Stubbs:plz speak louder or get closer to phone. thank you.. Ken Stubbs:thx Cheryl Langdon-Orr (CLO):better thx Trang Ken Stubbs:anacronym CDAR = What ? Alexander Schubert:Maybe we do it the other way around and ask ICANN Staff which part required the largest rescources in 2010/2011 - so we can make sure to provide input regarding these issues ASAP. Steve Chan:@Ken, Continuous Data-Driven Analysis of Root Server System Stability Ken Stubbs:thx.. we have far too many acronyms in ICANN Donna Austin, Neustar:Thanks Trang Ken Stubbs:First come- first served can be easily "gamed" Greg Shatan:I also have deep concerns regarding first come, first served. Trang Nguyen:Will do Steve Chan:The "Rounds" Google working document is available here: https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen t_d_1u3UzvZIXzjnxtklgPmqArqff6dyckUbyuzWyLz7dKOw_edit-3Fusp-3Dsharing <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume nt_d_1u3UzvZIXzjnxtklgPmqArqff6dyckUbyuzWyLz7dKOw_edit-3Fusp-3Dsharing&d=DwI CaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar 9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=ujxdhQjd EWLQLTcNH3sEzcTjp6z1CEUwpXZXVza6ft0&e> &d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXh FzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=uj xdhQjdEWLQLTcNH3sEzcTjp6z1CEUwpXZXVza6ft0&e= Emily Barabas:For those who prefer to follow in the Google Doc, it is available here: https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_documen t_d_1lzXxBLMtFr03BKnHsa-2DSs7kR7EAJt7pCI1EP3H81tfQ_edit-3Fusp-3Dsharing <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume nt_d_1lzXxBLMtFr03BKnHsa-2DSs7kR7EAJt7pCI1EP3H81tfQ_edit-3Fusp-3Dsharing&d=D wICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7 ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=jIhrij ihhHnZxIpY3gx_Pe9isAhap0HteboW65ZqLP4&e> &d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXh FzL7ar9Qfqa0AIgn-H4xR2EBk&m=0Wi1EWWuD3Nx9EZleORKf2eU-3jv623xrpDUQEjJ9ZM&s=jI hrijihhHnZxIpY3gx_Pe9isAhap0HteboW65ZqLP4&e= Emily Barabas:(New gTLD Framework of Predictability) Paul McGrady:Apologies all, but I need to step away early today. Thank you all for all your hard work on this! Trang Nguyen:Thank you, Avri. Will review and provide input as appropriate. Greg Shatan:Unfortunately, there's an overlap between this meeting and the Next-Gen RDS WG, so I will need to go to multitasking mode. Jeff Neuman:I thought it was supposed to be in WT1 Sara Bockey:Yes, I'm in the same boat as Greg Sara Bockey:Thanks all! Robin Gross:Thanks Avri and all, bye. Karen Day:Thanks, Avri Trang Nguyen:Thanks, all! Bye! Vanda Scartezini:thank you to all Bruna Santos:thanks all Christa Taylor:Thanks Dietmar Lenden - Valideus Ltd:Bye Ken Stubbs:thank you ! Cheryl Langdon-Orr (CLO):thanks everyone bye for now Terri Agnew:next New gTLD Subsequent Procedures Working Group is scheduled to take place on Monday, 12 June 2017 at 20:00 UTC. Greg Shatan:Bye! Phil Buckingham:thanks Avri

1 0

Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 30 May 2017
by Emily Barabas 30 May '17

30 May '17

Dear Working Group members, Please find below the action items and discussion notes from today’s meeting. These high-level notes are designed to help Working Group members navigate through the content of the call and are not a substitute for the chat room or the recording. The meeting recording and transcripts will soon be available at: https://community.icann.org/x/CtTRAw. Kind regards, Emily ====================================== 1) Welcome/SOIs - no updates 2) Work Track Updates - WT1 - next meeting is today at 20:00 UTC. The group will review progress and next steps for the WT and then focus on RSP Program requirements document. - WT2 - next meeting scheduled for this Thursday at 21:00 UTC, which will likely focus on Global Public Interest. This will be the list topic to introduce in this WT. The final session before ICANN59 will likely focus on Vertical Integration. - Question - what is the status of WT discussion on VI? - Response - the topic was introduced - focus: were anticipated benefits realized? If not, how can they be? Were possible anticipated harms observed? If so, how can they be mitigated? - WT3 - recent conversations focused on Community Applications and CPE. The next meeting will focus on Accountability Mechanisms. It will be on June 6 at 20:00 UTC. - Question - what is the scope of work around Accountability Mechanisms for this group? - Response - Want to take a broad look initially at accountability mechanisms in the gTLD Program and whether they are sufficient. The current measures mostly look at process rather than substance. Some may want to see mechanisms that also go to the substance of a decision. - WT4 - Last call was on Thursday, included a presentation from Patrik Fältström on SSAC Reports and Advisories. Upcoming call will take place next Thursday 8 June at 20:00 UTC. Overall plan for WTs: - The issues have been introduced through "blue sky" conversations in the Work Tracks. As groups finish this cycle, they will go through a second cycle to go through CC2 comments and come to their initial views. There will be a third pass before it comes back to the full group -- WTs will determine whether there is consensus for changing something and what should be changed. This will be documented for the full group to discuss further. WTs will go dormant, but the full group may ask WTs to revisit certain topics at a later point. 3) Update - Community Comment 2 - 25 comments received, cross section of the community submitted input. - Staff is preparing a summary document to be ready for 5 June document deadline for ICANN59. 4) Update and Discussion – GDD response to select questions from GDD Summit - Question raised at GDD Summit - what information does ICANN org need to take next steps towards subsequent procedures? Information requested from ICANN org: -- Will applications will be processed in rounds or first-come first-served? -- RSP Certification/Accreditation – Is the WG recommending that there will a program? - Time needed to prepare for upcoming procedures depends on the answer to these questions. - Once final recommendations are available, they will go the Board and if approved, will go to ICANN org for implementation. - Next step for Continuous Data-Driven Analysis of Root Server System Stability (CDAR) report – is ICANN Board consideration. - Results of Board consideration of the CDAR Report will impact this PDP. - The report will likely be considered in the Board's June meeting, but Trang will confirm. - Concern raised about first-come first-served approach to application processing -- this issue should be considered carefully with pros and cons explored. Chat excerpt: Ken Stubbs: First come- first served can be easily "gamed" Greg Shatan: I also have deep concerns regarding first come, first served. - This is one of the pending CC1 issues and the topic of a drafting team. Nothing has yet been decided. All are welcome to join and participate in drafting teams. 5) Drafting Team Update – Framework for Community Engagement and Predictability (https://docs.google.com/document/d/1lzXxBLMtFr03BKnHsa-Ss7kR7EAJt7pCI1EP3H8…) - This document is still in draft form and needs additional feedback from WG members. - This is a form of change control document. - This framework seeks to provide a predictable and clear way to handle changes if they come up after program launch or in implementation. - It may be helpful to have a discussion about the scope of the document. - Outstanding question to address: once the IRT completes its work, who is the right party to address changes and how they will be handled. - There is some guidance in Bylaws and Operating Procedures on how to handle changes at this stage. - Is it prescribed when an IRT ends? - When is it appropriate for a change to go out for public comment? - What would be potential parameters around "freezing" changes at a certain point? - Question: would the WG like feedback from ICANN org from an implementation feasibility perspective? - Response: feedback is welcome at any time in the document. - The topic of application change requests may be something for this WG to consider. 6) AOB

1 0

Responses to questions raised at the 2017 GDD Summit
by Trang Nguyen 30 May '17

30 May '17

All, At the recent 2017 GDD Summit in Madrid, Spain, the following questions relating to subsequent procedures for new gTLDs were raised: · Jeff Neuman (Valideus, co-chair of New gTLD Subsequent Procedures PDP WG): There are areas we can start working without going through the PDP. On more controversial issues, working toward making proposals. Starting with the geographic names issue, which is a big issue for governments. This will be a discussion item at ICANN 59. Akram, what are your top 10 issues that need to be resolved before we can take the next step? Are there gating items you can list? · Donna Austin (Neustar): If we can have some more communication from ICANN Org on how much lead time you need to prepare, and the order of things you need would be helpful. CCT Review team is almost finished. What is the next step in the process? The CDAR report – what happens with that now? Does the Board have to consider it? Does it go to a PDP? Some of these steps are unclear. We thank you for these questions and provide the following responses for your review and to help inform the ongoing work of the WG. As expressed on one of the previous WG’s calls, one of the biggest items that impact ICANN organization’s ability to begin implementation preparation and operational readiness is whether new gTLD applications would be received and processed in rounds, or on a first-come-first-serve basis. Another item currently under discussion in the WG that ICANN organization is not planning to begin implementation preparation and operational readiness on until the WG decides on a path forward is whether there would be some kind of pre-qualification for RSPs or grandfathering of current RSPs. Regarding lead time to prepare, there is preparation work that ICANN organization can begin doing while PDP discussions are taking place. The extent of such preparation work is largely dependent on the two items discussed above. We would welcome further discussions with the WG on this. For example, there were suggestions at ICANN58 that ICANN organization begin drafting the AGB. Further discussion as to what point in the WG’s discussion would it be appropriate for ICANN organization to begin drafting, and how ICANN organization is expected to interact with the WG while drafting the AGB would be helpful. Regarding the CCT reviews, the final recommendations of the review team will be considered by the Board and implemented by ICANN organization if approved. The CCT review team’s project plan anticipates publication of its final recommendations prior to ICANN60. Regarding the CDAR report that was published in March 2017, the next step for the report will be Board consideration. We hope this answer the questions raised and welcome further discussions with the WG on these topics. Regards, Trang

1 0

Proposed Agenda: New gTLD Subsequent Procedures Working Group, 30 May 2017 at 15:00 UTC
by Steve Chan 28 May '17

28 May '17

Dear WG Members, Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday, 30 May 2017 at 15:00 UTC. Please note, this call is scheduled for 90 minutes. 1) Welcome/SOIs 2) Work Track Updates 3) Update - Community Comment 2 4) Update and Discussion – GDD response to select questions from GDD Summit 5) Drafting Team Update – Framework for Community Engagement and Predictability (https://docs.google.com/document/d/1lzXxBLMtFr03BKnHsa-Ss7kR7EAJt7pCI1EP3H8…) 6) AOB If you need a dial-out or want to send an apology, please email gnso-secs(a)icann.org. Best, Steve Steven Chan  Sr. Policy Manager   ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org mobile: +1.310.339.4410 office tel: +1.310.301.5800 office fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

3 4

Proposed Agenda: New gTLD Subsequent Procedures Working Group, 15 May 2017 at 15:00 UTC
by Steve Chan 22 May '17

22 May '17

Dear WG Members, Apologies for the late delivery. Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday, 15 May 2017 at 15:00 UTC for 90 minutes. 1) Welcome/SOIs 2) Work Track Updates 3) GDD Summit Recap 4) Drafting Team Update – Different TLD Types (https://docs.google.com/spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJffzJ…) 5) Community Comment 2 (CC2) Update – Public Comment available here: https://www.icann.org/public-comments/cc2-new-gtld-subsequent-procedures-20… 6) ICANN59 Planning 7) AOB If you need a dial-out or want to send an apology, please email gnso-secs(a)icann.org. Best, Steve Steven Chan  Sr. Policy Manager   ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  steve.chan(a)icann.org mobile: +1.310.339.4410 office tel: +1.310.301.5800 office fax: +1.310.823.8649 Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/

29 114

Announcement: Pre-ICANN59 Policy Update Webinar Thursday, 15 June 2017 at 10:00 UTC and 19:00 UTC
by Terri Agnew 22 May '17

22 May '17

https://www.icann.org/news/announcement-2017-05-22-en Please RSVP via <https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> this form by 13 June 2017. You will receive remote participation details the week of 12 June 2017. The ICANN Policy Development Support Team will host a Policy Update Webinar on Thursday, 15 June 2017 at 10:00 and 19:00 Coordinated Universal Time (UTC), in preparation for the upcoming ICANN59 Policy Forum in Johannesburg, South Africa. The purpose of the webinar is to summarize policy activities across the ICANN policy development community and to brief the community on the Empowered Community consultation and cross-community sessions taking place in Johannesburg. Briefings on the Empowered Community Consultation and Cross-Community Sessions: * Special session on the Proposed Fundamental Bylaws Amendments * Next-Generation Generic Top-Level Domain (gTLD) Registration Directory Services (RDS) policy requirements * General Data Protection Regulation (GDPR) * Geographic names * Operational side of ICANN's Operating Plan and Budget * Who sets ICANN's priorities? Updates on Supporting Organizations and Advisory Committees: * Address Supporting Organization (ASO) and regional Internet registries (RIR) policy development * Country Code Names Supporting Organization (ccNSO) * Generic Names Supporting Organization (GNSO) * At-Large Advisory Committee (ALAC) and At-Large Community * Governmental Advisory Committee (GAC) * Root Server System Advisory Committee (RSSAC) * Security and Stability Advisory Committee (SSAC) The two sessions are duplicates, scheduled to accommodate different time zones. Each session runs in English for 90 minutes. The webinar will be conducted via Adobe Connect along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, participants may submit questions using the chat function in Adobe Connect. Recordings of the webinars will be made available <https://www.icann.org/resources/pages/presentations-2012-08-27-en> here. The Policy Development Support Team is always available to answer any questions via email at <mailto:policyinfo@icann.org> policyinfo(a)icann.org. Please RSVP via <https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> this form by 13 June 2017. You will receive remote participation details the week of 12 June 2017. Ozan Sahin Community Engagement Support Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6218 Mobile: +90.533.641.0007 Email: ozan.sahin(a)icann.org <mailto:ozan.sahin@icann.org> Skype: ozan.sahin.icann www.icann.org

1 0

Discussion on TLD categories and structure for application procedures
by Emily Barabas 22 May '17

22 May '17

Dear Working Group Members, There has recently been spirited discussion on the mailing list about two topics: whether categories of TLDs should be designated and the process for structuring future application procedures. Staff has attempted to capture key points, questions, and proposals from these discussions in two working documents: - Categories/different TLD types: https://docs.google.com/spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJffzJ… - Rounds/other mechanisms: https://docs.google.com/document/d/1u3UzvZIXzjnxtklgPmqArqff6dyckUbyuzWyLz7… As some may recall, the leadership team has created three Drafting Teams to address these two topics plus one additional topic. This may be a good moment to move the discussion from the main mailing list back into the Drafting Teams: - Categories/Different TLD Types -- Wiki: https://community.icann.org/x/YKLRAw | List: gnso-newgtld-types(a)icann.org<mailto:gnso-newgtld-types@icann.org> - Rounds/Other Mechanisms – Wiki: https://community.icann.org/x/ZKLRAw | List: gnso-newgtld-rounds(a)icann.org<mailto:gnso-newgtld-rounds@icann.org> - Predictability Framework/Community Engagement -- Wiki: https://community.icann.org/x/YqLRAw | List: gnso-newgtld-predict(a)icann.org A good first step could be for the Drafting Teams to review and build on the above working documents, leveraging the Drafting Team mailing lists. As a reminder, Drafting Teams are open to all Working Group members and all products of the Drafting Teams will go through the full Working Group. You can sign up for a Drafting Team by adding your name to this document: https://docs.google.com/document/d/1g-OoBec_Q6nnBofBvcTnfAotFh7yq07HUM7kxh6…. If you want to participate in a Drafting Team and do not use Google Docs, please email me, Steve, and/or Julie for assistance. Kind regards, Emily Emily Barabas | Policy Specialist ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas(a)icann.org | Phone: +31 (0)6 84507976

1 0

Re: [Gnso-newgtld-wg] category discussion was [] Proposed Agenda: New gTLD ...
by avri 18 May '17

18 May '17

Hi Alan, Categories is one of the pending CC1 overarching issues. We discussed the drafting team doc at the last meeting in order to get a conversation going to help us find a way to resolve the issue. The drafting teams have been slow getting to the work done so we decided to bring the work back to the full meeting for discussion. Then, hopefully, the volunteers on the drafting team can more the work forward. We need to get this issue moving since it touches on much of the work being done in the work groups. I do not see this as a short circuit but rather a discussion we need to have and I am happy to see the discussion on the list. Avri Sent from my T-Mobile 4G LTE Device null

2 1

Re: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent Procedures Working Group, 15 May 2017 at 15:00 UTC
by Carlos Raul Gutierrez 18 May '17

18 May '17

+1 Michele Carlos Raúl GUTIERREZ Apartado 1571-1000 San José COSTA RICA On May 15, 2017 08:40, "Michele Neylon - Blacknight" <michele(a)blacknight.com> wrote: Volker All valid points, but for every point there is an equally strong counterpoint. I’m not suggesting that the arguments for or against categories are right or wrong, but I think that completely discounting them causes as many problems as it solves. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ https://ceo.hosting/ Intl. +353 (0) 59 9183072 <+353%2059%20918%203072> Direct Dial: +353 (0)59 9183090 <+353%2059%20918%203090> ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845 *From: *<gnso-newgtld-wg-bounces(a)icann.org> on behalf of Volker Greimann < vgreimann(a)key-systems.net> *Date: *Monday 15 May 2017 at 16:16 *To: *"gnso-newgtld-wg(a)icann.org" <gnso-newgtld-wg(a)icann.org> *Subject: *Re: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent Procedures Working Group, 15 May 2017 at 15:00 UTC One argument against different categories might be accessability of the new gTLDs for applicants. If we reduce requirements for some applicants, why not for all? Will the applicants that benefit from lesser requirements be in a better position to get their TLD in case of a conflict? As an example, say a multi-million company that owns a brand that also is a generic term that a small public benefit initiative is also applying for, on top of the economic advantage that the one applicant has over the other we are now also saying that they must meet lower standards, making it easier and cheaper for them to operate the TLD in the long run, adding additional funds that can be thrown at beating the opponent in an auction process? We would also enter a minefield when a TLD fits into multiple categories. Does it then have to fulfill the requirements of all the categories or just the one the applicant intends to use it for? As we have seen, use cases may change over time. Am 15.05.2017 um 15:30 schrieb Michele Neylon - Blacknight: Martin 100% agree I never understood why the concept of categories was rejected. Saying it’s “hard” does not mean it’s “impossible” or that it shouldn’t be explored. After the lack of categories we (the community) had to then deal with a complicated patchwork of exemptions and other funky manipulations to get around the quite meaningless limitations that were being imposed. For example, this weekend in Madrid ICANN shared some stats about SLA breaches from new TLD registries. Some people would argue that a “.brand” should not have to meet the same SLA targets as a “.generic”. While I can understand the logic of that argument the current lack of categories does not allow for that kind of differentiation. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ https://ceo.hosting/ Intl. +353 (0) 59 9183072 <+353%2059%20918%203072> Direct Dial: +353 (0)59 9183090 <+353%2059%20918%203090> ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845 *From: *<gnso-newgtld-wg-bounces(a)icann.org> <gnso-newgtld-wg-bounces(a)icann.org> on behalf of Martin Sutton <martin(a)brandregistrygroup.org> <martin(a)brandregistrygroup.org> *Date: *Monday 15 May 2017 at 15:25 *To: *Jeff Neuman <jeff.neuman(a)comlaude.com> <jeff.neuman(a)comlaude.com> *Cc: *"gnso-newgtld-wg(a)icann.org" <gnso-newgtld-wg(a)icann.org> <gnso-newgtld-wg(a)icann.org> <gnso-newgtld-wg(a)icann.org> *Subject: *Re: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent Procedures Working Group, 15 May 2017 at 15:00 UTC That would be helpful. I have difficulties reconciling the notion of ignoring categories, as it caused no end of problems after applications were submitted and created unnecessary delays. Where there are well-defined categories and a proven demand, categories can be created and processes refined for that particular category, especially where the operating model is very different to the traditional selling /distribution to third parties. Kind regards, Martin *Martin Sutton* Executive Director Brand Registry Group martin(a)brandregistrygroup.org On 15 May 2017, at 15:17, Jeff Neuman <jeff.neuman(a)comlaude.com> wrote: Thanks Kurt. Can you recirculate that article you wrote 6 months ago? It may help our discussions later today. *Jeffrey J. Neuman* *Senior Vice President *|*Valideus USA* | *Com Laude USA* 1751 Pinnacle Drive, Suite 600 Mclean, VA 22102, United States E: jeff.neuman(a)valideus.com or jeff.neuman(a)comlaude.com T: +1.703.635.7514 <(703)%20635-7514> M: +1.202.549.5079 <(202)%20549-5079> @Jintlaw *From:* gnso-newgtld-wg-bounces(a)icann.org [mailto:gnso- newgtld-wg-bounces(a)icann.org <gnso-newgtld-wg-bounces(a)icann.org>] *On Behalf Of *Kurt Pritz *Sent:* Monday, May 15, 2017 6:35 AM *To:* Steve Chan <steve.chan(a)icann.org>; gnso-newgtld-wg(a)icann.org *Subject:* Re: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent Procedures Working Group, 15 May 2017 at 15:00 UTC Hi Everyone: In reading the agenda for today’s meeting, I read the spreadsheet describing the different TLD types. (See, https://docs.google.com/ spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJff zJAAhEvNlA/edit#gid=1186181551). It looks remarkably similar to a chart presented to the ICANN Board in 2010 or 2011 as the main argument for *not *adding to the categories of TLDs in the last round because they would be problematic (read, “impossible”) to implement. Even in this spreadsheet, I can argue whether most of the tick marks in the cells apply in all cases. This means that each of the many tick marks presents a significant barrier to: (1) getting through the policy discussion in a timely manner, and (2) a clean implementation. Categories of TLDs have always been problematic. The single most important lesson from the 2003-04 sponsored TLD round was to avoid a system where delegation of domain name registries was predicated upon satisfying criteria associated with categories. In the last round, the Guidebook provided for two category types: community and geographic. In my opinion, the implementation of both was problematic: look at the variances in CPE results and the difficulty with .AFRICA. This wasn’t just a process failure, the task itself was extremely difficult. Just how does an evaluation panel adjudge a government approval of a TLD application if one ministry says, ‘yes’ and the other ’no’? This sort of issue is simple compared to evaluating community applications. The introduction of a number of new gTLD categories with a number of different accommodations will lead to a complex and difficult application and evaluation process (and an expensive, complicated contractual compliance environment). It is inevitable that the future will include ongoing attempts to create policy for new categories as they are conceived. For those who want a smoothly running, fair, predictable gTLD program, the creation of categories should be avoided. Instead, the outcome of our policy discussion could be a process that remains flexible and can adapt to new business models as they are developed. An exemption process to certain contractual conditions can be created to encourage innovation while ensuring all policy goals embodied in the RA are met. Fair and flexible agreements can be written without the need, time and complexity of the creation of additional categories or separate agreements. While an exemption process sounds complex, it is not compared to the nightmare that the new gTLD process will become: never adequately administering to an ever-increasing number of categories. I wrote in more depth about this ~ 6 months ago - and would be happy to flesh out my thoughts on this again. Best regards, Kurt ________________ Kurt Pritz kurt(a)kjpritz.com +1.310.400.4184 <(310)%20400-4184> Skype: kjpritz On May 15, 2017, at 3:43 AM, Steve Chan <steve.chan(a)icann.org> wrote: Dear WG Members, Apologies for the late delivery. Below, please find the proposed agenda for the New gTLD Subsequent Procedures WG meeting scheduled for Monday, 15 May 2017 at 15:00 UTC for 90 minutes. 1) Welcome/SOIs 2) Work Track Updates 3) GDD Summit Recap 4) Drafting Team Update – Different TLD Types ( https://docs.google.com/spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJff zJAAhEvNlA/edit#gid=1186181551) 5) Community Comment 2 (CC2) Update – Public Comment available here: https://www.icann.org/public-comments/cc2-new-gtld- subsequent-procedures-2017-03-22-en 6) ICANN59 Planning 7) AOB If you need a dial-out or want to send an apology, please email gnso-secs(a)icann.org. Best, Steve *Steven Chan* Sr. Policy Manager *ICANN* 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 steve.chan(a)icann.org mobile: +1.310.339.4410 <(310)%20339-4410> office tel: +1.310.301.5800 <(310)%20301-5800> office fax: +1.310.823.8649 <(310)%20823-8649> Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages <http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…> . Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ http://gnso.icann.org/en/ _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 <+49%206894%209396901> Fax.: +49 (0) 6894 - 9396 851 <+49%206894%209396851> Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 <+49%206894%209396901> Fax.: +49 (0) 6894 - 9396 851 <+49%206894%209396851> Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone. _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg

1 0

Complaint to Ombuds: Meeting schedule was Re: Proposal to Extend CC2 Deadline
by Herb Waye 17 May '17

17 May '17

Dear all, This email is in response to an email complaint filed on May 1st with the Office of the Ombudsman, to which you were all cc’ed. Since taking office as the ICANN Ombuds last July I have been particularly focused on being a resource to the greater ICANN community and have been vocal in offering my assistance on a broader scale than as stated in the old bylaws: actions, inactions by Board, staff etc. The new bylaws (Oct. 2016) are much more focused on the community and fair treatment for all. This effort has resulted in not only an increase in people contacting me regarding conflict in many of the working groups, but more importantly, people are contacting me immediately when conflict arises. This allows prompt intervention and remedy rather than a deterioration of relationships and the undermining of efficiency and effectiveness. Without going into detail I am pleased to advise the working group that this complaint has been resolved and that I can bear witness to a unanimous demonstration of support for the leadership of the working group. I would like to highlight the professional, “human” approach taken by all involved and their willingness to communicate in a clear, respectful and objective manner. This cooperative atmosphere allowed for a timely discussion and quick resolution. In closing I would like to remind everyone that as a community we are all in this together and underline the importance of professional and respectful behavior in all our interactions, whether online or in person. I wish the entire working group and its co-chairs a productive and positive environment moving forward so together we can maintain ICANN as a safe, respectful and harassment free environment for all. Respectfully, Herb Herb Waye ICANN Ombudsman https://www.icann.org/ombudsman https://www.facebook.com/ICANNOmbudsman Twitter: @IcannOmbudsman ICANN Expected Standards of Behavior: https://www.icann.org/en/system/files/files/expected-standards-15sep16-en.p… Community Anti-Harassment Policy https://www.icann.org/resources/pages/community-anti-harassment-policy-2017… Confidentiality All matters brought before the Ombudsman shall be treated as confidential. The Ombudsman shall also take all reasonable steps necessary to preserve the privacy of, and to avoid harm to, those parties not involved in the complaint being investigated by the Ombudsman.The Ombudsman shall only make inquiries about, or advise staff or Board members of the existence and identity of, a complainant in order to further the resolution of the complaint. The Ombudsman shall take all reasonable steps necessary to ensure that if staff and Board members are made aware of the existence and identity of a complainant, they agree to maintain the confidential nature of such information, except as necessary to further the resolution of a complaint

4 3