February 2017 - Ccnso-council

Follow-up to my remarks in Thursday's meeting
by Stephen Deerhake Feb. 10, 2017

Feb. 10, 2017

Greetings, As I noted in my remarks during Thursday's call, the ICANN Board has passed a resolution in which it accepted the recommendation of its Board Governance Committee (BGC) that a new Board Accountability Mechanisms Committee be established to manage oversight of ICANN's accountability mechanisms. The establishment of this new Board Accountability Mechanisms Committee will require a change in a Fundamental Bylaw, which will trigger an "Approval Action Board Notice" and subsequent review (and approval?) by the Empowered Community of the proposed Bylaw change. The Board resolution is available here: https://www.icann.org/resources/board-material/resolutions-2017-02-03-en#2.a . Chris Disspain (Chair of the BGC) has written a blog post regarding the proposal, which can be found at https://www.icann.org/news/blog/chairman-s-blog-en. I confess that I never thought the first exercise of Community Oversight under the new Bylaws would involve an approval action over a Bylaws change, as it never occurred to me that the Board would start meddling with the Bylaws just over three months after their adoption. Having said that, I do not see anything nefarious in what the BGC has proposed, and what the Board has decided via their resolution to implement. Also, it appears that there is going to be a coordinated effort on the part of the Board and ICANN Staff to orchestrate the adoption of the revised Bylaw so as optimize the timing of the initiation of the "Approval Action Community Forum Period." My guess (and this is only a guess) is that this will coordinated so that the required Approval Action Community Forum can be scheduled for ICANN 59 in Johannesburg. FYI, there will be an organisational meeting of the Empowered Community Administration at ICANN 58 in Copenhagen. Lastly, I fully expect that the Guidelines Review Committee will have the necessary Guidelines for handling the Approval Action Process before the Council for adoption prior to the triggering by the ICANN Board of the Approval Action Board Notice, so we should be in good shape from a procedural standpoint. Please do not hesitate to contact me with any questions you might have about the Approval Action process, the Guidelines under development to handle the Approval Process, or the ECA in general. Best Regards, /Stephen

1 0

ccNSO Council adopted guideline
by Kimberly Carlson Feb. 9, 2017

Feb. 9, 2017

Dear all, On the 9 February call, the ccNSO Council adopted the following guideline: * Guideline: ccNSO Council practices: https://ccnso.icann.org/about/guidelines-council-practices-09feb17-en.pdf As a reminder, guidelines are posted here<https://ccnso.icann.org/about/guidelines.htm> and council decision/resolutions here<https://ccnso.icann.org/about/council/decisions-resolutions/2016>. For more information on the ccNSO Council, please visit their Wiki page at: https://community.icann.org/x/BiyAAw As always, if you have any questions, comments or concerns, please do not hesitate to contact me. 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 0

notes from the 9 February Council call
by Joke Braeken Feb. 9, 2017

Feb. 9, 2017

Dear All, Please find below the notes from the 9 February Council call. Best regards, Joke Braeken Apologies: Nigel Roberts NOTES 1. Welcome and Apologies ADMINISTRATIVE TOPICS 2. Minutes and Actions 1 still ongoing. 3. Overview inter-meeting Council decisions 3 decisions: - ccNSO Liaison to ALAC - limit scope ATRT3 - travel funding. (agenda item 8) 4. Appointment volunteers 4.1. ccNSO Liaison to GNSO several reminders sent out by the secretariat. Proposal to not only track attendance, but also voting behaviour. (response received or not). 2 applications received. Ben Fuller (.na) and Biyi Oladipo (.ng). Preferred candidate needs to be selected. Selection process to be started by secretariat tomorrow, and will be closed by the end of next week. Voting to be tracked (response received or not. no further details) SUBSTANTIVE TOPICS 5. Specific reviews 5.1. Update on current state of play specific reviews - SSR2 - Directory Services (DRS) waiting for the guidelines to be adopted. Perhaps another call for volunteers needed. We will approach those that sought support from the ccNSO. still waiting for the Operating Standards. A webinar will be held soon. Updates to follow in Copenhagen. SSR2: very few candidates (6) from the LAC-region, none selected to SSR2. RDS: only 1 applicant from LAC-region. next steps for SSR2? Expect team to meet in Copenhagen. Proceed with 15 members. Additional members to be added later potentially. Copenhagen is what they are aiming at for the first meeting. - ATRT3 5.2. Directory Services and ATRT 3 Selection Process 6. Organisation review ccNSO and its timeline Webinars that were planned could not happen so far. Briefing during ccNSO meeting days in CPH. Working Party members have been selected. 7. Update Guidelines 7.1. Date council elections GRC currently working on this. For discussion: council election in autumn. New council members always take their seat in March. But this is conflict with the ICANN bylaws, that say they need to take their seats at the last meeting of the year. NomCom follows the timeline as described in the bylaws. They take a seat at the last meeting of the year. What would be your preference? Shall we continue as we currently do? this will allow us to ask questions to those that accepted their nomination at the last meeting of the year. Or shall we shift the timeline, and have the Q&A during the policy meeting (2nd meeting of the year?). Then the elections would need to happen during the summer (northern hemisphere). Debbie: what will happen to policy team meeting B? Will enough people show up, and be able to ask questions to those that accepted their nominations? What if ccNSO members start opting out of that meeting? Katrina: still unclear how this Meeting B will evolve. Byron: Symbolic opportunity to stress the relative independence of the ccNSO. Might be a relatively minor issue. Is it worthwhile to change? We are independent of ICANN, and could make a symbolic statement. Katrina: will we run into trouble with the legal department? We are talking about the bylaws here. But I also agree with Byron Summary: message to be passed on to GRC. We will leave it as it currently is. 7.2. Adoption Council Practices Guideline mover? Byron Seconder? Stephen were sent out for review. no comments received. Against? none Abstentions? none This document has been approved. Will be posted on ccNSO website (with date of adoption, without "draft" in the footer) 8. ccNSO Travel Funding to date 12 slots. GRC is currently working on the guideline. Number of slots is smallest of all SO/ACs. Shows independence from ICANN, but makes participation by smaller ccTLDs more problematic. If we want to increase the number of slots, we should ask for this during the OPS plan and budget public comment period. (start of March) SOP WG working on document with financial contributions by ccTLDs to ICANN. This took into account only 12 slots. because of the link with the expected ccTLD finacial contribution ccNSO has been very reluctant to ask for increase Do we seek for an increase? If yes, how many? Peter Vergote: are the 12 slots on an annual basis, or per meeting? Katrina: per meeting. Debbie: more flexibility around those 12 slots perhaps. Debbie is funded by her employer. It would be great to manage a pool. to have a way that when a council member chooses not to take the funding, it goes to a community member. Katrina: 3 NomCom council members to be funded. 1 slot per region for the council members. Remaining slots go to the broader ccTLD community. If the council member does not use its slot, it will go indeed to the community. in principle 4 slots for non council members. We do not have the opportunity to fund liaisions for instance. Peter (CENTR): I missed the discussions that Nigel was contributing to. Are we missing out on strong contributors because of lack of travel sponsorship? What problem are we trying to solve? Katrina: indeed challenge for smaller registries to participate in person. Maureen: ALAC has 27 slots specifically for ALAC members and regional leaders. GNSO have over 40 travel slots. Ching: or nomcom councillors -- would it be possible to free these spots from the ccNSO so that it's directly sponsored via the ICANN general pool ? Bart: originally all SO/ACs received 12 slots. Others increased their numbers throughout the years 9. Updates CSC, RZERC, EC/AC Byron: regular CSC meeting next week. No update on January report yet. Each of the meetings goes smoother than previous one. Metrics they are monitoring are satisfactory. SLAs have been met. Minor comments, outside regular framework. No cause for concern on regular metrics. Survey on quality and performance of IANA in terms of satisfaction. Stephen: 1. EC is getting itself organised with help from ICANN staff. a mailing list is in place. 2. guideline for handling matters EC. Annex D section 2 has been the focus so far. Rejection. Outline reviewed by Jordan Carter and Ben Fuller. will be presented to GRC shortly. Hopefully ready to be voted on in CPH. 3. Recent Board meeting. Request by Board Governance Committee to form a new Board committee, to handle accountability mechanisms. Change to fundamental bylaw. Will trigger approval action request to the community. This will require at least 3 SO's to approve. 10. WG Updates 10.1. Update CCWGs - CCWG Auction Proceeds. Second meeting in a few hours time. More formal update to follow regarding the work to day. Breaking news: the GNSO appointed Co-chair Jonathan Robinson mentioned his intention of stepping down. Afilias (.web new gTLD application): could be a conflict of interest. He will transit this role until the GNSO appoints a new co-chair. 10.2. Update WG - GRC: council election guideline, travel funding guideline. and others linked to new bylaws - Programme WG. Draft agenda sent by email as well. confirmation when we will meet with the ICANN Board and the GAC. Cross-community topic supported by GNSO and ccNSO on Thursday morning. - drafting team discussed 2 draft charters. Topics have been identified after a 2nd reading. 2 charters hopefully to be completed in 2 weeks time. to be included in issue report, which will be shared prior to the CPH meeting. 11. Council Updates none 12. Liaison Updates updates provided in written. Welcome to Wafa. 13. Next meetings Copenhagen SUN: - prep meeting (lunch - noon) Discussion roles and responsibilities of the councillors 1st meeting of the year, chair and vice chairs to be elected, and standing committees. Annual work plan to be discussed. - ALAC ccNSO meeting. at 17pm. agenda to be organised very shortly. MON: - meeting with GNSO council. lunch. agenda to be defined TUE: - board- ccNSO meeting. their questions have not been presented yet. will most likely ask about the implementation and EC related mechanisms. Suggestions for topics to be discussed is welcome. EPSRP. we could ask for comments - ccNSO-GAC meeting. Chris and Mike keep reminding us that people who would like to take their seat on the ICANN Board, should learn well in advance. Briefing in CPH. Webinars to be organised as well. WED: council meeting at 5 pm. Elect chairs and vice-chairs. Peter (CENTR) - Liaison for the GNSO: Patrick was unsure in the beginning on the expectations. Need for briefing. - Latest financial contributions to ICANN by ccTLDs: where to find them? Bart: by CPH there will be a more updated version. 2012 until at least 2015 to be included on the financial contributions page on the ccNSO website. Leonid: mind high exchange deals commission fees in Copenhagen- 13% on cash exchange and 45 Danish crowns min (some USD 7-8) on cash withdrawals from ATM ( in addition to your bank's regular commission fees) 14. Work Plan included in prep materials. 15. AOB 16. Closure Thank you. 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

draff agenda for Copenhagen
by Alejandra Reynoso Feb. 9, 2017

Feb. 9, 2017

Dear All Please find attached the latest draft agenda. Still subject to change, but hopefully not by much ;) Best regards, Alejandra *Registro de Dominios .gt* -- Universidad del Valle de Guatemala. 18 Ave. 11-95. Z. 15. V.H. III. Edificio *J*. Oficina *204*. *Tels:* *+502.23688564* y *+502.23688565* * <http://www.gt/> ** <https://www.facebook.com/DominiosGT> <https://twitter.com/DominiosGT> ** <https://plus.google.com/u/0/107159401057178225886/posts> <http://www.linkedin.com/company/registro-de-dominios-gt>*

1 0

Webinar on 21 February: Operating Standards for ICANN Reviews. Recent Developments and Next Steps
by Joke Braeken Feb. 9, 2017

Feb. 9, 2017

Dear All, On Tuesday 21 February at 15:00 UTC [local times[timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.timeanddate.com_wo…>] and 23:00 UTC [local times[timeanddate.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.timeanddate.com_wo…>], ICANN’s department of Multistakeholder Strategy and Strategic Initiatives (MSSI) will host community-wide webinars on the Review Operating Standards, which, once in place, centralize operational best practices and processes regarding Organizational and Specific Reviews. How to join? Please email: mssi-secretariat(a)icann.org<mailto:mssi-secretariat@icann.org> to obtain a calendar invite with an agenda, Adobe Connect links, and dial-in details. Please note, the webinars accommodate different time zones, the content presented during both session will be identical, and both sessions will be recorded. Background During the webinar, a draft version of the Operating Standards that addresses those issues that comprise existing processes and best practices will be provided. The ICANN Bylaws[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> call for the drafting of review Operating Standards that "shall be developed through community consultation" (see Section 4.6). Operating Standards provide a system to conduct Specific and Organizational Reviews and tools to assist with the Review process. Specific Reviews (CCT Review, SSR Review, ATRT Review, and RDS/WHOIS Review) and Organizational Reviews (GNSO Review, At-Large Review, etc.) are mandated by the new Bylaws. These Reviews are very important to assess ICANN's performance with regard to its commitments. Review Operating Standards provide tools to bring consistent rules, clarity and transparency to the various Review processes. This webinar is just one step in the process of drafting and eventually approving ICANN Review Operating Standards through community consultation. There will be a public session in Copenhagen and a full public comment period once, through community consultation, a complete version of the Operation Standards has been drafted. For more information, background, and next steps, please also see the recent announcement on ICANN.org[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_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 Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

[06-2017] - Apply Now for Public Technical Identifiers (PTI) Director Positions: Deadline Is 21 March 2017
by Joke Braeken Feb. 9, 2017

Feb. 9, 2017

Dear Councillors, Please find below the proposed Triage recommendation 06-2017. Kindly provide me with your input by the end of 13 February 2017, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you. Topic: 06-2017 - Apply Now for Public Technical Identifiers (PTI) Director Positions: Deadline Is 21 March 2017 Originator: ICANN Nominating Committee (NomCom) Summary of request: The ICANN Nominating Committee (NomCom) invites interested individuals to submit applications and/or recommend candidates for key positions on PTI's Board of Directors. The NomCom is inviting applications and recommendations for two members of the PTI Board of Directors The two persons selected by the NomCom will serve alongside three PTI Board members selected by ICANN. Selections will be announced in August or September 2017. Successful candidates will assume their positions after ICANN's Annual General Meeting, to be held from 28 October to 3 November 2017. https://www.icann.org/news/announcement-3-2017-02-07-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Date received: 8 February 2017 Last day for Comments/input/response, if any: 21 March 2017, 23:59 Universal Coordinated Time (UTC). Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>; ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media accounts. Expertise needed, if any: NomCom selectees are expected to be knowledgeable about the environment in which ICANN and PTI operate and the technical functions for which ICANN and PTI are responsible. For information on additional qualifications, skills and time commitments for these positions, visit the NomCom webpage[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_nomcom20…>. Date of submission to Triage Committee: 8 February 2017 Recommendation received by Triage Committee: 9 February 2017 Date of submission to Council: 9 February 2017 Deadline Council decision: Monday 13 February 2017, 23:59 UTC Impact on ccNSO/ccTLDs: middle 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

draft agenda and resolution and additional material
by Bart Boswinkel Feb. 8, 2017

Feb. 8, 2017

Dear all, Please find included the draft agenda and resolutions (very limited number) Also included: · Applications GNSO liaison (Application 1 and Application 2) · Work plan Also included the ALAC update The year has begun busily with ALAC members participating in the new Auction Proceeds WG as well as the 12 ICANN Evolution subgroups (the CCWG Accountability workstream2); and preparing FY18 Budget Requests and also for the election of the At-Large Board member to replace Rinalia. On top of a controversial At-Large Review, its basically been business as usual, although we didn't develop any policy statements this month. Kind regards, Bart

1 0

REMINDER: Next ccNSO Council call - 9 Feb. @11:00 UTC
by Kimberly Carlson Feb. 8, 2017

Feb. 8, 2017

Dear all, As a friendly reminder, the next Council call will be Thursday, 9 February at 11:00 UTC. Please find the dial in details below: Dial in numbers: http://www.adigo.com/icann/ Conference ID: 5258 Adobe Room: https://participate.icann.org/ccnsocouncil/ Two-way audio will be available through the Adobe Room. Please let me know if you require a dial out. If you are unable to attend, please let Bart and I know as soon as possible. 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 0

ICANN Releases Identifier Systems SSR Activities Report
by Joke Braeken Feb. 8, 2017

Feb. 8, 2017

Dear All, As part of its continuing commitment to transparency and accountability, ICANN's Identifier Systems Security, Stability and Resiliency (OCTO SSR) department published its activities report for calendar year 2016. You can find the 2016 report here[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…>[PDF, 261 KB]. This reports describe the activities that are performed to maintain the security, stability, and resiliency of the Internet's global identifier systems. These activities include collaboration with, global security and operations groups and public safety communities where ICANN staff serves in several roles. Depending on the engagement or request, OCTO SSR staff: * offers security or DNS subject matter expertise; * facilitates cooperative action among ICANN and other communities to maintain Identifier System Security, Stability, and Resiliency; * conducts research; * engages with public and private sector actors in capability building related to Identifier Systems SSR; * supports the daily efforts of security or operations communities to mitigate the misuse or harmful use of the Identifier Systems (in particular, DNS or domain name registration services). The 2016 activities reports highlights collaboration and stakeholder activities from July 1 through December 31, 2016. The report summarizes activities performed as part of the identifier system SSR threat awareness and preparedness remit and provide progress reports on analytics or productivity improvement projects as well. A complementary report is published as well, OCTO SSR Training Metrics: Investigating Identifier Systems Abuse or Misuse. You can find this report here[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 545 KB]. For more information about IS-SSR click https://www.icann.org/resources/pages/is-ssr-2014-11-24-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. 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

triage recommendations [ 02 -2017 ], [ 03 -2017 ], [ 04 -2017 ] and [ 05 -2017 ].
by Joke Braeken Feb. 8, 2017

Feb. 8, 2017

Dear Councillors, Please find below details of triage recommendations [ 02 -2017 ], [ 03 -2017 ], [ 04 -2017 ] and [ 05 -2017 ]. Kindly provide me with your input by the end of 10 February 2017, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you. ||||||||||||||||||||||||||||||| Topic: [02-2017] - Webinar On the GNSO’s Policy Development Process On Curative Rights Protection Mechanisms for International Governmental and Non-Governmental Organizations Originator: GNSO Summary of request: Invitation to an interactive webinar on 7 February 2017 at 14:00 UTC, to discuss the preliminary recommendations just published for public comment by the Working Group for the GNSO Policy Development Process on access by International Governmental Organizations’ (IGO) and International Non-Governmental Organizations’ (INGO) access to domain name dispute resolution processes. The public comment period for the Working Group’s Initial Report (https://gnso.icann.org/en/issues/igo-ingo-crp-access-initial-19jan17-en.pdf…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issu…> closes on 1 March 2017. During this webinar, attendees will have the opportunity to ask questions following a brief presentation of the Working Group’s preliminary recommendations by the Working Group co-chairs. Attendees will learn about the Working Group’s initial proposals for: Whether to modify the Uniform Domain Name Dispute Resolution Policy (UDRP) or the Uniform Rapid Suspension (URS) process to address the specific needs of IGOs and INGOs; How an IGO may demonstrate standing to file a complaint under the UDRP or URS in the absence of trademark rights; A Policy Guidance document to clarify the scope of application of the UDRP and URS to IGOs; and Considerations relating to possible claims of jurisdictional immunity by IGOs in appeals from UDRP and URS determinations. Date received: 30 January 2017 Last day for Comments/input/response, if any: the webinar is scheduled for 7 February 2017, 14 UTC Recommended action, if any: share via twitter (done) Expertise needed, if any: gTLDs, dispute resolution, IGO, NGO Date of submission to Triage Committee: Friday, 03 February 2017 Recommendation received by Triage Committee: 7 February 2017 Date of submission to Council: 8 February 2017 Deadline Council decision: 10 February 2017, 23:59 UTC Impact on ccNSO/ccTLDs: low ||||||||||||||||||||||||||||||| Topic: [03-2017] - Call for volunteers third review ICANN Accountability and Transparency (ATRT3) Originator: ICANN Summary of request: ICANN is seeking volunteers to serve on the third review of ATRT3. Read more about the context & chronology, the scope of the AT-review. compensation, responsibilities, skills and expertise, desired attributes, methodology, budget and support and additional materials on https://www.icann.org/news/announcement-2017-01-31-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> and https://community.icann.org/display/atrt/Applications+Received Date received: 2 February 2017 Last day for Comments/input/response, if any: Friday, 21 April 2017, 23:59 UTC Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>; ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media accounts. (Please note: the ATRT3 is an agenda topic for the 9 February ccNSO Council meeting. https://ccnso.icann.org/workinggroups/agenda-draft-council-09feb17-en.pdf[c…<https://urldefense.proofpoint.com/v2/url?u=https-3A__ccnso.icann.org_workin…> ) Expertise needed, if any: reviews, ccNSO Date of submission to Triage Committee: Friday, 03 February 2017 Recommendation received by Triage Committee: 7 February 2017 Date of submission to Council: 8 February 2017 Deadline Council decision: 10 February 2017, 23:59 UTC Impact on ccNSO/ccTLDs: high ||||||||||||||||||||||||||||||| Topic: [04-2017] - At-Large Review, draft report Originator: ICANN, Multistakeholder Strategy and Strategic Initiatives (MSSI) Summary of request: The draft report of the At-Large Review has been published for public comment. Following the closure of this public comment, ITEMS International (ITEMS) - who is the independent examiner conducting the At-Large Review - will update its report based on feedback received and publish its Final Report. https://www.icann.org/news/announcement-2017-02-01-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Date received: 02 February 2017 Last day for Comments/input/response, if any: 24 March 2017 Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>; ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media accounts. Expertise needed, if any: reviews, At-Large, community, structure, functions, adherence to its mission, ICANN bylaws Date of submission to Triage Committee: Friday, 03 February 2017 Recommendation received by Triage Committee: 7 February 2017 Date of submission to Council: 8 February 2017 Deadline Council decision: 10 February 2017, 23:59 UTC Impact on ccNSO/ccTLDs: low ||||||||||||||||||||||||||||||| Topic: [05-2017] - Thick WHOIS Registration Data Directory Services Requirements to Take Effect Originator: ICANN Summary of request: ICANN announced that all ICANN gTLD contracted parties must update their registration data directory services to comply with the Thick Whois Transition Policy for .COM, .NET and .JOBS[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> and Registry Registration Data Directory Services Consistent Labeling and Display Policy[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. The policies require all gTLD registrations to be Thick with a consistent labeling and display of WHOIS output. gTLD registry operators currently providing Thin WHOIS services – .COM, .NET and .JOBS – must submit all new domain name registrations as Thick WHOIS by 1 May 2018. These registries must also migrate all data required for Thick WHOIS services for existing domain names by 1 February 2019. These changes are required by the Thick Whois Transition Policy for .COM, .NET and .JOBS. In addition, registries and registrars are required to implement the data specifications defined in the Registry Registration Data Directory Services Consistent Labeling and Display Policy by 1 August 2017. ICANN has notified contracted parties of their new responsibilities. https://www.icann.org/news/announcement-2-2017-02-01-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Date received: 03 February 2017 Last day for Comments/input/response, if any: none Recommended action, if any: share with ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>; ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>; ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org> and on the ccNSO social media accounts. Expertise needed, if any: WHOIS, gTLDs Date of submission to Triage Committee: Friday, 03 February 2017 Recommendation received by Triage Committee: 7 February 2017 Date of submission to Council: 8 February 2017 Deadline Council decision: 10 February 2017, 23:59 UTC Impact on ccNSO/ccTLDs: low 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

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

ccNSO Council mailing list
by Kimberly Carlson Feb. 7, 2017

Feb. 7, 2017

Dear Councilors, This email is to inform you, as the new ccNSO Council designated liaison to the ALAC, Wafa Dahmani has now been subscribed to the ccNSO Council mailing list. 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 0

final reminder: a ccNSO appointed Liaison to the GNSO sought. Application deadline: tomorrow, 7 February 2017, 23:59 UTC
by Joke Braeken Feb. 6, 2017

Feb. 6, 2017

Dear All, This e-mail serves as a final 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 tomorrow, 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<http://ccnso.icann.org/> From: Joke Braeken <joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>> Date: Tuesday, 24 January 2017 at 21:51 To: "ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>" <ccnso-members(a)icann.org<mailto:ccnso-members@icann.org>>, "ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org>" <ccTLDcommunity(a)cctld-managers.org<mailto:ccTLDcommunity@cctld-managers.org>>, "ccnso-council(a)icann.org<mailto:ccnso-council@icann.org>" <ccnso-council(a)icann.org<mailto:ccnso-council@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<http://ccnso.icann.org/> 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

GNSO activity brief: Jan 2017
by Patrick Myles Feb. 5, 2017

Feb. 5, 2017

Hi Councillors, Attached is the latest activity brief from the GNSO council (also copied below for quick reference) . Their last meeting was 19 January and next one will be 16 Feb 2017. Regards ---- Registration Directory Service (formerly WHOIS) Review Team ICANN is seeking volunteers to serve on the second review of Registration Directory Service (formerly known as the WHOIS Review). The deadline for applications has been extended to 20 January 2017. Thick Whois Implementation The Thick Whois Implementation Review Team (IRT) have written to the GNSO regarding challenges associated with implementation of thick Whois relating to developments in privacy laws. The developments relate to: * New requirements under EU General Data Protection Regulation (into force May 2018). * In the wake of the invalidation of the US-EU Safe Harbor Program and development of the EU-US Privacy Shield, the use of consent to effectuate transfers of personal data has been called into question by regulators in the EU. The IRT believes that these EU-based developments must be taken into account by registries and registrars as they seek to implement consensus policy regarding Thick Whois while remaining compliant with applicable privacy and data protection laws. Letter from the IRT<https://gnso.icann.org/en/drafts/gnso-appointments-procedure-15dec16-en.pdf> Erika Mann and Michele Neylon are to work with staff to develop possible responses to the IRT letter. In the meantime ICANN have announced that all ICANN gTLD contracted parties must update their registration data directory services to comply with the Thick Whois Transition Policy for .COM, .NET and .JOBS. See announcement<https://www.icann.org/news/announcement-2-2017-02-01-en> GNSO Representatives to 2nd Security, Stability & Resiliency Review Team The GNSO Council nominated James Gannon, Denise Michel, Emily Taylor as primary candidates for the SSR2RT Planning for ICANN58 Aiming to ensure overlapping sessions in situations of clashes are kept to a minimum with no overlap of groups. The EU Data Protection session is tentatively scheduled and that the Data Protection Commissioners are seeking endorsement from the GAC and the GNSO Other * GNSO mailing list upgrade - The mailing list software (Majordomo) used for running the GNSO Council mailing list is at the end of its life. ICANN IT, will be migrating the list to a new platform (Mailman) on which all of the GNSO mailing lists will now be hosted. * GNSO to run webinar on Curative Rights Protection Mechanisms for IGO/INGO on 7 February 2017 to outline preliminary recommendations * Latest schedule for ICANN58 meeting sees GNSO/ccNSO meeting on day 3 at 12.15-13.45 Next GNSO Council meeting - 16 February 2017 [cid:image001.png@01D27FAF.9CCF95A0] Patrick Myles Data Analyst CENTR - Belliardstraat 20, 1040 Brussels, Belgium tel +32 2 627 55 50 - mob +61 405 60 67 15 www.centr.org<http://www.centr.org/> - Twitter<https://twitter.com/CENTRnews> - Facebook<https://www.facebook.com/centrnews> - LinkedIn<https://www.linkedin.com/company/centr> - Skype: pat_centr

1 0

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

Feb. 3, 2017

Dear Bernard, All, The ccNSO Council supports the suggestion to limit the scope of the ATRT3 review. Kind regards, ]{atrina From: Patrik Fältström <patrik(a)frobbit.se> Date: Friday 27 January 2017 12:29 To: Bernard Turcotte <turcotte.bernard(a)gmail.com> Cc: Katrina Sataki <katrina(a)nic.lv>, <thomas.schneider(a)bakom.admin.ch>, James Bladel <jbladel(a)godaddy.com>, <ASO-chairs(a)aso.icann.org>, Louie Lee <louie(a)louie.net>, <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>, <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>, SSAC SSAC <ssac(a)icann.org> Subject: Re: CCWG-Accountability WG proposal for a Limited Scope of the ATRT3 Review - reminder [+SSAC] Dear Bernard, My apologies for missing you actually had a question at the end. I interpreted the message as a description of the situation, which SSAC already have said we are comfortable with. The SSAC supports the proposal from the CCWG-A Co-Chairs that the scope of ATRT3 be restricted to a review of the implementation of ATRT2 recommendations. Patrik Fältström SSAC Chair On 25 Jan 2017, at 21:41, Bernard Turcotte wrote: > > 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> 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- >> board-08aug16-en.pdf> 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-a >> l-24oct16-en.pdf> 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 >> https://mm.icann.org/mailman/listinfo/acct-staff >> >

1 0

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

Re: [ccnso-council] FW: CCWG-Accountability WG proposal for a Limited Scope of the ATRT3 Review - reminder
by ceo Feb. 3, 2017

Feb. 3, 2017

Dear Katrina, No objection from me Regards, Abdalla Omari On Jan 31, 2017 12:12 PM, Katrina Sataki <katrina(a)nic.lv> wrote: > > 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 Satak

1 0

Re: [ccnso-council] FW: CCWG-Accountability WG proposal for a Limited Scope of the ATRT3 Review - reminder
by ceo Feb. 3, 2017

Feb. 3, 2017

Dear Katrina, No objection from me Regards, Abdalla Omari On Jan 31, 2017 12:12 PM, Katrina Sataki <katrina(a)nic.lv> wrote: > > 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 Satak

1 0

February Council Meeting - Draft Agenda
by Kimberly Carlson Feb. 2, 2017

Feb. 2, 2017

Dear all, The next ccNSO Council call will be on 9 February, @11:00 UTC. The draft agenda and relevant background material has been posted here<https://ccnso.icann.org/about/council/minutes.htm> and on the Council wiki space<https://community.icann.org/x/sJLRAw>, any additional material will be published as well. The recording and minutes will be posted after the meeting. Please let me know if you have any additional questions, comments or concerns. 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 0

Draft agenda 9 February 2017 meeting (11.00 UTC)
by Bart Boswinkel Feb. 2, 2017

Feb. 2, 2017

Dear all, Please find included the draft agenda 9 February meeting, which is scheduled at 11.00 UTC. You should have received calendar invites. Also included Guideline ccNSO Council Practices (item 7.2 draft agenda). This document was shared with you in December. Since then no changes to document. Kind regards, Bart Draft Agenda ccNSO Council Meeting 9 February 2017, 11.00 UTC 1) Welcome and Apologies Attendance list is available at: http://ccnso.icann.org/about/council/attendance.htm Administrative Topics 2) Minutes and Actions Minutes 12 January 2016. Action 125-01: The Chair to inform ICANN staff as well as relevant SOAC chairs on selection. Completed Action 125-02: Secretariat to launch selection process – ccNSO liaison to the ALAC Completed Action 125-03: Add EC Ac and empowered community related work as an agenda topic for joint sessions with SOACs Ongoing 3) Overview inter-meeting Council decisions · Selection ccNSO liaison to ALAC · Decision to support limited scope ATRT 3 review · Support for Nigel Roberts suggestion to seek additional information (see further item 8 of agenda) 4) Appointment volunteers 4.1 Appointment ccNSO Liaison to GNSO For Decision The call for volunteers for the ccNSO liaison to GNSO will close 7 February 2017 Substantive topics 5) Specific reviews 5.1 Update on current state of play specific reviews For discussion o SSR 2 o Directory Services ( WHOIS) o ATRT 3 5.2 Directory Services and ATRT 3 selection process For discussion The call for volunteers for the Directory Services has closed on 20 January 2017 (after being extended). The list of volunteers is available at: https://community.icann.org/pages/viewpage.action?pageId=63145857 Potentially 6 candidates listed will seek endorsement from the ccNSO. The call for volunteers for ATRT 3 was published recently (31 January): https://www.icann.org/news/announcement-2017-01-31-en The ccNSO Guideline as adopted by Council on Selection of candidates for the specific reviews does not match the process as initiated nor are the required Operating Standards ( section 4.6 (a) (i). These Standards are supposed to provide the specific guidance on the selection process of candidates as well operating practices for each of the specific reviews and review teams, for example internal decision making. For discussion: selection process and other steps 6) Organizational review of the ccNSO and its timeline. For information As discussed the ccNSO Councilors on the working party are expected to meet with the Board Operational Effectiveness Committee (OEC) and the Council is expected to decide to initiate a call for volunteers for the community members on the “working party”. To date it is suggested to: - As discussed on the 12 January Councillors on the working party have been put their name forward. They include one Councillor form every region and one former NomCom appointee. - Webinar for Councillors has been organized. The recording will be made available. Purpose of the webinar was to explain scope of the review, the process itself, anticipated roles of the Council and working party and Independent Reviewer. The Copenhagen conversation with the OEC is foreseen to define the scope of the review. To inform the community a session has been included as part of the ccNSO meeting days in Copenhagen 7) Update Guidelines 7. 1. Date Council elections For discussion to provide guidance to GRC The GRC is currently working on the Council Guideline and seeks guidance from Council. Since the creation of the ccNSO Council election were organized with the understanding that (re-)elected Councillors take their seat at the end the February/March f-2-f meeting. This was done with an understanding that the ICANN Bylaws state that (re-)elected Councillors take their seat at the end of annual general meeting, which coincides with the ICANN annual meeting. 7.2 Adoption Council Practices Guideline For decision The Guideline Review Committee (GRC) has updated the ccNSO Council Meetings Guideline (2008) (https://ccnso.icann.org/about/guidelines-ccnso-council-meetings-08may08-en.…) The updated version was shared with Council and no comments were received. That version was also shared with the community to seek their feed-back and comments, and again no comments were received. The GRC submits its draft Guideline: ccNSO Council Practices for adoption. Once adopted it will replace the ccNSO Council Meetings Guideline. Document: 8) ccNSO Travel funding For discussion: request increase travel slot numbers FY 18 and beyond. To date the ccNSO can assign 12 travel slots ( a travel slot is the combination of travel, hotel accommodation, and per diem). The mechanism of assignement is guided by the ccNSO travel funding guideline and managed by the ccNSO Council travel funding committee. If the Council intends to request an increase the number of travel slots for FY 2018 and beyond, the window of opportunity is limited to the public comment period on FY 2018 Ops Plan and Budget public comment period. Increases in travel funding to ICANN meetings are intended to be structural i.e. not just for FY 18, it will be treated as part of regular budget. The public comment will open early March. Note that the expenses associated with ccNSO travel slots are part of the specific costs attributed to the ccTLD community (as defined in the ccNSO Finance WG Final report: http://archive.icann.org/meetings/buenosaires2013/en/schedule/sun-finance/p…) Discussion topics: - Does the Council want to request increase in number of travel slots? If so, how to organize, ccNSO statement procedure) - What is number of slots needed? For whom? If the number of slots will be increased, the ccNSO Travel Funding Guideline will need to be updated as well. 9) Updates CSC, RZERC and EC AC · CSC (Byron Holland) · EC AC (Stephen Deerhake) · RZERC (written update Peter Koch) 10) WG updates 10.1 Update CCWGs · CCWG Accountability (no material changes since previous Council update) · CCWG Use of country and territory names (written update Annebeth Lange) · CCWG Internet Governance (Young Eum Lee) · CCWG Auction Proceeds (Ching Chiao) 10.2 Update WG · GRC (Katrina Sataki) · Update Programme WG (Alejandra Reynoso) · Update Drafting Team& PDP ( Nigel Roberts, Bart Boswinkel) 11) Council Updates 11.1 Chair Update 11.2 Vice-Chair Update 11.3 Councilors Update 11.4 Regional Organizations Update 11.5 Secretariat update 12) Liaison Updates 12.1 GNSO Update. 12.2 ALAC Update (Interim: Maureen Hilyard). 13) Next meetings · Copenhagen meetings o Sunday, 12 March 2017, Workshop and prep meeting f-2-f meeting, Copenhagen ICANN 58, Sunday 12 March, noon local time, lunch included. § Workshop to discuss: · Roles and responsibilities ccNSO Councilors, includes prep chair and vice – chairs election, membership standing committees · Annual Work Plan § Prep meeting: Prep discussions and assignment of leads on core topics meeting. o ALAC-ccNSO Council meeting (tentatively) Sunday 12 March 17.00 local) o ccNSO-GNSO Councils meeting, Monday 13 March, 12.15-13.45 local time. o Board- ccNSO meeting. Most likely Tuesday 14 March 2016 in the morning. TBC’ed. Suggested topics: § Implementation of 1 October 2016 Bylaws: · Implementation of operation of processes and mechanisms related to the Empowered Community. o Board Designations by EC AC o Clarity around roles and responsibilities of all parties involved with respect to Budget and Operational Plans · Concurrent Specific Reviews without agreement on parameters (Operating Standards) which is also Bylaw requirement and are supposed to set the ground rules for each of the reviews, including the selection of candidates · Concurrently ccNSO expected to participate in 3 Accountability related efforts: CCWG WS 2, ATRT 3 and ccNSO review, in addition 2 other specific reviews (SSR2 and ATRT 3). § WG EPSRP next steps (Board response to letter) o ccNSO-GAC meeting, tentatively Tuesday 14 March. · Meeting with current ccNSO appointed Board members and Becky Burr, to start succession plan on replacement of Mikel Silber. Mike’s term ends October/November 2018. His replacement will need to be selected and nominated starting August /September 2017. The Board members will provide initial overview of their roles and responsibilities, time commitment etc. · Council meeting 15 March 17.00 Local time o Chair, vice-chair election 14) Work Plan 15) AOB 16) Closure

1 0

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

ccNSO Activity Summary January 2017
by Kimberly Carlson Feb. 1, 2017

Feb. 1, 2017

ccNSO Activity Summary January 2017 ICANN58: Meetings Page<https://meetings.icann.org/en/copenhagen58> Call for presenters: Tech Day - please email: ccnso-techwg(a)icann.org<mailto:ccnso-techwg@icann.org> ICANN58 Cross-Community Topic Proposals<https://meetings.icann.org/en/ICANN58-topics> Draft Block Schedule<https://meetings.icann.org/sites/default/files/icann58_blocksched_jan17.pdf> Working/Study Group Meeting Output: Recordings of various Working Group Meetings can be found here: http://ccnso.icann.org/calendar 9 January - Guidelines Review Committee Telephone Conference - Mp3<http://audio.icann.org/ccnso/ccnso-grc-09jan17-en.mp3> 11 January - DT-Review Mechanism and Retirement charter - Mp3<http://audio.icann.org/ccnso/ccnso-dt-rmre-11jan17-en.mp3>, wiki space<https://community.icann.org/x/MbHDAw> 18 January - Meetings Programme Working Group Telephone Conference - Mp3<http://audio.icann.org/ccnso/ccnso-programme-18jan17-en.mp3>, Adobe Connect<https://participate.icann.org/p7dupdt8jpj/?launcher=false&fcsContent=true&p…> 25 January - DT-Review Mechanism and Retirement charter - Mp3<http://audio.icann.org/ccnso/ccnso-dt-rmre-25jan17-en.mp3>, wiki space<https://community.icann.org/x/54XRAw> 30 January - Guidelines Review Committee Telephone Conference - Mp3<http://audio.icann.org/ccnso/ccnso-grc-30jan17-en.mp3> 30 January - Letter from ccNSO to ICANN Board re: EPSRP Final report can be found here<https://ccnso.icann.org/about/sataki-to-crocker-30jan17-en.pdf>. ccNSO Council: ccNSO Council preparation material and output can be found here: http://ccnso.icann.org/about/council/minutes.htm 12 January - ccNSO Council Telephone Conference - Mp3<http://audio.icann.org/ccnso/ccnso-council-12jan17-en.mp3> ccNSO Council Decisions and Resolutions: http://ccnso.icann.org/about/council/decisions-resolutions.htm ccNSO Council Wiki space <https://community.icann.org/x/BiyAAw> Links and Announcements regarding the IANA Stewardship Transfer and ICANN's Accountability Process: IANA Stewardship Transition Implementation Page<https://www.icann.org/stewardship-implementation> CSC Reports and Findings<https://www.icann.org/en/csc/reports> Other Announcements: Travel to and from the United States<https://www.icann.org/news/blog/travel-to-and-from-the-united-states> IANA Functions Customer Survey Results Available<https://www.icann.org/news/announcement-2-2017-01-11-en> Apply Now for ICANN Leadership Positions: Deadline Is 21 March 2017<https://www.icann.org/news/announcement-3-2017-01-11-en> ICANN Quarterly Stakeholder Report - Register for the FY17 Q2 Call on 15 February, 15:00 UTC<https://www.icann.org/news/announcement-2017-01-12-en> NextGen@ICANN Program Opens Application Round for ICANN59<https://www.icann.org/news/announcement-2017-01-16-en> PTI Board Adopts FY18 Budget and Publishes Report of Public Comments<https://www.icann.org/news/announcement-2017-01-23-en> _______________________________________________________________________________________________ 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 0