February 2018 - council - lists.icann.org

Please review: GNSO Council motions 22 February 2018
by Terri Agnew 23 Feb '18

23 Feb '18

Dear councilors, The following resolutions were passed by the GNSO Council at its meeting on Thursday, 22 February 2018. It has been posted on the GNSO website here: https://gnso.icann.org/en/council/resolutions 20180222-1 Amended motion – Adoption of the charter for the ICANN Procedure For Handling WHOIS Conflicts with Privacy Law Implementation Advisory Group (WHOIS Procedure IAG) Submitted by: Donna Austin Seconded by: Heather Forrest Whereas, 1.In November 2005, the Generic Names Supporting Organization (GNSO) concluded a policy development process (PDP) on WHOIS conflicts with privacy law, which recommended the creation of a procedure to address conflicts between a contracted party's WHOIS obligations and local/national privacy laws or regulations. 2. The ICANN Board of Directors adopted the recommendations in May 2006 and the final procedure was made effective in January 2008. 3. As noted in the GNSO Operating Procedures, “Periodic assessment of PDP recommendations and policies is an important tool to guard against unexpected results or inefficient processes arising from GNSO policies”. As called for in Step 6 of the <https://www.icann.org/resources/pages/whois-privacy-conflicts-procedure-200…> ICANN Procedure For Handling WHOIS Conflicts with Privacy Law, “ICANN will review the effectiveness of the process annually”. 4. Following a a review of the procedure in May 2014 and the submission of the Final Report of the Implementation Advisory Group (IAG) in May 2016, the GNSO Council concluded that the proposed modification to the procedure with the alternative trigger as outlined in Appendix I of the <http://gnso.icann.org/en/drafts/iag-review-whois-conflicts-procedure-append…> IAG Final Report conforms to the intent of the original policy recommendations and confirmed its non-objection to the modification being implemented by Global Domains Division staff. 5. In conjunction, the GNSO Council requested that ICANN staff, based on their experience of administering the modification, assess the practicality and feasibility of this new trigger in comparison to the existing trigger as well as the other triggers discussed in the IAG Final Report, and report back accordingly to the GNSO Council. 6. Review of the WHOIS Procedure commenced on 3 May 2017 by <https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en> publishing for public comment a paper outlining the new Alternative Trigger and soliciting public feedback on its implementation. 7. On 1 August 2017, Akram Atallah, President, ICANN Global Domains Division, <https://gnso.icann.org/en/correspondence/atallah-to-bladel-et-al-01aug17-en…> wrote to the GNSO Council to provide an update on the comments received and outlining possible next steps for the GNSO Council to consider. 8. The GNSO Council reviewed the available materials, including the GDD’s possible next steps, and agreed to form a drafting team to develop a charter for a new implementation advisory group to review the public comments in order to assess whether modifications to the Revised ICANN Procedure for Handling WHOIS Conflicts with Privacy Law are necessary and to make recommendations to the GNSO Council accordingly. 9. The drafting team submitted the <https://gnso.icann.org/en/drafts/draft-icann-procedure-whois-conflicts-iag-…> proposed charter for the ICANN Procedure For Handling WHOIS Conflicts with Privacy Law Implementation Advisory Group (WHOIS Procedure IAG) to the GNSO Council on 20 January 2018, and a later edited version on 23 January 2018. 10. The GNSO Council has reviewed and discussed the <https://gnso.icann.org/en/drafts/draft-icann-procedure-whois-conflicts-iag-…> proposed charter. Resolved, 1.The GNSO Council adopts the <https://gnso.icann.org/en/drafts/draft-icann-procedure-whois-conflicts-iag-…> proposed charter for the ICANN Procedure For Handling WHOIS Conflicts with Privacy Law Implementation Advisory Group (WHOIS Procedure IAG). 2. The GNSO Council appoints Keith Drazek as the GNSO Council Liaison to the Implementation Advisory Group. Until such time the IAG has appointed a Chair, the GNSO Council Liaison will serve as the interim Chair. 3. The GNSO Council request staff to circulate the call for volunteers on or after June 1, 2018 to the GNSO Stakeholder Groups with the request for each Stakeholder Group to appoint up to 3 members to the IAG. Further, staff are requested to circulate through the normal communication channels a call to the wider ICANN community for volunteers for interested participants and observers to join the IAG. 4.The GNSO Council thanks the drafting team for its efforts. vote results <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-22feb18-en.…> 20180222-2 Nomination of GNSO Replacement Candidate for Second Security, Stability, and Resiliency of the DNS (SSR2) Review Team Submitted by Susan Kawaguchi Seconded by Rafik Dammak WHEREAS, 1. On 19 January 2017, the GNSO Council nominated (see https://gnso.icann.org/en/council/resolutions#201701) the following candidates to serve on the SSR2-RT (in alphabetical order): James Gannon, Denise Michel, and Emily Taylor as its primary three candidates for the SSR2-RT, noting that these candidates under the new ICANN Bylaws are entitled to be selected. Furthermore, the GNSO nominated (in alphabetical order): Howard Eland, Scott McCormick, Rao Naveed bin Rais, and Norm Ritchie to be considered for inclusion in the SSR2-RT by the SO-AC Chairs should additional places be available. 2. On 14 February 2017, ICANN announced the selection of the 16-member team (see https://www.icann.org/news/announcement-2-2017-02-14-en), which included the three primary candidates nominated by the GNSO Council. 3. Following the resignation of Emily Taylor on 16 July 2017 (see http://mm.icann.org/pipermail/ssr2-review/2017-July/000468.html), the GNSO Council tasked the GNSO Standing Selection Committee (SSC) with recommending a candidate for this vacancy. The SSC recommended Norm Ritchie, who was subsequently nominated by the GNSO Council on 24 August 2017 (see https://gnso.icann.org/en/council/resolutions#201708). 4. On 8 December 2017, James Gannon submitted his resignation to the SSR2-RT (see: http://mm.icann.org/pipermail/ssr2-review/2017-December/000920.html) 5. The GNSO Council asked the SSC to consider an analysis of the skills that existing SSR2-RT members possess (see https://community.icann.org/download/attachments/79433986/SSR2%20Skills%20M… <https://community.icann.org/download/attachments/79433986/SSR2%20Skills%20M…> &modificationDate=1518099841494&api=v2) in order to identify if one of the candidates might have specific skills that are currently underrepresented in the Review Team. The GNSO Council further tasked the GNSO Standing Selection Committee (SSC) with recommending a replacement candidate, taking into account the analysis of existing and needed skills on the Review Team, the criteria outlined in the call for volunteers, as well as the desire to ensure a RT that is balanced for diversity and expertise (https://www.icann.org/news/announcement-3-2016-06-30-en). 6. Out of the three candidates that were nominated in the initial selection process for consideration, beyond those that were entitled to be selected, the following two expressed that they were still interested in serving on the SSR2-RT: Scott McCormick and Rao Naveed bin Rais. 7. The SSC submitted its recommendation to the GNSO Council on 12 February 2018. 8. The GNSO Council considered the recommendation of the SSC. Resolved, 1. The GNSO Council nominates Rao Naveed bin Rais to replace James Gannon on the SSR2-RT. 2. The GNSO Council instructs the GNSO Secretariat to communicate resolved #1 to the staff supporting the SSR2-RT as soon as possible. 3. The GNSO Council instructs the GNSO Secretariat to inform the selected applicant that he has been chosen and that the GNSO Council expects that the applicant will represent the views of the entire GNSO community in his work on the SSR2-RT, and provide regular feedback as a group on the discussions taking place in the SSR2-RT, as well as the positions being taken by GNSO Review Team Members. 4. The GNSO Council asks the GNSO Secretariat to send a response to the applicant who was not selected, thanking him for his continued interest. The response should also encourage him to follow the SSR2-RT work, and participate in Public Comments and community discussions. 5. If the Council is in a position to nominate an additional candidate for the SSR2-RT in the future, the Council will consider Scott McCormick as a first choice for this position, following the SSC’s recommendation that he is also a strong and qualified candidate. vote results <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-22feb18-en.…> Thank you, Terri

1 0

Draft of Public Comments - ICANN's Draft FY19 Budget and Ops Plan
by Berry Cobb 23 Feb '18

23 Feb '18

GNSO Council, On behalf of the SCBO, please find attached a working draft of comments for the GNSO Council to consider in preparation for the meeting this Thursday at 12:00 UTC. Note, that several points within this draft do not have full agreement by the SCBO at this time, but input from the Council is welcome. The draft will be presented by Ayden (SCBO Chair) during agenda item #7. Here, the Council will deliberate on the draft of comments and the proposed approach leading up to planned submission on 8 March. SCBO Membership and SG/C Subject Matter Experts: https://community.icann.org/pages/viewpage.action?pageId=74580769 Proposed timeline to submit the comments: . 19 Feb - Submit draft of comments to Council for review prior to next Council meeting . 22 Feb - GNSO Council meeting; draft of comments on agenda and deliberation . 26 Feb - SCBO meeting . 27 Feb - Send latest draft to Council . 02 Mar - Deadline for GNSO Council input, suggest edits . 05 Mar - SCBO meeting; send final version to Council list for review . 07 Mar - Last call for objections from Council . 08 Mar - Submit GNSO Council comments to comment forum absent any objections . 08 Mar - Draft FY19 ICANN Budget comments due Thank you. B Berry A. Cobb 720.839.5735 mail(a)berrycobb.com @berrycobb

4 5

Mp3, AC recording and AC Chat transcript/ GNSO Council Teleconference 22 February 2018
by Terri Agnew 22 Feb '18

22 Feb '18

Dear all, Please find the mp3 recording of the GNSO Council teleconference, held on Thursday, 22 February 2018 at: https://audio.icann.org/gnso/gnso-council-22feb18-en.mp3 as well as the Adobe chat at: https://gnso.icann.org/en/meetings/transcript-chat-council-22feb18-en.pdf And the Adobe recording: <https://participate.icann.org/p6hlh7tp8de/?OWASP_CSRFTOKEN=1606aaffffef62ce…> https://participate.icann.org/p6hlh7tp8de/ 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

1 0

Re: [council] [Ext] RE: Deadline today: Document and Motion deadline Monday 12 February 2018 at 23:59 UTC for the GNSO Council Meeting 22 February at 12:00 UTC
by Nathalie Peregrine 22 Feb '18

22 Feb '18

Dear Keith, Thank you for your email. Given that the Whois Conflict motion was deferred on the Council meeting held on the 30 January 2018, it automatically reappears as motion for consideration on the agenda for the following meeting, so can be found here: https://community.icann.org/x/WgK8B Kind regards, Nathalie From: "kdrazek(a)verisign.com" <kdrazek(a)verisign.com> Date: Monday, February 12, 2018 at 9:45 PM To: Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [Ext] RE: Deadline today: Document and Motion deadline Monday 12 February 2018 at 23:59 UTC for the GNSO Council Meeting 22 February at 12:00 UTC Hi Nathalie, Donna is on vacation this week and I have been assigned her proxy. Do I need to re-submit the motion on the Whois Conflict with National Law procedure? We deferred the motion from our January meeting to our February meeting, so I’m not clear on the procedure. Regardless, I would like to move forward the motion for consideration this month. Thanks, Keith From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Nathalie Peregrine Sent: Monday, February 12, 2018 7:01 AM To: council(a)gnso.icann.org Cc: gnso-secs(a)icann.org Subject: [EXTERNAL] [council] Deadline today: Document and Motion deadline Monday 12 February 2018 at 23:59 UTC for the GNSO Council Meeting 22 February at 12:00 UTC Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 12 February 2018 at 23:59 UTC) of the GNSO Council Meeting on 22 February 2018 at 12: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/WgK8B[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…>

4 6

Re: [council] Revised GNSO Liaison to WGs role description
by Darcy Southwell 22 Feb '18

22 Feb '18

Thanks, Marika. I made a few minor edits related to spelling/punctuation. I think your changes reflect the discussions we had and better clarify the liaison role. Darcy From: council <council-bounces(a)gnso.icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Monday, February 12, 2018 at 5:53 AM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Revised GNSO Liaison to WGs role description Dear All, Following the discussions during the Council Strategic Planning Session in Los Angeles, please find attached an updated version of the GNSO Liaison to WGs role description for your review and consideration. The proposed changes in redline format aim to address the comments and suggestions made during the meeting. Please share any further comments and/or edits you may have with the mailing list. Best regards, Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages. _______________________________________________ council mailing list council(a)gnso.icann.org https://mm.icann.org/mailman/listinfo/council

2 1

FW: Notice to GNSO Council - Public Comment on Community gTLD Change Requests
by Marika Konings 21 Feb '18

21 Feb '18

Forwarding on behalf of Russ Weinstein ---- Dear Heather and GNSO Councilors, I wanted to follow up on an item the GDD discussed with the GNSO Council at the ICANN60 meeting, a draft procedure for Community gTLD Change Requests. Based on the guidance<https://gnso.icann.org/en/meetings/minutes-council-1-01nov17-en.pdf> from the Council, ICANN org has collaborated with the Community gTLD working group to develop an draft procedure for ICANN to consider changes to a community gTLD operator’s community registration policies, Specification 12 of their registry agreement. On 14 February 2018, ICANN opened a Public Comment period<https://www.icann.org/public-comments/community-gtld-change-procedure-2018-…> on the Draft Procedure for Community gTLD Change Requests. The proposed draft procedure published in the Public Comment proceeding is the outcome of collaboration and coordination between the working group and the ICANN org over the past few months. These efforts resulted in alignment on the published version of the draft procedure. The proposed procedure provides requirements and criteria for ICANN to consider proposed changes to a community gTLD registry operator’s Specification 12 (Community Registration policies) of the registry agreement. Currently, ICANN has not been approving changes to Specification 12 due to some ambiguity between policy and implementation related to this topic. Please see the rationale included in Section I of the Public Comment proceeding for further information. After the Public Comment closes, the ICANN org and the working group plan to submit the summary and analysis of comments to the GNSO Council. We expect to include a cover note indicating whether or not any policy issues were identified in the public comment forum to ensure it does not raise policy issues before moving toward implementation of a procedure. If the Council advises differently, we’d appreciate input as soon as possible in order to prepare the appropriate work. Here’s the announcement: https://www.icann.org/news/announcement-2-2018-02-14-en. The Public Comment period is now open at https://www.icann.org/public-comments/community-gtld-change-procedure-2018-…. Thanks, Russ Weinstein Director, Registry Services & Engagement ICANN

2 1

FW: [Ext] FW: Revised GNSO Liaison to WGs role description
by Marika Konings 21 Feb '18

21 Feb '18

Dear All, Please find below some suggested additions to the GNSO Liaison to WGs role description from Jeff Neuman. Are there any concerns about adding these provisions to the document? Best regards, Marika From: Jeff Neuman <jeff.neuman(a)comlaude.com> Date: Tuesday, February 20, 2018 at 09:23 To: Heather Forrest <haforrestesq(a)gmail.com>, Marika Konings <marika.konings(a)icann.org>, 'Rafik Dammak' <rafik.dammak(a)gmail.com>, Donna Austin <Donna.Austin(a)team.neustar>, Steve Chan <steve.chan(a)icann.org> Subject: [Ext] FW: Revised GNSO Liaison to WGs role description For what it is worth, I have looked at this document and although it does so good things for its relationship with the GNSO Council, the way it is written it is very one sided towards Council. There should be more provisions in here about the GNSO Liaison working with the Working Group Leadership. For example, it could/should include: * The GNSO Council liaison is responsible for ensuring that the WG Chair(s) are informed about activities of the GNSO Council that have an impact on the Working Group. This includes not only actions taken with respect to substance related to the Working Group, but also any actions taken on matters upon which the Work Group depends or on which the Council depends on the Working Group. * The GNSO Council Liaison should participate in regular meetings with the WG Leadership and consult with WG Leadership prior to providing updates or reports to the GNSO Council. * The GNSO Council Liaison should be the person upon whom the Working Group relies to convey any communications, questions or concerns to the GNSO Council. Those are just a few thoughts from the top of my head based on my observations and having served previously as a liaison to PDPs as well as on the Council. Feel free to forward to the Council list if you want. 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<mailto:jeff.neuman@valideus.com> or jeff.neuman(a)comlaude.com<mailto:jeff.neuman@comlaude.com> T: +1.703.635.7514 M: +1.202.549.5079 @Jintlaw From: council [mailto:council-bounces@gnso.icann.org] On Behalf Of Marika Konings Sent: Monday, February 12, 2018 8:54 AM To: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: [council] Revised GNSO Liaison to WGs role description Dear All, Following the discussions during the Council Strategic Planning Session in Los Angeles, please find attached an updated version of the GNSO Liaison to WGs role description for your review and consideration. The proposed changes in redline format aim to address the comments and suggestions made during the meeting. Please share any further comments and/or edits you may have with the mailing list. Best regards, Marika 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[learn.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

Fwd: [ICANN-CSC] CSC report PTI performance January 2018
by James Gannon 20 Feb '18

20 Feb '18

Hi All, Please find below the CSC Report for Jan 2018. Available as always for questions or comments. -James Gannon Non RySG Liaison to the CSC. Begin forwarded message: From: Bart Boswinkel <bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>> Subject: [ICANN-CSC] CSC report PTI performance January 2018 Date: 16 February 2018 at 16:06:04 GMT+1 To: "soac-infoalert(a)icann.org<mailto:soac-infoalert@icann.org>" <soac-infoalert(a)icann.org<mailto:soac-infoalert@icann.org>> Cc: "icann-csc(a)icann.org<mailto:icann-csc@icann.org>" <icann-csc(a)icann.org<mailto:icann-csc@icann.org>> Dear all, On behalf of the chair of the CSC, Byron Holland, please find included the CSC findings on PTI performance January 2018. Kind regards, Bart Boswinkel 16 February 2018 Dear Community Members, As chair of the Customer Standing Committee I am providing you our January 2018 monthly report on the performance of Public Technical Identifiers (PTI). I am pleased to inform you the CSC has concluded that PTI’s overall performance over January 2018 was again “Excellent”- PTI met all the service level agreement at 100 % !. The CSC was informed that during the reporting period PTI has not received complaints. The January 2018 PTI Naming Performance Report to the CSC, which includes the listing of the individual service level metrics along with their actual and historical performance, can be found at: https://www.iana.org/performance/csc-reports/201801. The CSC and PTI have had productive discussions on Remedial Action Procedures, as foreseen in the CSC charter. The CSC was also informed on the progress of the work of the CSC Charter Review team, a joint ccNSO – Registry Stakeholder Group effort, and looks forward to its findings and proposals. The CSC regular meeting is scheduled at or around the 15th every month, and the CSC report on the PTI performance is send out shortly after that meeting. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list at https://mm.icann.org/mailman/listinfo/csc-announce . Any comments on our reporting to you is welcome. The CSC became effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found at https://www.icann.org/csc[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_csc&d=Dg…> . Kind regards, Byron Holland Chair CSC _______________________________________________ ICANN-CSC mailing list ICANN-CSC(a)icann.org<mailto:ICANN-CSC@icann.org> https://mm.icann.org/mailman/listinfo/icann-csc

2 1

Amended Motion SSC Selection of SSR2 Candidate
by Susan Kawaguchi 20 Feb '18

20 Feb '18

Hello All, The Standing Selection Committee respectfully submits an amended motion has come to full consensus on nominating Rao Naveed Bin Rais for the vacant seat on SSR 2 RT. Please see the Amended Motion attached below. Best regards, Susan Kawaguchi Chair Standing Selection Committee

1 0

Draft GNSO Council Strategic Planning Session Report for your review and comment
by Heather Forrest 20 Feb '18

20 Feb '18

Dear colleagues, Attached please find a draft report of our three-day strategic planning session in January, as prepared by Marika, Rafik and myself. (Donna is currently on leave, and will provide input on her return - we're keen to get this out as soon as possible, so will absorb her input and suggestions as we work through input from you all) I have attached a PDF version and MS Word version - the PDF contains all annexes, but the Word version is missing an annex due to formatting constraints. Please feel free to provide input in whatever form or format works best for you. Sincere thanks again to all for making the three days so productive, Heather

3 2