June 2016 - Ccnso-council - lists.icann.org

New membership application - .ba (Bosnia and Herzegovina)
by Eng. Abibu Ntahigiye June 8, 2016

June 8, 2016

Dear fellow Councillors, A new membership application has been received from .ba (Bosnia and Herzegovina). The Secretariat has checked and found that .ba has no pending issues with IANA. Please feel free to provide your comments before further consideration of .ba application possibly at the next ccNSO Council call on 16 June 2016. rgds ---------------------------------------------------------------------------- Eng. Abibu R. Ntahigiye; Manager, tzNIC; +255 784 279 511

1 0

Request from ICANN (re CSC) and draft letter to the community
by Katrina Sataki June 8, 2016

June 8, 2016

Dear Colleagues, Please see below the request for Appointment of Members and Liaisons to the CSC sent by ICANN to SO/ACs. Now it's time to inform the community. Here's the draft letter we'd like to send as soon as possible - big thanks to David McAuley (GRC) for taking the lead and drafting it. If you have any comments/suggestions/corrections, please do not hesitate to let me know as soon as possible. I think we need to send this out to the community not later than on Monday: -------------------- Dear Colleagues, On Friday, May 27, the ICANN Board approved the new ICANN Bylaws for IANA Stewardship Transition, deemed to be effective upon the expiration of the IANA Functions Contract between ICANN and NTIA. You will note that Article 17 of the new bylaws calls for the creation of the Customer Standing Committee (CSC). The CSC's role will be to monitor the performance of the Post Transition IANA entity (PTI), which will perform the IANA Functions relevant for the ccTLDs post transition (see: https://www.icann.org/iana_imp_docs/43-csc-scope-and-responsibilities-v-v2) . The ccNSO has to appoint two members representing ccTLD registry operators (the ccTLD manager does NOT have to be a member of the ccNSO) according to the internal procedures of the ccNSO. On 2 June 2016 the ccNSO Council received the request to appoint members to the Customer Standing Committee by 22 July 2016 (--include link--). Since April 2016 the ccNSO is working on a new guideline with respect to the selection and appointment of the ccTLD members on the CSC and related aspects. It is expected that the ccNSO Council will adopt the guideline at its meeting on 16 June. During the ccNSO meeting in Helsinki more detailed information on the entire process will be presented to the community and the formal call for expressions of interest will be issued on or around 30 June. This will, unfortunately, provide a very limited application window (two weeks) to meet the deadline of 22 July 2016. In order to enable interested candidates to prepare and send in their application within the envisioned tight application window, we will provide all the necessary information about the requirements and documents that have to be submitted. Expression of Interest will require a candidate to indicate how she or he meets at least the following requirements: - Direct experience and knowledge of the IANA naming function - Analytical skills, ability to interpret quantitative and qualitative evidence, and capacity to draw conclusions purely based on evidence - Able to work and communicate in written and spoken English - Effective communication skills - Experience in managing and/or participating in committees (e.g. meeting coordination, reporting, and escalation) in order to contribute meaningfully to CSC processes - Demonstrated ability in relationship management to support diplomatic discussion, consensus driven decision making, and productive negotiation In addition, the call will ask the applicant to submit at least the following: - Explanation of the interest in becoming a member of the CSC - A resume, curriculum vitae or biography in support of the Expression of Interest; - If employed by a ccTLD manager, a letter of support for the appointment signed by a member of candidate's organization's senior management; and - An indication whether the candidate is available to be elected for a 2 or 3-year term. In the course of the upcoming weeks I will keep you updated on the progress made. Kind regards, ------------------------ Thank you! Regards, ]{atrina From: Trang Nguyen [mailto:trang.nguyen@icann.org] Sent: Thursday, June 02, 2016 1:52 AM To: jbladel(a)godaddy.com; pdiaz(a)pir.org; patrik(a)frobbit.se; alan.greenberg(a)mcgill.ca; oscar(a)lacnic.net; katrina(a)nic.lv; bverd(a)verisign.com; Thomas.Schneider(a)bakom.admin.ch; tsinha(a)umd.edu Cc: David Olive <david.olive(a)icann.org>; Heidi Ullrich <Heidi.Ullrich(a)icann.org>; Carlos Reyes <carlos.reyes(a)icann.org>; Marika Konings <marika.konings(a)icann.org>; Steve Sheng <steve.sheng(a)icann.org>; Olof Nordling <olof.nordling(a)icann.org>; Bart Boswinkel <bart.boswinkel(a)icann.org>; Julie Hedlund <julie.hedlund(a)icann.org>; 'jrobinson(a)afilias.info' <jrobinson(a)afilias.info>; Lise Fuhr <Fuhr(a)etno.eu>; Austin, Donna <Donna.Austin(a)neustar.biz>; Yuko Green <yuko.green(a)icann.org> Subject: Request for Appointment of Members and Liaisons to the Customer Standing Committee (CSC) Dear Chairs and Co-Chairs, Please see attached a request from ICANN for appointment of members and liaisons to the Customer Standing Committee (CSC). Warm regards, Trang Nguyen Senior Director, Strategic Programs ICANN

5 12

Call for CSC volunteers coming!
by Katrina Sataki June 6, 2016

June 6, 2016

Dear Colleagues, On Friday, May 27, the ICANN Board approved the new ICANN Bylaws for IANA Stewardship Transition, deemed to be effective upon the expiration of the IANA Functions Contract between ICANN and NTIA. You will note that Article 17 of the new bylaws calls for the creation of the Customer Standing Committee (CSC). The CSC's role will be to monitor the performance of the Post Transition IANA entity (PTI), which will perform the IANA Functions relevant for the ccTLDs post transition (see: <https://www.icann.org/iana_imp_docs/43-csc-scope-and-responsibilities-v-v2> https://www.icann.org/iana_imp_docs/43-csc-scope-and-responsibilities-v-v2) The ccNSO has to appoint two members representing ccTLD registry operators (the ccTLD manager does NOT have to be a member of the ccNSO) according to the internal procedures of the ccNSO. On 2 June 2016 the ccNSO Council received the request to appoint members to the Customer Standing Committee by 22 July 2016 - <http://ccnso.icann.org/workinggroups/csc-appointment-request-03jun16-en.pdf > http://ccnso.icann.org/workinggroups/csc-appointment-request-03jun16-en.pdf. Since April 2016 the ccNSO is working on a new guideline with respect to the selection and appointment of the ccTLD members on the CSC and related aspects. It is expected that the ccNSO Council will adopt the guideline at its meeting on 16 June. During the ccNSO meeting in Helsinki more detailed information on the entire process will be presented to the community and the formal call for Expression of Interest will be issued on or around 30 June. This will, unfortunately, provide a very limited application window (two weeks) to meet the deadline of 22 July 2016. In order to enable interested candidates to start working on their application in advance of the envisioned tight application window, we will provide all the necessary information about the requirements and documents that have to be submitted. Expression of Interest will require a candidate to indicate how she or he meets at least the following requirements: - Direct experience and knowledge of the IANA naming function - Employed or have active backing by a ccTLD manager - Analytical skills, ability to interpret quantitative and qualitative evidence, and capacity to draw conclusions purely based on evidence - Able to work and communicate in written and spoken English - Effective communication skills and commitment to inform the ccTLD community on a regular basis in person at the ccNSO meetings or RO meetings or via e-mail - Experience in managing and/or participating in committees (e.g. meeting coordination, reporting, and escalation) in order to contribute meaningfully to CSC processes - Demonstrated ability in relationship management to support diplomatic discussion, consensus driven decision making, and productive negotiation In addition, the call will ask the applicant to submit at least the following: - Explanation of the interest in becoming a member of the CSC - A resume, curriculum vitae or biography in support of the Expression of Interest - An indication whether the candidate is available to be elected for a 2 or 3-year term, and - An indication of commitment of your organization to your participation to the CSC. Finally, the interested candidates should be aware that travel funding is not provided. In the course of the upcoming weeks I will keep you updated on the progress made. Kindest regards, Katrina Sataki Chair of the ccNSO

1 0

Triage recommendation 21-2016: ICANN, RySG Propose Amendment to New gTLD Registry Agreement
by Joke Braeken June 3, 2016

June 3, 2016

Dear Councillors, Please find below the proposed Triage recommendation 21-2016. Kindly provide me with your input by the end of Tuesday 7 June 2016, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you. Topic: 21-2016 - ICANN, RySG Propose Amendment to New gTLD Registry Agreement Originator: ICANN Summary of request: ICANN issued for public comment a proposed amendment to the base New gTLD Registry Agreement<https://newgtlds.icann.org/sites/default/files/agreements/agreement-approve…>. The public comment period ends 13 July 2016. The RySG initiated the process. Following the conclusion of the public comment period, ICANN and the RySG working group for these negotiations will consider the comments and submit the proposed final version of the amendment for approval by registry operators and the ICANN board (see Section 7.6 of the registry agreement). If these approvals are obtained, the amendment will become effective upon 60 days notice from ICANN to the registry operators. https://www.icann.org/news/announcement-2016-05-31-en Date received: 01 June 2016 Last day for Comments/input/response, if any: 13 July 2016 Recommended action, if any: none Expertise needed, if any: legal Recommendation received by Triage Committee: 03 Juni 2016 Date submission to Council: 03 June 2016 Deadline Council decision: Tuesday 7 June 2016, 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

Triage recommendation 20-2016: Draft ICANN restated Articles of Incorporation
by Joke Braeken June 3, 2016

June 3, 2016

Dear Councillors, Please find below the proposed Triage recommendation 20-2016. Kindly provide me with your input by the end of Tuesday 7 June 2016, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you. Topic: 20-2016 - Draft restated Articles of Incorporation Originator: ICANN Summary of request: As ICANN continues its implementation planning work on the IANA Stewardship Transition Coordination Group (ICG) and Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) proposals, another key item is the revision of ICANN's Articles of Incorporation. The proposed draft of the Restated Articles of Incorporation was developed collaboratively by the ICANN legal team and the independent counsel hired to advise the CCWG-Accountability and the Cross Community Working Group to Develop an IANA Stewardship Transition Proposal on Naming Related Functions (CWG-Stewardship). Both the independent counsel to the community groups and ICANN's General Counsel agree that the draft Restated Articles are consistent with the community proposals relating to the IANA Stewardship Transition.These proposed draft Restated Articles are out for public comment to allow any interested party to review and provide feedback. https://www.icann.org/public-comments/draft-restated-articles-incorporation… Date received: 28 May 2016 Last day for Comments/input/response, if any: 6 July 2016 Recommended action, if any: e-mail to cctldworld@ Expertise needed, if any: legal Recommendation received by Triage Committee: 03 Juni 2016 Date submission to Council: 03 June 2016 Deadline Council decision: Tuesday 7 June 2016, 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

Pre-ICANN56 Policy Update Webinar on Thursday, 16 June 2016
by Joke Braeken June 3, 2016

June 3, 2016

Dear All, PRE-ICANN56 POLICY UPDATE WEBINAR https://www.icann.org/news/announcement-2016-06-02-en# The ICANN Policy Development Support Team will provide a Policy Update Webinar on Thursday, 16 June 2016 at 10:00 UTC and 19:00 UTC, in preparation for the upcoming ICANN Policy Forum in Helsinki. The purpose of the webinar is to summarize policy activities across the ICANN policy development community and briefing the community on the Cross-Community sessions taking place in Helsinki. The two sessions are duplicates, scheduled to accommodate different time zones. Each session runs for 90 minutes and will be conducted in English. The webinar will be conducted in Adobe Connect along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, questions may be submitted using the chat function in Adobe Connect. Recordings of the webinars will be made available here <https://www.icann.org/resources/pages/presentations-2012-08-27-en>. The Policy Development Support Team is always available to answer any questions via email at policyinfo(a)icann.org<mailto:policyinfo@icann.org>. Please RSVP via this form <http://goo.gl/forms/NEFg46A88QnWK8Z33> by 10 June 2016. Remote participation details will be sent the week of 13 June 2016. AGENDA: 1. Cross-Community Sessions Briefings: * ICANN Accountability & Cross-Community Working Group (CCWG) Update * Charter for the Cross-Community Working Group (CCWG) on the use of new generic Top Level Domain (gTLD) Auction Proceeds * Draft Framework of Principles for Future Cross-Community Working Groups * New gTLD Subsequent Procedures Policy Development Process (PDP) * Next Generation generic Top Level Domain (gTLD) Registration Directory Service (WHOIS) Policy Development Process (PDP) * Review of All Rights Protection Mechanisms in all generic Top Level Domains (gTLDs) Policy Development Process (PDP) 2. Supporting Organizations & Advisory Committee Updates: * Address Supporting Organization (ASO) and Regional Internet Registries (RIR) Policy Development * Country Code Names Supporting Organization (ccNSO) * ICANN Operational Plan & Budget * Country & Other Geographic Names Forum * Generic Names Supporting Organization (GNSO) * GNSO Review * Possible Modification of the WHOIS Conflicts with Local Law Procedure * At-Large Advisory Committee (ALAC) and At-Large Community * Policy Advice Development * Next Steps on the At-Large Review * Activities at ICANN56, including Outreach and Engagement and Regional At-Large Organizations (RALO) Sessions * Government Advisory Committee (GAC) * 2-Character Labels and Country Names as Second Level Domains in New generic Top Level Domains (gTLDs) * Advice Effectiveness * Privacy and Proxy Services Accreditation * International Governmental Organization (IGO) Acronyms Protections in New generic Top Level Domains (gTLDs) * Root Server System Advisory Committee (RSSAC) Advisory * Security and Stability Advisory Committee (SSAC) * Publications * DNSSEC Workshop 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 Survey on ccNSO Council Accountability
by Bart Boswinkel June 2, 2016

June 2, 2016

Dear all, As you may recall the Council discussed the need for a survey on ccNSO Council accountability at tis meeting in April. As you may also recall drafting was in progress. Please find included draft for discussion etc. by Council. We have used the basic concepts from the CCWG Accountability around accountability (transparency, consultation, review and redress) as starting point to look into the different aspects. WE would appreciate your feed-back etc. by 7 June 2016, to be able to launch the survey in time for the Helsinki meeting. Thank you and kind regards, Bart -------------------------------------------------------------------------- Background & Introduction The ccNSO provides a platform to nurture consensus, technical cooperation and skill building among ccTLDs and facilitates the development of voluntary best practices for ccTLD managers. The policy development process (http://ccnso.icann.org/policy/development) is managed by the ccNSO Council<http://ccnso.icann.org/about/council.htm>, which consists of 18 Councillors (15 elected by ccNSO members, three appointed by the ICANN Nominating Committee). The Councillors are actively involved in determining the work and direction of the ccNSO: they lead and participate in various ccNSO-working groups; they engage the community in topical issues and they develop positions based on community feedback. The ccNSO Council meets regularly at ICANN’s international meetings, and at (monthly) scheduled telephone conferences. All the documents, minutes of the meetings, resolutions and discussions are published on the ccNSO website and on the ccNSO Council wiki space. In order to further improve the transparency and accountability of the ccNSO Council, in light of the upcoming discussions on the accountability of the ccNSO as part of the process to enhance ICANN’s Accountability, we invite you to answer the ccNSO Council Accountability survey by 22 June 2016. Your answers will be most appreciated. Results of the survey will be made available shortly after 22 June 2016 on the ccNSO website. GENERAL INFORMATION 1. Which region does your ccTLD belong to? Please select one. o Africa o Asia-Pacific o Europe o Latin-America & Caribbean o North America 2. What is your relationship to the ccNSO? o The ccTLD is a member o The ccTLD is not a ccNSO member 3. Your ccTLD is potentially a member of one or more Regional Organisations. Select all that apply. o AfTLD o APTLD o CENTR o LACTLD o None of the above TRANSPARENCY Definition: the ccNSO Council is answerable to its stakeholders by being open and visible to them. 4. How do you receive information about the activities of the ccNSO and ccNSO Council? Select all that apply. o Updates by individual Councillors (face-to-face and teleconferences) o Minutes of ccNSO Council meetings (face-to-face and teleconferences) o ccNSO Council Correspondence o Monthly activity updates o Councillors attendance sheets o Information regarding ccNSO Council Elections o Councillors attendance sheet o ccNSO Council wiki o none 5. Which channels do you use to receive information about the activities of the ccNSO Council? Please select all that apply. o Mailing list o ccNSO website o ccNSO Council wiki space o ICANN meetings o Updates provided to the regional organisations during their meetings (AfTLD, APTLD, CENTR, LACTLD) o Social media o Other, please specify: ......................................................................................................................................... o None 6. What would be your preferred method to learn about the activities and decisions of the ccNSO Council? ......................................................................................................................................................................................... ......................................................................................................................................................................................... 7. Overall, how well do you consider yourself to be informed about the ccNSO Council activities? 1 very well informed 2 Well informed 3 neutral 4 not well informed 5 not informed at all If not well informed or not informed at all, please suggest how the ccNSO Council could improve its information flow to you? ....................................................................................................................................................................................................... CONSULTATION Definition: the ccNSO Council continually takes input from and explains its positions to the stakeholders 8. Does - in your opinion - the ccNSO Council welcome input from the community and explain its decisions and activities? 1 Always 2 Most of the time 3 Sometimes 4 Hardly ever 5 Not at all 6 No Opinion If hardly ever or Not at all: How could this be improved? ....................................................................................................................................................................................... ....................................................................................................................................................................................... If no opinion, please specify: .......................................................................................................................................................................................... .......................................................................................................................................................................................... REVIEW Definition: the ccNSO Council's actions, policies and programmes are subject to outside monitoring and evaluation. 9. According to the Rules of the ccNSO (http://ccnso.icann.org/about/ccnso-rules-dec04-en.pdf) actions and decisions of the ccNSO Council become effective only 7 days after the decision is published on the ccNSO website. Do you review the decisions as soon as they are published? 1 Yes, always 2 Yes, sometimes 3 Hardly ever 4 Never REDRESS Definition: the ccNSO Council makes compensations for any harms of its actions and omissions, for example, by means of policy changes, institutional reforms, resignations, etc. 10. According to the Rules of the ccNSO (http://ccnso.icann.org/about/ccnso-rules-dec04-en.pdf) , if members disagree with a ccNSO Council decision, with a few listed exceptions, they may ask for a vote. Are you aware of this redress mechanism? 1 Yes 2 No 11. Is – in your view – a members vote sufficient mechanism to redress a ccNSO Council decision? 1 yes 2 no 3 No opinion If No opinion: Please specify ....................................................................................................................................................................................... ....................................................................................................................................................................................... 12. What other redress mechanisms would you suggest? Please specify ....................................................................................................................................................................................... ....................................................................................................................................................................................... FINAL REMARKS 13. Any other comments or suggestions? ....................................................................................................................................................................................... .......................................................................................................................................................................................

2 2

RE: [ccnso-council] FW: ATTENTION! Information on CSC
by Katrina Sataki June 1, 2016

June 1, 2016

Hi Barrack, Thank you very much for your comment! I agree with your point. BUT! Please take into account: 1) we have to select only 2 members. As Alejandra rightfully pointed out, there's no much room for diversity. We have 5 regions, we have really big, medium-sized and small registries. We have ccTLDs run by private comapnies, governmental institutions, academic institutions, NGOs, not for profit organisations, etc. 2 seats!!! 2) I think that this time it is not only about representation and goodwill. If we needed to choose a dentist, for example, we would not think "Our eye doctor is old and comes from Europe, the surgeon is a young Brazilian, psychotherapist is very small and skinny - so, the dentist must be a big woman from Australia" No, we would look for a professional who knows how to fix an aching tooth. If the big woman from Australia happens to be a superb dentist - it's wonderful. But if she does not have a clue, then better not to let her touch our teeth. I think this is what my colleagues councillors mean when they say that knowledge of IANA system should be prior to other considerations. 3) the diversity of the entire CSC composition should be considered. But! Liaisons do not vote. Members do. Therefore the members we select must be professionals who are able to soothe our toothache. Thanks! Regards, ]{atrina -----Original Message----- From: Barrack Otieno [mailto:otieno.barrack@gmail.com] Sent: Wednesday, June 01, 2016 2:14 PM To: Katrina Sataki <katrina(a)nic.lv> Cc: ccnso-council(a)icann.org Subject: Re: [ccnso-council] FW: ATTENTION! Information on CSC Hi Katrina, I would like to emphasize on one point diversity. We should strive to be diverse since it always attracts goodwill due to the fact that it enhances representation. Regards On 6/1/16, Katrina Sataki <katrina(a)nic.lv> wrote: > Dear All, > > > > Thanks for all your comments! > > > > To foster further discussion I’ll try to address your comments and > questions. > > > > VOTING: > > Those who responded support the idea of having a sub-committee. Please > note that according to the current plan in any case evaluation of > candidates and selection of 2 CSC members from the ccNSO is done by > full ccNSO Council (with exception of those Councillors who decide to > apply for CSC, of course). > > The role of the sub-committee we need to agree on is: do we want the > sub-committee to only liaise with the RySG and GNSO – OR – we agree > that the sub-committee also votes on the full slate on behalf of the ccNSO Council. > Alejandra supported the first option. As far as I understand, Debbie > also prefers the first option. What do others think? Please take into > account that if we ask for a full ccNSO Council vote we will need a > quorate ccNSO Council either on a call or via emails in early August! > > > > SELECTION: > > In the guideline there will be requirements for CSC members and in > their applications the candidates will be asked to meet these > requirements. I think these requirements should be used to evaluate the candidates. > > > > DIVERSITY: > > We need to select people who know their stuff. At the same time, the > CWG in their proposal clearly stated that diversity needs to be > considered. Yes, we need knowledgeable people but are we ok if all the > members of the CSC (2 from ccNSO and 2 from GNSO) are from the same > region? If yes, we must be ready to 1) accept this risk and 2) justify our position. > > Yes, we will coordinate the full slate with the GNSO and hopefully > will be able to work on diversity. Other SO/ACs are asked to submit 2 > candidates each even though they have only 1 seat each. We hope that > this would give us (ccNSO and GNSO) a leverage to ensure diversity. > > However, this might not be enough. > > Your thoughts? > > > > Kind regards, > > > > ]{atrina > > -- Barrack O. Otieno +254721325277 +254733206359 Skype: barrack.otieno PGP ID: 0x2611D86A

5 13

ccNSO Council in Helsinki
by Kimberly Carlson June 1, 2016

June 1, 2016

Dear all, The ccNSO Council will meet in Helsinki as follows: Monday, 27 June ccNSO Council Prep - Veranda 3 *11:15 - 12:00 EET local time Room: Veranda 3 (*please note: because of the block scheduling, this meeting is listed with a 10:45 start time, the meeting will not start until 11:15). Thursday, 30 June ccNSO Council Meeting - Veranda 2 11:15 - 12:00 EET local time The schedule is subject to change, so please continue to check the main meeting schedule Please let me know if you wish to participate in these meeting remotely. Kind regards, Kim Carlson

1 0

ccNSO Activity Summary May 2016
by Kimberly Carlson June 1, 2016

June 1, 2016

ccNSO Activity Summary May 2016 ICANN 56 Helsinki Meetings Page<https://meetings.icann.org/en/helsinki56> and Registration<https://registration.icann.org/> * Final call for Presenters - Tech Day - email ccnso-techwg(a)icann.org<mailto:ccnso-techwg@icann.org> Working/Study Group Meeting Output: Recordings of various Working Group Meetings can be found here: http://ccnso.icann.org/calendar 2 May - CWG on Country and Territory Names as TLDs - recording<http://audio.icann.org/gnso/gnso-ctn-02may16-en.mp3> 2 May - CWG-ISTP 9 May - Guidelines Review Committee - recording<http://audio.icann.org/ccnso/ccnso-grc-09may16-en.mp3> 11 May - Meetings Programme WG - recording<http://audio.icann.org/ccnso/ccnso-programme-11may16-en.mp3> 12 May - CWG-ISTP 23 May - Guidelines Review Committee - recording<http://audio.icann.org/ccnso/ccnso-grc-23may16-en.mp3> 23 May - CWG-ITSP 23 May - CWG on Country and Territory Names as TLDs - recording<http://audio.icann.org/gnso/gnso-ctn-23may16-en.mp3> TLD OPS Standing Committee - TLD Monitoring Tools<http://ccnso.icann.org/workinggroups/tld-monitoring-tools-31may16-en.pdf> ccNSO Council: *New ccNSO Council Wiki workspace can be found here<https://community.icann.org/x/BiyAAw> 12 May - ccNSO Council Meeting ccNSO Council preparation material and output can be found here: http://ccnso.icann.org/about/council/minutes.htm ccNSO Council Decisions and Resolutions: http://ccnso.icann.org/about/council/decisions-resolutions.htm Links and Announcements regarding the IANA Stewardship Transfer and ICANN's Accountability Process: IANA Stewardship Transition Implementation Page<https://www.icann.org/stewardship-implementation> 10 May - IANA Stewardship Transition Planning Update (Volume 2)<https://www.icann.org/news/blog/iana-stewardship-transition-planning-update…> - by Trang Nguyen 27 May - New ICANN Bylaws<https://www.icann.org/news/blog/new-icann-bylaws> - by Steve Crocker Other Announcements: Explore Our First ICANN Post-Public Meeting Technical Report<https://www.icann.org/news/blog/explore-our-first-icann-post-public-meeting…> ICANN56, the New Meeting Format, and What that Means to You<https://www.icann.org/news/blog/icann56-the-new-meeting-format-and-what-tha…> Changing the Keys to the Domain Name System (DNS) Root Zone<https://www.icann.org/news/blog/changing-the-keys-to-the-domain-name-system…> Relocating ICANN57<https://www.icann.org/news/blog/relocating-icann57> The First Week<https://www.icann.org/news/blog/the-first-week> Revisions to ICANN Expected Standards of Behaviors<https://www.icann.org/public-comments/expected-standards-revisions-2016-05-…> - open for public comment Recordings of Calls with Community on Public Comments Submitted on the Draft FY17 Operating Plan and Budget Now Available<https://www.icann.org/news/announcement-2016-05-11-en> Call for Expressions of Interest for 2017 Nominating Committee Chair and Chair-Elect<https://www.icann.org/news/announcement-2016-05-24-en>

1 0