July 2019 - Ccnso-council - lists.icann.org

triage recommendations 36-2019 until 39-2019
by Joke Braeken July 24, 2019

July 24, 2019

Dear councillors, Please find the latest Triage Committee recommendations (36, 37, 38, 39-2019) included below. If you do not agree with the recommendations, kindly let me know by Wednesday, 24 July 23:59 UTC. Thank you. Best regards, Joke Braeken Number: 36-2019 Topic: Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project Request from: SSAC Summary: Purpose: As part of the project plan for the name collision analysis project (NCAP), the SSAC would like to seek public input on the definition of name collision and scope of inquiry for the name collision analysis project. Current Status: Draft Definition of Name Collision and Scope of Inquiry for the Name Collision Analysis Project for public comment Next Steps: The NCAP discussion group will finalize the definition of name collision and scope of inquiry for the name collision analysis project after considering the public input. Close date: 12 august 2019 Read more: https://www.icann.org/public-comments/proposed-definition-name-collisions-2… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> Recommended action: send to ccnso-members@, cctld-community@, ccnso-council@ and share via social media Impact on ccNSO: low Relevance for ccTLDs: middle Deadline triage committee input: Friday, 19 July 2019 (23:59 UTC) Number: 37-2019 Topic: Request for Proposal: Name Collision Analysis Project (NCAP) Study 1 Request from: ICANN Org, OCTO Summary: ICANN is seeking to identify a contractor to perform the research, analysis, and writing necessary to produce Study 1 of the Name Collision Analysis Project (NCAP). The scope of NCAP Study 1 is larger than usual work undertaken by SSAC, so the ICANN organization's Office of the CTO (OCTO) is facilitating the work and is engaging a contractor to perform Study 1 Close date: by 23:59 UTC on 30 July 2019 Read more: https://www.icann.org/news/announcement-2019-07-09-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: send to ccnso-members@, cctld-community@, ccnso-council@ and share via social media Impact on ccNSO: low Relevance for ccTLDs: middle Deadline triage committee input: Friday, 19 July 2019 (23:59 UTC) Number: 38-2019 Topic: GNSO Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms Policy Recommendations for ICANN Board Consideration Request from: ICANN Org, policy development support Summary: Purpose: This public comment proceeding seeks to obtain community input prior to Board action on certain final policy recommendations from the Generic Names Supporting Organization Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms. Current Status: The GNSO Council approved PDP Recommendations 1-4 during its meeting on 18 April 2019. The GNSO Council did not approve PDP Recommendation 5 which therefore does not form part of this public comment proceeding. Next Steps: The ICANN Board is expected to meet to discuss taking action on the four approved recommendations following the close of this public comment proceeding. Close date: 20 Aug 2019 23:59 UTC Read more: https://www.icann.org/public-comments/igo-ingo-crp-recommendations-2019-07-… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> Recommended action: none Impact on ccNSO: none Relevance for ccTLDs: none Deadline triage committee input: Friday, 19 July 2019 (23:59 UTC) Number: 39-2019 Topic: The Annual ICANN APAC Space Survey is Now Open Request from: ICANN Org, APAC Summary: Survey to help to make the APAC Space more relevant to the Asia Pacific (APAC) community, and improve the APAC Space as a platform that fosters community discussion. Close date: 1 August 2019 Read more: https://www.icann.org/news/announcement-2019-07-15-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: send to ccnso-members@, cctld-community@, ccnso-council@ and share via social media Impact on ccNSO: low Relevance for ccTLDs: low Deadline triage committee input: Friday, 19 July 2019 (23:59 UTC) 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

5 4

Friendly reminder: Application/expression of Interest membership IFRT
by Bart Boswinkel July 24, 2019

July 24, 2019

Dear all, Please be aware that If you have any objection or do not support the appointment, please respond by 23 July 2019, 23.59 UTC. If you want to express your support please do not hesitate to do so! Kind regards, Bart From: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Tuesday, 16 July 2019 at 15:08 To: <ccNSO-Council(a)icann.org> Subject: Application/expression of Interest membership IFRT Dear all, We are pleased to inform you that the secretariat received one application to become appointed as ccTLD representative from a non-ccNSO member. Included you will find the (redacted) CV and completed Expression of Interest from Unguec Stephen Kang. .ss (NCA, Southern Sudan, AF region) As there is only one candidate, please indicate If you have any objection or do not support the appointment, please respond by 23 July 2019, 23.59 UTC FOR YOUR INFORMATION The criteria for selection are the following: Non-ccNSO member ) conformed) , from AF, AP or NA region (confirmed) Skill set and experience (see temporary guideline, which is included) Direct experience and knowledge of the IANA naming functions. Understanding the purpose of the IFR. Analytical skills, ability to interpret quantitative and qualitative evidence, and the capacity to draw conclusions purely based on evidence. Experience in managing and/or participating in committees (e.g. meeting coordination, reporting, and escalation) to contribute meaningfully to IFR processes. Demonstrated ability in relationship management to support discussion, consensus-driven decision making, and productive negotiation. Excellent communication skills to represent ccTLD interests and to keep the ccNSO Council and broader ccTLD community informed on progress. Ability to work and communicate in written and spoken English. Kind regards, Bart

2 2

Council comments on ccNSO review
by Katrina Sataki July 23, 2019

July 23, 2019

Dear Councillors, As agreed, we're preparing a statement on the draft report on ccNSO2, i.e. our review: https://drive.google.com/file/d/1HB52_HV-MxzEPGQaACIos0Q31jTCWXqU/view Please feel free to express yourselves by 23 July, 12 UTC. Thank you! Kind regards, ]{atrina

4 3

Re: [ccnso-council] triage recommendations 36-2019 until 39-2019
by Stephen Deerhake ＠ ASNIC July 22, 2019

July 22, 2019

I have no problem with any of them /Stephen From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Joke Braeken <joke.braeken(a)icann.org> Date: Monday, July 22, 2019 at 04:41 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] triage recommendations 36-2019 until 39-2019 Dear councillors, Please find the latest Triage Committee recommendations (36, 37, 38, 39-2019) included below. If you do not agree with the recommendations, kindly let me know by Wednesday, 24 July 23:59 UTC. Thank you. Best regards, Joke Braeken Number: 36-2019 Topic: Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project Request from: SSAC Summary: Purpose: As part of the project plan for the name collision analysis project (NCAP), the SSAC would like to seek public input on the definition of name collision and scope of inquiry for the name collision analysis project. Current Status: Draft Definition of Name Collision and Scope of Inquiry for the Name Collision Analysis Project for public comment Next Steps: The NCAP discussion group will finalize the definition of name collision and scope of inquiry for the name collision analysis project after considering the public input. Close date: 12 august 2019 Read more: https://www.icann.org/public-comments/proposed-definition-name-collisions-2… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> Recommended action: send to ccnso-members@, cctld-community@, ccnso-council@ and share via social media Impact on ccNSO: low Relevance for ccTLDs: middle Deadline triage committee input: Friday, 19 July 2019 (23:59 UTC) Number: 37-2019 Topic: Request for Proposal: Name Collision Analysis Project (NCAP) Study 1 Request from: ICANN Org, OCTO Summary: ICANN is seeking to identify a contractor to perform the research, analysis, and writing necessary to produce Study 1 of the Name Collision Analysis Project (NCAP). The scope of NCAP Study 1 is larger than usual work undertaken by SSAC, so the ICANN organization's Office of the CTO (OCTO) is facilitating the work and is engaging a contractor to perform Study 1 Close date: by 23:59 UTC on 30 July 2019 Read more: https://www.icann.org/news/announcement-2019-07-09-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: send to ccnso-members@, cctld-community@, ccnso-council@ and share via social media Impact on ccNSO: low Relevance for ccTLDs: middle Deadline triage committee input: Friday, 19 July 2019 (23:59 UTC) Number: 38-2019 Topic: GNSO Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms Policy Recommendations for ICANN Board Consideration Request from: ICANN Org, policy development support Summary: Purpose: This public comment proceeding seeks to obtain community input prior to Board action on certain final policy recommendations from the Generic Names Supporting Organization Policy Development Process on IGO-INGO Access to Curative Rights Protection Mechanisms. Current Status: The GNSO Council approved PDP Recommendations 1-4 during its meeting on 18 April 2019. The GNSO Council did not approve PDP Recommendation 5 which therefore does not form part of this public comment proceeding. Next Steps: The ICANN Board is expected to meet to discuss taking action on the four approved recommendations following the close of this public comment proceeding. Close date: 20 Aug 2019 23:59 UTC Read more: https://www.icann.org/public-comments/igo-ingo-crp-recommendations-2019-07-… [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> Recommended action: none Impact on ccNSO: none Relevance for ccTLDs: none Deadline triage committee input: Friday, 19 July 2019 (23:59 UTC) Number: 39-2019 Topic: The Annual ICANN APAC Space Survey is Now Open Request from: ICANN Org, APAC Summary: Survey to help to make the APAC Space more relevant to the Asia Pacific (APAC) community, and improve the APAC Space as a platform that fosters community discussion. Close date: 1 August 2019 Read more: https://www.icann.org/news/announcement-2019-07-15-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> Recommended action: send to ccnso-members@, cctld-community@, ccnso-council@ and share via social media Impact on ccNSO: low Relevance for ccTLDs: low Deadline triage committee input: Friday, 19 July 2019 (23:59 UTC) 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

2 1

Statement on Bylaws change
by Katrina Sataki July 18, 2019

July 18, 2019

Dear Councillors, Please find a draft for our statement on the Bylaws amendment: https://drive.google.com/file/d/1GA51v2igH-5_p8pJxv9BPZjvAcYsGOp_/view I would like to submit it on Friday, therefore, please do your magic by Friday, 12:00 UTC. Thank you! Kind regards, ]{atrina

3 2

SUBMIT suggestions of Cross-community topics for ICANN 66 (deadline Friday 12 July, 23:59 UTC)
by Alejandra Reynoso July 18, 2019

July 18, 2019

Dear All, ICANN’s meetings team will soon start collecting a list of topics to be organised as cross-community sessions for the Annual General Meeting (2nd to 7th November 2019) in Montréal. If there is a topic that you would like to see included as cross-community session, kindly send your proposal to joke.braeken(a)icann.org and/or alejandra.reynoso(a)cctld.gt no later than Friday 12th July, 23:59 UTC. Proposals for cross-community sessions must include: 1. Title 2. Background/Importance. Must have potential to attract a sizable audience (200+) 3. Session goals and expected outcomes 4. Hyperlinks to any relevant documentation (if available) 5. Suggested format of the session Only complete proposals will be taken into consideration by the ICANN's meetings team. Please note that having too many sessions sponsored by the ccNSO in one ICANN meeting has proven to be too exhausting and the Meetings Programme Committee will review proposals with implementation in mind. Thank you! Best regards, Alejandra Reynoso On behalf of the Meetings Programme Committee -- [image: Photograph] *Alejandra Reynoso*Investigación & Desarrollo | Dominios .gt *P:* +502 23688565 *E:* alejandra.reynoso(a)cctld.gt 18 Ave. 11 <https://maps.google.com/?q=18+Ave.+11&entry=gmail&source=g>-42 Zona 15, V.H. III. Guatemala, Guatemala www.gt

1 1

Board elections guideline
by Katrina Sataki July 18, 2019

July 18, 2019

Dear Councillors, We have received a response from ICANN Legal about our Board nomination process, in particular on section 3.5 which describes the due diligence check. ICANN Legal expressed no concerns about GDPR, nor any other substantive concerns about the process (see attachment). However, they did draw attention to the following: 1) some suggested language edits and clarifications about the way how to contact the due diligence provider. It's what was meant in the guideline anyway, only now it has been made clearer, therefore, I think we can accept those suggestions, without any further discussions; 2) as I already mentioned before - following our discussions with the community - the guideline requires to vet all the candidates before the members vote. ICANN Legal suggests that we consider vetting only the winner - to cut the costs. If I understand it correctly, costs may be less of a problem with only 2 or 3 candidates. As far as I can tell, we have never had more than 2. Therefore, technically, we can assume that this time will be no different and still can go with the process as described in the guideline. In parallel and awaiting the outcome from the legal review, we looked at the Selection timeline (as required under the old and recently adopted guideline). While developing the timeline, we learned that a due diligence check by the independent provider may take from 4 to 8 weeks (and in some cases, depending on the country of residence, even longer). Today, the Secretariat and I discussed the possible timeline for the Board election. It has become pretty obvious that if we vet the candidates in the manner as foreseen under the guideline, we run a high risk of NOT having the results of the background check by our meeting in Montreal. Or, to be more precise, if we do interview them in Montreal, it is still not clear if the candidate(s) will be eligible. Which might be a good thing - even if anyone has to step down (because of a failed background check), nobody would suspect anything. In any case, taking into account the points above and under the assumption we all agree that the membership should have the opportunity to interview the candidates before taking a vote, we will need to defer a decision on the timeline to our call on 22 August when we need to decide on one of two following options: * Option 1: we vet all the candidates before the vote, i.e. go with the current version of the guideline. If we choose this path, we also need to choose one of the sub-options: *** Sub-option 1.a : we interview the candidates in Montreal knowing that the background checks are not completed yet. *** Sub-option 1.b : we postpone the interview of candidates to Cancun (March 2020) and vote after that. Even under this option there will still be time for members vote. * Option 2: we change the process to vet only the winning candidate. However, we need to understand that no matter how hard we protect the results, information about the winner will eventually leak anyway (for example, the losing candidates will know they have lost because they are not contacted by the due diligence provider). If we go for this option, I believe it does not change the essence (nomination, voting, appointment, the fact that the appointed candidate has undergone a background check) of the guideline and therefore there is no need to publish the guideline for public comments from the community (any objections to that?). While discussing the timeline, we realised one more thing: as you remember, there was a request from the community to add an option "None of the above" allowing people to vote against ALL the candidates. The current version of the guideline says that if the number of candidates being nominated equals the number of seats (e.g. one candidate to one seat or 2 candidates to 2 seats) we do not vote - the Council just nominates the candidate(s). Taking into account that members now can dismiss candidates by voting for "None of the above", it seems only fair to apply this principle also to the case when there is only one candidate per seat, i.e. call for a members vote anyway (which in itself is probably the right thing to do). Therefore, I would like to suggest to remove the first two paragraphs from Section 3.7. Another thing for our Council call on 22 August. Meanwhile, if there are any questions/suggestions/preferences, please feel free to share them on the list! Kind regards, ]{atrina

1 0

FW: [ICANN Community Leaders] 18 July Update
by Katrina Sataki July 18, 2019

July 18, 2019

FYI From: SO-AC-SG-CLeaders [mailto:so-ac-sg-cleaders-bounces@icann.org] On Behalf Of ICANN Community Leadership Digest Sent: Thursday, July 18, 2019 5:00 PM To: so-ac-sg-cleaders(a)icann.org Subject: [ICANN Community Leaders] 18 July Update <http://r20.rs6.net/on.jsp?ca=ed8230d3-1b13-414c-8393-a76601e7a331&a=1122025…> Thursday, 18 July 2019 ICANN Community Leadership Digest <https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…> This twice-weekly digest helps ICANN community leaders track requests and provides updates from ICANN org. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> TABLE OF CONTENTS Information Sharing * NEW: Accountability and Transparency Review -- Highlights from ICANN65 and Share Your Views * REMINDER: Post-ICANN65 Policy Report Now Available * REMINDER: NextGen@ICANN Survey * REMINDER: Update and Information on IRP IOT Re-Composition * REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs ICANN66 Planning * NEW: Plenary Session Topics: Proposals Due Friday, 2 August * NEW: Publication Support Deadlines Public Comment * CLOSING TOMORROW: Study on Technical Use of Root Zone Label Generation Rules * CLOSING NEXT WEEK: Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review * CLOSING NEXT WEEK: Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership * CLOSING NEXT WEEK: Proposed IANA SLAs for Publishing LGRs/IDN Tables * Draft Final Report of the Second Country Code Names Supporting Organization Review * Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan * Evolving the Governance of the Root Server System * Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project Information Sharing NEW: Accountability and Transparency Review -- Highlights from ICANN65 and Share Your Views Executive: Theresa Swinehart, Senior Vice President, Multistakeholder Strategy and Strategic Initiatives FOR: All Community Leaders INFORMATION SHARING The third Accountability and Transparency Review Team (ATRT3) had a productive five days at ICANN65. Read the team's latest <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> blog post to learn more. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> REMINDER: Post-ICANN65 Policy Report Now Available Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Post-ICANN65 Policy Report written by the ICANN Policy Development Support team captures decisions and outcomes from the Supporting Organizations and Advisory Committees. While the report provides an overview of activities held during the Policy Forum, it also looks ahead at the work to come in the upcoming months. Included in the report are various resources to support the ongoing, sustained engagement of the community on several important issues. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> REMINDER: NextGen@ICANN Survey Executive: Sally Costerton, Senior Adviser to President and Senior Vice President, Global Stakeholder Engagement FOR: All Community Leaders INFORMATION SHARING The ICANN organization is initiating a <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> community consultation to identify improvement opportunities for the <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> NextGen@ICANN Program. The review will start with gathering community input via a survey about several aspects of the NextGen@ICANN Program, including its purpose, goals, processes, and synergies with the ICANN academic community. The <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> survey (PDF with background at the beginning and questionnaire questions at the end) is intended for all ICANN community groups; individuals are encouraged to work with their relevant Supporting Organizations, Advisory Committees, stakeholder groups, and constituencies. Responses are due Monday, 9 September. Based on the input received from the survey, ICANN org will draft a proposal for program improvements that will be published for Public Comment. Once all feedback is received, ICANN org will prepare the final proposal for program improvements. <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Sally Costerton's blog about the NextGen@ICANN Community Consultation <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> REMINDER: Update and Information on IRP IOT Re-Composition Executive: John Jeffrey, General Counsel FOR: All SO/AC Chairs INFORMATION SHARING As the ICANN Board committee with oversight responsibility of ICANN's accountability mechanisms, the Board Accountability Mechanisms Committee (BAMC) considers the work of the [Independent Review Process (IRP)] Implementation Oversight Team (IOT) to be paramount to ICANN's accountability...we seek your help in finding additional volunteers within the community that meet the qualifications identified in the attached letter, outlining skills and experience requirements, to join the IOT and help to conclude its work in a timely fashion. <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Read more. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> REMINDER: Planning Assumptions for Subsequent Procedures for New gTLDs Executive: Cyrus Namazi, Senior Vice President, Global Domains Division FOR: All Community Leaders INFORMATION SHARING In December 2015, the GNSO initiated a Policy Development Process (PDP) to determine if changes to existing policy recommendations are needed before the next round of gTLDs. The PDP Working Group expects to publish its final report with its recommendations by December 2019. These recommendations may lead to procedural changes for subsequent rounds of gTLD applications, which ICANN org must implement and manage. In the course of our preparatory work toward the planning and implementation of the new policy, ICANN org has compiled a number of fundamental operationally focused assumptions to help with the preliminary planning and operational readiness of the organization. These assumptions have been shared with the ICANN Board, and now ICANN org would like to share them with relevant parts of the community. ICANN66 Planning NEW: Plenary Session Topics: Proposals Due Friday, 2 August Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING The official submission period to propose plenary session topics for ICANN66 is from Monday, 22 July to Friday, 2 August. The proposal form is now open for anyone who wants to get a head start! <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Plenary Session Topic Proposal Form An online report of proposals will be shared with the ICANN Public Meeting Community Planning Group as soon as it becomes available. <https://imgssl.constantcontact.com/letters/images/1101116784221/S.gif> NEW: Publication Support Deadlines Executive: David Olive, Senior Vice President, Policy Development Support FOR: All Community Leaders INFORMATION SHARING Design Deadline If you require design assistance for an ICANN66 publication, all text, images, layout, and publication type/size requirements (i.e. newsletter, 1-pager, tri-fold, etc.) are due Friday, 23 August. Due to budget constraints, please keep in mind that all materials, new or updated, need to be evergreen. Translation Deadline If your ICANN66 publication requires translation, please provide the final material(s) by Friday, 6 September. This ensures that there is enough time to translate the publication by the print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. Print-Only Deadline If you only need your ICANN66 publication printed (meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications), please provide the file along with the quantity you want printed and dimensions of the publication by Friday, 20 September. Please work directly with your Policy support staff to submit these requests. Public Comment <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Study on Technical Use of Root Zone Label Generation Rules CLOSES TOMORROW: Friday, 19 July <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Fundamental Bylaws Amendment Proposal -- IANA Naming Function Review CLOSING NEXT WEEK: Friday, 26 July 2019 <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Revisions to the ICANN Bylaws re SSAC and RSSAC Leadership CLOSING NEXT WEEK: Friday, 26 July 2019 <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Proposed IANA SLAs for Publishing LGRs/IDN Tables CLOSING NEXT WEEK: Friday, 26 July 2019 <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Draft Final Report of the Second Country Code Names Supporting Organization Review Close Date: 4 August 2019 <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Draft Financial Assumptions & Projections and Operating Initiatives for the Development of the Fiscal Years 2021-2025 Operating & Financial Plan Close Date: Monday, 5 August 2019 <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Evolving the Governance of the Root Server System Close Date: Friday, 9 August 2019 <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Proposed Definition of Name Collisions and Scope of Inquiry for the Name Collisions Analysis Project Close Date: Monday, 12 August 2019 Volume 1, Issue 33 | <http://r20.rs6.net/tn.jsp?f=001HL-NI6ZSdvZnc7WUYy-H7OqYn1C9ruES4hMjLed898Qd…> Archive | Next Issue: Monday, 22 July 2019 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 <https://visitor.constantcontact.com/do?p=un&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Unsubscribe so-ac-sg-cleaders(a)icann.org <https://visitor.constantcontact.com/do?p=oo&m=00115LrDzKl3LoTB9FWCDiE2A%3D&…> Update Profile | <http://www.constantcontact.com/legal/about-constant-contact> About Constant Contact Sent by <mailto:david.olive@icann.org> david.olive(a)icann.org in collaboration with <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> <http://www.constantcontact.com/index.jsp?cc=nge&rmc=VF19_3GE> Try email marketing for free today!

1 0

Call for volunteers: ccNSO appointed member of ICANN's NomCom FY 2020
by Kimberly Carlson July 17, 2019

July 17, 2019

Dear all, In accordance with the ccNSO Guideline: Appointment of delegate to the Nominating Committee (http://ccnso.icann.org/workinggroups/appointment-nomcom-delegate-05nov08.pdf [ccnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__ccnso.icann.org_working…>), the ccNSO Council is now looking for a volunteer to serve on the 2020 ICANN Nominating Committee (NomCom) on behalf of the ccNSO. Candidates may self-nominate. Closing date for nomination is Friday 19 July 2019, 23.59 UTC. Please note that you are required to be associated with a ccTLD manager. In addition, after being selected, you will need to consent to ICANN processing your personal data for the purpose of serving on the NomCom under ICANN’s data protection policy (Terms of Service [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_…>) If you are interested in serving in this position, please, send an email to the ccNSO Secretariat (ccnsosecretariat(a)icann.org<mailto:ccnsosecretariat@icann.org>), and include a short motivation letter why you wish to serve on the NomCom and explain briefly how you meet the selection criteria listed below. The list of candidates will be presented to all ccNSO Councillors eligible to vote and who will then take a decision by email vote. Under the 1 October 2016 Bylaws the NomCom is an independent committee tasked with nominating eight members of the Board of Directors and other key positions within ICANN's structure. The 2020 NomCom will select Directors of the ICANN Board, member(s) of the ALAC, member(s)of the GNSO Council, 1 member of the ccNSO Council. More information on the criteria for serving as appointee on the NomCom can be found at the end of this email and on the NomCom itself at: https://www.icann.org/resources/pages/nomcom-2013-12-13-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> . On behalf of the ccNSO Secretariat, Kind regards, Kimberly Carlson Selection Criteria Specific criteria for selecting a delegate to the NomCom are provided in Article 8, Section 4 of ICANN’s Bylaws (https://www.icann.org/resources/pages/governance/bylaws-en/#article8 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>): “Section 4. CRITERIA FOR SELECTION OF NOMINATING COMMITTEE DELEGATES Delegates to the ICANN Nominating Committee shall be: 1. Accomplished persons of integrity, objectivity, and intelligence, with reputations for sound judgment and open minds, and with experience and competence with collegial large group decision-making; 2. Persons with wide contacts, broad experience in the Internet community, and a commitment to the success of ICANN; 3. Persons whom the selecting body is confident will consult widely and accept input in carrying out their responsibilities; 4. Persons who are neutral and objective, without any fixed personal commitments to particular individuals, organizations, or commercial objectives in carrying out their Nominating Committee responsibilities; 5. Persons with an understanding of ICANN's mission and the potential impact of ICANN's activities on the broader Internet community who are willing to serve as volunteers, without compensation other than the reimbursement of certain expenses; and 6. Persons who are able to work and communicate in written and spoken English.” All FY 2020 NomCom members should be able to attend the first formal meeting of the 2020 NomCom (during or around ICANN 66) and most likely the June 2020 (ICANN68) meeting. Travel and hotel accommodation will be provided. In addition: * NomCom delegates should have a high-level network of contacts essential to candidate recruitment. * The person should be able to join monthly teleconferences (typically 13:00 or 14:00 UTC). Note that the committee's workload will increase significantly during Apr/May/June 2020 when the candidate assessment process will be at its busiest. Conference calls are held more frequently (typically weekly) during this time as well. * The person must be able to attend the NomCom selection meeting in June 2020. * The person should be willing to work in a large, consensus-oriented committee. The NomCom has its own guideline <https://www.icann.org/resources/pages/2015-guidelines-2014-11-14-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>> and procedure <https://www.icann.org/resources/pages/2015-procedures-2014-11-14-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>> . These reference documents provide additional information about the work of the NomCom.

1 1

Call for volunteers: Customer Standing Committee (CSC)
by Kimberly Carlson July 17, 2019

July 17, 2019

Dear all, The ccNSO Council is seeking volunteers who wish to be a member on the Customer Standing Committee (CSC). If interested, please send the following documents to: Kimberly.Carlson(a)icann.org<mailto:Kimberly.Carlson@icann.org> no later than Friday 26 July 2018 (23:59 UTC). 1. Filled in application form (attached) 2. Your resume, curriculum vitae, or biography. 3. If applicable, a letter of support from your employer in respect to the required time commitment to participate actively in the CSC. The ccNSO Council will then select a candidate following the procedure detailed in the Guideline: ccNSO Actions Respecting the Customer Standing Committee. The CSC has been established to ensure the satisfactory performance of the Internet Assigned Numbers Authority (IANA) naming function. The CSC monitors PTI’s performance of the IANA naming function by analyzing performance reports on a monthly basis and publishing its findings. It is authorized to undertake remedial action to address poor performance, and if performance issues are not remedied, the CSC is authorized to escalate the performance issues to the ccNSO and GNSO for consideration. Additionally, the CSC may recommend changes to the naming Service Level Expectations as well as enhancements to the provision of the IANA naming services. To understand the scope of the requirements and duties of membership of the CSC please review both the CSC Candidates Qualification Requirements and the CSC Charter . Links • Applicable Guideline: ccNSO Actions Respecting the Customer Standing Committee (http://ccnso.icann.org/workinggroups/guidelines-ccnso-csc-16jun16-en.pdf) • CSC Charter: https://www.icann.org/en/system/files/files/csc-charter-amended-27jun18-en.… • CSC Skill-set requirements: https://www.icann.org/en/system/files/files/csc-skill-set-matrixmembers- liaisons-04jun19-en.pdf • Background CSC: https://www.icann.org/en/system/files/files/csc-overview-members-liaisons- 04jun19-en.pdf Thank you and kind regards, Kimberly Carlson

1 1