March 2018 - council - lists.icann.org

Reminder: Informal Council prep session Tuesday 13 March cancelled
by Nathalie Peregrine 13 Mar '18

13 Mar '18

Dear councilors, As a reminder, the GNSO Council informal prep session initially scheduled for today at 18:30 has been cancelled. The GNSO Council meeting will take place tomorrow, Wednesday 14 March 2018 at 1300 local time (17:00 UTC) in room 104. 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 1

Fwd: SSR2-RT
by Heather Forrest 13 Mar '18

13 Mar '18

Dear Council colleagues, Please see below an update from SO/AC Chairs on SSR2-RT. Best wishes, Heather ---------- Forwarded message ---------- From: Heather Forrest <haforrestesq(a)gmail.com> Date: Tue, Mar 13, 2018 at 2:08 PM Subject: SSR2-RT To: Khaled Koubaa <khaled.koubaa(a)board.icann.org> Cc: SO-AC Chairs List <soac-chairs(a)icann.org>, Board Calendaring < board-caucus-ssr2(a)icann.org>, ssr2-review(a)icann.org Dear Khaled, Thank you for your reply on behalf of the Board OEC to our request for support in the appointment of an external facilitator to enable the re-start of SSR2-RT. In this message, while ICANN61 is underway, we hope to answer the questions you have raised to make tangible progress during this meeting and immediately provide the RT members and the broader community with much-needed action and clarity. In short, to the extent that a procure process is necessary, we ask that it commence immediately. The appointment of the facilitator and all new members (already in progress within the SO/ACs) will signal the formal "un-pause" or "re-start" of the SSR2-RT. Our overarching aim is to empower the RT members to come together as a group and progress their work. To that end, it is absolutely imperative that the RT members be involved in this discussion. Our responses here should be interpreted as guidance from the community rather than a top-down mandate. We therefore have included the RT members in this reply, and ask that going forward our communications include them, and that they contribute to these recommendations. To guide the procurement process (specific details for which are set out below) we wish to explain in more detail the intended role of the facilitator. Our email of 15 February stated: "The primary aim of the external facilitator would be to facilitate this transition process, with a view to winding facilitation down when RT members and leaders consider that issues are satisfactorily resolved to continue their work." We consider the role of the facilitator to be a) onboarding new members who have joined since the "pause" and agreeing on leadership from within the current membership; b) helping the group to work through concerns around membership and scope as identified in a confidential survey conducted by the SO/AC Chairs shortly after the pause; and c) helping the RT to identify ways to reach consensus. Specifically in response to the procurement practice: - Skill set requirements: To most effectively fulfil a), b) and c) above, the facilitator should be external to ICANN, with expertise in group dynamics and empowering group members with divergent views and experience to coalesce around a common goal. The SO/AC Chairs will provide the confidential responses received to the survey conducted following ICANN60 which sought RT member input on issues relating to membership and scope, and which generated quite divergent responses. The facilitator must therefore establish a safe space in which the broad range of views on membership and scope can be discussed and common positions identified, with agreement on moving forward in an agreed statement of scope and list of members. - Experience requirements: As appropriate to meet skill set requirements above - Scope of work: a) helping the group to coalesce around leadership and onboarding new members who have joined since the "pause"; b) helping the group to work through concerns around membership and scope as identified in a confidential survey conducted by the SO/AC Chairs shortly after the pause; c) helping the RT to identify ways to reach consensus. - Timing and duration: Facilitation ends when all expected deliverables (below) are completed. - Expected deliverables: a) confirmation of membership list of RT going forward, with chair/s identified; b) an agreed statement of scope; and c) if considered necessary by the RT members, a request from the RT for additional or different resources (ie, more members with particular skills, refinements to staff support), with a clear statement as to how any such request is necessary to and directly supportive of the RT's work. We appreciate your positive response to our initial request, and are prepared to respond promptly to any further questions this week, in order that the procurement process can commence immediately. We ask further that this be prioritised by the OEC so that the facilitator's appointment - and thus the re-start of SSR2-RT - can take place as soon as possible, and *no later than 1 May* for scheduling to take full advantage of face to face time at ICANN62. Kind regards, on behalf of, SO/AC Chairs

1 0

Fwd: [ICANN-CSC] CSC Findings PTI performance February 2018
by James Gannon 13 Mar '18

13 Mar '18

Hi All As always please find below the CSC report for Feb 2018. Unfortunately was not able to be in PR this time but hope to see you all potentially in Panama! -James Gannon (Non-Registry Liason to the CSC) Begin forwarded message: From: Bart Boswinkel <bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org>> Subject: [ICANN-CSC] CSC Findings PTI performance February 2018 Date: 12 March 2018 at 18:58:37 CET 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>> 12 March 2018 Dear Community Members, As chair of the Customer Standing Committee I am pleased to provide you our monthly report on the performance of Public Technical Identifiers (PTI) over February 2018. I am pleased to inform you the CSC has concluded that PTI’s overall performance over January 2018 was Satisfactory – The service level agreement at 96.9% for the month of February 2018. Missed service level agreements that were satisfactorily explained and not an indication of a performance issue. The CSC was informed that during the reporting period PTI has not received complaints. The February 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/201802 . The CSC and PTI have concluded their discussions on Remedial Action Procedures, as foreseen in the CSC charter and now awaits formal agreement. 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 in the near future. Further, the members of the CSC re-appointed the chair for another year. 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 Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org<http://ccnso.icann.org/> -- _______________________________________________ ICANN-CSC mailing list ICANN-CSC(a)icann.org<mailto:ICANN-CSC@icann.org> https://mm.icann.org/mailman/listinfo/icann-csc

2 1

Call for volunteers - GNSO Council liaison to the ccNSO
by Marika Konings 13 Mar '18

13 Mar '18

Sending on behalf of the GNSO Council Leadership Team Dear All, As communicated during the GNSO Council meeting on 14 March 2018, Keith Drazek advised of his intention to step down as the GNSO Council Liaison as soon as a replacement has been found. As a reminder, the role of the GNSO liaison to the ccNSO is to follow the deliberations of the ccNSO and note issues or topics being discussed that are of mutual interest. Furthermore, the liaison is expected to be available to answer any questions or relay any queries the ccNSO may have for the GNSO Council. As such, the GNSO liaison to the ccNSO is expected to: * Participate in the meetings and activities of the ccNSO Council, as appropriate and practicable; * Be sufficiently informed of ongoing GNSO efforts to communicate and advocate the positions of the GNSO to the ccNSO on topics of mutual interest; * Report to the GNSO on current and upcoming activities of the ccNSO that may be of relevance to the ccNSO and broader ccTLD community; * Actively prepare for and participate in bilateral meetings between the GNSO and ccNSO Councils. * Report to the GNSO Council not less than once a month on the activities of the ccNSO. This can be done in writing to the Council mailing list and could include sharing meeting agenda’s and/or meeting outcomes. The liaison should seek specific direction from the GNSO Council on issues of mutual interest where GNSO Council input is required. If you are interested in volunteering to serve as the GNSO Council liaison to the ccNSO, please communicate your interest to the mailing list. To maintain continuity, the Council should confirm a replacement during its meeting at ICANN61. Best regards, Heather, Donna and Rafik Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

2 1

Updated Final Proposed Agenda GNSO Council Meeting - 14 March 2018 at 1300 local time
by Nathalie Peregrine 12 Mar '18

12 Mar '18

Dear all, Please below find the final proposed agenda for the GNSO Council Meeting on 14 March 2018 at 13:00 local time. The agenda items have been moved around to accommodate external speakers and to ensure their presence at the GNSO Council meeting. Final Proposed Agenda 14 March 2018 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://c ommunity.icann.org/x/XgK8B This agenda was established according to the GNSO Operating Procedures v3.2, updated on 01 September 2016. 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. Local time 13:00 San Juan. Coordinated Universal Time: 17:00 UTC: https://tinyurl.com/y7st3et9 10:00 Los Angeles; 13:00 Washington; 17:00 London; 22:00 Islamabad; (Thursday 15 March) 02:00 Tokyo; 04: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 of the GNSO Council meeting on the 30 January 2018 were posted on 16 February 2018 Minutes of the GNSO Council meeting on the 22 February 2018 were posted on XXXXXXX Item 2: COUNCIL DISCUSSION – Discussion with ICANN Finance on the Draft FY19 ICANN Operating Plan and Budget (15 minutes) The GNSO Council determined that it would provide a Council specific response (not to supersede any response from any SG/C) to certain ICANN budget related public comments. Operating on an interim charter, the Standing Committee on Budget and Operations (SCBO) submit a public comment [INSERT LINK] to the Draft FY19 ICANN Operating Plan and Budget by the 8 March 2018 deadline. With the public comment period closed, ICANN Finance has offered to meet with the GNSO at ICANN61 to discuss their submitted public comments, or other finance related topics of interest to the GNSO. Here, the Council will meet with ICANN Finance to discuss finance related items of interest to the GNSO. 2.1 – Presentation of topic (Council Leadership) 2.2 – Council discussion 2.3 – Next steps Item 3. Opening Remarks / Review of Projects & Action List (10 mins) 3.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List and Action Item List Item 4. Consent Agenda (0 min) None Item 5: COUNCIL UPDATE – Updated Charter for the Cross Community Engagement Group on Internet Governance (15 minutes) At ICANN57 in Hyderabad in November 2016, the GNSO Council approved a motion conditioning the future participation of the GNSO as a Chartering Organization of the CCWG on Internet Governance (CCWG-IG) upon a comprehensive review of the group’s Charter by the CCWG-IG, in accordance with the Framework of Uniform Principles for CCWGs that had been adopted recently by the ccNSO and GNSO Councils (http://gnso.icann.org/en/drafts/uniform-framework-principles-recommendation…). In its resolution, the GNSO Council had noted that the CCWG-IG’s future work is expected to be subject to a clear work plan, with regular updates and clear deliverables, and had requested that, by ICANN58, the CCWG-IG was to report on its findings, which report may include a revised charter, and the CCWG-IG was to also consider whether it will be preferable to reconstitute the group under a new structure (https://gnso.icann.org/en/council/resolutions - 20161107-3). The CCWG-IG provided a written report on its 2016 activity and a draft revised Charter for the GNSO Council’s consideration on 10th March 2017 (http://mm.icann.org/pipermail/council/2017-March/019816.html) At its Public Meeting at ICANN58 in Copenhagen on 15 March 2017 and its joint meeting with the ccNSO Council on 13 March 2017, the Council engaged in a discussion with the CCWG-IG co-chairs regarding the group’s reports. At the GNSO Council’s call on 18 May 2017, the Council continued its discussion of the topic as well as during ICANN59 during which it became clear that although there is strong support to continue the GNSO’s involvement in Internet Governance, a CCWG is not considered the appropriate vehicle for such involvement. On 24 August 2017, the Council adopted a motion that among other things, requested that the members of the CCWG-IG explore a framework / model that addresses the concerns expressed by the GNSO Council and then submit this framework / model for Council consideration between ICANN60 and ICANN61. On 22 February 2018, the Council received an update, where it was shared that the CCWG-IG was proposing to restructure itself as a Cross Community Engagement Group. The Council was introduced to the draft charter for this revised cross community group. Here the Council, after having received an update and an opportunity to review the draft charter, will continue its discussion on the revised structure. 5.1 – Introduction of topic (Rafik Dammak) 5.2 – Council discussion 5.3 – Next steps Item 6: COUNCIL DISCUSSION – Update on the GNSO Council’s input to the consultation on the Fellowship Program (15 minutes) On 31 January 2018, ICANN Organization’s Public Responsibility Support department launched a community-wide consultation on the Fellowship Program, to help inform its future direction. A supplementary document was shared at that time, which included available data on Fellows, a questionnaire, and other details about the consultation process. A small group of Councilors volunteered to formulate Council’s response to the questionnaire and/or any questions about the program, by the 30 March 2018 deadline. Here, the Council will receive an update on the progress to date. 6.1 - Update on work to date (Rafik Dammak) 6.2 – Council discussion 6.3 – Next steps Item 7: COUNCIL DISCUSSION – Review of the Inter-Registrar Transfer Policy (IRTP) (15 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 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. 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 agrees with the approach outlined in the letter, ICANN Org would intend to deliver the report by 1 May 2018 and therefore requests that Council provide feedback by 30 March 2018. Here, the Council will consider the proposal and discuss immediate next steps. 7.1 – Presentation of topic (Jennifer Gore, ICANN Organization) 7.2 – Council discussion 7.3 – Next steps Item 8: ANY OTHER BUSINESS (5 minutes) 8.1 – Update from the GNSO Review Working Group ________________________________ 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/en/council/op-procedures-01sep16-en.pdf. References for Coordinated Universal Time of 17:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-7 10:00 San José, Costa Rica (CST) UTC-6 11:00 New York/Washington DC, USA (EDT) UTC-4 13:00 Buenos Aires, Argentina (ART) UTC-3 14:00 Rio de Janeiro, Brazil (BRST) UTC-3 14:00 London, United Kingdom (GMT) UTC 17:00 Paris, France (CEST) UTC+1 18:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 18:00 Islamabad, Pakistan (PKT) UTC+5 22:00 Singapore (SGT) UTC+8 (+ 1 day) 01:00 Tokyo, Japan (JST) UTC+9 (+ 1 day) 02:00 Sydney/Hobart, Australia (AEDT) UTC+11 (+ 1 day) 04:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of March 2018, 2:00 or 3:00 local time (with exceptions) for EU countries. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com and https://tinyurl.com/y7st3et9

2 1

Lunch buffet ready for ccNSO GNSO Council lunch
by Nathalie Peregrine 12 Mar '18

12 Mar '18

Dear all, The lunch buffet for GNSO and ccNSO councilors only is already open in room 104 for the GNSO and ccNSO Council lunch scheduled from 12:15 to 13:30. Kindly make your way there as soon as you can to ensure the meeting starts in a timely manner. Thank you! 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

Re: [council] Payment information Council dinner last night
by Michele Neylon - Blacknight 12 Mar '18

12 Mar '18

Huge thanks to Nathalie for putting last night together To those of you who’ve already reimbursed me – thanks 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: Sunday 11 March 2018 at 08:10 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Payment information Council dinner last night Dear all, Thank you so much for attending the GNSO Council dinner last night! As a reminder, please remember to reimburse Michele, as he advanced payment for all councilors. Price per head was $60, please use Michele’s Paypal account as preferred method of payment: Paypal: michele(a)ceo.hosting<mailto:michele@ceo.hosting>, make sure to choose the option: Send money to a friend, to avoid incurring Paypal fees. Looking forward to seeing you all for the GNSO Working session starting in just under an hour in room 104. Thank you, Nathalie

2 1

Joint meeting with the Governmental Advisory Committee
by Marika Konings 11 Mar '18

11 Mar '18

Dear All, As a reminder, the joint meeting with the GAC takes place today at 15.15 in Ballroom B (the GAC room). The proposed agenda for the meeting is as follows: 1. Welcome – Manal Ismail (GAC) & Heather Forrest (GNSO) 2. Update on latest developments regarding Red Cross/Red Crescent and IGOs (Heather Forrest) 3. Update on current PDPs and on GAC engagement in these 4. Completion of implementation of GAC-GNSO CG recommendations 5. Status update on ‘onboarding’ of new GNSO Liaison to the GAC (Julf Helsingius / Ghislain de Salins) 6. Exchange of views on proposed FY19 Budget 7. AOB The GAC has indicated that they would like to raise GDPR as part of AOB. 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<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

Payment information Council dinner last night
by Nathalie Peregrine 11 Mar '18

11 Mar '18

Dear all, Thank you so much for attending the GNSO Council dinner last night! As a reminder, please remember to reimburse Michele, as he advanced payment for all councilors. Price per head was $60, please use Michele’s Paypal account as preferred method of payment: Paypal: michele(a)ceo.hosting<mailto:michele@ceo.hosting>, make sure to choose the option: Send money to a friend, to avoid incurring Paypal fees. Looking forward to seeing you all for the GNSO Working session starting in just under an hour in room 104. Thank you, Nathalie

1 0

Sad news
by Heather Forrest 10 Mar '18

10 Mar '18

Dear Council colleagues, It is with tremendous sadness that we announce the passing of a member of the GNSO Council, Ben Fuller. Ben has served very ably as the ccNSO liaison to the GNSO Council. We were alerted late last night to this terrible news. Ben was at home this week recovering solidly from heart surgery in February and had planned to be back in the saddle with us for ICANN62. Leadership is arranging flowers on behalf of the Council to Ben's family to express our condolences. We will also find out the best channel for conveying personal messages and let you know once that is identified. Best wishes, Heather, Donna, Rafik

6 7