September 2021 - Ccnso-council

Thursday, 2 September 2021 | Improved Public Comment Feature Launches!
by ICANN Community Leadership Digest Sept. 2, 2021

Sept. 2, 2021

Thursday, 2 September 2021 ICANN Community Leadership Digest The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved Table of Contents Webinars NEXT WEEK: Shaping the Future of the Internet: A Webinar on ICANN's Newcomer Programs REMINDER: FY 23-27 Operating and Financial Plan and FY23 Operating Plan and Budget Webinar Information Sharing NEW: ICANN Training Days for the Eastern European and Central Asian Community NEXT WEEK: Deadline Extended: Expressions of Interest for Registration Data Accuracy Scoping Team Chair ICANN72 Planning DEADLINE TODAY: Join the ICANN72 Plenary Session Planning Teams Public Comment NEW: ICANN Launches Improved Public Comment Feature Infographic: What is Public Comment? Step-by-Step Public Comment Submission Guidelines Zoom Replay: Public Comment Submission Training Zoom Replay: Public Comment User Experience Demonstration Webinars NEXT WEEK: Shaping the Future of the Internet: A Webinar on ICANN's Newcomer Programs ICANN invites the community to join a webinar on Thursday, 9 September 2021 at 14:00 UTC to learn more about newcomer programs and opportunities for engagement. Register Read more. REMINDER: FY23-27 Operating and Financial Plan and FY23 Operating Plan and Budget Webinar ICANN org invites the ICANN community to participate in one of two webinars on the planning process for the FY23-27 Operating and Financial Plan and FY23 Operating Plan and Budget. Please register for one of the two webinars: ● Wednesday, 15 September 2021 at 00:00 UTC Register ● Wednesday, 15 September 2021 at 15:00 UTC Register The ICANN org Planning team will discuss the FY23 planning process, key assumptions, and timeline. There will be an opportunity to ask questions. In addition to the webinars, the ICANN community has further opportunity to participate in this planning process. The draft plans will be published for Public Comment in early December 2021. Community participation in ICANN's planning process is a cornerstone of transparency and accountability to the global multistakeholder community. ICANN thanks all the community members who contribute to this important process. Information Sharing NEW: ICANN Training Days for the Eastern European and Central Asian Community ICANN invites the Internet community in Eastern Europe and Central Asia to join a pilot regional event, the ICANN Training Days, on 13-14 September. This event aims at providing targeted technical training to address the critical needs of registries and registrars in Eastern Europe and Central Asia, with a special focus on Uzbekistan. Read more. NEXT WEEK: Deadline Extended: Expressions of Interest for Registration Data Accuracy Scoping Team Chair The Generic Names Supporting Organization (GNSO) Council is seeking Expressions of Interest (EOI) to chair the Registration Data Accuracy Scoping Team. The Council approved the formation of the team and provided instructions during its meeting on 22 July 2021. The deadline to submit an EOI has been extended to Thursday, 9 September 2021 at 23:59 UTC. All submissions must be sent to gnso-secs(a)icann.org. Read more. ICANN72 Planning DEADLINE TODAY: Join the ICANN72 Plenary Session Planning Teams ICANN72 will feature two plenary sessions. Weekly one-hour planning calls begin next week. To join a planning team, please participate in the relevant Doodle poll: Designing Hybrid ICANN Public Meetings Moving Forward with the Public Interest Framework Public Comment NEW: ICANN Launches Improved Public Comment Feature The Information Transparency Initiative (ITI) has reached another important milestone with the release of an improved Public Comment feature. This enhanced feature is part of the ICANN organization's ongoing commitment to increase the findability and transparency of our information. Read more about the improvements! There are no open proceedings. See upcoming proceedings. Infographic: What is Public Comment? Step-by-Step Public Comment Submission Guidelines Zoom Replay: Public Comment Submission Training Zoom Replay: Public Comment User Experience Demonstration Volume 3, Issue 65 | Archive | Next Issue: Monday, 6 September 2021 ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe ccnso-council(a)icann.org Update Profile | Constant Contact Data Notice Sent by david.olive(a)icann.org powered by Try email marketing for free today!

1 0

Re: [ccnso-council] [Ext] Bylaw changes to Article 10 and Annex B
by Alejandra Reynoso Sept. 1, 2021

Sept. 1, 2021

Dear Erika The ccNSO welcomes this opportunity to provide a response to your suggestions regarding the proposed changes to Article 10 and Annex B of the ICANN Bylaws. The ccNSO Council was consulted from 13-19 August and had no issues with the proposed amendments. As a next step, the ccNSO Members were consulted from 20-27 August. We received three (3) comments: Comment #1: "I really disagree with the deprecation of the word "country" and its replacement by "territory". Among the ccTLDs, countries are the rule, and non-country territories are the exception. We are ccTLDs, not tcTLDs, and the ccNSO is not the tcNSO. I don't think it is a good idea to have the bylaws break in its use of terms from long standing tradition. RFC1591 speaks only of countries, never of territories, even though I suppose Postel was aware he was abusing the word "country" a little bit. The FoI report uses "countries or territories" a lot, but even then, "country" is used twice as often as "territory". My preference would be to use "countries" throughout, and have a note at the beginning specifying that the use of this word in the bylaws must be interpreted to mean "countries or territories". My second best choice would be to use "countries or territories" everywhere. " Finally, I would suggest a better wording for the phrase "or other area of particular geopolitical interest listed on the ‘International Standard ISO 3166-1,...', which might be understood as if other territories that did not get their own code would be of no particular geopolitical interest. A better phrase could be 'or other geographical area listed on the ‘International Standard ISO 3166-1,...' " Comment #2: "Use the word 'country' throughout and insert at the beginning language that defines 'country' to mean names of countries (current and non-current), dependencies, and other areas of particular geopolitical interest and their subdivisions." Taken from the ISO 3166 definitions Comment #3: “I would like to include the term "territories" in Comment #2’s proposed definition. Defining 'country' as the names of countries (current and non-current), dependencies, territories, and other areas of particular geopolitical interest and their subdivisions. While it was implicit in the previously proposed definition, I would like to make it explicit.” The comments refer to the second paragraph in Article 10.4.a. which currently states: “For purposes of this Article, and Annexes B and C of these Bylaws, “Territory” is defined to be the country, dependency or other area of particular geopolitical interest listed on the ‘International Standard ISO 3166-1, Codes for the representation of names of countries and their subdivisions – Part 1: Country Codes’, or, in some exceptional cases listed on the reserved ISO 3166-1 code elements.” We appreciate the comments made, however we want to point out that the definition as proposed was already included in the proposed overall policy for the inclusion of IDNccTLD Managers in the ccNSO selection of IDN ccTLD strings (ccPDP2) as adopted by the ccNSO in 2013, and submitted to the Board. The definition was confirmed again in the October 2019 consultation resulting in the request to change Article 10 and Annex B of the Bylaws and in the ccNSO Statement on the first set of questions from ICANN Legal more recently. With respect to the substance of the comments: Firstly, according to the English Dictionary ( https://www.merriam-webster.com/dictionary/territory) the word territory is being used correctly. We note that this term is not part of the reference to geographic entities referenced in ISO 3166. Secondly, we note that in other relevant documents, such as the FOI <https://ccnso.icann.org/sites/default/files/filefield_46435/foi-final-07oct…> and the IDN Fast Track <https://www.icann.org/en/system/files/files/idn-cctld-implementation-plan-2…>, "countries or territories" is the term that is mainly used, but in the discussions with respect to the ccPDP4 (de-)selection of IDNccTLD strings, the term ‘Territory’ will be proposed and is defined in the same manner. Therefore, taking in consideration the feedback received, the ccNSO Council suggests moving forward with the current definition. Finally, some additional edits that are needed: 1. Change the heading of Article 10.4.e. The suggestion is to strike “and Territory” from the heading: “Designation of Representative and Territory“. The new heading should read “Designation of Representative”, since the section is about the designation of the ccTLD Representative. 2. Correct the typo in Article 10.4.e.iii: "manger" needs to become "manager". 3. Capitalize the first letter of "Emissary" in Article 10.4.e.iii. at the end of the sentence "is deemed to be the emissary for that Territory". 4. Change "e-mail" to "electronic means" in Annex B.1.a . All other proposed amendments are supported. Please find enclosed the updated proposed Bylaw changes. Please do not hesitate to contact us, if you have any questions. Best regards, Alejandra Reynoso ccNSO Council Chair -- [image: Photograph] *Alejandra Reynoso*Investigación & Desarrollo | Dominios .gt *P:* +502 23688565 *E:* alejandra.reynoso(a)cctld.gt 18 Ave. 11-95 Zona 15, V.H. III. (A-109) Guatemala, Guatemala www.gt

1 0

Call For Volunteers: team to review and recommend improvements to the ccNSO Onboarding Course on ICANN Learn
by Joke Braeken Sept. 1, 2021

Sept. 1, 2021

Dear All, The ccNSO is now looking for for a limited number of volunteers who will review and suggest improvements for the current ccNSO Onboarding Course on ICANN Learn. The call for volunteers for the course revision team opens Wednesday, 1 September 2021 (23:59 UTC) and closes Wednesday, 15 September 2021 (23:59 UTC). What is this about? The ccNSO Onboarding Course (ICANN Learn identifier 150.1) was created a few years ago, as part of the efforts by the ccNSO to inform the broader community about its role in supporting ccTLDs and its place within the ICANN ecosystem. The course is available on ICANN Learn, an online learning platform requested by and built for the global ICANN community. Courses cover the basics of what ICANN and the various Supporting Organisations and Advisory Committees do, how to get involved, and more. For more information visit http://learn.icann.org The ccNSO Outreach and Involvement Standing Committee (OISC) recently suggested the ccNSO Council to undertake an extensive review of the ccNSO Onboarding Course on ICANN Learn, before having the course translated in the various languages ICANN provides translations in. The Council then requested the OISC to take all steps necessary to start and complete the review as soon as possible, including but not limited to seeking volunteers to assist in the review, and developing a work plan and report to the Council on a regularly basis. A small team of ccTLD representatives – under the auspices of the OISC - is now expected to review the course and to recommend improvements. The team will perform an extensive revision of the current course, addressing both content, accessibility, and other aspects. How to apply? Are you associated with a ccTLD manager, interested in e-learning and related matters and keen on serving on the course revision team? You are invited send an email to joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>. The call for volunteers for the course revision team closes Wednesday, 15 September 2021 (23:59 UTC). Basic knowledge about the ccNSO and its role is required. Moreover, you are expected to have completed the ccNSO Onboarding Course (ICANN Learn identifier 150.1) ahead of the first meeting by the course revision team. By submitting your personal data, you acknowledge that your personal data will be processed in accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy<https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!PtGJab4…>) and you agree to abide by the electronic Terms of Service (https://www.icann.org/privacy/tos<https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!PtGJab4!vp…>) Time Commitment The small team is expected to meet regularly (a bi-weekly meeting pace is suggested). The first meeting will take place end September, and the work is expected to be completed at or around ICANN72, held 25-28 October 2021. Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0