January 2017 - council - lists.icann.org

Community Budget Requests for FY18 - GNSO Council Submission
by James M. Bladel Feb. 8, 2017

Feb. 8, 2017

Councilors - As discussed during our 19 JAN call, please find attached two FY18 Budget Request submissions on behalf of the GNSO Council. The first is to allocate travel support funds for chairs of PDP working groups to attend ICANN meetings who might not otherwise be able. This is aligned with the GNSO's desire to make & keep support for policy development work a priority in the budget. The second provides for a GNSO Council Strategic Planning session, outside of the full ICANN schedule, for Councilors to meet and set priorities for the upcoming Council year. This pilot would take place in January 2018. Please note these request submissions are coming from the Council, and are not intended to replace or supplement requests that are coming on behalf of your SGs and Cs. Discuss on this thread if you have any questions, edits or objections to these requests. The deadline for submission has been extended, and requests will now be accepted until 10 FEB 2017. Thank you, J. ------------- James Bladel

5 6

Fwd: CCWG-Accountability WG proposal for a Limited Scope of the ATRT3 Review - reminder
by James M. Bladel Feb. 7, 2017

Feb. 7, 2017

Councilors - Please see the message from CCWG Staff, below. Most of the SO-AC chairs (myself included) took this note as informational, and missed the call to action. In a nutshell, the CCWG co-chairs note that the upcoming ATRT3 review team will overlap significantly with the recently completed (Workstream 1) and ongoing work (Workstream 2) of CCWG-ACCT. Like the approach to WHOIS2, they are proposing a reduced scope for this next review to avoid collision/duplication of work. I'd welcome any comments or thoughts you might have on this, and we can add it as a discussion item for our draft agenda for our Council call in February. Thank you, J. ------------- James Bladel _____________________________ From: Bernard Turcotte <turcotte.bernard(a)gmail.com<mailto:turcotte.bernard@gmail.com>> Sent: Wednesday, January 25, 2017 14:41 Subject: CCWG-Accountability WG proposal for a Limited Scope of the ATRT3 Review - reminder SO and AC Chairs, This is a reminder that the CCWG-Accountability has not received any replies to its December 2nd proposal (original message below) regarding the scope of the upcoming ATRT3 review which will be publishing its call for volunteers by the end of January. As stated in the proposal there are a number of significant overlaps between the work of the CCWG-Accountability and a standard ATRT review which would cause an important duplication of work between these two processes. The CCWG-Accountability simply wishes to ensure that the SO's and AC's are aware that if there is no request from the SO's and AC's to modify the scope of the ATRT3 review prior to its launch that it will proceed as a standard review. The Co-Chairs of the CCWG-Accountability remain available to the SO's and AC's for further discussions or answer any questions. Bernard Turcotte ICANN Staff Support to the CCWG-Accountability for The Co-Chairs of the CCWG-Accountability. On Fri, Dec 2, 2016 at 5:07 AM, Mathieu Weill <mathieu.weill(a)afnic.fr<mailto:mathieu.weill@afnic.fr>> wrote: Dear SO & AC Chairs, The CCWG-Accountability (CCWG) at its face to face meeting at the ICANN 56 in Helsinki considered the implications of the collision of topics, and therefore efforts, between ATRT3 and Work Stream 2 (WS2) (please see Annex 1 for a detailed consideration of this issue). In its discussion of this issue the CCWG considered the following points: • Collision of topics between WS2 and ATRT3 - There is potential for significant overlap between WS2 topics and the scope of ATRT3 as 6 of the 9 WS2 topics are accountability and transparency issues ATRT3 could also consider. • Timing of the two activities - WS2 began in July 2016 with an objective of completing its work by the end of 2017. ATRT3, which is expected to take 12 months to complete, is currently scheduled to begin in January 2017 but could potentially be delayed until February 2018 under the new Bylaws (which require ATRT every 5 years versus the AoC requirement for every 3 years). It would seem inefficient, at best, to have both of these activities working on the same topics independently, while drawing on the same pool of community volunteers. At worst, ATRT3 and WS2 groups could issue recommendations that are conflicting or duplicative. • Implementation of recommendations – The Bylaws for WS2 give CCWG recommendations greater weight when it comes to board consideration, relative to recommendations from an ATRT organized under the AoC. While in Helsinki, the CCWG concluded its preferred approach, as communicated in our 8-Aug-2016letter<https://www.icann.org/en/system/files/correspondence/sanchez-et-al-to-icann…> to the Board of ICANN: Convene ATRT3 as soon as possible with the limited scope of assessing implementation of ATRT2 recommendations. Allow WS2 to handle new recommendations for accountability and transparency. The fourth ATRT would convene before 2022 and would assess all accountability and transparency topics and make recommendations The ICANN Board replied<https://www.icann.org/en/system/files/correspondence/crocker-to-sanchez-et-…> to the CCWG letter on 24-Oct-2016, saying, It is not up to the Board to dictate the scope of this important community review. While we share the concerns raised of avoiding duplication of resources, it is essential that the broader ICANN community have a voice in determining how the ATRT3 should be scoped in alignment with the Bylaws. The Board and the ICANN Organization stand ready to support the community’s direction. Accordingly, the CCWG is now proposing to community leadership the following approach: • Requesting that the SO/AC leadership select (following the new Bylaws) a small group of review team members that have either participated in or closely tracked ATRT2. • Requesting the ICANN organization to do a "self-assessment" reporting on a) the extent to which each recommendation was followed and/or implemented; b) the effectiveness in addressing the issues identified by ATRT2; and c) the need for additional implementation. • Specifically request that the Review Team exclude the issues that are already covered by the CCWG-Accountability WS2 (see Annex 1). • Suggesting that the work be conducted & completed more quickly than normal, such as asking that the Final Report be issued within six months If the suggested approach above is agreeable to SO/AC community, the next steps would be: • SO/AC leadership to issue a public statement or a letter to ICANN CEO and Board Chair that explains why limited scope is appropriate and articulates that they have broad support of the ICANN community • Call for Volunteers to note limited scope & unique expertise sought • Reach out to previous ATRT Review Team members and encourage them to apply for the narrowly-scoped ATRT3 Review Team • Propose a Charter for the ATRT3 Review Team to adopt that tracks the limited Scope Best regards, Thomas Rickert, Leon Sanchez & Mathieu Weill CCWG-Accountability Co-chairs _______________________________________________ Acct-Staff mailing list Acct-Staff(a)icann.org<mailto:Acct-Staff@icann.org> https://mm.icann.org/mailman/listinfo/acct-staff

3 3

Updated draft Minutes Meeting of the GNSO Council 19 January 2017 to review
by Nathalie Peregrine Jan. 31, 2017

Jan. 31, 2017

Dear all, Please find the draft minutes of the GNSO Council meeting on the 19 January 2017 edited with Heather’s changes and updated Action Items. Kind regards, Nathalie From: "owner-gnso-secs(a)icann.org" <owner-gnso-secs(a)icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Monday, January 30, 2017 at 6:28 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] Draft Minutes Meeting of the GNSO Council 19 January 2017 to review Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting on the 19 January 2017 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 10th February 2017. Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC 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<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Draft Minutes Meeting of the GNSO Council 19 January 2017 to review
by Nathalie Peregrine Jan. 31, 2017

Jan. 31, 2017

Dear Councilors, Attached, please find the draft minutes of the GNSO Council meeting on the 19 January 2017 for your review. If there are no comments, these minutes will be published on the website as approved, according to the GNSO Rules of Procedure <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_counc…> section 3.5 "If no objections are received within 10 days, the minutes will be deemed to have been approved for posting" on 10th February 2017. Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC 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<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

2 2

(no subject)
by Erika Mann Jan. 31, 2017

Jan. 31, 2017

Dear All - I just wanted to inform you that ICANN is now publishing all registry change of control and assignments. Thanks goes to Cyrus and team for getting this done! I wanted to let you know that we now publish all the registry change of control and assignments here: https://www.icann.org/resources/pages/registry- agreement-assignment-direct-changes-of-control-2017-01-27-en Best, Erika

3 3

Action Items: GNSO Council meeting on 19 January 2017
by Nathalie Peregrine Jan. 30, 2017

Jan. 30, 2017

Dear Councilors, Please find the action items, below and as attachment, arising from the GNSO Council meeting on 19 January 2017. Please take note of the action items coming out of the Council meeting before the break and the proposed timing for delivering on these actions. The next GNSO Council meeting is on the 16 February 2017. ACTION ITEMS FROM GNSO COUNCIL MEETING 19 January 2017 Item 2. Review of Projects & Action List Action Items: Response to GAC Communique * As a Council response is likely to be more helpful if one is finalized and communicated sooner rather than later, Council to consider whether it will be possible (and desirable) to aim to have future responses completed before the Board and GAC have their post-ICANN Meeting call to discuss the Communique. Item 4. COUNCIL VOTE – Endorsement of GNSO Representatives to the Second Security, Stability & Resiliency Review Team (SSR-2 RT) Voting Results: * Motion passed unanimously * 3 primary candidates endorsed (James Gannon, Denise Michel, Emily Taylor) * 4 additional candidates endorsed, to be considered by the SO/AC leaders if additional slots become available on the SSR-2 RT (Howard Eland, Scott McCormick, Rao Naveed bin Rais, Norm Ritchie) Action Items: * Policy staff to notify candidates selected (including alternates) and send names to ICANN’s Multi-Stakeholder Strategy & Strategic Initiatives (MSSI) Department staff supporting the SSR-2 RT (IN PROCESS) * Council to review process for selection of RT representatives, particularly the ability of candidates to be endorsed by more than one SO/AC, and not just those applicants that sought a particular SO/AC’s endorsement (IN PROCESS) * Council leadership, Susan Kawaguchi and Ed Morris to continue work on finalizing proposal regarding selection process for RT and other GNSO appointments for Council consideration Item 5. COUNCIL DISCUSSION – Proposal for a Facilitated Discussion between the GAC and the GNSO to Resolve Outstanding Differences in GAC Advice and GNSO Policy Recommendations concerning Second Level Protections for International Governmental Organization (IGO) Acronyms and Certain Names and Acronyms of the Red Cross Movement Action Items: * Staff to confirm availability of Thomas Rickert (Chair, original IGO-INGO PDP), and Philiip Corwin and Petter Rindforth (Co-Chairs, IGO-INGO Curative Rights PDP), to serve as GNSO representatives (along with GNSO Council leadership and the GNSO Liaison to the GAC) for the facilitated discussion (IN PROCESS) * Subject to their confirmation, Thomas, Phil, Petter and Carlos to be added by staff to the new Board-GAC-GNSO Representatives’ Discussion Group (IN PROCESS) * Staff to send links to the new Discussion Group to Council mailing list (DONE) * Staff to notify the GAC and Board members of the Discussion Group, and Bruce Tonkin (facilitator) of GNSO appointments (IN PROCESS) * Staff to invite Bruce Tonkin to the next GNSO Council meeting Item 6. COUNCIL DISCUSSION – Letter from Thick WHOIS Implementation Review Team on Privacy Issues relating to Implementation of the Thick WHOIS Consensus Policy Recommendations Action Items: * Staff to post legal review document referred to in the letter to the Council mailing list (DONE) * Following receipt of the legal review document, Erika Mann and Michele Neylon to work with staff to develop possible responses to the IRT letter for the Council’s consideration, based on further legal developments relating to the topics noted in the letter * Council to continue discussion on the mailing list, to see if there is a need to respond to the IRT * Staff to share IRT letter with RDS WG leadership as the subject concerns all registries and registrars using a thick model and is not limited to the specific issue of transition from thin to thick WHOIS (DONE) Item 7: COUNCIL DISCUSSION – Community Budget Requests for Financial Year 2018 Action Items: · Council leadership to work with staff to develop possible draft proposals for Council consideration (DONE) Item 8: COUNCIL DISCUSSION – Planning for ICANN58 Action Items: · Council to continue discussion on mailing list · Council leadership to suggest adding session on data privacy to Day 3 schedule (DONE) Please let me know if I missed anything or if you have questions. Thank you. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC 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<learn.icann.org/courses/gnso> 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

FOR INFORMATION & CIRCULATION: Webinar on IGO-INGO Curative Rights - the PDP Working Group's Initial Report
by Mary Wong Jan. 30, 2017

Jan. 30, 2017

Dear Councilors, On 7 February 2017 at 1400 UTC, Phil Corwin and Petter Rindforth – Working Group co-chairs of the GNSO PDP on IGO-INGO Access to Curative Rights Protection Mechanisms - will be presenting a webinar where they will discuss the Working Group’s preliminary recommendations: https://www.icann.org/news/announcement-2-2017-01-27-en. Given the history and complexity of the topic, we hope this webinar will be helpful to Councilors and your respective community groups. A link to a sign-up form for the webinar as well as the Initial Report can be found in the webinar announcement. Please circulate the announcement to your communities, and note that the public comment period will close on 1 March 2017. For those who will not be able to attend the webinar in real-time, a recording as well as the slides will be made available. Thanks and cheers Mary Mary Wong Senior Policy Director Internet Corporation for Assigned Names and Numbers (ICANN) Email: mary.wong(a)icann.org Telephone: +1-603-5744889

1 0

Document and Motion deadline Monday, 6 February 2017 at 23:59 UTC for the GNSO Council Meeting 16 February 2017 at 12:00 UTC
by Nathalie Peregrine Jan. 26, 2017

Jan. 26, 2017

Dear Councilors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 6 February 2017 at 23:59 UTC) of the GNSO Council Meeting on 16 February 2017 at 12:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/x/PI7RAw Thank you very much. Kind regards, Nathalie -- Nathalie Peregrine Specialist, SOAC 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<learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

PLEASE REVIEW: updated draft GNSO Block Schedule for ICANN58
by Mary Wong Jan. 26, 2017

Jan. 26, 2017

Dear Councilors, Following additional coordination with our colleagues supporting other SO/ACs and projects, we have updated the draft GNSO Block Schedule that was last circulated for the Council meeting last Thursday. Please use the attached, updated version for your and your group’s planning purposes as it contains several substantial updates. These changes include: · Updated timings for the various sessions on Day 2 (Sunday 12 March), which is the all-day GNSO Working Session · A slightly earlier start for Day 2 (Sunday), to allow for an on-time start (given the single day allocation, there is also an assumption that the preparation for the joint meetings with the Board, GAC and ccNSO will be done prior to ICANN58, e.g. via teleconference and the mailing list) · Addition of a session for data privacy (per Council discussion on the call last week, which request has now been conveyed to the Meetings Team) · A 2-hour slot (per Council leadership request) on Day 5 (Wednesday 15 March) for the GNSO Council Public Meeting · Specific allocated slots on Day 5 (Wednesday) for those GNSO Working Groups, CCWGs (other than Accountability), and IRTs in which GNSO community members are involved – note that staff is proposing these slots after consultation with colleagues from GDD and ccNSO and GAC support Staff is now in the process of preparing GNSO session requests for submission into the overall ICANN meeting schedule. In that regard, I’ll note that those SG/C requests that were sent to Glen are also being processed by staff at this time. Thanks and cheers Mary

1 0

FOR INFORMATION & DISTRIBUTION: IGO-INGO Curative Rights PDP Initial Report now open for public comment
by Mary Wong Jan. 25, 2017

Jan. 25, 2017

Dear Councilors, Staff is pleased to inform you that the IGO-INGO Curative Rights PDP Working Group, co-chaired by Phil Corwin and Petter Rindforth, published its Initial Report for public comment on Friday 20 January: https://www.icann.org/public-comments/igo-ingo-crp-access-initial-2017-01-2…. The public comment period closes on 1 March 2017, and the Working Group is planning on holding an open community session to discuss its preliminary recommendations during ICANN58. In addition, as noted during the last GNSO Council meeting, Phil and Petter will be conducting a webinar in early February to present the preliminary recommendations to the community. We are also consulting with Carlos (GNSO liaison to the GAC) and GAC support staff to find out if, and what sort of, separate session should be conducted for the GAC. We will be sure to provide that information to you when confirmation details are available. Following its review of all public comments and community feedback received, the Working Group will prepare its Final Report with its final recommendations for submission to the Council for your review and action. Thanks and cheers Mary Mary Wong Senior Policy Director Internet Corporation for Assigned Names and Numbers (ICANN) Email: mary.wong(a)icann.org Telephone: +1-603-5744889

2 1