January 2017 - Ccnso-council

Council Minutes and Decisions
by Kimberly Carlson March 9, 2017

March 9, 2017

Dear all, The minutes from the 12 January Council meeting has been posted here: (https://ccnso.icann.org/about/council/minutes.htm) Intermeeting decisions and resolutions are posted here: https://ccnso.icann.org/about/council/decisions-resolutions/2017 For additional information, please visit the ccNSO Council Wiki space at: https://community.icann.org/x/BiyAAw Thank you and kind regards, Kim Carlson _______________________________________________________________________________________________ Kimberly Carlson SO/AC Support Coordinator Internet Corporation for Assigned Names and Numbers Email Kimberly.Carlson(a)icann.org Skype kimberly.carlson.icann [cid:image001.png@01D243BB.E5949130]

1 1

ccNSO report on EPSRP
by Katrina Sataki Feb. 7, 2017

Feb. 7, 2017

Dear Steve, In response to the June 2015 Board resolution, I am pleased to provide the Board the requested further guidance on and refinement of the methodology of second string similarity review process. For the Board’s convenience I have included the ccNSO Council’s resolution (Annex A) and an overview of the development of the requested guidance, including the interaction between the ccNSO Working Group, SSAC and the ccNSO Council (Annex B). In addition, I request the ICANN Board of Directors to discuss and adopt the ccNSO IDN ccTLD Policy Development Process (PDP). The proposed policy was submitted to the ICANN Board in September 2013. In parallel with this submission, the ccNSO requested the Board to introduce it first as part of the Fast Track Process to experiment with the methodology and two-panel mechanism. The Extended Process Similarity Review Panel was introduced in December 2013 and now, with conclusion of the 3rd review of the Fast Track process (March 2015) and the related proposed guidance on and refinement of the methodology, the ccNSO Council is of the view that the experimental Fast Track should be replaced by the overall policy. On behalf of the ccNSO Katrina Sataki, Chair

2 1

FW: CCWG-Accountability WG proposal for a Limited Scope of the ATRT3 Review - reminder
by Katrina Sataki Feb. 3, 2017

Feb. 3, 2017

Dear Colleagues, Sorry I did not send this to you earlier – hoped to have some more clarity around Operating Standard but apparently we won’t have the document in place any time soon which means that with ATRT3 we’ll need to use the same method as with SSR2 and RDS (e.g., decide what to do on the go) . Suggest we support CCWG-Accountability’s proposal to limit the scope of the ATRT3 review. Any objections? Thank you! Kind regards, ]{atrina From: Bernard Turcotte [mailto:turcotte.bernard@gmail.com] Sent: Wednesday, January 25, 2017 10:41 PM To: Katrina Sataki <katrina(a)nic.lv>; thomas.schneider(a)bakom.admin.ch; James Bladel <jbladel(a)godaddy.com>; ASO-chairs(a)aso.icann.org Cc: Louie Lee <louie(a)louie.net>; Patrik Fältström <patrik(a)frobbit.se>; tsinha(a)umd.edu; bverd(a)verisign.com; Alan Greenberg <alan.greenberg(a)mcgill.ca>; Olof Nordling <Olof.nordling(a)icann.org>; Thomas Rickert <thomas(a)rickert.net>; Heidi Ullrich <Heidi.ullrich(a)icann.org>; ACCT-Staff (acct-staff(a)icann.org) <Acct-staff(a)icann.org>; aso(a)icann.org; Bart Boswinkel <Bart.boswinkel(a)icann.org>; León Felipe Sánchez Ambía <leonfelipe(a)sanchez.mx>; David Olive <David.olive(a)icann.org>; Marika Konings <Marika.konings(a)icann.org>; Carlos Reyes <Carlos.reyes(a)icann.org>; Steve.sheng(a)icann.org; Mathieu Weill <mathieu.weill(a)afnic.fr>; Larisa B. Gurnick <larisa.gurnick(a)icann.org>; Steve Crocker <steve.crocker(a)board.icann.org> 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-2016 letter <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

4 4

Call for Volunteers: ccNSO appointed Liaison to the GNSO
by Joke Braeken Feb. 2, 2017

Feb. 2, 2017

Dear All, Per ccNSO council decision<https://ccnso.icann.org/about/council/decisions-resolutions/2017> (Resolution 125-02), the ccNSO launches a call for volunteers to fill the vacancy of ccNSO appointed Liaison to the GNSO. Candidates are asked to submit their applications to the ccNSO Secretariat (ccnsosecretariat(a)icann.org)<mailto:ccnsosecretariat@icann.org)> or joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> by 7 February 2017, 23:59 UTC. Read the announcement here: https://ccnso.icann.org/announcements/announcement-24jan17-en.htm Background Patrick Myles stepped down as ccNSO Liaison to the GNSO. In order to help ensure that the ccNSO can liaise effectively with the GNSO, the ccNSO is looking for a member of the ccTLD community to be appointed as GNSO liaison. The roles and responsibilities of the ccNSO Liaison to the GNSO are: * 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. How to Apply? Interested individuals are invited to provide the following: * A resume, curriculum vitae, or biography * A letter of motivation detailing your interest in serving as ccNSO Liaison to the GNSO and what you will bring to this position. * Letter from your employer supporting you with respect to the required time commitments, confirming that you will attend GNSO meetings regularly and inform the ccNSO Council and broader ccTLD community. * If not directly related to a ccTLD Manager, demonstrate active backing by a ccTLD manager * Statement of interest that identifies potential conflict of interest in your service as Liaison Please email your application to the ccNSO secretariat (ccnsosecretariat(a)icann.org)<mailto:ccnsosecretariat@icann.org)> or joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> by 7 February 2017, 23:59 UTC. 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 1

reminder - Call for Volunteers: ccNSO appointed Liaison to the GNSO
by Joke Braeken Jan. 30, 2017

Jan. 30, 2017

Dear All, This e-mail serves as a reminder: the ccNSO launched a call for volunteers to fill the vacancy of ccNSO appointed Liaison to the GNSO. Candidates are asked to submit their applications to the ccNSO Secretariat (ccnsosecretariat(a)icann.org)<mailto:ccnsosecretariat@icann.org)> or joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> by 7 February 2017, 23:59 UTC. Please find further details in the email below. 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 From: Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 24 January 2017 at 21:51 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, "ccnso-council(a)icann.org" <ccnso-council(a)icann.org> Subject: Call for Volunteers: ccNSO appointed Liaison to the GNSO Dear All, Per ccNSO council decision<https://ccnso.icann.org/about/council/decisions-resolutions/2017> (Resolution 125-02), the ccNSO launches a call for volunteers to fill the vacancy of ccNSO appointed Liaison to the GNSO. Candidates are asked to submit their applications to the ccNSO Secretariat (ccnsosecretariat(a)icann.org)<mailto:ccnsosecretariat@icann.org)> or joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> by 7 February 2017, 23:59 UTC. Read the announcement here: https://ccnso.icann.org/announcements/announcement-24jan17-en.htm Background Patrick Myles stepped down as ccNSO Liaison to the GNSO. In order to help ensure that the ccNSO can liaise effectively with the GNSO, the ccNSO is looking for a member of the ccTLD community to be appointed as GNSO liaison. The roles and responsibilities of the ccNSO Liaison to the GNSO are: * 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. How to Apply? Interested individuals are invited to provide the following: * A resume, curriculum vitae, or biography * A letter of motivation detailing your interest in serving as ccNSO Liaison to the GNSO and what you will bring to this position. * Letter from your employer supporting you with respect to the required time commitments, confirming that you will attend GNSO meetings regularly and inform the ccNSO Council and broader ccTLD community. * If not directly related to a ccTLD Manager, demonstrate active backing by a ccTLD manager * Statement of interest that identifies potential conflict of interest in your service as Liaison Please email your application to the ccNSO secretariat (ccnsosecretariat(a)icann.org)<mailto:ccnsosecretariat@icann.org)> or joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> by 7 February 2017, 23:59 UTC. 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

Selection ccNSO appointed liaison to ALAC
by Bart Boswinkel Jan. 23, 2017

Jan. 23, 2017

Dear all, Last week the selection process for the ccNSO appointed liaison to ALAC closed. The secretariat received 14 votes. Based on the votes 10 Councilor preferred Wafa and 4 Ben. Included is the overview. Kind regards, Bart

1 0

RE: [ccnso-council] Item for AOB - running out of time
by ceo Jan. 21, 2017

Jan. 21, 2017

Dear Katrina, I think its in order for us to ask for more funding. This will enable more members to attend meetings Regards, Abdalla On Jan 13, 2017 4:52 PM, Katrina Sataki <katrina(a)nic.lv> wrote: > > > Nigel, > > Thank you very much for pushing this forward. > > My undersanding is: > 1) ccNSO has never asked for increase in travel funding since 2008 when the concept was first introduced. > 2) if we decide to ask for an increase we must do it NOW as FY 2018 is in the phase of active preparation and is due to public comments already in March (correct me if I'm wrong). It means that it might be too late to raise the issue in Copenhagen because then we can aim only for FY 2019. > > Therefore if the Council decides that we should ask for more funded seats (any proposals?) then we should send a request ASAP. Please express your support or objections by 20 January. > > Kind regards, > > ]{atrina > > > > -----Original Message----- > From: owner-ccnso-council(a)icann.org [mailto:owner-ccnso-council@icann.org] On Behalf Of Nigel Roberts > Sent: Thursday, January 12, 2017 10:09 PM > To: ccnso-council(a)icann.org > Subject: [ccnso-council] Item for AOB - running out of time > > > About a year ago, we had some informal discussions with Xavier that was aimed at understanding the requirements on the Council for the allocation of resources for funding Council members and others to ICANN meetings. > > Strangely (to me) this turned out to not be predicated on on a budget, but on 'per seat' basis. Two questions arise from this answer :- > > - what requirement (e.g. from Finance or ICANN Board) is there on the ccNSO to allocate funds differentially between different classes of members > > - where does the differential between ccNSO number of seats and (e.g.) ALAC and GAC come from? > > This inquiry fell by the wayside. > > > I wish to suggest a small informal meeting in CPH including Chair or one of the Vice-Chairs, and myself (since I've been doing the research) and one other Council Member (perhaps from LAC or Africa?). > > Situation has worked, by-and-large, this last few years, largely becuase of the support given from large registries who do not need travel support for their elected Councillors. > > But I can see it could inhibit good candidates from developing regions and also small registries in other regions. > > On the assumption Council continues to approve of this line of inquiry, I shall see if I can arrange something. > > Council is asked if it objects to this further inquiry > >

1 0

Council minutes - 12 January
by Kimberly Carlson Jan. 20, 2017

Jan. 20, 2017

Dear Councilors, Please find, attached, the 12 January 2017 minutes for your review. Kind regards, Kim Carlson _______________________________________________________________________________________________ Kimberly Carlson SO/AC Support Coordinator Internet Corporation for Assigned Names and Numbers Email Kimberly.Carlson(a)icann.org<mailto:Kimberly.Carlson@icann.org> Skype kimberly.carlson.icann [cid:image001.png@01D243BB.E5949130]

1 0

e-mail addresses subscribed to the mailing list ccnso-members@icann.org?
by Joke Braeken Jan. 20, 2017

Jan. 20, 2017

Hi Derek, Would it be possible to send me a recent list of all e-mail addresses subscribed to the mailing list ccnso-members(a)icann.org? I am not sure why, but the WHO-command works for instance for the ccnso-council mailing list, but not for the ccnso-members mailing list … The password I am using is correct: subscriptions to that list work just fine. 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 1

Reminder: Selection ALAC liaison
by Bart Boswinkel Jan. 20, 2017

Jan. 20, 2017

Dear all, This is a kind reminder. To date I have recveived an email with preferred candidate from 5 of you!! Kind regards, Bart From: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Friday 13 January 2017 at 12:04 To: "ccnso-council(a)icann.org" <ccnso-council(a)icann.org> Subject: Selection ALAC liaison Dear all, Per Council decision, the secretariat is initiating the selection process for the position ccNSO Liaison to ALAC. Please find included: · Description of the nomination procedure (see below) · Information regarding the two candidates (was already included in material for the 12 January Council meeting) You are requested to submit the name of your preferred candidate either to the ccNSO secretariat (ccNSOsecretariat(a)icann.org)<mailto:ccNSOsecretariat@icann.org)> or to me directly ( bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org> ), with subject line: Selection ALAC liaison. PLEASE SEND YOUR EMAIL BY THURSDAY 19 JANUARY 23.59 UTC Thank you and kind regards, Bart Selection Process Introduction As decided on the most recent Council meeting (12 January) you are requested, to select the ccNSO appointed liaison to ALAC. As agreed the selection will be done using the standard selection process. The applicants The list of applicant and their application letters etc. are included again. As none of the applicants is a member of Council, all Councillors are eligible to participate in the nomination process, you are all requested to send the name of your preferred candidate. Selection and procedure Based on the material provided, you are requested to assess which candidate you find most suited as liaison to ALAC. To assist you in your assessment the description of liaisons role as included in the call for volunteers is included (see below. Once you completed your assessment you are requested to mail your preference to Bart (bart.boswinkel(a)icann.org<mailto:bart.boswinkel@icann.org> , or the ccNSO secretariat (ccNSOsecretariat(a)icann.org)<mailto:ccNSOsecretariat@icann.org)> with subject line: Selection ALAC liaison PLEASE SEND YOUR EMAIL BY THURSDAY 19 JANUARY 2017 23.59 UTC Administrative Procedure After we received your email, we will acknowledge receipt and include a ballot number and date of receipt. On 20 JANUARY 2017 we 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. As agreed by Council resolution and in accordance with the relevant ccNSO Guideline the candidate receiving most supportive votes, is selected. In the event the two candidates are equally preferred run-off selection will be needed. Roles and responsibilities of the ccNSO Liaison to the ALAC * To participate diligently and actively in the meetings and activities of the ALAC on an ongoing and longterm basis * To communicate and advocate the positions of the ccNSO to the ALAC; * To report to the ccNSO on current and upcoming activities of the ALAC 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 ALAC. * Participate in ALAC-ccNSO Council meetings agenda committee to prepare the f-2-f meetings, if any.

2 2