August 2021 - Ccnso-council

REMINDER | Pre-ICANN72 ccTLD News Sessions: Apply now for a speaking slot
by Joke Braeken Sept. 3, 2021

Sept. 3, 2021

Hello everyone, This is a reminder that it is still possible to apply for a speaking slot for the upcoming virtual pre-ICANN72 ccTLD News Sessions. The deadline for submitting a presentation proposal is 13 September 2021 (23:59 UTC). Read more here: https://ccnso.icann.org/en/announcements/announcement-02aug21-en.htm Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org From: Ccnso-members <ccnso-members-bounces(a)icann.org> on behalf of "ccnso-members(a)icann.org" <ccnso-members(a)icann.org> Reply to: Joke Braeken <joke.braeken(a)icann.org> Date: Monday, 2 August 2021 at 16:22 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "ccTLDcommunity(a)cctld-managers.org" <ccTLDcommunity(a)cctld-managers.org>, ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-members] Pre-ICANN72 ccTLD News Sessions: Apply now for a speaking slot Dear All, Do you have a best practice, project solution or case study you want to share with the broader community? A recent market development from your ccTLD, or perhaps some legal or operational news that is engaging, relevant and informative to other ccTLDs from across the world? We want to hear from you! On 6 and 7 October 2021, there will be the next edition of the virtual ccTLD News Sessions, organized by the ccNSO Meetings Programme Committee (MPC). The MPC has now issued a call for presentations and is seeking speakers on a variety of ccTLD-related topics. The deadline for submitting a presentation proposal is 13 September 2021 (23:59 UTC). How to apply? Please send your presentation proposal – including the information below - to Joke Braeken (joke.braeken(a)icann.org)<mailto:joke.braeken@icann.org)>, no later than 13 September 2021 (23:59 UTC) * Title of your presentation * First name of the presenter * Last name of the presenter * ccTLD of the presenter * Short summary of your presentation (max 10 sentences) * Profile picture, to be used when promoting the agenda Next steps Each proposal for a presentation is reviewed and evaluated by MPC. The agenda for the upcoming ccTLD News Session will become public mid-September 2021. A preparatory meeting for presenters will be held on 23 September, followed by a dry-run on 30 September. There will be 2 options to participate to the pre-ICANN71 Virtual ccTLD News Sessions: Wednesday, 6 October 2021 (13 UTC) and Thursday, 7 October 2021 (6 UTC). Each session will have a separate agenda. The ccNSO Meeting Programme Committee looks forward to your suggestions. Thank you! Best regards, Joke Braeken On behalf of the ccNSO Meetings Programme Committee About the ccTLD News Sessions Previous editions of the ccTLD News Sessions had an excellent collection of case studies, statistics, new developments, trends and more. The ccTLD News Sessions have been a part of the ccNSO Members Meetings for several years and has provided a global platform for both experienced and new people to meet, share experiences and discuss ccTLD-related aspects. For reference, the most recent session was held prior to ICANN71. The presentations and recordings are available at https://community.icann.org/display/ccnsowkspc/ICANN71+%7C+ccNSO+Members+Me… Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org>

1 2

Final reminder | Draft overview ccTLD contribution FY21
by Joke Braeken Aug. 31, 2021

Aug. 31, 2021

Dear All, I am sending you a final reminder regarding the email below. If you have any comments please do not hesitate to contact ICANN Accounting (accounting(a)icann.org<mailto:accounting@icann.org>) latest by today, Tuesday 31 August 2021 (23:59 UTC) at its latest. Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of ccnso-council <ccNSO-Council(a)icann.org> Reply to: Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Friday, 6 August 2021 at 14:01 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, "cctldcommunity(a)cctld-managers.org" <cctldcommunity(a)cctld-managers.org>, "ccTLDWorld(a)icann.org" <ccTLDWorld(a)icann.org> Cc: ccnso-council <ccNSO-Council(a)icann.org>, ICANN Accounting <accounting(a)icann.org> Subject: [ccnso-council] Draft overview ccTLD contribution FY21 Dear all, Please find attached the draft of ccTLD contributions report for FY2021 (1 July 2020-30 June 2021). If you have any comments please do not hesitate to contact ICANN Accounting ( email address in the cc) or me by 31 August 2021 at its latest. The final version will be published by ICANN around 15 September 2021. With respect to the report itself, please note the following changes to the report this year: 1. The report is now listed in alphabetical order (in English) of the country name, not ordered by the ASCII abbreviation. This is due to the inclusion of IDN ccTLD contributions beginning this year. 2. There is a footnote for contributions received from IDN ccTLD operators before because these were not listed separately previous to FY2021. Kind regards, Bart Boswinkel VP Policy Support – ccNSO relations

1 0

[REVIEW DRAFT] Feedback on Proposed Amendments to Article 10 and Annex B
by Alejandra Reynoso Aug. 30, 2021

Aug. 30, 2021

Dear Councillors Following the ccNSO Members' consultation regarding the Proposed Amendments to Article 10 and Annex B. It is time to report back to ICANN Legal with our findings, suggestions and/or edits. I have drafted an email response in the following Google Doc: https://docs.google.com/document/d/12zZZuHmyatXuMDuHg4y0xl4SwyKG3DexPivAkyU… Please review it and feel free to edit and add comments until next Tuesday 31/August, so it can be finalized by Wednesday 1/September. Have a great weekend! *:)* Best regards, Alejandra -- [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

3 3

Monday, 30 August 2021 | New Public Comment Feature Launches TOMORROW!
by ICANN Community Leadership Digest Aug. 30, 2021

Aug. 30, 2021

Monday, 30 August 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 NEW: Shaping the Future of the Internet: A Webinar on ICANN's Newcomer Programs NEW: FY 23-27 Operating and Financial Plan and FY23 Operating Plan and Budget Webinar Information Sharing NEW: Deadline Extended: Expressions of Interest for Registration Data Accuracy Scoping Team Chair 🚨🚨TOMORROW: Nominations for NextGen@ICANN Mentor Positions ICANN72 Planning NEW: Join the ICANN72 Plenary Session Planning Teams Public Comment Step-by-Step Public Comment Submission Guidelines Zoom Replay: Public Comment Submission Training Zoom Replay: Public Comment User Experience Demonstration Webinars NEW: 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. NEW: 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. Information Sharing NEW: 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. 🚨🚨TOMORROW: Nominations for NextGen@ICANN Mentor Positions The NextGen@ICANN Program seeks nominations for its Mentor Program through Tuesday, 31 August 2021. The community-nominated selection committee will be responsible for overseeing the mentor selection process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here. Interested community groups should select their respective volunteers and notify deborah.escalera(a)icann.org. ICANN72 Planning NEW: 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 New Public Comment Feature Launches TOMORROW! Step-by-Step Public Comment Submission Guidelines Zoom Replay: Public Comment Submission Training Zoom Replay: Public Comment User Experience Demonstration Volume 3, Issue 64 | Archive | Next Issue: Thursday, 2 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

Board Report for adoption by the ccNSO Coucil
by Bart Boswinkel Aug. 30, 2021

Aug. 30, 2021

Dear Alejandra, Please find included the Board Report for adoption by the ccNSO Council. The Board report contains per requirements of Annex B: * The Result of the members vote * The ccNSO Recommendation, following the vote by the Members of the ccNSO * The Final Report, which contains the proposed policy process for retirement of ccTLDs After adoption of the Board report it needs to be submitted to the ICANN Board of Directors for consideration by the Board. Kind regards, Bart Boswinkel Issue Manager ccPDP3 Retirement of ccTLDs

1 0

Re: [ccnso-council] [ccnso-members] Proposed Amendment Article 10 (ccNSO) Bylaws
by Alejandra Reynoso Aug. 27, 2021

Aug. 27, 2021

Dear Eberhard Thank you for your message and proposed text. I will include it in my communication with ICANN Legal In the proposed Bylaw amendment it says "For purposes of this Article 10, a “ccTLD manager” is the organization or entity responsible for managing *a ccTLD according to and under the current heading “Delegation Record” in the Root Zone Database*, or under any later modification, for that country-code top-level domain." Does it address your concern regarding the association of a ccTLD with a country? If not, what wording would you suggest? Please note that the ccNSO Council mailing list is added in copy. Best regards, Alejandra -- [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 On Fri, Aug 27, 2021 at 10:24 AM Dr Eberhard W Lisse via Ccnso-members < ccnso-members(a)icann.org> wrote: > I fully agree with Patricio, and would not be able to vote in favour of > this Bylaw change. > > As he wrote, the easy part first: > > From the Standard itself: > > The ISO 3166 series provides universally applicable > coded representations of names of countries (current and > non-current), dependencies, and other areas of > particular geopolitical interest and their subdivisions. > > ISO 3166-1 establishes codes that represent the current > names of countries, dependencies, and other areas of > particular geopolitical interest, on the basis of > country names obtained from the United Nations. > > ISO 3166-2 establishes a code that represents the names > of the principal administrative divisions, or similar > areas, of the countries and entities included in ISO > 3166-1. > > ISO 3166-3 establishes a code that represents non- > current country names, i.e. the country names deleted > from ISO 3166 since its first publication in 1974. > > The ISO 3166 series do not express any opinion > whatsoever concerning the legal status of any country, > dependency, or other area named herein, or concerning > its frontiers or boundaries. > > And hence I would refine Patricio's proposal to 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. > > However, I will also not be able to vote in favor of Bylaw change > that creates (even) the hint of an impression of a linkage between a > country (itself) and a ccTLD. > > ccTLDs are NAMED after 2 letter codes representing the NAME(S) of > countries, they have no other (intrinsic) relationship with > countries themselves, per se, or as far as ICANN is concerned. > > Please forward to the Council list. > > greetings, el > > > On 2021-08-27 17:44 , Alejandra Reynoso via Ccnso-members wrote: > > Dear Patricio > > > > Thank you very much for your comment and feedback. I will forward > > your concern to ICANN Legal. > > > > Additionally, I want to take this opportunity to remind everyone that > > later in the bylaw change process there will be a public comment > > period, where you are welcome to participate. > > > > Best regards, > > Alejandra > [...] > > On Fri, Aug 20, 2021 at 10:30 AM Patricio Poblete via Ccnso-members > > <ccnso-members(a)icann.org> wrote: > > > > Hello all, > > > > Some comments, speaking exclusively as a ccTLD administrator. > > > > First the easy stuff: in (e) (iii), change "manger" to "manager" > > > > Now, the main point. 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,...' > > > > Thanks for your attention, > > > > Patricio > [...] > > -- > Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist > el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell) > PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP > 10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply > Book your Covid-10 Vaccination at https://c19.idtoday.com.na > _______________________________________________ > Ccnso-members mailing list > Ccnso-members(a)icann.org > https://mm.icann.org/mailman/listinfo/ccnso-members > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on.

1 0

Re: [ccnso-council] [ccnso-members] Proposed Amendment Article 10 (ccNSO) Bylaws
by Alejandra Reynoso Aug. 27, 2021

Aug. 27, 2021

Dear Patricio Thank you very much for your comment and feedback. I will forward your concern to ICANN Legal. Additionally, I want to take this opportunity to remind everyone that later in the bylaw change process there will be a public comment period, where you are welcome to participate. Best regards, Alejandra -- [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 On Fri, Aug 20, 2021 at 10:30 AM Patricio Poblete via Ccnso-members < ccnso-members(a)icann.org> wrote: > Hello all, > > Some comments, speaking exclusively as a ccTLD administrator. > > First the easy stuff: in (e) (iii), change "manger" to "manager" > > Now, the main point. 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,...' > > Thanks for your attention, > > Patricio > > On Fri, Aug 20, 2021 at 5:48 AM Bart Boswinkel via Ccnso-members < > ccnso-members(a)icann.org> wrote: > >> Dear all, >> >> As you may recall, the ccNSO requested a change of Article 10 and Annex B >> of the ICANN Bylaws to enable IDNccTLD Managers to become members of the >> ccNSO. Recently ICANN legal raised some additional questions and >> suggested some further changes to the proposed Bylaw changes. The proposed >> changes are included in the redlined document and listed at the end of this >> email. The ccnSO Council had no issues with the further changes (Council >> was consulted from 13-19 August). As a next step you are asked, whether >> you have any concerns / comments regarding the latest proposed changes to >> Article 10 and Annex B. The proposed changes are listed at the end of this >> email and included in the attached document. If so please mail them to the >> membership list by Friday *27 August 2021, noon UTC. * >> >> >> >> Kind regards, >> >> Bart Boswinkel >> >> ccNSO support staff >> >> >> >> >> >> *Background.* >> >> The change request of Article 10 and Annex B is the result of an >> extensive consultation of the ccNSO members. It started with the second >> ccNSO Policy Development Process on IDNccTLDs, which was adopted by the >> membership in 2013. Additional community consultations took place in >> October 2019 on separating the Bylaw change effort and the launch of the 4 >> th ccNSO PDP on the selection of IDNccTLD strings and finally as part of >> the ccNSO Statement process on the proposed changes of Article 10 and Annex >> B ( https://ccnso.icann.org/en/about/ccnso-to-icann-legal-18feb21-en.pdf) >> . >> >> >> >> Recently ICANN legal provided a response to the ccNSO Statement on the >> proposed changes to Article 10 of the ICANN Bylaws. ICANN legal had some >> questions and suggested some additional changes. The proposed changes are >> included in the redlined document and listed at the end of this email. >> >> >> >> Recently the drafting team that prepared the ccNSO Statement has reviewed >> the additional proposals and had no comments nor did the ccNSO Council when >> they were consulted from 13- 19 August 2021 on the proposed changes. As a >> next step you are asked, whether you have any concerns/comments regarding >> the latest proposed changes to Article 10 and Annex B. >> >> >> >> If there are no major concerns from your end, the consultation will be >> closed and ICANN informed that the ccNSO supports the amendment of Article >> 10 and Annex B as proposed. >> >> >> >> >> >> *T**he **additional **proposed amendments to **Article 10 and Annex B of >> **the Bylaws**.* >> >> >> >> *Article 10 * >> >> >> >> - Section 10.4 (a) – changed “variant” to “modification” since >> variant has a special meaning in this context. Let me know if this works. >> - Section 10.4(i) – added the concept of plurality. Now, the rule >> would be that the a majority of the Emissaries entitled to vote in a >> Geographic Region is needed for quorum, and a candidate must receive a >> plurality of votes cast by the Emissaries within the Geographic Region to >> win. >> >> >> >> In addition the drafting teams suggests to change the heading of Article >> 10. 4.e. The suggestion is to strike “and Territory” from the heading: “ *Designation >> of Representative and Territory* “. The section is about the designation >> of the ccTLD Representative. >> >> >> >> *Annex B* >> >> - Section 1.a. – Changed “affirmative vote of” to “documentation of >> support from” so as not to confuse the issue about voting on requesting an >> Issue Report. >> - Section 1.e. – Changed the language regarding requesting an Issue >> Report by the members of the ccNSO. The language now reads, “At least >> ten members of the ccNSO from at least ten different Territories may call >> for the creation of an Issue Report at any meeting or by electronic means.” >> - Section 1, last paragraph – Deleted the following phrase from the >> last paragraph of Section 1 so as to not confuse the issue about voting on >> requesting an Issue Report: “Any request for an Issue Report must be in >> writing and must set out the issue upon which an Issue Report is requested >> in sufficient detail to enable the Issue Report to be prepared. It shall be >> open to the Council to request further information or undertake further >> research or investigation for the purpose of determining whether or >> not the requested Issue Report should be created.” This final >> sentence creates ambiguity. >> - Section 2, 1st paragraph – changed the time from 7 days to 14 days >> for when the Council is required to appoint an Issue Manager after receipt >> of a request for an Issue Report. Also, deleted the references to the Item >> 1 sub-points since the timing requirement will apply to all of Item 1. >> - Section 3.a – changed “e-mail” to “electronic means” >> - Section 4 – changed “e-mail” to “electronic means” >> - Section 7.b. – changed “e-mail” to “electronic means” >> >> >> >> >> >> Although out of scope, the drafting team re-iterated the need to discuss >> the issue pertaining to a single entity organization managing multiple >> ccTLD related to different Territories and their ability to cast multiple >> votes. This was already raised as an issue when they drafted the ccNSO >> position, but brought to the attention of the Council again. >> >> >> >> >> >> >> _______________________________________________ >> Ccnso-members mailing list >> Ccnso-members(a)icann.org >> https://mm.icann.org/mailman/listinfo/ccnso-members >> _______________________________________________ >> By submitting your personal data, you consent to the processing of your >> personal data for purposes of subscribing to this mailing list accordance >> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and >> the website Terms of Service (https://www.icann.org/privacy/tos) You >> can visit the Mailman link above to change your membership status or >> configuration, including unsubscribing, setting digest-style delivery or >> disabling delivery altogether (e.g., for a vacation), and so on. > > _______________________________________________ > Ccnso-members mailing list > Ccnso-members(a)icann.org > https://mm.icann.org/mailman/listinfo/ccnso-members > _______________________________________________ > By submitting your personal data, you consent to the processing of your > personal data for purposes of subscribing to this mailing list accordance > with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and > the website Terms of Service (https://www.icann.org/privacy/tos) You can > visit the Mailman link above to change your membership status or > configuration, including unsubscribing, setting digest-style delivery or > disabling delivery altogether (e.g., for a vacation), and so on.

1 0

CALL FOR VOLUNTEERS: Customer Standing Committee Effectiveness Review team
by Kimberly Carlson Aug. 27, 2021

Aug. 27, 2021

27 August 2021 In accordance with the Guideline: ccNSO Appointment Procedures<https://ccnso.icann.org/sites/default/files/field-attached/guidelines-ccnso…>, the ccNSO Council is now looking for two (2) volunteers to serve on the second Customer Standing Committee Effectiveness Review team on behalf of the ccNSO. This call for volunteers opens Friday, 27 August 2021 and closes Friday 10 September 2021 (23:59 UTC). How to apply? You are required to be associated with a ccTLD manager. If you are interested in serving in this position, send an email to Kimberly.Carlson(a)icann.org<mailto:Kimberly.Carlson@icann.org>. Please include a motivation letter explaining why you wish to serve on the Effectiveness team and how you meet the candidate requirements below. 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…>) The second CSC Effectiveness Review Section 17.3 (b) of the ICANN Bylaws and the Charter of the Customer Standing Committee (hereafter: CSC) require that the “… effectiveness of the CSC will initially be reviewed two years after the first meeting of the CSC; and then every three years thereafter. The method of review will be determined by the ccNSO and GNSO.” The CSC was established in October 2016 and conducted its first meeting on 6 October 2016. In October 2018, the first review of the CSC Effectiveness Review was kicked-off, and was concluded in March 2019, with adoption of the Final CSC Effectiveness Review Report by the ccNSO and GNSO Councils. The CSC Effectiveness Review is intended to consider the Effectiveness of the CSC in carrying out its mission as defined in the Charter of the CSC. The Review Team The ccNSO and GNSO will each appoint two members to CSC Review Team, in accordance with their internal processes. At least one member appointed by the ccNSO Council and one member appointed by the GNSO Council should be related to or associated with a TLD Operator (direct customer of the IANA Naming Function). Time Commitment As member you should be able to join the regular teleconferences. Note that the committee's workload usually increases significantly around the time reports need to be drafted (two: the Interim Report and Final Report) . As member you are also expected to participate actively in the consultations of interested stakeholder group. The Review Team is expected to deliver its final report by April 2022.

1 0

Thursday, 26 August 2021 | ENDS TODAY: Public Comment - Proposal for Greek Root Zone Label Generation Rules
by ICANN Community Leadership Digest Aug. 26, 2021

Aug. 26, 2021

Thursday, 26 August 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 Information Sharing NEW: Results of the Audit on Registrars' Compliance with DNS Abuse Obligations NEXT WEEK: Nominations for NextGen@ICANN Mentor Positions Public Comment Step-by-Step Public Comment Submission Guidelines Zoom Replay: Public Comment Submission Training Zoom Replay: Public Comment User Experience Demonstration 🚨🚨ENDS TODAY: Proposal for Greek Root Zone Label Generation Rules Publications NEW: OCTO-027: Hyperlocal Root Zone Technical Analysis Information Sharing NEW: Results of the Audit on Registrars' Compliance with DNS Abuse Obligations ICANN Contractual Compliance has completed its audit of registrars’ compliance with the Registrar Accreditation Agreement (RAA) requirements related to the mitigation of Domain Name System (DNS) abuse. The report summarizes the methodology and the results of the audit of 126 registrars who in aggregate manage over 90% of all registered generic second-level domain names. Read more. NEXT WEEK: Nominations for NextGen@ICANN Mentor Positions The NextGen@ICANN Program seeks nominations for its Mentor Program through Tuesday, 31 August 2021. The community-nominated selection committee will be responsible for overseeing the mentor selection process. Communities may choose to appoint program alumni and are encouraged to appoint active community members who have an interest in mentoring students. Guidelines for the program can be found here. Interested community groups should select their respective volunteers and notify deborah.escalera(a)icann.org. New Public Comment Feature Launches 31 August! Step-by-Step Public Comment Submission Guidelines Zoom Replay: Public Comment Submission Training Zoom Replay: Public Comment User Experience Demonstration 🚨🚨 ENDS TODAY: Proposal for Greek Root Zone Label Generation Rules Close Date: Thursday, 26 Aug 2021 Publications NEW: OCTO-027: Hyperlocal Root Zone Technical Analysis Volume 3, Issue 63 | Archive | Next Issue: Monday, 30 August 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] [ccnso-members] About the Rules webinar tomorrow
by Kimberly Carlson Aug. 26, 2021

Aug. 26, 2021

Dear ccNSO Members, Please find the webinar details below: * Date: Thursday, 26 August 2021 * Time: 12:00 UTC (for other times<https://www.timeanddate.com/worldclock/fixedtime.html?msg=GRC+SG+Webinar+on…>) * Zoom Meeting: https://icann.zoom.us/j/92071930729?pwd=dzhDQjh5R3BvU1pyZW1UQmgxNHpIQT09 | Meeting ID: 920 7193 0729 | Passcode: ccNSO-0826 The July survey results are attached, as well as the Headings document that will be reference during tomorrow’s webinar. Thank you, Kim From: Ccnso-members <ccnso-members-bounces(a)icann.org> on behalf of "McAuley, David via Ccnso-members" <ccnso-members(a)icann.org> Reply-To: "McAuley, David" <dmcauley(a)verisign.com> Date: Wednesday, August 25, 2021 at 5:22 AM To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org> Subject: [ccnso-members] About the Rules webinar tomorrow Dear ccNSO members, Please join us this Thursday, August 26, at 12:00 UTC for a presentation on the work of the Guideline Review Committee’s Subgroup on the ccNSO Rules. We will present our draft on revised rules and will be seeking your comments as we endeavor to put the draft into final form for review at ICANN72. You will soon be receiving certain materials relating to the webinar: * A document that we in the subgroup refer to as the ‘Headings’ document – it will show proposed text for new rules along with relevant old text provisions – this is the primary document we will be using; * A set of slides that we intend to use at the webinar. We will begin the webinar with a brief introduction from ccNSO Council Chair (and subgroup member), Alejandra Reynoso. Then we will turn to a very brief review of results from our survey among membership earlier this summer. We will then turn to the draft rules. Some of the sections we will refer to in summary form and others – on the decision-making roles of members and Council; on voting; and on thresholds/quorums – we will actually read our current draft (it is not too long) to ensure good focus. A few preliminary observations: * While we will do some polling, there will be several options to choose from, this webinar will NOT involve a vote on new rules. The subgroup is hoping for feedback as we get words on paper. Know that no new rule will be adopted that is not noticed, voted upon, and approved in accordance with the current rule – which you can see at https://ccnso.icann.org/en/about/rules.htm [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/rules.htm__;!!P…>. (See Section 8 – Changes to the Rules.) * The webinar will be recorded in case you cannot attend the event or if you wish to go back later and re-listen to a part of it. We also invite feedback on list. Please encourage your ccNSO member contacts to weigh in as well – this is an important moment for the governance of the ccNSO and we hope for as much engagement and feedback as possible. Thank you all, I hope to see you there. David McAuley Subgroup Chair David McAuley Sr International Policy & Business Development Manager Verisign Inc. 703-948-4154

1 1