February 2017 - Ccnso-council

[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