February 2019 - Ccnso-council

outcome of the Council Selection Process for the ccNSO appointed liaison to the GNSO
by Joke Braeken Feb. 25, 2019

Feb. 25, 2019

Dear all, This is to inform you about the outcome of the second round of the Council Selection Process for the ccNSO appointed liaison to the GNSO, which closed Friday, 22 Febr. 2019 (23:59 UTC). The applicants were (in alphabetical order): Moore, Alyssa (.ca) Simon, Maarten (.nl) In the table included below and in attachment, you will be able to find an overview of the ballot numbers, their date of receipt and the order of preference as listed by the individual council members. 15 councillors submitted their preference before the deadline. ballot number date receipt ballot Alyssa Moore (20 points) Maarten Simon (25 points) 1 15 February 2019 1 2 2 15 February 2019 2 1 3 15 February 2019 1 2 4 15 February 2019 1 2 5 15 February 2019 2 1 6 17 February 2019 2 1 7 17 February 2019 2 1 8 17 February 2019 1 2 9 17 February 2019 1 2 10 17 February 2019 1 2 11 18 February 2019 1 2 12 19 February 2019 1 2 13 21 February 2019 2 1 14 21 February 2019 1 2 15 22 February 2019 1 2 The candidate with the most supportive votes: Maarten Simon Next Steps The volunteer who receives the majority of the votes lodged shall be considered to be appointed by the ccNSO Council. The Chair of the ccNSO will inform the ICANN Secretary and the respective Supporting Organization or Advisory Committee of the appointment. Background * ccNSO Guideline: Liaison and Observers https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/… [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…> * The current GNSO liaison, Biyi Oladipo (.ng), will take a seat on the ccNSO Council at the end of ICANN64 in Kobe. Consult the latest council election report here [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…>. * Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-21jan19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> Thank you. Best regards, 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

1 0

Reminder - ACTION REQUIRED: 2nd round selection process for the ccNSO appointed liaison to the GNSO
by Joke Braeken Feb. 21, 2019

Feb. 21, 2019

Dear councillors, This is a reminder regarding the second round in the selection process for the ccNSO appointed liaison to the GNSO, which closes tomorrow, Friday, 22 February 2019 (23:59 UTC) 13 out of 18 councillors casted their vote to date. See: https://community.icann.org/display/ccNSOCWS/Council+vote+tracker+-+2019 The call for volunteers for the ccNSO appointed liaison to the GNSO closed 4 February 2019, 23:59 UTC), and the first selection round closed 12 February 2019 (23:59 UTC). Since two candidates were equally preferred, the secretariat is now initiating a second round in the selection process for the ccNSO appointed liaison to the GNSO. Your action is required by Friday, 22 February 2019 (23:59 UTC) Who is eligible to vote? All current members of the ccNSO Council. Consult the list here: https://community.icann.org/display/ccNSOCWS/Council+vote+tracker+-+2019 Please find included: * Description of the selection process (see below) * Application material as submitted by the 2 candidates that were equally preferred in the first selection round, in alphabetical order: Moore, Alyssa (.ca) Simon, Maarten (.nl) INSTRUCTIONS: * Please select your preferred candidate by sending an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, no later than Friday, 22 February 2019 (23:59 UTC), with the subject line: ccNSO appointed Liaison to the GNSO. * Your most preferred candidate should receive three (2) points, the second and least preferred candidate one (1) point. If you believe a candidate does not meet the criteria: please assign zero (0) points. A kind reminder that the ccNSO Secretariat will track and publish for each council member its participation in an election process. Consult the link here: https://community.icann.org/display/ccNSOCWS/Council+vote+tracker+-+2019 Thank you and kind regards, Joke Braeken SELECTION PROCESS The applicants in alphabetical order: Moore, Alyssa (.ca) Simon, Maarten (.nl) The application material as submitted by the applicants is included in attachment. Selection and procedure You are requested to assess which candidate you find most suited as ccNSO appointed member to the GNSO, based on the material provided. To assist you in your assessment, the expectations and responsibilities of the ccNSO appointed liaison to the GNSO can be consulted here: https://ccnso.icann.org/en/announcements/announcement-21jan19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> INSTRUCTIONS: * Please select your preferred candidate by sending an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>, no later than Friday, 22 February 2019 (23:59 UTC) , with the subject line: ccNSO appointed Liaison to the GNSO. * Your most preferred candidate should receive three (2) points, the second and least preferred candidate one (1) point. If you believe a candidate does not meet the criteria: please assign zero (0) points. Administrative Procedure After we received your email, we will acknowledge receipt and include a ballot number and date of receipt. On Monday, 25 February 2019, the ccNSO Secretariat will circulate an email to the list, which will include an overview in the following format: - Ballot number, - Date ballot was received, - preferred candidate per ballot. This email will also include the total level of preference per candidate. The candidate receiving most supportive votes, is selected. In the event the two candidates are equally preferred; a run-off selection will be needed. The volunteer who receives the majority of the votes lodged shall be considered to be appointed by the ccNSO Council as of the date of adoption of the Election Report. The Chair of the ccNSO will inform the ICANN Secretary and the respective Supporting Organization or Advisory Committee of the appointment. Background * ccNSO Guideline: Liaison and Observers https://ccnso.icann.org/sites/default/files/file/field-file-attach/2017-04/… [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…> * The current GNSO liaison, Biyi Oladipo (.ng), will take a seat on the ccNSO Council at the end of ICANN64 in Kobe. Consult the latest council election report here [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_sites_…>. * Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-21jan19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=Dw…> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso…> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGa…>

1 0

Re: [ccnso-council] Risk Mitigation Process under Fast Track Process
by Peter Vergote Feb. 21, 2019

Feb. 21, 2019

Hi Bart, I support. Best regards, Peter From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Wednesday, 20 February 2019 at 17:52 To: "ccnso-council(a)icann.org" <ccnso-council(a)icann.org> Subject: [ccnso-council] Risk Mitigation Process under Fast Track Process Dear all, One of the topics introduced on the last Council call was on the work of the joint ccNSO-SSAC joint working party regarding the Guideline for the Risk Mitigation Process, as part of the Fast Track Implementation Plan. As said on call the SSAC was asked whether they had any objection to the way forward as proposed by the working party and accordingly SSAC has no objection to the approach proposed. Please note this is NOT about changing the Fast Track Implementation Plan. The ICANN Board has already adopted the changes the joint ccNSO -SSAC working party has proposed in 2017. To recap, the working party proposes: 1. the amended Guideline (included) 2. A test of the Guideline with the only case pending ( .EU in Greek), document included 3. Recommending ICANN (Board, or the Organisation, whomever is mandated) to take a final decision (see included draft cover letter) 4. Expression of support of proposed approach by ccNSO Council and non-objection by SSAC (note the SSAC position was framed this way top overcome procedural issues), reflected in the draft cover letter, You are now asked to express whether you support, abstain of have objection to the approach proposed by the joint working party. Please respond to the list by 27 February 2019, 17.00 UTC (preferably earlier). Kind regards, Bart

1 0

Re: [ccnso-council] Risk Mitigation Process under Fast Track Process
by Peter Vergote Feb. 21, 2019

Feb. 21, 2019

From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Wednesday, 20 February 2019 at 17:52 To: "ccnso-council(a)icann.org" <ccnso-council(a)icann.org> Subject: [ccnso-council] Risk Mitigation Process under Fast Track Process Dear all, One of the topics introduced on the last Council call was on the work of the joint ccNSO-SSAC joint working party regarding the Guideline for the Risk Mitigation Process, as part of the Fast Track Implementation Plan. As said on call the SSAC was asked whether they had any objection to the way forward as proposed by the working party and accordingly SSAC has no objection to the approach proposed. Please note this is NOT about changing the Fast Track Implementation Plan. The ICANN Board has already adopted the changes the joint ccNSO -SSAC working party has proposed in 2017. To recap, the working party proposes: 1. the amended Guideline (included) 2. A test of the Guideline with the only case pending ( .EU in Greek), document included 3. Recommending ICANN (Board, or the Organisation, whomever is mandated) to take a final decision (see included draft cover letter) 4. Expression of support of proposed approach by ccNSO Council and non-objection by SSAC (note the SSAC position was framed this way top overcome procedural issues), reflected in the draft cover letter, You are now asked to express whether you support, abstain of have objection to the approach proposed by the joint working party. Please respond to the list by 27 February 2019, 17.00 UTC (preferably earlier). Kind regards, Bart

1 0

QUESTION: New membership application: .tc
by Katrina Sataki Feb. 21, 2019

Feb. 21, 2019

Dear Abibu, All, Sorry, I am a little late with my question but could anyone please explain what does the response from IANA Services actually mean: “Even though John Williams is still listed in the IANA Root Zone Database, we know from discussions with .TC operators and the TC Regulatory Authority that Mr. John Williams is no longer serving in this capacity. Melrex (the TLD Manager) and TCI Telecommunications Commission are in discussions about operating .TC going forward” If I understand it correctly, there are discussions and IANA is informed about them even though there are no formal requests to transfer the ccTLD. Correct? Technically, it should not be our concern who is the admin contact as long as the TLD Manager is correct. But if we are informed about the discussions, maybe we should at least inquire what is going on there? As we have no formal procedure for dealing with issues like this, we need to agree on the way forward. What is your opinion? Thank you! Regards, ]{atrina From: Ccnso-council [mailto:ccnso-council-bounces@icann.org] On Behalf Of Abibu R. Ntahigiye Sent: Thursday, February 14, 2019 4:09 PM To: ccnso-council(a)icann.org Subject: [ccnso-council] New membership application: .tc Dear All, The ccNSO Secretariat has received a new application for ccNSO membership, from .tc (Turks and Caicos Islands). Kindly provide me with your input by the end of 19 February 2019 23:59 UTC, in case you do not agree with the ccNSO membership accreditation. The following checks have been completed for this ccNSO membership application: * The ccNSO Secretariat confirms that the application details are those of the ccTLD Manager as specified in the IANA Database * The ccNSO Secretariat informed the IANA Services staff about the membership application. * IANA Services provided the following information: 1. There are no currently pending requests for .TC 2. Even though John Williams is still listed in the IANA Root Zone Database, we know from discussions with .TC operators and the TC Regulatory Authority that Mr. John Williams is no longer serving in this capacity. Melrex (the TLD Manager) and TCI Telecommunications Commission are in discussions about operating .TC going forward. Details of the application: Name of ccTLD Manager: Melrex TC Name of Representative: John Williams Name of Primary Contact: John Williams Primary Contact Address: TCI Telecommunications Commission P.O. Box 203 872 Business Solutions Building Leeward Highway Providenciales Turks And Caicos Islands Primary Contact Telephone Number: 649-946-1900 Primary Contact E-Mail: johnwilliams(a)tcitelecommission.tc <mailto:johnwilliams@tcitelecommission.tc> rgds -- Eng. Abibu R. Ntahigiye | CEO, Tanzania Network Information Centre, 147 Kambarage Road - Mikocheni Tel: +255 (22) 2772659 | Mobile: +255 767 279511 Fax: +255 (22) 2772660 Email: abibu(a)tznic.or.tz <mailto:abibu@tznic.or.tz> | Website: www.tznic.or.tz <http://www.tznic.or.tz> Visit www.karibu.tz <http://www.karibu.tz> for your .tz domain registration

4 3

Re: [ccnso-council] Risk Mitigation Process under Fast Track Process
by Stephen Deerhake ＠ ASNIC Feb. 20, 2019

Feb. 20, 2019

Greetings Bart, I abstain. Best regards, /Stephen From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Wednesday, February 20, 2019 at 20:53 To: "ccnso-council(a)icann.org" <ccnso-council(a)icann.org> Subject: [ccnso-council] Risk Mitigation Process under Fast Track Process Dear all, One of the topics introduced on the last Council call was on the work of the joint ccNSO-SSAC joint working party regarding the Guideline for the Risk Mitigation Process, as part of the Fast Track Implementation Plan. As said on call the SSAC was asked whether they had any objection to the way forward as proposed by the working party and accordingly SSAC has no objection to the approach proposed. Please note this is NOT about changing the Fast Track Implementation Plan. The ICANN Board has already adopted the changes the joint ccNSO -SSAC working party has proposed in 2017. To recap, the working party proposes: 1. the amended Guideline (included) 2. A test of the Guideline with the only case pending ( .EU in Greek), document included 3. Recommending ICANN (Board, or the Organisation, whomever is mandated) to take a final decision (see included draft cover letter) 4. Expression of support of proposed approach by ccNSO Council and non-objection by SSAC (note the SSAC position was framed this way top overcome procedural issues), reflected in the draft cover letter, You are now asked to express whether you support, abstain of have objection to the approach proposed by the joint working party. Please respond to the list by 27 February 2019, 17.00 UTC (preferably earlier). Kind regards, Bart

1 0

FW: Call for Volunteers: the ccNSO seeks 1 mentor and 1 mentee for the ccNSO Community Onboarding Programme (COP)
by Joke Braeken Feb. 20, 2019

Feb. 20, 2019

Dear all, This is a reminder that the ccNSO seeks 1 mentor and 1 mentee for the ccNSO Community Onboarding Programme (COP). If you are interested in joining either as mentor or mentee to the ccNSO COP, kindly review the section “how to join” included below. The application window opens Wednesday, 6 February 2019 (noon UTC). The closing date of this call for volunteers is 20 February 2019, 23:59 UTC. Applications received prior to the opening date or after the closing date will not be considered. Objective of the ccNSO COP The ccNSO COP is designed to improve engagement and retention of new participants within the ccNSO by creating a structured, year-round onboarding process and mentorship structure, tailored by and for the ccNSO. ccNSO COP mentor/mentee: role & term of appointment 1. ccNSO COP mentor A mentor is defined as an experienced member of the community best suited to share knowledge of and experience in the ccNSO environment. The role of the mentor: ● Be available to the mentee through previously agreed upon communication channels, at reasonable time frames throughout the experience (pre-, during and post- an ICANN meeting) ● Guide the mentee through all available resources and share relevant information ● Respond in a timely manner to any queries from the mentee ● Facilitate introductions to Community Members, for instance while attending ICANN meetings ● Provide an update the ccNSO Council and/or Secretariat when requested to do so ● Whenever possible, attend ccNSO-relevant sessions at ICANN meetings. The term of appointment of the ccNSO COP mentor shall be one (1) year. A mentor may be re-appointed for two additional terms (in total 3 terms). 2. ccNSO COP mentee A mentee is defined as a relatively new member of the community who has demonstrated both the potential and desire to actively engage and participate in the work of the ccNSO. The role of the mentee: ● Be available to the mentor through previously agreed upon communication channels, at reasonable time frames throughout the experience (pre-, during and post- an ICANN meeting) ● Read the available ccNSO onboarding materials, and where possible provide suggestions for improvements ● Be a good listener and have an open mind to allow guidance through the ccNSO activities ● Work towards the goal of contributing to the work of the ccNSO ● Provide an update the ccNSO Council and/or Secretariat when requested to do so ● Whenever possible, attend ccNSO-relevant sessions at ICANN meetings. The term of appointment of the ccNSO COP mentee shall be one (1) year. A mentee cannot be re-appointed. Who can join? People associated with a ccTLD manager, whether members or non-members of the ccNSO, may apply for the role of ccNSO COP mentor/mentee. Decisions on whether to award the role of ccNSO COP mentor/mentee shall be based on the merits of each application and the criteria included in the Terms of Reference located here [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_abo…>. The ccNSO COP mentor and mentee will be selected based on how well the application material they submitted meets the following set of criteria: Requirements for mentees: * Able to work and communicate in written and spoken English * Have a basic knowledge of ICANN and specifically the ccNSO * Be a fairly new community member * Show genuine interest to contribute to the work of the ccNSO * Should be employed or have active backing by a ccTLD manager and should demonstrate the support by the ccTLD manager in respect to the required time commitment to participate actively in the ccNSO COP Requirements for mentors: * Able to work and communicate in written and spoken English * Have a good knowledge of ICANN and specifically the ccNSO * Actively contributes to the work of the ccNSO * Be approachable and accessible, with the goal of advancing the onboarding experience of the mentee * Ability and willingness to share best practices and experiences * Should be employed or have active backing by a ccTLD manager and should demonstrate the support by the ccTLD manager in respect to the required time commitment to participate actively in the ccNSO COP How to join and next steps If you are interested in joining either as mentor or mentee to the ccNSO COP, kindly fill out the application form located here (https://www.surveymonkey.com/r/ccNSOCOP [surveymonkey.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.surveymonkey.com_r…>), starting from Wednesday 6 February 2019 (noon UTC). Additional background application materials - such as the active backing by the ccTLD Manager - can be sent via e-mail to joke.braeken(a)icann.org Closing date of this call for volunteers is Wednesday, 20 February 2019, 23:59 UTC. Applications received prior to the opening date or after the closing date will not be considered. Once the application window closed, the ccNSO COP Selection Committee members will evaluate all applications. The outcome of the ccNSO COP Selection Committee deliberations will be published on the ccNSO website, latest by Friday, 15 March 2019. All applicants will receive a personal notification as well. Background and links * About the ccNSO COP The ICANN Community Onboarding Programme results from discussions between the community and the ICANN starting at ICANN49 and concluding at ICANN51. This broader consultation process sought to address volunteer burnout and improve newcomer retention rates. In January 2016, the ICANN COP Pilot was launched to develop an individualized, tailored mentorship process. The programme concluded at the end of ICANN’s FY18. The objective of the ccNSO COP is to continue a COP tailored to the needs and within the limits of the ccNSO environment. * ccNSO funded travel support The ccNSO Travel Support Programme is provided by ICANN to advance the work of the ccNSO as a whole and is therefore aimed at supporting the attendance to ICANN public meetings for community members that are contributing towards its work. ICANN provides support for a limited number of ccNSO slots. Candidates from all regions and sectors, including the ccNSO COP mentor and mentee, may apply for ccNSO travel support. Decisions on whether to award travel support to an application shall be based on the merits of each application and the criteria included in the ccNSO Travel Support Guideline as published on the ccNSO website. Read more here on how to apply for travel funding for ICANN65, Marrakech: https://ccnso.icann.org/en/announcements/announcement-01feb19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> * Links * About the ccNSO COP Selection Committee: https://ccnso.icann.org/en/about/cop-selection [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_abo…> * Terms of Reference ccNSO COP: https://ccnso.icann.org/en/about/ccnso-draft-cop-06dec18-en.pdf [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_abo…> * Announcement call for volunteers: https://ccnso.icann.org/en/announcements/announcement-05feb19-en.htm [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_en_ann…> Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ccNSO&d=Dw…> Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ccnso…> http://ccnso.icann.org [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org&d=DwMGa…>

1 0

Questions to the Board!
by Katrina Sataki Feb. 18, 2019

Feb. 18, 2019

Dear Colleagues, Here is a proposal for the questions to the Board. Today is the deadline... Sorry, for the late email! Please let me know ASAP if you have any corrections/additions! -- 1. ICANN's mission As the Board adopts ICANN's Strategic Plan, Operating Plans and related budgets, what criteria does the Board use to determine whether an activity is within ICANN's mission? With ICANN's funding levelling or on the decline, do you consider all the activities as equally important or do you see some activities as of a higher priority for fulfilling ICANN's mission? 2. Confusing similarity The joint ccNSO -SSAC working party has provided feed-back and input to ICANN Org's proposed guideline to operationalize the amended Fast Track process (inclusion of Risk Mitigation to overcome the only pending case of confusing similarity). In addition and overstepping the original request, the working party suggests that ICANN takes a final decision on the one and only pending case. Once the current pending case under the IDN ccTLD Fast Track Process is resolved, we propose that all processes and procedures relating to the evaluation of confusing similarity be reviewed and evaluated, with a two-fold goal. Firstly, originally (in 2009) the process and procedures for evaluation of strings of the new gTLD round and the overall policy for IDN ccTLDs were supposed to be consistent. However, due to the incremental changes of the ccTLD Fast Track process since 2009, the discrepancy between these processes has increased. Secondly, since the introduction of sting similarity review in 2009, the methods to evaluate string similarity and underlying scientific insights in this area have evolved and, therefore, a review of the original approach is highly desirable. Should we still strive to harmonize string similarity review under the two processes? If so, how could we all ensure this given both are developed under different PDPs? 3. Progress on IFR During our Barcelona meeting we informed you that the ccNSO - despite all the efforts - has not been able to appoint to the IFRT a representative from a ccTLD manager that is not a member of the ccNSO. We suggested to appoint a representative from a ccNSO member ccTLD on an interim basis to ensure that ccTLD community which is one of the direct customer groups of PTI, is represented on the review by 3 members. Since then ICANN Org reached out to all the appointing entities to seek support for this solution. It is our understanding that one of the appointing entities objected, with reference to the Bylaws. As this Review has been launched under auspices of the Board, could you provide an update on the current status? How will it be ensured that 3 members of the ccTLD community are included in the IFRT? Looking to the future, the next IFR shall be convened in five years, measured from the date the previous was convened (September 2018). It is clear that with the growing number of ccNSO members, in five years it will be even more difficult to find a non-member ccTLD representative. To change this, a fundamental Bylaw change is required. What is the process to introduce the change in time for the next IANA Functions review? --- Kind regards, ]{atrina

1 0

online decision: Appointment new member MPC
by Joke Braeken Feb. 18, 2019

Feb. 18, 2019

Dear Councillors, Please find below a draft resolution, presented to you for an online decision. Kindly provide me with your input by the end of Friday, 22 February 2019, 23:59 UTC, in case you do not agree with the proposed resolution. Appointment new member For decision: formal appointment new member ccNSO Meetings Programme Committee. Mustafa Mohamed (.so) has applied for membership of the ccNSO MPC. Draft Resolution The ccNSO Council approves membership of Mustafa Mohamed (.so) to the ccNSO Meetings Programme Committee. The secretariat is requested to inform the Committee chair and take all other necessary steps to include Mustafa as a member of the MPC. Thank you. Best regards. 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

2 1

ccNSO-related session at ICANN64-Kobe and remote participation details
by Kimberly Carlson Feb. 18, 2019

Feb. 18, 2019

Dear all, The ICANN64 | Kobe schedule website is now published: https://64.schedule.icann.org/ Below, please find the ccNSO-related session at ICANN64-Kobe and remote participation details (JST time). All meetings are open to observers, unless otherwise noted. Calendar invites will be sent to the individual working groups/committees. Day 1, Saturday, 9 March * Guidelines Review Committee<https://64.schedule.icann.org/meetings/962145> | 1030-1200 (block 2) | Room 403 (KICC) | https://participate.icann.org/kix64-403/ * Study Group on use of Emoji as SLDs <https://64.schedule.icann.org/meetings/962146> | 1330-1500 (block 3) |Room 403 (KICC) | https://participate.icann.org/kix64-403/ * cc PDP on Retirement<https://64.schedule.icann.org/meetings/962147> | 1515-1830 (blocks 4 & 5) | Room 403 (KICC) | https://participate.icann.org/kix64-403/ Day 2, Sunday, 10 March * ccNSO Council Workshop<https://64.schedule.icann.org/meetings/962064> | 900-1200 (blocks 1 & 2) | Emerald | https://participate.icann.org/kix64-emerald/ * ccNSO Council Preparatory Session<https://64.schedule.icann.org/meetings/962065> | 12:15-13:30 | Emerald | https://participate.icann.org/kix64-emerald/ * Strategic Operational Planning Standing Committee (SOPC)<https://64.schedule.icann.org/meetings/962041> | 1330-1500 (block 3) | Diamond | https://participate.icann.org/kix64-diamond/ * Technical Working Group<https://64.schedule.icann.org/meetings/962066> | 1330-1500 (block 3) | Emerald | https://participate.icann.org/kix64-emerald/ * TLD Ops Standing Committee<https://64.schedule.icann.org/meetings/962067> | 1515-1645 (block 4) | Emerald | https://participate.icann.org/kix64-emerald/ * TLD Ops Document Drafting<https://64.schedule.icann.org/meetings/962068> | 1700-1830 (block 5) | Emerald | https://participate.icann.org/kix64-emerald/ * Joint session: ALAC and ccNSO<https://64.schedule.icann.org/meetings/961993> | 1700-1830 (block 5) | Topaz | https://participate.icann.org/kix64-topaz/ Day 3, Monday, 11 March * TechDay | 1030-1645 (block 2<https://64.schedule.icann.org/meetings/962022>, block 3<https://64.schedule.icann.org/meetings/962023> & block 4<https://64.schedule.icann.org/meetings/962024>) | Ohwada A | https://participate.icann.org/kix64-ohwadaa/ * Customer Standing Committee public meeting<https://64.schedule.icann.org/meetings/962165> (block 2) | Lilac | * Joint session: ccNSO and GNSO<https://64.schedule.icann.org/meetings/961973> | 12:00-13:00 | Ohwada C | https://participate.icann.org/kix64-ohwadac/ Day 4, Tuesday, 12 March * Members meeting day 1<https://64.schedule.icann.org/meetings/962025> | 900-1645 | Ohwada A | https://participate.icann.org/kix64-ohwadaa/ * Joint Session: Board and ccNSO<https://64.schedule.icann.org/meetings/962029> | 1100-1200 | Ohwada A | https://participate.icann.org/kix64-ohwadaa/ * Meeting with ccNSO Review Independent Examiner<https://64.schedule.icann.org/meetings/962030> - Meridian | 1700-1800 | Ohwada A | https://participate.icann.org/kix64-ohwadaa/ Day 5, Wednesday, 13 March * Members meeting day 2<https://64.schedule.icann.org/meetings/962031> | 900-1645 | Ohwada A | https://participate.icann.org/kix64-ohwadaa/ * Joint Session: ccNSO and GAC<https://64.schedule.icann.org/meetings/961963> | 1030-1115 | Ohwada B | https://participate.icann.org/kix64-ohwadab * ccNSO Council Meeting<https://64.schedule.icann.org/meetings/961963> | 1700-1830 (block 5) (***Session will NOT be in the ccNSO room***) | Emerald | https://participate.icann.org/kix64-emerald/ Day 6, Thursday, 14 March * Meetings programme committee<https://64.schedule.icann.org/meetings/962120> | 1030-1200 (block 2) | Ruby | https://participate.icann.org/kix64-ruby Two-way audio requests must be made in advance. Email me with those requests. Schedule is subject to change, so please continue to check the full ICANN schedule: https://64.schedule.icann.org/ And the wiki: https://participate.icann.org/p3yhxmdzn8o/ Additional calendar invites will be sent to those who requests one. Other helpful links: Hotel & Travel<https://64.schedule.icann.org/pages/3290> Venue Map<https://64.schedule.icann.org/floor_maps/3664?per_page=30&with%5bfloor_map_…> Location Information<https://64.schedule.icann.org/pages/3291> _______________________________________________________________________________________________ Kimberly Carlson ccNSO Support Lead Administrator Internet Corporation for Assigned Names and Numbers Skype kimberly.carlson.icann www.icann.org Top of Form Bottom of Form

1 0