September 2021 - Ccnso-council

Re: [ccnso-council] Dropped off the list?
by Alejandra Reynoso Sept. 24, 2021

Sept. 24, 2021

Hi Sebastien The ccNSO council mailing list has been quite active recently, so it is indeed strange that you haven't seen any emails from it. It must be as you say and your email could be outdated. Could Joke or Kim please have a look into this? Regarding the gNSO joint session, I haven't heard back from Philippe yet, but I am on the understanding that the meeting has been confirmed administratively (date and time). I was planning on writing an email to Philippe as a follow up, to confirm the topics and agenda; unless you want to reach to him first. Thank you for keeping in touch. 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 Thu, Sep 23, 2021 at 8:34 AM Sebastien(a)registry.godaddy <Sebastien(a)registry.godaddy> wrote: > Dear Alejandra and Joke, > > > > Back from a few needed days away from my desk, and preparing for my future > ICANN commitments I realise that the ccnso-council list has been awfully > quiet in my inbox. > > > > 6 weeks ago, I lost access to my Neustar email (a year after our group > left the company it was time to cut the cord) and it feels that coinciding > with the council’s own summer break, it is around that time that I lost my > connection to the council list. > > > > Could you kindly check that I am indeed listed as > sebastien(a)registry.godaddy and not under any variation of Neustar or ARI > Services? > > > > Alejandra, I do acknowledge your email from 24 August, and as it looks > like no one answered (how rude!) I’ll chase Philippe and Maarten on setting > time up. > > > > Kindly, > > > > > > *Sebastien Ducos* > > GoDaddy Registry | Senior Client Services Manager > > [image: signature_2099404703] > > +33612284445 > > +61449623491 > > Level 8, 10 Queens Road > > Melbourne, VIC, Australia > > 3004 > > sebastien(a)registry.godaddy > > www.linkedin.com/in/sebastienducos > > >

2 1

Termination ccNSO membership
by Joke Braeken Sept. 24, 2021

Sept. 24, 2021

Dear Councillors, Please find below a draft resolution, presented to you for an online decision. Kindly provide me with your input by the end of Monday, 27 September 2021, 23:59 UTC, in case you do not agree with the proposed resolution. Termination ccNSO membership For decision End of ccNSO membership of . S.E. MOLDDATA Background Following a recent transfer of the .md ccTLD to a new TLD manager, there is a discrepancy between the data of the ccTLD manager in the IANA delegation record and the ccTLD manager data as included in the ccNSO member database. Draft Resolution The ccNSO Council concludes that the ccNSO membership of S.E. MOLDDATA has ended after completion of the transfer process of .md to IP Serviciul Tehnologia Informatiei si Securitate Cibernetica The secretariat is requested to take all necessary steps to inform MOLDDATA. on behalf of Council about this decision, and to remove references to MOLDDATA as .md ccTLD manager from the ccNSO website and membership records, including removing email addresses from the ccNSO members mailing lists where needed. This resolution becomes effective seven (7) days after publication on the ccNSO Website. Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

10 9

Online decision: Appointment Vice Chair MPC
by Joke Braeken Sept. 23, 2021

Sept. 23, 2021

Dear Councillors, Please find below a draft resolution, presented to you for an online decision. Kindly provide me with your input by the end of Thursday, 23 September 2021, 23:59 UTC, in case you do not agree with the proposed resolution. Appointment Vice Chair MPC For decision: formal appointment Vice Chair ccNSO Meetings Programme Committee (MPC) Following a call for nominations and a selection procedure, the MPC members selected Gudrun Poulsen (.fo) as their preferred candidate for the role of MPC Vice Chair. Draft Resolution The ccNSO Council approves appoints Gudrun Poulsen as ccNSO Meetings Programme Committee Vice Chair. The secretariat is requested to take all other necessary steps to include Gudrun as MPC Vice Chair. Thank you. Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

2 1

Re: [ccnso-council] Termination ccNSO membership
by Stephen Deerhake ＠ ASNIC Sept. 23, 2021

Sept. 23, 2021

Might I propose some alternative language that is somewhat less harsh? Termination ccNSO membership For decision End of ccNSO membership of . S.E. MOLDDATA Background Following a recent transfer of the .md ccTLD to a new TLD manager, there is a discrepancy between the data of the ccTLD manager in the IANA delegation record and the ccTLD manager data as included in the ccNSO member database. Draft Resolution The ccNSO Council has determined, after the transfer of the delegation of the .md ccTLD (Moldavia) from S.E. MOLDDATA to IP Serviciul Tehnologia Informatiel si Securitate Cibernetica, that the membership of S.E. MOLDDATA in the ccNSO has concluded. Further, the ccNSO Council directs the ccNSO Secretariat to take the appropriate steps to wind down S.E. MOLDDATA’s presence in ccNSO affairs, including mailing lists, etc. Lastly, the ccNSO Council directs the Council Chair to reach out to the new delegee of .md, IP Serviciul Tehnologia Informatiel si Securitate Cibernetica, to encourage them to continue .md’s presence within the ccNSO by applying for ccNSO membership. Best Regards, /Stephen From: Ccnso-council <ccnso-council-bounces(a)icann.org> on behalf of Joke Braeken via Ccnso-council <ccnso-council(a)icann.org> Reply-To: Joke Braeken <joke.braeken(a)icann.org> Date: Thursday, September 23, 2021 at 11:52 To: ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-council] Termination ccNSO membership Dear Councillors, Please find below a draft resolution, presented to you for an online decision. Kindly provide me with your input by the end of Monday, 27 September 2021, 23:59 UTC, in case you do not agree with the proposed resolution. Termination ccNSO membership For decision End of ccNSO membership of . S.E. MOLDDATA Background Following a recent transfer of the .md ccTLD to a new TLD manager, there is a discrepancy between the data of the ccTLD manager in the IANA delegation record and the ccTLD manager data as included in the ccNSO member database. Draft Resolution The ccNSO Council concludes that the ccNSO membership of S.E. MOLDDATA has ended after completion of the transfer process of .md to IP Serviciul Tehnologia Informatiei si Securitate Cibernetica The secretariat is requested to take all necessary steps to inform MOLDDATA. on behalf of Council about this decision, and to remove references to MOLDDATA as .md ccTLD manager from the ccNSO website and membership records, including removing email addresses from the ccNSO members mailing lists where needed. This resolution becomes effective seven (7) days after publication on the ccNSO Website. Thank you. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0

Thursday, 23 September 2021 | Join the SSAD ODP Update Webinar
by ICANN Community Digest Sept. 23, 2021

Sept. 23, 2021

Thursday, 23 September 2021 ICANN Community 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 TOMORROW: Register Now for the SSAD ODP Update Webinar NEXT WEEK: Register Now for the Subsequent Procedures ODP Update Webinar Information Sharing NEW: Chair's Blog: September Board Workshop Recap REMINDER: NextGen@ICANN Application Round for ICANN73 Now Open REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Public Comment REMINDER: Draft PTI and IANA FY23 Operating Plan and Budgets REMINDER: Initial Report from the EPDP on Specific Curative Rights Protection for IGOs REMINDER: Proposed Amendment 5 to the .name Registry Agreement REMINDER: ICANN Launches Improved Public Comment Feature Webinars TOMORROW: Register Now for the SSAD ODP Update Webinar ICANN invites the community to join a follow-up webinar on the System for Standardized Access/Disclosure (SSAD) Operational Design Phase (ODP) on Friday, 24 September 2021 at 03:00 UTC (Thursday, 23 September 2021 at 20:00 PDT). Please register in advance for details on how to join the webinar. The webinar will provide a status report on the progress made during the ODP and share additional details about when the Operational Design Assessment (ODA) is expected to be delivered to the ICANN Board. It will also include a general discussion of the ODP moving forward and lessons learned. The webinar will be presented in English with interpretation in Arabic, Chinese, French, Russian, and Spanish. Video and audio recordings will be published on the SSAD ODP webpage. NEXT WEEK: Register Now for the Subsequent Procedures ODP Update Webinar ICANN org will host a webinar on Tuesday, 28 September 2021 at 20:00 UTC (local time) to provide an update on the New Generic Top-Level Domain (gTLD) Subsequent Procedures Policy Development Process (SubPro) Operational Design Phase (ODP). The webinar will give an overview of the scope and timeline of the ODP. It will also include a general overview of the ICANN org ODP process followed by a question and answer segment. Read more. Please register in advance for details on how to join the webinar. Information Sharing NEW: Chair's Blog: September Board Workshop Recap The ICANN Board recently finished four productive days where it considered a variety of topics and issues impacting ICANN today and in the future. As I explained in my pre-workshop blog, the pandemic has required us to continue to adapt our ways of working together. With thanks to our virtual tools, support from across the ICANN ecosystem, and a good deal of equanimity from my colleagues, the Board is pressing forward with its important work and delivering on ICANN's mission. Read more. REMINDER: NextGen@ICANN Application Round for ICANN73 Now Open Applications for the NextGen@ICANN program at ICANN73 are now being accepted. The deadline for applications is Monday, 25 October 2021. Read more. REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested ICANN community members must apply in advance of ICANN72, and those who meet the eligibility requirements will be selected to participate. The application deadline is Friday, 08 October 2021 at 23:59 UTC. The application process opens today, and program details are available here. The goal of this program is to facilitate participation in ICANN Public Meetings during the pandemic. It offers community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Read more. Public Comment REMINDER: Draft PTI and IANA FY23 Operating Plan and Budgets Open for Submissions Date: Wednesday, 15 September 2021 Closed for Submissions Date: Monday, 25 October 2021 REMINDER: Initial Report from the EPDP on Specific Curative Rights Protections for IGOs Open for Submissions Date: Tuesday, 14 September 2021 Closed for Submissions Date: Sunday, 24 October 2021 REMINDER: Proposed Amendment 5 to the .name Registry Agreement Open for Submissions Date: Friday, 10 September 2021 Closed for Submissions Date: Wednesday, 20 October 2021 REMINDER: 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! 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 70 | Archive | Next Issue: Monday, 27 September 2021 STAY INFORMED: Subscribe here 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] Proposed Amendment Article 10 (ccNSO) Bylaws
by Alejandra Reynoso Sept. 22, 2021

Sept. 22, 2021

Dear Patricio This topic will be raised today at the council call. 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 Thu, Sep 16, 2021 at 6:48 AM Patricio Poblete <ppoblete(a)nic.cl> wrote: > Dear Alejandra, > > I would like to know about the conclusion of this discussion, and whether > the word "country" is still being deprecated and replace by "territory" in > the proposed amendment to the bylaws. > > Patricio > > On Fri, Aug 27, 2021, 11:45 Alejandra Reynoso <alejandra.reynoso(a)cctld.gt> > 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 >> >> >> -- >> >> [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. >> >>

2 3

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

Sept. 22, 2021

Dear Patricio In our recent phone call, we reviewed the milestones of this process, and confirmed that: 1) From April to June 2019 the ccPDP2 was reviewed by a ccNSO working group, who recommended to split ccPDP2 into a Bylaw change and formal review of the proposed policy to select IDNccTDLstrings (which is now ccPDP4); 2) further consultations with the community were made in 2019 & 2020 when the definition and use of the term were explicitly discussed and nobody objected; 3) the Bylaw change was submitted to the ICANN Board in March 2020; 4) ICANN legal raised some editorial questions that were reviewed by a drafting team and finally, 5) the term and definition were further presented under the ccPDP4 context at ICANN71 when the polling resulted in support of the definition. We were in agreement that due process was followed and that issues with content should have been raised earlier, while friendly disagreeing if the suggested change is just an editorial matter or not. 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, Sep 17, 2021 at 8:47 AM Patricio Poblete <ppoblete(a)nic.cl> wrote: > Dear Alejandra, > > A couple of comments about your report yesterday to the Council. > > While it is true that in 2013 the membership voted to support the ccPDP2 > report (voted twice, actually, as the first vote did not meet the quorum > requirement), no one could say that it was a referendum on terminology > (e.g. "territory" vs. "country"). The real substantive decision was about > the mechanism for participation of IDN CCTLD managers, a decision I voted > for and still fully support. > > As we know, the ccPDP2 process did not go on at the time, and the > innovation in terminology that it attempted to introduce was largely > forgotten. The *Framework of Interpretation* report, adopted the > following year, consistently uses the phrase "country or territory". The > *Retirement* report, approved this year, does not mention the word > "territory" at all. In that, it is consistent with *RFC1591*. > > When reactivating the work suspended in 2013 to amend Article 10 of the > ICANN Bylaws, it is appropriate to reconsider the terminology used, and to > make sure that it is consistent with current practice. It is clear that the > 2013 attempt to introduce "territory" as the accepted word to characterize > country-code TLDs did not get traction, as clearly no later work has > adopted that terminology. > > I agree with your stated position that this is not the time to reconsider > substantive matters, but I believe that changing "territory" to "country or > territory" would be a timely and needed editorial change to make before > these amendments become part of the ICANN Bylaws. > > Patricio > > On Fri, Aug 27, 2021 at 11:45 AM Alejandra Reynoso < > alejandra.reynoso(a)cctld.gt> 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 >> >> >> -- >> >> [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

Reminder | Call for nominations to the ccNSO Council
by Joke Braeken Sept. 22, 2021

Sept. 22, 2021

Dear All, This is a reminder about the ongoing call for nominations to the ccNSO Council: the nomination and secondment procedure closes Wednesday, 6 October 2021 (23:59 UTC). All materials related to this Council Election, including instructions on how to nominate or second candidates, have been posted here: https://ccnso.icann.org/en/about/elections/council.htm Here is the archive for nominations and secondments: http://forum.icann.org/lists/ccnso-nominations Below is a short summary of the status per region: REGION Has at least one candidate been nominated? Seconding received? ASIA-PACIFIC Y Y LAC Y N NORTH AMERICA Y Y EUROPE Y Y AFRICA N N Best regards, 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: Tuesday, 14 September 2021 at 08:35 To: "ccnso-members(a)icann.org" <ccnso-members(a)icann.org>, ccnso-council <ccnso-council(a)icann.org> Subject: [ccnso-members] Call for nominations to the ccNSO Council starts 15 September Dear All, The 3-year term for five members of the ccNSO Council will end in March 2022, at the conclusion of the ICANN73 Community Forum: * Africa: Biyi Oladipo * Asia Pacific: Jordan Carter * Europe: Nick-Wenban Smith * Latin America/Caribbean: Demi Getschko * North America: Pablo Rodriguez The ccNSO is opening a call for nominations to fill those seats: the nomination and secondment procedure starts Wednesday, 15 September 2021 (00:01 UTC) and closes 3 weeks later Wednesday, 6 October 2021 (23:59 UTC). All materials related to this Council Election will be posted here: https://ccnso.icann.org/en/about/elections/council.htm [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/about/elections/counc…> The ICANN Bylaws, Article 10 – Section 10.4 (g)<https://www.icann.org/resources/pages/governance/bylaws-en/#article10> state: "(g) The ccNSO Council members selected by the ccNSO members from each Geographic Region (see Section 10.3(a)(i)) shall be selected through nomination, and if necessary, election, by the ccNSO members within that Geographic Region. At least 90 days before the end of the regular term of any ccNSO-member-selected member of the ccNSO Council, or upon the occurrence of a vacancy in the seat of such a ccNSO Council member, the ccNSO Council shall establish a nomination and election schedule, which shall be sent to all ccNSO members within the Geographic Region and posted on the Website." How to nominate and second a candidate Timeline The nomination and secondment procedure starts Wednesday, 15 September 2021 (00:01 UTC) and closes 3 weeks later Wednesday, 6 October 2021 (23:59 UTC). Who can nominate or second? The ICANN Bylaws, Article 10 – Section 10.4 (h)<https://www.icann.org/resources/pages/governance/bylaws-en/#article10> state: "(h) Any ccNSO member may nominate an individual to serve as a ccNSO Council member representing the ccNSO member's Geographic Region. Nominations must be seconded by another ccNSO member from the same Geographic Region. By accepting their nomination, individuals nominated to the ccNSO Council agree to support the policies committed to by ccNSO members." As per the relevant ccNSO guideline [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/fiel…>, new ccNSO members are able to participate in the nomination process if the ccNSO membership application has been approved by the ccNSO Council one day prior the nomination process starts, i.e. latest on 14 September 2021. Self-nominations As per the relevant ccNSO guideline [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/fiel…>, ccNSO members may self-nominate themselves, but are not allowed to second their nomination. Self-nominations must be seconded by two ccNSO members from the region. Instructions Nominations and secondments should be sent by e-mail to the Election Manager at the following e-mail address: ccnso-nominations(a)icann.org<mailto:ccnso-nominations@icann.org>. Templates for nominating and seconding nominations are provided below. You are kindly invited to follow these instructions closely, and not to use alternative templates. Template for nominations: NOMINATION TO THE CCNSO COUNCIL 1. Your full name: 2. Your e-mail address: 3. Your ccTLD: 4. Your geographic region: 5. Full name of the person you nominate to the ccNSO council: 6. e-mail address of the person you nominate: Template for seconding nominations: SECONDING A NOMINATION TO THE CCNSO COUNCIL 1. Your full name 2. Your e-mail address: 3. Your ccTLD: 4. Your geographic region: 5. Full name of the nominee you would like to second: Archive for nominations and secondments: http://forum.icann.org/lists/ccnso-nominations [forum.icann.org]<https://urldefense.com/v3/__http:/forum.icann.org/lists/ccnso-nominations__…> Eligibility requirements to be elected to the ccNSO Council A Councillor can be any individual nominated, seconded and elected as described in the ccNSO Council Election Guideline [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/fiel…>. Individuals are elected in their personal capacity and serve the ccTLD community. Councillors do not represent the views and interests of their employers. Candidates need to be neither resident in the region, nor a citizen of a country, within the region in which they stand for election. A valid candidate is one that has been nominated and seconded according to the ccNSO council Election Guideline, and that has accepted the nomination. If there is more than one valid candidate in a Geographical Region, an election shall be conducted in that region. Voting will be by secret ballot: the ballot is identified only by a code and not by a name. During a Council Election Webinar (16 September 2021, noon UTC), the ccNSO Chair and other Councillors give an overview of the election process and address the need to replace Councillors at reasonable and regular intervals. Moreover, they provide further information about the required skill sets for Councillors, the time commitment and working methods of the ccNSO Council. Consult the webinar recording<https://community.icann.org/display/ccnsowkspc/ccNSO+Webinars> here. Accepting nominations After closure of the nomination period, the Election Manager will ask the candidates that are nominated to accept their nomination. Self-nominations are understood to have accepted their nomination. The Election Manager will provide a list with the name(s) of the candidate(s) who have accepted their nomination. A record of who has nominated and seconded the candidate(s) is publicly available: http://forum.icann.org/lists/ccnso-nominations [forum.icann.org]<https://urldefense.com/v3/__http:/forum.icann.org/lists/ccnso-nominations__…> Next steps The Election Manager will ask the candidates to provide a written candidate statement. A Question and Answer session with the candidate(s) will be held at ICANN72 in October. The session is tentatively scheduled for Tuesday, 26 October 2021 (16:00-17:00 UTC). The draft ICANN72 ccNSO Members Meeting schedule is published here: https://community.icann.org/x/hAEuCg In preparation of the Q&A session, the written candidate statements will be posted on the ccNSO website. The Q&A session gives the ccNSO members and broader ccTLD community an opportunity to interact with the candidates. If at the close of nominations there are no more valid candidates in a particular geographic region than there are seats on the ccNSO Council available for that geographic region, then the nominated candidates shall be selected to serve on the ccNSO Council. Otherwise, an election shall be held for that geographic region, to select the ccNSO Councillors from among the valid candidates. Links * Archive for nominations and secondments<https://mm.icann.org/pipermail/ccnso-nominations/> * Relevant ccNSO guideline [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/sites/default/files/fiel…> * Timeline [ccnso.icann.org]<https://urldefense.com/v3/__https:/ccnso.icann.org/en/workinggroups/timelin…> * ccNSO Council Election Webinar: recording<https://community.icann.org/display/ccnsowkspc/ccNSO+Webinars> Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0

Monday, 20 September 2021 | THIS WEEK: SSAD ODP Webinar
by ICANN Community Digest Sept. 20, 2021

Sept. 20, 2021

Monday, 20 September 2021 ICANN Community 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 THIS WEEK: Register Now for the SSAD ODP Update Webinar REMINDER: Register Now for the Subsequent Procedures ODP Update Webinar Information Sharing NEW: NextGen@ICANN Application Round for ICANN73 Now Open NEW: ICANN Publishes FY21 Financial Results REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Public Comment REMINDER: Draft PTI and IANA FY23 Operating Plan and Budgets REMINDER: Initial Report from the EPDP on Specific Curative Rights Protection for IGOs REMINDER: Proposed Amendment 5 to the .name Registry Agreement REMINDER: ICANN Launches Improved Public Comment Feature Webinars THIS WEEK: Register Now for the SSAD ODP Update Webinar ICANN invites the community to join a follow-up webinar on the System for Standardized Access/Disclosure (SSAD) Operational Design Phase (ODP) on Friday, 24 September 2021 at 03:00 UTC (Thursday, 23 September 2021 at 20:00 PDT). Please register in advance for details on how to join the webinar. The webinar will provide a status report on the progress made during the ODP and share additional details about when the Operational Design Assessment (ODA) is expected to be delivered to the ICANN Board. It will also include a general discussion of the ODP moving forward and lessons learned. The webinar will be presented in English with interpretation in Arabic, Chinese, French, Russian, and Spanish. Video and audio recordings will be published on the SSAD ODP webpage. REMINDER: Register Now for the Subsequent Procedures ODP Update Webinar ICANN org will host a webinar on Tuesday, 28 September 2021 at 20:00 UTC (local time) to provide an update on the New Generic Top-Level Domain (gTLD) Subsequent Procedures Policy Development Process (SubPro) Operational Design Phase (ODP). The webinar will give an overview of the scope and timeline of the ODP. It will also include a general overview of the ICANN org ODP process followed by a question and answer segment. Read more. Please register in advance for details on how to join the webinar. Information Sharing NEW: NextGen@ICANN Application Round for ICANN73 Now Open Applications for the NextGen@ICANN program at ICANN73 are now being accepted. The deadline for applications is Monday, 25 October 2021. Read more. NEW: ICANN Publishes FY21 Financial Results Today, the Internet Corporation for Assigned Names and Numbers (ICANN) announced its unaudited financial results for the financial year ending 30 June 2021. Additionally, Public Technical Identifiers (PTI) published its unaudited financial results for the financial year ending 30 June 2021. Read more. REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Interested ICANN community members must apply in advance of ICANN72, and those who meet the eligibility requirements will be selected to participate. The application deadline is Friday, 08 October 2021 at 23:59 UTC. The application process opens today, and program details are available here. The goal of this program is to facilitate participation in ICANN Public Meetings during the pandemic. It offers community members who have limited Internet capacity financial assistance to increase their Internet bandwidth. Read more. Public Comment REMINDER: Draft PTI and IANA FY23 Operating Plan and Budgets Open for Submissions Date: Wednesday, 15 September 2021 Closed for Submissions Date: Monday, 25 October 2021 REMINDER: Initial Report from the EPDP on Specific Curative Rights Protections for IGOs Open for Submissions Date: Tuesday, 14 September 2021 Closed for Submissions Date: Sunday, 24 October 2021 REMINDER: Proposed Amendment 5 to the .name Registry Agreement Open for Submissions Date: Friday, 10 September 2021 Closed for Submissions Date: Wednesday, 20 October 2021 REMINDER: 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! 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 69 | Archive | Next Issue: Thursday, 23 September 2021 STAY INFORMED: Subscribe here 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

NOTES | ccNSO Council Meeting 176 | 16 September 2021 (20 UTC)
by Joke Braeken Sept. 16, 2021

Sept. 16, 2021

NOTES | ccNSO Council Meeting 176 | 16 September 2021 (20 UTC) 1. Welcome and roll call Welcome by chair Alejandra 1 apology, this meeting is quorate Materials will be posted here: https://community.icann.org/display/ccNSOCWS/16+September+2021+-+20%3A00+UTC 2. Relevant Correspondence See https://ccnso.icann.org/en/about/statements.htm * ALAC: no joint session during ICANN72 * CSC effectiveness review: see agenda item 12 * letter to ICANN Board, changes to bylaws: see agenda item 9 3. Minutes & Action Items a. Minutes Meeting 175 b. Action items and To-do’s, if any * Tech WG update: No concrete action to date. Stephen will propose a new version of the charter, to be approved by WG in the next 3 weeks, then send to GRC. Will not be completed by ICANN72, but aiming for November timeframe. * Triage: deferred to next Council call 4. Intermeeting Decisions (since 22 July 2021) Item 5-8 Written updates unless special developments Council needs to be aware off and Q&A 5. Update ECA & CSC (written updates) See written summary circulated on mailing list and posted on workspace Questions or comments? none 6. Update WGs taken (written updates) a. IGLC b. SOPC a. GRC b. OISC c. TLD-OPS d. Technical WG e. MPC See written summary circulated on mailing list and posted on workspace OISC: request to update the ccNSO meetings guideline. OISC asks Council to pass on this request to the MPC. Out of scope for the OISC to adjust the guideline. Councillors agree MPC: Council to formally appoint Gudrun Poulsen as MPC Vice Chair. deferred to email decision. 7. Updates ccPDPs (written updates) a. Update ccPDP3 - Review Mechanism b. Update IDN ccPDP4 Questions or comments? none 8. Update liaisons a. Update ALAC Liaison (written update) b. Update GNSO Liaison (written update) Questions or comments? none Item 9 - 17 for discussion during the meeting 9. Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat Chair update 1. meeting with Göran. 1:1 prior to every icann meeting. topics discussed · ICANN73. potentially hybrid. worsening pandemic situation · ccPDP3 · ccnso sessions at ICANN72 · ccNSO membership during pandemic 2. meeting with icann org executives on next steps ccnso website. Small committee of councillors : steering committee. will report on progress 3. Bylaw change progress. Some community members had comments. definition of “territory” from 1 bylaw section to another. The Concern is about the introduction of the term “territory” as a concept to describe the geographic areas to which country codes have been assigned. History & background: · march 2020 bylaw request · definition already in 2020 request · definition supported through ccPDP council and membership decision making process in 2013. · discussed in Montreal at ICANN66. no concerns raised at the time Matter closed. no substantive change of the definition on the fly. that would need a new PDP. matter in the hands of the Board. there will be a public consultation. Alejandra to respond to Patricio and others along the lines of what she explained. Some councillors agreed via green checks in zoom, no objections or concerns raised. Question from Javier on ICANN73. asks about Board decision, and when the decision will be made Alejandra mentioned that no decision has been made yet. Vice chair update by Jordan Progress in the October meeting Vice chair update by Pablo See written update 10. Adoption Board Report ccPDP3 Retirement move? Pablo Second? Jordan Any questions on the resolution? none Stephen thanks all for the support. Resolution approved 11. Update Council elections Joke provides an update on the nomination and secondment process. See https://ccnso.icann.org/en/announcements/announcement-13sep21-en.htm Question by Stephen regarding the nomination which the nominator requested not to publish. transparency reasons? Election Manager will include it in the Election Report. 12. CSC 2nd Effectiveness Review Approval of candidates Review Team All in favour 13. Progress expanded role Triage committee deferred to next meeting 14. ICANN72 Meetings Note: tentative schedule a. ccNSO Council i.Council Prep Meeting: 19 October | 12:00-13:00 UTC ii.Council meeting: 28 October | 1730-1900 UTC b. Bilateral Council meetings i.ccNSO - GNSO: 20 October | 19:00-20:00 UTC ii.ccNSO Joint session with ICANN Board of Directors: 28 October | 1600-1700 UTC proposed topics from ccNSO side: 1. Introduction and explanation of the proposed policy for process on retirement of ccTLDs 2. Thank you Nigel Roberts and giving him opportunity to share his views 3. Other suggestions? none c. ccTLD relevant sessions i.ccNSO webinar for newcomers: Date and time TBC ii.ccTLD news sessions (note: correction times!) ccTLD News #1 - General session: 6 October | 1300-15:00 UTC (new: 2 hour session with break in the middle) ccTLD News #2 - Hot topics Internet Governance: 7 October | 06:00 - 07:30 UTC iii.Tech Day Parts 1, 2 & 3: 25 October | 1600-1700, 1730-1900, 1930-2100 UTC iv.ccNSO Members meetings 1. Governance session: 26 October | 1730-1900 UTC 2. Q&A candidates ccNSO Councillors: 26 October | 1600-1700 UTC 3. ccNSO & DNS Abuse Session Parts 1 &2: 27 October | 2130-0030 UTC v.SOPC session with ICANN org planning team: 26 October | 1930-2100 UTC vi.TLD-OPS session: 28 October | 1930-2100 UTC vii.Plenary session(s) 1. Plenary Session: Moving Forward with the Global Public Interest Framework: 26 October | 2130-2300 UTC 2. Plenary Session: How to Design Inclusive, Equitable Hybrid ICANN Meetings: 27 October | 1730-1900 UTC 15. Council Workshop: ICANN Hybrid Meeting, what are the requirements from a Council perspective? For discussion and input during ICANN72 Plenary Session: How to Design Inclusive, Equitable Hybrid ICANN Meetings: 27 October | 1730-1900 UTC 3-12-3 Game 4 breakout groups: 3 council groups, 1 general group Reporting back from the various groups: 1. Group Katrina / rapporteur Katrina * meetings have always been hybrid. but in the past the remote participants were in the minority. prep work needed. timezone is an important decision * from experience we see that hybrid meetings do not work. experience from what happens currently in offices * what type of work makes sense in a hybrid manner? what needs to be done intersessionally? focus on what you want to achieve * we need good moderators/chairs. staff to watch the remote participants, follow chat etc. additional screens needed around the room. those who are in the room to feel as if they are connecting remotely * social gatherings: not addressed * when should we have hybrid meetings? the when is important! 2. Group Joke / Jordan as rapporteur Brainstorming on yellow post-its. only the green post-its were assessed. * people from regions will be only ones attending. unbalanced attendance * to make hybrid meetings work, video is needed. change set-up. see people speaking when they are remote participants. depends on internet connection. needs to become an option * opportunity to reach out to more stakeholders. translation efforts for ccNSO. high effort, also costs involved 3. Group Claudia / Alejandra as rapporteur quite some time spent on brainstorming, but impact-effort was not completed. * be more selective on what makes it to the agenda * networking in the virtual environment needed. * we should only talk about participants, whether they are remote or not. experience should be the same for all. * if people can have their vaccinations, distancing and facemasks might be seen as a limiting factor. those remote have an advantage 4. Group Bart / Pablo as rapporteur * enough fresh air needed * equal participation * vaccinations required. masks wearing, testing Secretariat to produce a summary of the discussions, potentially to be converted into an action plan. 16. Next Meetings · ICANN72: Thursday, 28 October 2021 | 1730 - 1900 UTC · 18 November 2021 | 1200 UTC · 17 December 2021 | 1800 UTC 17. AOB 18. Closure Thank you. Bye all. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0