April 2018 - council - lists.icann.org

Re: [council] [Ext] Re: ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan
by Nathalie Peregrine 23 Apr '18

23 Apr '18

Thank you, Michele, We would kindly ask that all councilors take the time to share their impressions on Adobe Connect and/or the alternative tools they have tested in ICANN conference calls recently: RP-tool(a)icann.org<mailto:RP-tool@icann.org> This will allow a clear decision to be made between Adobe Connect, WebEx and Zoom, therefore, if you do have a strong preference for one tool or another, please indicate it via the above email address. Please also circulate to your membership groups in order to gather as much information as possible. Kind regards, Nathalie From: Michele Blacknight <michele(a)blacknight.com> Date: Saturday, April 21, 2018 at 10:53 AM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [Ext] Re: [council] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan Thanks Nathalie I’m not sure how others feel, but it looks to me like ICANN has taken all necessary steps to relaunch Adobe Connect securely, so I’d hope that we will be able to start using it again soon. Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/[blacknight.blog]<https://urldefense.proofpoint.com/v2/url?u=https-3A__blacknight.blog_&d=DwM…> https://ceo.hosting/[ceo.hosting]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ceo.hosting_&d=DwMGaQ&…> Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845 From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Friday 20 April 2018 at 21:13 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan Dear all: Please take a look at this blog on Adobe Connect. And note the request: Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Best regards, David https://www.icann.org/news/blog/adobe-connect-what-next[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> ADOBE CONNECT – WHAT NEXT? As you know, the ICANN organization took down its Adobe Connect service midway through the ICANN61 meeting in response to reported issues[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> with this service. Concurrently, we began to conduct our own forensic analysis of the reported incident and began working with our Adobe cloud service provider, CoSo Cloud LLC, and through them with Adobe to learn more. Shortly thereafter, we rolled out instances of Zoom and WebEx for the community to support remote participation (RP) and collaboration. Here's where we are now: The Forensics Investigation With respect to our forensics work, we received application logfiles from CoSo Cloud, going back for a period of one year. ICANN Engineering and Security teams have examined these application log files and the results of our investigation clearly show "fingerprints of incursion" by the researcher who reported the issue. We were unable to find any other indication that anyone else either identified or exploited this issue. Thanks to the person who found the bug again. Working closely with CoSo Cloud, we were able to recreate the reported issue, and understand the conditions required to trigger it. This information has been communicated to Adobe, and Adobe is working on a software fix to address the root cause of the issue. We have also been working with CoSo on options to re-enable Adobe Connect in the shorter term. We have determined there are two viable paths to accomplish this goal. They are: 1. Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or 2. Implement a programmatic fix from CoSo Cloud to substantially reduce the window during which the issue can be exploited. With respect to the first option, we attempted to hack the hardened configuration in a test environment last week, and were not able to do so over the course of 7 hours. Separately, CoSo Cloud and Adobe conducted similar tests and confirmed that this configuration is protected from exploitation of the issue. Community Feedback and Next Steps For the last three weeks, we have been gathering limited feedback regarding users' experiences with WebEx and Zoom. So far, we have input from about 200 people, including ICANN org meeting organizers and the ICANN community. Our analysis of this feedback indicates a desire to revert back to an Adobe Connect, providing the security of the service is ensured. Accordingly, we would like to propose the following plan to the broader community for consideration: 1. We would like to restore Adobe Connect services with both the new hardened configuration and the programmatic fix discussed above. Our intent would be to restore service by 3 May. This would allow us to use Adobe Connect during several upcoming events including the Board Workshop, the GDD Industry Summit, and ICANN62. 2. Once Adobe releases a new version of the software with a fix for this issue from their perspective, and provides assurance the update has been adequately tested, we will move toward that release of Adobe Connect in a prudent manner, with the help of CoSo Cloud. We believe that this approach will ensure the security of our content, and of our community interactions, while also enabling our community to use the collaboration tools of their choice. Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Meanwhile, we will continue to offer WebEx and Zoom for RP and collaboration purposes. We will also continue to follow industry developments, including the research ALAC is doing on the RP and collaboration space, to ensure we are using secure and cost-effective tools that are appropriate for our needs. I look forward to your comments! David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Re: [council] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan
by Michele Neylon - Blacknight 22 Apr '18

22 Apr '18

Thanks Nathalie I’m not sure how others feel, but it looks to me like ICANN has taken all necessary steps to relaunch Adobe Connect securely, so I’d hope that we will be able to start using it again soon. 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 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845 From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Friday 20 April 2018 at 21:13 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan Dear all: Please take a look at this blog on Adobe Connect. And note the request: Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Best regards, David https://www.icann.org/news/blog/adobe-connect-what-next ADOBE CONNECT – WHAT NEXT? As you know, the ICANN organization took down its Adobe Connect service midway through the ICANN61 meeting in response to reported issues<https://www.icann.org/news/blog/issues-with-adobe-connect-at-icann61> with this service. Concurrently, we began to conduct our own forensic analysis of the reported incident and began working with our Adobe cloud service provider, CoSo Cloud LLC, and through them with Adobe to learn more. Shortly thereafter, we rolled out instances of Zoom and WebEx for the community to support remote participation (RP) and collaboration. Here's where we are now: The Forensics Investigation With respect to our forensics work, we received application logfiles from CoSo Cloud, going back for a period of one year. ICANN Engineering and Security teams have examined these application log files and the results of our investigation clearly show "fingerprints of incursion" by the researcher who reported the issue. We were unable to find any other indication that anyone else either identified or exploited this issue. Thanks to the person who found the bug again. Working closely with CoSo Cloud, we were able to recreate the reported issue, and understand the conditions required to trigger it. This information has been communicated to Adobe, and Adobe is working on a software fix to address the root cause of the issue. We have also been working with CoSo on options to re-enable Adobe Connect in the shorter term. We have determined there are two viable paths to accomplish this goal. They are: 1. Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or 2. Implement a programmatic fix from CoSo Cloud to substantially reduce the window during which the issue can be exploited. With respect to the first option, we attempted to hack the hardened configuration in a test environment last week, and were not able to do so over the course of 7 hours. Separately, CoSo Cloud and Adobe conducted similar tests and confirmed that this configuration is protected from exploitation of the issue. Community Feedback and Next Steps For the last three weeks, we have been gathering limited feedback regarding users' experiences with WebEx and Zoom. So far, we have input from about 200 people, including ICANN org meeting organizers and the ICANN community. Our analysis of this feedback indicates a desire to revert back to an Adobe Connect, providing the security of the service is ensured. Accordingly, we would like to propose the following plan to the broader community for consideration: 1. We would like to restore Adobe Connect services with both the new hardened configuration and the programmatic fix discussed above. Our intent would be to restore service by 3 May. This would allow us to use Adobe Connect during several upcoming events including the Board Workshop, the GDD Industry Summit, and ICANN62. 2. Once Adobe releases a new version of the software with a fix for this issue from their perspective, and provides assurance the update has been adequately tested, we will move toward that release of Adobe Connect in a prudent manner, with the help of CoSo Cloud. We believe that this approach will ensure the security of our content, and of our community interactions, while also enabling our community to use the collaboration tools of their choice. Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Meanwhile, we will continue to offer WebEx and Zoom for RP and collaboration purposes. We will also continue to follow industry developments, including the research ALAC is doing on the RP and collaboration space, to ensure we are using secure and cost-effective tools that are appropriate for our needs. I look forward to your comments! David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

3 2

[article] DPAs to pros: There's no grace period, folks
by Ayden Férdeline 22 Apr '18

22 Apr '18

Item 7 on our agenda for this week's Council meeting is a discussion of the potential impact on the RDS PDP WG from the finalisation of an interim model for compliance with GDPR. There is a lot of uncertainty around what this model might consist of, and ICANN seems to be suggesting some kind of legal action (presumably against the Data Protection Authorities for enforcing the law) is imminent unless ICANN is given a moratorium of some sort. In light of this uncertainty, I found this article to be an interesting read. The Irish Data Protection Authority has been quoted as saying, "There is no grace period. The grace period ends the 25th of May," and the French and UK DPAs are also ready to enforce the law from day one. https://iapp.org/news/a/dpas-to-pros-theres-no-grace-period-folks/ Best wishes, Ayden Férdeline

1 0

Customer Standing Committee Charter Review--Report published for public comment
by Austin, Donna 20 Apr '18

20 Apr '18

Hi Everyone Some of you may recall that during the GNSO and ccNSO Council meeting in San Juan, I provided an update on the progress of the review being conducted into the CSC Charter. This is a review required by the Charter and reflected in the ICANN bylaws. The CSC Review Team has published its report that includes proposed amendments to the Charter for public comment until 1 June 2018, and is available here: https://community.icann.org/display/CRT/Reports?preview=/84213949/84214351/… In accordance with the Charter, any recommended changes are to be ratified by the ccNSO and the GNSO. It is aim to have the Amended Charter considered and hopefully approved by the Council during our meeting in Panama. Thanks Donna Donna Austin Neustar, Inc. / Senior Policy Manager, Registry Solutions Mobile: +1 310 890 9655 donna.austin(a)team.neustar<mailto:donna.austin@team.neustar> / Website: home.neustar<http://www.home.neustar/> Follow Neustar: LinkedIn<http://www.linkedin.com/company/5349> / Twitter<http://www.twitter.com/neustar> Reduce your environmental footprint. Print only if necessary. ________________________________ The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

1 0

Explanatory Note From ICANN org Regarding the Community gTLD Change Request
by Steve Chan 20 Apr '18

20 Apr '18

Dear Councilors, Below, please find an explanatory note from ICANN org related to the Community gTLD Change Request process and the related public comment; the Report of Comments is now published. Please note, this topic is captured on the Consent Agenda in the Final Proposed Agenda circulated earlier by staff. Best, Steve Executive Summary Following the guidance from the GNSO Council in November 2017, the ICANN org and the Community gTLD Change Request Working Group collaborated to revise the draft procedure for ICANN to consider change requests to Specification 12 of Community generic Top Level Domain (gTLD) Registry Agreements requested by community gTLD registry operators. Subsequently, the ICANN org initiated a public comment proceeding from 14 February to 2 April 2018. Based on the results of the public comment proceeding, the ICANN org recommends continuing to treat this as a matter of implementation. We kindly request the GNSO Council’s review and confirmation. Background Community gTLD registry operators formed a working group in 2016 to develop a draft procedure by collaborating with the ICANN org and by seeking input from the RySG. The Applicant Guidebook and new gTLD Registry Agreement (RA) imply there should be a mechanism to allow modifications to Specification 12 of the RA, but the Applicant Guidebook also noted that the criteria for changes to community restrictions might be a policy matter. Therefore, the ICANN org encouraged the working group to consult with the GNSO Council to ensure this is a matter for implementation (which it did in September and October 2017). In November 2017, the GNSO Council provided guidance to publish the draft procedure for Public Comment after the working group addressed comments on the procedure from the ICANN org. From the Council’s guidance, “in the event that comments are received indicating the process is not consistent with existing policy the Council will reconsider the matter. Absent such comments the process will be understood as this being an implementation matter.” Summary of Public Comments ICANN received a total of seven comments during the public comment proceeding. Aside from one comment requesting additional background, all other commenters noted general support for the development of a procedure that allows ICANN to consider modifications, but not removal, of the community restrictions in Specification 12. Two of these commenters suggested edits or sought clarification on procedural clarifications and implementation details. The ICANN org confirms no comments were received that indicated the process is not consistent with existing policy. For additional details, please see the Report of Comments. Summary of Changes Made to the Draft Procedure The ICANN org and the working group discussed updates to the draft procedure based on the comments and are working to finalize the procedure to implement and post on ICANN.org. A number of these accepted changes were requests to clarify questions within Annex A (Community gTLD Change Request Form) and the timing of certain steps. Conclusion After consideration of comments received, the ICANN org and the Community gTLD Change Request Working Group concluded that comments did not indicate the procedure is in conflict with existing policy. Barring feedback to the contrary from the GNSO Council, the ICANN org concludes this can continue to be handled as an implementation matter. Following the guidance from the GNSO Council in November 2017, we kindly request the council’s review and confirmation. Steven Chan  Policy Director, GNSO Support 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/

1 0

ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan
by Nathalie Peregrine 20 Apr '18

20 Apr '18

Dear all: Please take a look at this blog on Adobe Connect. And note the request: Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Best regards, David https://www.icann.org/news/blog/adobe-connect-what-next ADOBE CONNECT – WHAT NEXT? As you know, the ICANN organization took down its Adobe Connect service midway through the ICANN61 meeting in response to reported issues<https://www.icann.org/news/blog/issues-with-adobe-connect-at-icann61> with this service. Concurrently, we began to conduct our own forensic analysis of the reported incident and began working with our Adobe cloud service provider, CoSo Cloud LLC, and through them with Adobe to learn more. Shortly thereafter, we rolled out instances of Zoom and WebEx for the community to support remote participation (RP) and collaboration. Here's where we are now: The Forensics Investigation With respect to our forensics work, we received application logfiles from CoSo Cloud, going back for a period of one year. ICANN Engineering and Security teams have examined these application log files and the results of our investigation clearly show "fingerprints of incursion" by the researcher who reported the issue. We were unable to find any other indication that anyone else either identified or exploited this issue. Thanks to the person who found the bug again. Working closely with CoSo Cloud, we were able to recreate the reported issue, and understand the conditions required to trigger it. This information has been communicated to Adobe, and Adobe is working on a software fix to address the root cause of the issue. We have also been working with CoSo on options to re-enable Adobe Connect in the shorter term. We have determined there are two viable paths to accomplish this goal. They are: 1. Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or 2. Implement a programmatic fix from CoSo Cloud to substantially reduce the window during which the issue can be exploited. With respect to the first option, we attempted to hack the hardened configuration in a test environment last week, and were not able to do so over the course of 7 hours. Separately, CoSo Cloud and Adobe conducted similar tests and confirmed that this configuration is protected from exploitation of the issue. Community Feedback and Next Steps For the last three weeks, we have been gathering limited feedback regarding users' experiences with WebEx and Zoom. So far, we have input from about 200 people, including ICANN org meeting organizers and the ICANN community. Our analysis of this feedback indicates a desire to revert back to an Adobe Connect, providing the security of the service is ensured. Accordingly, we would like to propose the following plan to the broader community for consideration: 1. We would like to restore Adobe Connect services with both the new hardened configuration and the programmatic fix discussed above. Our intent would be to restore service by 3 May. This would allow us to use Adobe Connect during several upcoming events including the Board Workshop, the GDD Industry Summit, and ICANN62. 2. Once Adobe releases a new version of the software with a fix for this issue from their perspective, and provides assurance the update has been adequately tested, we will move toward that release of Adobe Connect in a prudent manner, with the help of CoSo Cloud. We believe that this approach will ensure the security of our content, and of our community interactions, while also enabling our community to use the collaboration tools of their choice. Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Meanwhile, we will continue to offer WebEx and Zoom for RP and collaboration purposes. We will also continue to follow industry developments, including the research ALAC is doing on the RP and collaboration space, to ensure we are using secure and cost-effective tools that are appropriate for our needs. I look forward to your comments! David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Final Proposed Agenda GNSO Council Meeting - 26 April 2018 at 21:00 UTC
by Nathalie Peregrine 20 Apr '18

20 Apr '18

Dear all, Please below find the final proposed agenda for the GNSO Council Meeting on 26 April 2018 at 21:00 UTC. Additional links will be provided when they become available. Final proposed agenda 26 April 2018 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/8YLpB 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: 21:00 UTC: https://tinyurl.com/ycdbsh8u 14:00 Los Angeles; 17:00 Washington; 22:00 London; 02:00 Islamabad; (Friday 27 March) 06:00 Tokyo; 07:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/stream01.m3u 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 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/en/meetings/minutes-council-22feb18-en.pdf> of the GNSO Council meeting on the 22 February 2018 were posted on 9th March 2018 Minutes<https://gnso.icann.org/en/meetings/minutes-council-14mar18-en.pdf> of the GNSO Council meeting on the 14 March 2018 were posted on 5th April 2018 Item 2. Opening Remarks / Review of Projects & Action List (10 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List<https://community.icann.org/x/RgZlAg> Item 3. Consent Agenda (5 min) * Motion<https://community.icann.org/x/9oLpB> to adopt the GNSO Council response to the GAC Communique for submission to the ICANN Board. * The GNSO Council agrees that ICANN org should continue to treat the Community gTLD Change Request process as a matter of implementation. Item 4: COUNCIL VOTE – In Memory of Stéphane Van Gelder (10 minutes) In March of 2018, the Council was informed of Stéphane Van Gelder’s passing. Stéphane entered the domain name business in the late 1990s. He served on the GNSO Council from 2008 through 2012, serving as Vice-Chair in 2010, and Chair in 2011and 2012. Stéphane had a number of notable achievements while presiding as Council Chair, including the completion of an extensive update to the GNSO’s operating procedures, establishment of the DNS Security & Stability Analysis working group jointly with the ALAC, ccNSO, and NRO, completion of the Applicant Guidebook for the 2012 New gTLD Program, and several other important projects. Perhaps most importantly, Stéphane was well-respected and liked for his passion, fairness, his ability to find the best in people, and his true gift for uniting people. Stéphane’s passing is a great loss for many in the ICANN Community that had the pleasure to work and interact with him. Here, the Council wishes to recognize the significant contributions Stéphane made to the GNSO Council during his tenure, the wonderful traits he brought to this world, and how much he will be missed. As well, on behalf of the current and previous GNSO Councils, we offer our deepest and heartfelt sympathies to his family and friends at this most difficult time. 4.1 – Presentation of motion <https://community.icann.org/x/9oLpB> (Rafik Dammak) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5: UPDATE – CCWG-Accountability-WS2 status of work and expected timeline for delivery of Final Report (15 minutes) The Co-Chairs of the CCWG-Accountability-WS2 had indicated that the group would not complete its work in FY17 as originally planned. On 18 May 2017 via its Consent Agenda<https://gnso.icann.org/en/council/resolutions#201705>, the GNSO Council validated an extension of the mandate and funding for the CCWG-Accountability-WS2 in FY18. Here the Council will receive an update from the GNSO appointed co-chair to the CCWG-Accountability on the status of work and expected timeline for delivery of the Final Report. 5.1 – Update (Thomas Rickert, CCWG co-chair) 5.2 – Council discussion 5.3 – Next steps Item 6: UPDATE – IGO-INGO Access to Curative Rights Protection Mechanisms (10 minutes) The IGO-INGO Access to Curative Rights Protection Mechanisms PDP WG had been working to resolve a final recommendation relating to IGO jurisdictional immunity and registrants’ rights to file court proceedings. During the course of trying to determine consensus on a set of options for this final recommendation, several WG members challenged the proposed method for determining initial consensus and appealed via section 3.7 of the GNSO Working Group Guidelines<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-g…>. Following discussions with the members utilizing the appeal process and the GNSO chair and the Council liaison to the WG, the Council liaison to the WG solicited input from the WG members on the set of options under consideration. On 19 April 2018, the Council liaison to the WG led a WG call and provided an update on the input received from WG members, as well as discussed next steps. Here, the Council liaison to the WG will update the Council on the status of the WG. 6.1 – Update (Heather Forrest, Council Chair and Susan Kawaguchi, Council liaison to the WG) 6.2 – Council discussion 6.3 – Next steps [PLACEHOLDER] Item 7: UPDATE – ICANN Board Temporary Policy Proposal (15 minutes) On 23 March, the Council received correspondence<https://www.icann.org/en/system/files/correspondence/chalaby-to-forrest-et-…> from the ICANN Board, suggesting that the ICANN Board meet with Council leadership and leadership of the RDS PDP WG to discuss the potential impact on the WG from the finalization of an interim model for compliance with GDPR. On 11 April 2018, members of the ICANN Board, Council leadership, and leadership of the RDS PDP WG met to discuss possible impacts of GDPR on GNSO policy. Council leadership has prepared a briefing note<https://gnso.icann.org/sites/default/files/file/field-file-attach/gnso-gdpr…> from this meeting and the recording has also been made available. Here, the Council will receive an update on the current status and discuss next steps. 7.1 – Update (Council Leadership) 7.2 – Council discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION – Discussion of Updates to the Consensus Policy Implementation Framework (CPIF) (10 minutes) On 24 June 2015, the Council adopted the outputs of the non-PDP Policy and Implementation WG, which included the Consensus Policy Implementation Framework (CPIF). The CPIF provides guidance to ICANN Org and the community for implementing policy and has been in use since its adoption by the GNSO Council. As noted in Point H of the CPIF, which directs “ICANN staff [to] continually review the implementation framework and related materials to encapsulate additional best-practices or to adjust the steps as a result of lessons learned with previous Consensus Policy projects,” a cross-functional group of representatives from ICANN’s GDD and GNSO Policy Development Support teams have reviewed the Framework, and are proposing a number of amendments to it for the consideration of the GNSO Council. On 5 March 2018, a redlined CPIF document and a document detailing a set of guidelines for ICANN Org to follow when considering engagement in a GNSO PDP were circulated<https://mm.icann.org/pipermail/council/2018-March/020976.html> on the Council email list. Here, the Council will consider the proposed changes and additional document developed by ICANN’s GDD and discuss next steps. 8.1 – Presentation of topic (Council Leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION – Review of the Inter-Registrar Transfer Policy (IRTP) (10 minutes) A recommendation from the 2014 Inter-Registrar Transfer Policy (“IRTP”) Part D PDP Working Group’s Final Report recommended that the GNSO Council, in conjunction with ICANN Org, “convene a panel to collect, discuss, and analyze relevant data to determine whether [the policy updates resulting from the IRTP WGs] have improved the IRTP process and dispute mechanisms, and identify possible remaining shortcomings.” This review was recommended to take place 12 months after the IRTP Part D recommendations were implemented. On 28 February 2018, ICANN Org sent a letter<https://gnso.icann.org/en/drafts/irtp-to-gnso-council-28feb18-en.pdf> to the GNSO Council, noting that the updated IRTP went into effect on 1 December 2016 and therefore, the policy was in place for over 12 months. ICANN Org suggested that a Post-Implementation IRTP Status Report be generated, offering a framework for that report. The ICANN Org envisions that the report, if and when drafted, would be published for public comment. The report and a summary of public comment would be provided to the GNSO Council, for it to determine next steps. If the Council agreed with the approach outlined in the letter, ICANN Org had suggested delivery of the report by 1 May 2018. On 14 March 2018, Council received an update from the ICANN Org and had subsequent discussion on its email list. The Council has not yet agreed whether it believes the ICANN Org should undertake the post implementation analysis on IRTP. Here, the Council will continue to consider the proposal and discuss immediate next steps. 9.1 – Presentation of topic (Council Leadership) 9.2 – Council discussion 9.3 – Next steps Item 10: UPDATE – Privacy and Proxy Services Accreditation Issues (PPSAI) Implementation Review Team (IRT) (10 minutes) On 21 January 2016, the GNSO Council adopted<https://gnso.icann.org/en/council/resolutions#201601> the Final Report of the Privacy and Proxy Services Accreditation Issues (PPSAI) PDP and requested that an Implementation Review Team (IRT) be established upon ICANN Board adoption of the PDP recommendations. On 9 August 2016, the ICANN Board adopted<https://features.icann.org/gnso-policy-recommendations-privacy-proxy-servic…> the PDP WG’s Final recommendations. On 30 November 2017, the GNSO Council resolved<https://gnso.icann.org/en/council/resolutions#201711> that, “The GNSO Council directs the PPSAI IRT to consider the issue of privacy/proxy registrations and IRTP Part C as outlined in the annex to the GNSO Council letter<https://gnso.icann.org/en/correspondence/bladel-to-crocker-01dec16-en.pdf>…” The Council also resolved that this work should take place after the PPSAI IRT comment period. The PPSAI IRT is scheduled to publish its implementation plan for public comment in late April or early May of 2018. There is some concern amongst IRT members that some elements of that implementation plan have strayed into policy work. Here, the Council liaison to the WG will provide an update on the status of the IRT. 10.1 – Update (Darcy Southwell, Council liaison to the IRT) 10.2 – Council discussion 10.3 – Next steps Item 11: UPDATE – Joint Timeline of the All Rights Protection Mechanisms in All gTLDs and New gTLD Subsequent Procedures PDP WGs (10 minutes) The Review of All Rights Protection Mechanisms in All gTLDs PDP WG is the midst of its Phase 1 review of Rights Protection Mechanisms (RPMs), focused on those related to the New gTLD Program and the New gTLD Subsequent Procedures PDP WG is working towards publishing its Initial Report. The Council has recently discussed the joint timeline of the two PDP WGs and the extent to which there are dependencies between the two PDP WGs. Concerns have been raised by Councilors and other community members about the proposed timelines of the two PDP WGs. Here, the Council will receive an update on the current status and discuss next steps. 11.1 – Update (Paul McGrady, Donna Austin, and Keith Drazek, Council liaisons to the WGs) 11.2 – Council discussion 11.3 – Next steps Item 12: ANY OTHER BUSINESS (5 minutes) 12.1 – Update on scheduling for ICANN62 ________________________________ 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 21:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 14:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-4 17:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRST) UTC-3 18:00 London, United Kingdom (GMT) UTC+1 22:00 Paris, France (CEST) UTC+2 23:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+2 23:00 Islamabad, Pakistan (PKT) UTC+5 (+ 1 day) 02:00 Singapore (SGT) UTC+8 (+ 1 day) 05:00 Tokyo, Japan (JST) UTC+9 (+ 1 day) 06:00 Sydney/Hobart, Australia (AEDT) UTC+10 (+ 1 day) 07: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/ycdbsh8u

1 0

Motion for SSC Charter Revision
by Rafik Dammak 20 Apr '18

20 Apr '18

Hi all, I am submitting the motion (attached) for the adoption of SSC charter review. You can also find attached the revised charter. Best Regards, Rafik

2 2

Please review Project List
by Nathalie Peregrine 19 Apr '18

19 Apr '18

Dear Councilors, Attached please find the updated Project List in both red-line and clean version for your review before the Council meeting. If there are no comments, the list will be posted on the website on page: http://gnso.icann.org/en/council/project<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> and be directly viewed at :http://gnso.icann.org/meetings/projects-list.pdf<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_meetings…> Thanks so much, Kind regards, Nathalie 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

Deadline today: Document and Motion deadline Monday 16 April March 2018 at 23:59 UTC for the GNSO Council Meeting 26 April 2018 at 21:00 UTC
by Nathalie Peregrine 16 Apr '18

16 Apr '18

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 16 April 2018 at 23:59 UTC) of the GNSO Council Meeting on Thursday 26 April 2018 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/9oLpB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you very much. With kind regards, Nathalie 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