February 2017 - Ccnso-council

Updated schedule of the next ccNSO Members Meeting: ICANN58 in Copenhagen
by Joke Braeken Feb. 13, 2017

Feb. 13, 2017

Dear All, The draft schedule of the next ccNSO Members Meeting, posted on https://ccnso.icann.org/meetings/copenhagen58/agenda.htm, has been updated. During the ccNSO Members Meeting, the broader ccTLD community will discuss and be informed on a number of topics relevant for the world's country codes, including: - ccNSO Working Group updates - Session with the ccNSO appointed ICANN Board Members - Policy Development Session on the Retirement of ccTLDs and the Review Mechanism for the decisions on delegation, revocation and retirement of ccTLDs - ICANN updates, including among others a briefing on the upcoming ccNSO Review - Legal Session (Forum) on the topic of law enforcement in the DNS - Accountability Framework and the Exchange of Letters - Update by the Regional Organisations - Update and next steps ICANN accountability - ccTLD News session - Updates by the CSC and RZERC, and the services delivered by PTI to the ccTLD community High-level ccNSO schedule for ICANN58: SUNDAY 12 March 2017: Working Group meetings (TLD-OPS, SOP, GRC) | TLD-OPS closed workshop | ccNSO council preparatory meeting | joint session between ALAC and ccNSO MONDAY 13 March 2017: Tech Day | CSC public meeting TUESDAY 14 March 2017: ccNSO Members Meeting - day 1, including a joint session between ccNSO and GAC and one with the ICANN Board | ccNSO Cocktail WEDNESDAY 15 March 2017: ccNSO Members Meeting - day 2 | ccNSO council face-to-face meeting THURSDAY 16 March 2017: Cross-community session jointly proposed by ccNSO and GNSO “Towards a data driven ICANN” Updates, including remote participation details, will be posted on https://ccnso.icann.org/meetings/copenhagen58 closer to the meeting. The full ICANN58 meeting schedule will be posted on 20 February 2017 on https://meetings.icann.org/en/copenhagen58#schedule Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

reminder FW: FY17 Q2 Stakeholder Call will take place on 15 February 2017 at 15:00 UTC
by Joke Braeken Feb. 13, 2017

Feb. 13, 2017

Dear All, This e-mail serves as a reminder regarding the FY17 Q2 Stakeholder Call, which will take place on 15 February 2017 at 15:00 UTC. The call will focus on how ICANN has implemented community policy for the quarter ending 31 December 2016. The call will also provide an Africa and Middle East update, as part of a new format aimed at spotlighting regional activities. Further information can be found in the email below. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org From: Joke Braeken <joke.braeken(a)icann.org> Date: Tuesday, 17 January 2017 at 13:59 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccnso-council(a)icann.org" <ccnso-council(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org> Subject: FY17 Q2 Stakeholder Call will take place on 15 February 2017 at 15:00 UTC Dear All, ICANN has announced its FY17 Q2 Stakeholder Call, which will take place on 15 February 2017 at 15:00 UTC. The call will focus on how ICANN has implemented community policy for the quarter ending 31 December 2016. The call will also provide an Africa and Middle East update, as part of a new format aimed at spotlighting regional activities. Please click here[docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_forms_…> to register for the call and to receive joining instructions. If you are unable to access the form, pleaseemail us<mailto:icann.communications@icann.org> to register with your full name and an email address. The call is open for all to attend and live interpretation is offered in Arabic, Chinese, English, French, Portuguese, Russian and Spanish. There will be a Questions & Answers (Q&A) session and all materials (recordings, transcripts and presentations) will be archived and made available on the ICANN website[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. These calls were set up to enhance ICANN's accountability and transparency efforts, and are a great way for you to stay informed on what the organization has done in line with ICANN's mission of keeping the Internet secure, stable and interoperable. More information: https://www.icann.org/news/announcement-2017-01-12-en Please visit the Reporting page[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> on the ICANN website for more information, including recordings of previous calls. The presentation will be posted 24-48 hours in advance. 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

Thick WHOIS Registration Data Directory Services Requirements to Take Effect
by Joke Braeken Feb. 13, 2017

Feb. 13, 2017

Dear all, 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 Labelling and Display Policy by 1 August 2017. ICANN has notified contracted parties of their new responsibilities. Read more here: 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…> 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 report of the At-Large Review has been published for public comment
by Joke Braeken Feb. 13, 2017

Feb. 13, 2017

Dear All, The draft report of the At-Large Review has been published for public comment. The public comment period will remain open until 24 March 2017. 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…> Join ICANN and independent examiner ITEMS International (ITEMS) for a webinar on the Draft Report[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_syste…> [PDF, 2.31 MB] of the Review of the At-Large Community[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> on 27 February 2017 at 13:00 UTC. The webinar will include an overview of findings and recommendations presented by ITEMS followed by an open Q&A session. It is one of several opportunities to ask questions about how ITEMS reached their draft conclusions, express support or raise concerns. Read more about the webinar here: https://www.icann.org/news/announcement-2017-02-10-en Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 0

selection process: ccNSO Liaison to the GNSO
by Joke Braeken Feb. 13, 2017

Feb. 13, 2017

Dear All, Per Council decision, the secretariat is initiating the selection process for the position of ccNSO Liaison to the GNSO. Please find included: · Description of the nomination procedure (see below) · Information regarding the two candidates, Ben Fuller (.na) and Biyi Oladipo (.ng), as included as well in the material for the 9 February Council meeting You are requested to submit the name of your preferred candidate either to the ccNSO secretariat (ccNSOsecretariat(a)icann.org<mailto:ccNSOsecretariat@icann.org> ) or to me directly (joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>), with subject line: Selection GNSO liaison. PLEASE SEND YOUR EMAIL BY FRIDAY 17 FEBRUARY 23:59 UTC A kind reminder that from now on we will track and publish for each council member its participation in an election process. Thank you and kind regards, Joke Braeken SELECTION PROCESS Introduction As decided on the most recent Council meeting (9 February) you are requested, to select the ccNSO appointed liaison to the GNSO. As agreed the selection will be done using the standard selection process. The ccNSO Secretariat will track and publish for each council member its participation in an election process. The applicants The list of applicants and their application material are included in attachment. As none of the applicants is a member of the ccNSO Council, all Councillors are eligible to participate in the nomination process. You are all requested to send the name of your preferred candidate. Selection and procedure Based on the material provided, you are requested to assess which candidate you find most suited as liaison to the GNSO. To assist you in your assessment, the description of the liaisons’ role as included in the call for volunteers is included (see below). Once you completed your assessment you are requested to mail your preference to Joke (joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>), or the ccNSO secretariat (ccNSOsecretariat(a)icann.org)<mailto:ccNSOsecretariat@icann.org)> with subject line: Selection GNSO liaison. PLEASE SEND YOUR EMAIL BY FRIDAY 17 FEBRUARY 23:59 UTC Administrative Procedure After we received your email, we will acknowledge receipt and include a ballot number and date of receipt. On Monday 20 February 2017, we will circulate an email to the list, which will include an overview in the following format: - Ballot number, - Date ballot was received, - preferred candidate per ballot. This email will also include the total level of preference per candidate. As agreed by Council resolution and in accordance with the relevant ccNSO Guideline the candidate receiving most supportive votes, is selected. In the event the two candidates are equally preferred; a run-off selection will be needed. 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. 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

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