May 2018 - council - lists.icann.org

Email addresses for abstention form
by Nathalie Peregrine May 30, 2018

May 30, 2018

Hi Steve, As per our conversation earlier, please update the abstention form on the GNSO website to ensure completed forms get sent to: council(a)gnso.icann.org<mailto:council@gnso.icann.org> gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> Other email addresses can be erased. Thanks! 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

Document and Motion deadline Saturday 2 June 2018 at 23:59 UTC for the extraordinary GNSO Council Meeting 12 June 2018 at 12:00 UTC
by Nathalie Peregrine May 30, 2018

May 30, 2018

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Saturday 2 June 2018 at 23:59 UTC) of the extraordinary GNSO Council Meeting focusing on next steps following the ICANN Board adoption of the temporary specification, on Tuesday 12 June 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/-ycFBQ [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

GNSO Council Abstention Notification Form [#274]
by ICANN May 30, 2018

May 30, 2018

1 0

Action Items: GNSO Council meeting 24 May 2018
by Nathalie Peregrine May 29, 2018

May 29, 2018

Dear Councilors, Please find the action items, as stated during the meeting, below arising from the GNSO Council meeting held on Thursday 24 May 2018. Please take note of the action items coming out of the Council sessions and the proposed timing for delivering on these actions. Please ensure your wiki logins are up to date as all Action Items have been assigned to councilors and/or staff and posted on the Action Item wiki page here[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. If you are logged into the wiki when you go to that page, your name will be highlighted alongside the action item assigned to you. Please refer to this page for the recent status updates on the Action items. ACTION ITEMS FROM THE GNSO COUNCIL MEETING 24 MAY 2018 Item 2. Opening Remarks / Review of Projects & Action Items List Action Items: * Council Leadership to prepare note of thanks for Chuck Gomes for his work on the gTLD Registration Data Services PDP, as well as his overall contributions to the GNSO. * Council Leadership to prepare note of thanks for Phil Corwin for his work on the IGO-INGO Access to Curative Rights Protection Mechanisms PDP. * Council Leadership to prepare note of thanks for J. Scott Evans for his work on the Review of All Rights Protection Mechanisms in All gTLDs PDP. Item 3. Consent Agenda Voting Results: * Motions passed unanimously by voice vote. Action Items: * ICANN Staff to communicate Council approval of the appointment of Brian Beckham as an additional co-chair for the Review of All Rights Protection Mechanisms in All gTLDs Policy Development Process Working Group. Item 4: COUNCIL VOTE – Adoption of Revised Charter for the GNSO Standing Selection Committee (SSC) Voting Results: * Motion passed unanimously by voice vote. Action Items: * ICANN Staff to send the updated Charter to the Stakeholder Groups/Constituencies and Nominating Committee (NomCom) appointees on the GNSO Council and remind SG/Cs/NomCom appointees that they should reconfirm their SSC representatives within three weeks following the 2018 Annual General Meeting. * Council Leadership to confirm at its earliest convenience whether a member of the GNSO Council leadership team will serve as an ex-officio member of the SSC and communicate this decision to the SSC. Item 5: UPDATE – IGO-INGO Access to Curative Rights Protection Mechanisms Action items: * Susan Kawaguchi and Heather Forrest to prepare report on the usage of the 3.7 Appeal Process contained in the GNSO Operating Procedure that is intended to capture the process used and lessons learned. Item 6: UPDATE – Review of the Customer Standing Committee (CSC) Charter Action items: * Councilors to review draft comments on the “Review of the Customer Standing Committee (CSC) Charter” and provide suggested edits. * Rafik Dammak to submit comments on behalf of Council, on the basis of non-objection, by 1 June deadline. Item 7: COUNCIL DISCUSSION – Short-Term and Long-Term Options to Adjust the Timeline for Specific Reviews Action Items: * Council to determine next steps, which could include 1) requesting Q&A with MSSI; 2) convening a drafting team and drafting a letter, and/or; 3) filing a public comment to one or both of the short-term and long-term public comment proceedings. Item 8: COUNCIL DISCUSSION – Next steps following adoption of ICANN Board Temporary Specification Action Items: * ICANN Staff to create Google Doc to capture input from Councilors and their respective SG/Cs about what should be discussed in meeting with the ICANN Board. * By 1 June, Councilors to seek input from their respective SG/Cs to determine what they believe should be discussed in meeting the with the ICANN Board, and enter the information in the Google Doc created. * ICANN Staff to schedule meeting with the Board to take place shortly after 1 June. * ICANN Staff to create doodle poll to schedule extraordinary meeting on or around 14 June. * RDS PDP Leadership to prepare post mortem on what took place in the PDP Thank you, 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

Fwd: [CORRESPONDENCE] Chalaby to Forrest re: GDPR Consultation with GNSO
by Heather Forrest May 29, 2018

May 29, 2018

Dear Council colleagues, Please find below a letter to the Council from Board Chairman Cherine Chalaby, who followed our discussions last week on next steps. His invitation of further questions from us link neatly to our discussions in the Council meeting on a follow-up call with the Board. A Google doc for capturing questions for the Board was circulated by staff soon after the Council meeting ended. Unless there are objections I suggest that Council leadership and staff start on Monday working on scheduling this call for the week of 4 June (ie, after we have had the opportunity next week to discuss within SG/Cs and capture questions in the Google doc). Based on the number of volunteers who raised hands during our Council meeting, I suggest we open the call invitation to all interested GNSO Council members. Best wishes and happy weekend to all, Heather ---------- Forwarded message ---------- From: Wendy Profit <wendy.profit(a)icann.org> Date: Sat, May 26, 2018 at 5:09 AM Subject: [CORRESPONDENCE] Chalaby to Forrest re: GDPR Consultation with GNSO To: Heather Forrest <haforrestesq(a)gmail.com> Cc: Cherine Chalaby <cherine.chalaby(a)board.icann.org>, Correspondence < Correspondence(a)icann.org>, Secretary <secretary(a)icann.org>, Board Ops Team < board-ops-team(a)icann.org>, "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, " gnso-chairs(a)icann.org" <gnso-chairs(a)icann.org> Dear Heather, Please find the attached letter from Cherine Chalaby regarding a request on behalf of the ICANN Board for consultation with the GNSO. You may expect the letter to be posted to the ICANN Correspondence page: https://www.icann.org/resources/pages/correspondence. With warm regards, Wendy Profit ICANN – Senior Manager, Board Operations 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094

3 3

Re: [council] [gnso-secs] [CORRESPONDENCE] Chalaby to Forrest re: GDPR Consultation with GNSO
by Heather Forrest May 28, 2018

May 28, 2018

Many thanks, Nathalie, for posting. Not having heard any objections, the leadership team will draft a concise reply thanking Cherine and the Board for following our discussions, and suggest we begin scheduling the call. If anyone does object, please say. Best wishes, Heather On Mon, May 28, 2018 at 5:42 PM, Nathalie Peregrine < nathalie.peregrine(a)icann.org> wrote: > Dear all, > > > > This has now been posted to the GNSO Correspondence page > <https://gnso.icann.org/en/council/correspondence>. > > > > Thank you, > > > > Kind regards, > > > > Nathalie > > > > > > Nathalie Peregrine > > Manager, Operations Support (GNSO) > > Internet Corporation for Assigned Names and Numbers (ICANN) > > Email: nathalie.peregrine(a)icann.org > <http://nathalie.peregrine@icann.org%20> > > Skype: nathalie.peregrine.icann > > > > Find out more about the GNSO by taking our interactive courses and > visiting the GNSO Newcomer pages > <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…> > > > > > > > > *From: *Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Wendy Profit > <wendy.profit(a)icann.org> > *Date: *Friday, May 25, 2018 at 9:12 PM > *To: *Heather Forrest <haforrestesq(a)gmail.com> > *Cc: *Secretary <secretary(a)icann.org>, Correspondence < > Correspondence(a)icann.org>, Board Ops Team <board-ops-team(a)icann.org>, " > gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, "gnso-chairs(a)icann.org" < > gnso-chairs(a)icann.org>, Cherine Chalaby <cherine.chalaby(a)board.icann.org> > *Subject: *[gnso-secs] [CORRESPONDENCE] Chalaby to Forrest re: GDPR > Consultation with GNSO > > > > Dear Heather, > > > > Please find the attached letter from Cherine Chalaby regarding a request > on behalf of the ICANN Board for consultation with the GNSO. > > > > You may expect the letter to be posted to the ICANN Correspondence page: > https://www.icann.org/resources/pages/correspondence. > > > > With warm regards, > > > > Wendy Profit > > ICANN – Senior Manager, Board Operations > > 12025 Waterfront Drive, Suite 300 > <https://maps.google.com/?q=12025+Waterfront+Drive,+Suite+300+%0D%0A+Los+Ang…> > > Los Angeles, CA 90094 > <https://maps.google.com/?q=12025+Waterfront+Drive,+Suite+300+%0D%0A+Los+Ang…> > > > > >

1 0

Reminder: Doodle poll: extraordinary GNSO Council meeting
by Nathalie Peregrine May 28, 2018

May 28, 2018

Dear all, A reminder to please complete the below Doodle poll. For the time being, preferred slots are: Tuesday 12 June 2018 and Wednesday 13 June 2018 at 12:00 pm UTC. Doodle poll: https://doodle.com/poll/2fuuiaia5gc59crq [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_2fuuia…> This will close Tuesday 29 May 2018 at COB UTC. Kind regards, Nathalie From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Friday, May 25, 2018 at 1:24 PM To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] Doodle poll: extraordinary GNSO Council meeting Dear all, As a follow up to the GNSO Council meeting held on the 24 May 2018, please be so kind as to complete the below Doodle poll in order to schedule an extraordinary GNSO Council meeting prior to ICANN62. This Doodle poll will close on the 29th May 2018 at COB UTC. Doodle poll: https://doodle.com/poll/2fuuiaia5gc59crq [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_2fuuia…> 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

ePDP
by Susan Kawaguchi May 27, 2018

May 27, 2018

Hello All, I have given the potential ePDP much thought over the last two days. To effectively do this work at the speed that it will require we need to focus the ePDP. As you all know this is a tremendous amount of work. We need to address the following: Including at the very least the GAC and SSAC in this ePDP will be critical. The members of the team should be limited to 5-6 members of each SG/AC. Each member must agree to accept the fast paced extensive work load, participating on calls, subgroups and drafting when necessary. Understand that their work is representational of the community they are affiliated with and will receive endorsement to express views. Create a leadership team with extensive knowledge and time to focus on this work. Select a Chair that will have the time and skills to effectively manage the ePDP. Include a Board member for oversight and check ins on the team. This ePDP should focus on the critical needs identified in the Annex of the Temporary Spec. first as these issues are of critical importance. (copied below for ease of reference) Annex: Important Issues for Further Community Action The purpose of this Annex is to set forth implementation issues raised during the course of development of this Temporary Specification for which the ICANN Board encourages the community to continue discussing so that they may be resolved as quickly as possible after the effective date of the Temporary Specification. This Annex does not create new or modified requirements for Registrar or Registry Operator, nor is it intended to direct the scope of the Policy Development Process, which will be initiated as a result of the Board’s adoption of thisTemporary Specification. 1. Pursuant to Section 4.4, continuing community work to develop an accreditation and access model that complies with GDPR, while recognizing the need to obtain additional guidance from Article 29 Working Party/European Data Protection Board. 2. Addressing the feasibility of requiring unique contacts to have a uniform anonymized email address across domain name registrations at a given Registrar, while ensuring security/stability and meeting the requirements of Section 2.5.1 of Appendix A. 3. Developing methods to provide potential URS and UDRP complainants with sufficient access to Registration Data to support good-faith filings of complaints. 4. Consistent process for continued access to Registration Data, including non- public data, for users with a legitimate purpose, until the time when a final accreditation and access mechanism is fully operational, on a mandatory basis for all contracted parties. 5. Distinguishing between legal and natural persons to allow for public access to the Registration Data of legal persons, which are not in the remit of the GDPR. 6. Limitations in terms of query volume envisaged under an accreditation program balanced against realistic investigatory cross-referencing needs. 7. Confidentiality of queries for Registration Data by law enforcement authorities. Looking forward to discussing further tonight. Susan Kawaguchi BC Councilor.

6 7

Fwd: Appointment of the ccNSO liaison to the GNSO
by Heather Forrest May 26, 2018

May 26, 2018

Dear Council colleagues, I am pleased to bring to your attention the notification below from Katrina Sataki, ccNSO Chair, regarding the appointment of Adebiyi Oladipo as ccNSO liaison to the GNSO. Best wishes, Heather ---------- Forwarded message ---------- From: Katrina Sataki <katrina(a)nic.lv> Date: Sat, May 26, 2018 at 2:35 AM Subject: Appointment of the ccNSO liaison to the GNSO To: Heather Forrest <haforrestesq(a)gmail.com> Cc: ccnsosecretariat(a)icann.org, Marika Konings <marika.konings(a)icann.org>, biyi(a)biyioladipo.name.ng To : Heather Forrest, Chair of the GNSO Council Re: appointment of the ccNSO liaison to the GNSO 25 May 2018 Dear Heather, It is my pleasure to inform you that the ccNSO Council has appointed Adebiyi Oladipo (.ng) as the ccNSO liaison to the GNSO. I hope the GNSO support team will add Adebiyi (biyi(a)biyioladipo.name.ng) at their earliest convenience to the relevant mailing lists and send him details of any upcoming meetings. For your information I have included the relevant section from the Guideline: ccNSO Liaisons and Observers (https://ccnso.icann.org/ sites/default/files/file/field-file-attach/2017-04/ guideline-liaisons-observers-24mar17-en.pdf ) on the expected roles and responsibilities from our appointed liaisons: • To participate diligently and actively in the meetings and activities of the GNSO on an ongoing and long-term basis; • To communicate and advocate the positions of the ccNSO to the GNSO; • To report to the ccNSO on current and upcoming activities of the GNSO that may be of relevance to the ccNSO and broader ccTLD community; • If feasible and considered relevant ask to the ccNSO for advance guidance, if any, on matters that are going to be discussed by the GNSO; • Participate in GNSO-ccNSO Council meetings agenda committee to prepare the f-2-f meetings, if any. Finally, as both Adebiyi and Phillippe are (relatively) new with respect to their roles as liaisons, we suggest that for both liaisons we try to organise a high-level webinar to brief them on the working method and procedures of the GNSO and ccNSO (Councils) respectively. All Councillors are also welcome, should they wish to participate. If you agree, I suggest that we ask Marika Konings and Bart Boswinkel to organise such a webinar, preferably before ICANN62. On behalf of the ccNSO Council, Katrina Sataki, Chair

1 0

FW: NOTES: ccNSO council meeting | 24 May 2018, 12 UTC
by philippe.fouquart＠orange.com May 25, 2018

May 25, 2018

Councilors, For your information, you’ll find below draft notes of the yesterday’s ccNSO council call. I’d like to draw your attention on a few points which are related to on-going work here: - The appointment of a new ccNSO liaison to GSNO, to be formally notified to the GSNO council later - Elements on on-going/planned changes to the customer standing committee, which shed some light on the rationale for the proposed charter review / report consultation were are having just now - The creation of a study group on emojis, which includes “proponents” of that use. - Placeholder for discussion on CSC effectiveness during our joint meeting in Panama These are only informal notes and we should take them as that but I think it’s worthwhile sharing now given our on-going work. Hope this is helpful. Regards, Philippe From: Ccnso-council [mailto:ccnso-council-bounces@icann.org] On Behalf Of Joke Braeken Sent: Thursday, May 24, 2018 3:44 PM To: ccnso-council(a)icann.org Subject: [ccnso-council] NOTES: ccNSO council meeting | 24 May 2018, 12 UTC Dear all, Please find some high-level notes from the ccNSO Council earlier today below. Best regards, Joke 1. Welcome and apologies Attendance list is available at: http://ccnso.icann.org/about/council/attendance.htm 2. Minutes and Actions 3. Overview inter-meeting council decisions * Appointed coordination team CSC related matters * Decided on the start date of the european special council elections 4. Guideline: ccNSO Procedure for the exercise of the empowered community’s rights to reject Specified Actions Complicated, but the guideline can be found in your inbox. GRC has done its best, even though future adjustments might be needed. Thanks to Stephen for his efforts in drafting the guideline. ECA Update: GNSO Rejection Action Petition Period. Has to do with voting thresholds for the various houses. Letter from ICANN legal : 21 may clarification of the 19 may letter, which contains a mistake (reference to Annex A, whereas it should be ICANN Bylaws chapter 11). Purely a GNSO matter, administrative clean-up. * Approval of the proposed guideline Against? Abstentions? All in favour. The guideline is adopted. 2. Call for volunteers (Councillors) to serve as Rejection Action Petition Manager and back-up Chair is deputy for the position of Stephen in the ECA. So Katrina and Stephen cannot apply for this position. We need a Rejection Action Petition Manager, and a Deputy Rejection Action Petition Manager. They review the petitions we receive, and advise the council on the way forward. We are planning to run some educational sessions, to ensure that those that volunteer are well aware of the process. These people cannot submit any rejection action petitions Action Item: Secretariat will send out call for volunteers to the ccNSO Council. 3. Call for 2 additional volunteers (Councillors) Rejection Action Petition Review Committee Action Item: Secretariat will send out call for volunteers to the ccNSO Council. 5. Appointment ccNSO Liaison to the GNSO Council One response to the call for volunteers: Adebiyi Oladipo (.ng) Chairs, vice-chairs are appointed on a yearly basis. However, the guideline on the appointment of liaisons does not specify this yearly appointment. To be reviewed. No necessarily a term limit. Move? Nigel Seconder? Abibu Against? None Abstentions? None All in favour Action item: chair to inform Biyi and the GNSO Council. GRC to update the guideline 6. Study Group Emoji * Response on letter ICANN CTO Not clear why we have received this letter. We previously discussed what we were going to do with SSAC, with the community, etc. Is there a need to respond? What points to be included in that response? Nigel: proposes that the chair thanks the CTO and noted its content. 2. Appointment members Study Group Call for volunteers, with a good response rate. Table with all volunteers. 2 volunteers not associated to a ccTLD: Jon Roig and Page Howard. All submitted their Consent Form. Nigel: regarding the membership of the Study Group, it is desirable that we have a diversity of viewpoints. Concerned if a Study Group has too many viewpoints that point in one direction. Move? Stephen Seconded? Alejandra For decision: We appoint all volunteers. Chair invited to inform SSAC. SSAC to participate as well in this Group Against? None Abstentions? None All in favour 7. CSC members selection process * Position Jay Daley Jay replaced Brian Cute as interim CEO of PIR. Jay’s term ends in October. Nigel: supports the proposed resolution. Useful opportunity to address a Conflict of Interest Policy, that applies to for instance councillors and appointees to for instance CSC. Bart: in the amended charter there will be note regarding changing circumstances for members of the CSC (Khal Ferer and Elaine Pruise also changed their affiliation) Stephen: also supports Jay staying on board. 2. Kick-off selection process ccNSO appointed member on CSC Guideline: specifies that we need to start a month before the term expires. 4 members, 2 appointed by ccNSO, 2 by RySG. Initial appointment: 1 member will serve for 3 years (Byron), 1 will serve for 2 years (Jay). ccNSO council and GNSO Council will need to appoint the full slate, which means members and liaisons. Term of liaisons from RSAC and GAC will end. They may be re-appointed. Proposed timeline displayed in zoom. Committee with 6 members, 1 per region, and 1 NomCom appointee, that consults with RySG instead of the entire council. For decision: does the selection committee only consult with RySG, or will they also approve the full slate on behalf of the full ccNSO Council? This is what we did last time. However, the member is selected by the entire council. Move? Pablo Seconded? Stephen Against? None Abstentions? None All in favour 8. Scheduling of specific, organisational, and other reviews ICANN Org invites the community to provide feedback. Obvious that we nor ICANN Org can cope with all the reviews running in parallel. WHOIS RS2: one of the arguments used was that we asked for the Operating Standards to be in place first. We also mentioned that there are too many reviews in parallel. Options: * GRC statement to be prepared, to be reviewed by the ccNSO Council. * Should we not stay involved? Draft resolution: prepare a ccNSO statement Move? Stephen Seconded? Alejandra? Abstentions? None Against? None All in favour 9. Engagement Group on IG * Overview of activities and update Young-eum: The group sent the proposed reviewed charter to the SO/ACs. Waiting for comments. Katrina: comments on the wording. In the April 2017 council meeting, we agreed upon questions to the CCWG. They were brought to the attention of the leadership during the June meeting. To date, no response has been received. Our questions are still relevant, and feedback would be appreciated. Young-eum: The group’s sentiment was to address these issues in the revised charter. Additional response to the questions separately is desirable. Concerns by Katrina: * ccNSO as participating organisation does not have any say in the membership. What is our role here? What is the role of the council? * How will the reporting back to the community happen? * How are the community views being gathered? * What happens on a global level and within icann? E.g. ICANN Board group that deals with IG, ICANN Org staff that works on IG, the engagement group on IG. How are these initiatives related, coordinated? Young-eum: We often do not know what other organisations are planning, e.g. ITU. That is also why the roles are sometimes not clearly outlined. This group is trying to coordinate the activities within ICANN as a group working together with ICANN staff and the board. To address issues outside of ICANN. Often this is ad hoc. Katrina: proposed to re-send the questions, and wait for feedback. Many ccTLDs and RO’s are involved in IG work. 2. Amendment of Charter 10. Responsiveness Councillors on calls to assist preparing Panama Sessions Katrina: None of the councillors stepped forward. Barrack volunteered. Discouraging that none of the council members stepped forward. Call to work together and to distribute the workload. Unless there are more volunteers from the council that step forward, we will start appointing people. Let’s lead by example, and give the good example to the community. You know what the value is of the ccNSO. Everybody has certain qualities, and the majority of the ccTLDs are non native EN speakers. Pablo: * LACTLD will be organising a workshop on June 21-22 in Panama. There will be a session on the participation of the ccTLDs from the region in the ccNSO: discussion panel. Pablo, Demi, Bart will be part of that panel. To help encourage the community to further engage with the ccNSO. Especially to those non-spanish speaking ccTLDs from the region. * Thanks for the support by you and the Secretariat. Thanks also to fellow council members that provide a helping hand. People are hesitant to ask for help. Margarita: follow-up from the discussion in Puerto Rico. If you do not add value, and are not an active participant, it does not make sense to participate. Language barrier: non English speakers. Stephen: Ability to engage in a conversation in a second language is appreciated. 11. PDP Retirement Getting prepared for the Panama meeting. Face-to-face meeting in Panama from 09:00 to noon on Thursday. Closure on language at the face to face meeting 12. ECA, CSC, RZERC Update * ECA 21 may letter as a correction, however the 19th of may was a deadline. ECA is wondering what to do about this. Nigel: important to set the expectations. We expect people to follow the rules. 2. CSC Report received 3. RZERC Report received 13. ICANN62 * ccNSO Council meetings Monday, 25 June (Day 1) 12:15-13:30 – ccNSO Council Preparatory Meeting (lunch) Monday, 25 June 2018 (Day 1) 18.30-19:30 – Joint ccNSO / GNSO (with cocktail) Topics: CSC charter update, initiating CSC Effectiveness review, progress cross-community groups (Auction Proceeds, Internet Governance) Tuesday, 26 June 2018 (Day 2) 14:00-15:00– Joint ccNSO / GAC Topics meeting with GAC? Peter: joint session with GAC reduced to 60 minutes. Kindly inform Peter on the topics to be addressed. E.g. participation of GAC in the ccNSO PDP Wednesday 27 June 2018 (Day 3) 17:00-18:30 ccNSO Council Face to Face Meeting 2. ICANN62 ccNSO Meetings Agenda Block Schedule displayed on zoom. Main changes: * ccNSO Council on Wednesday * ccNSO cocktail: requested to have it after the networking hour scheduled by ICANN. Starting at 19:30 * ccTLD News Slightly shorted, and the volunteer session is now slightly longer Pablo: will there be a follow-up session on the disaster session from Puerto Rico? Alejandra: yes. Wednesday, from 09:00 to 09:45, to build on something for Barcelona. 14. Council updates * Chair update * Vice-chair update * Councillor update * Regional organisations Update * Secretariat update 15. WG Update * GRC * CCWG Auction Proceeds * SOPC * GNSO PDP Subsequent procedures WT5 16. Liaison updates * GNSO Update * ALAC update 17. Next meetings 27 June – face to face, Panama City 23 August – 12:00 UTC (July and Aug combined) 20 September 18:00 UTC October – face to face, Barcelona (date tbd) 15 November – 11:00 UTC 13 December – 17:00 UTC 18. AOB * GDPR: If you go to the ccNSO website, you will see a link to the updated privacy policy. * NomCom update by Pablo. In March, a number of applications were received. Candidates that applied for various positions. 37 individuals were interviewed. Face-to-face meetings in Panama. The final selection will be made there. * Does GDPR affect our procedures? The ccNSO website is maintained by ICANN Org, part of the internal ICANN Org rules and procedures. Other changes: subscription to WGs. We now seek consent. SOI being published: will have an impact. Bart to verify. Thank you all, see you in Panama, and remember to volunteer. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1