- Ccnso-council - lists.icann.org

Join the Virtual ccTLD News Sessions | 6 & 7 October
by Joke Braeken Sept. 29, 2021

Sept. 29, 2021

Dear All, You are invited to participate in the upcoming pre-ICANN72 Virtual ccTLD News Sessions, held on Wednesday, 6 October (starts at 13 UTC) and Thursday, 7 October (starts at 6 UTC). Recordings will become available here<https://community.icann.org/display/ccnsowkspc/ccNSO+Webinars>. Wednesday, 6 October 2021 | 13:00-15:00 UTC ccTLD News Session #1 Join us for the first pre-ICANN72 ccTLD News Session and listen to representatives from ccTLDs across the globe, sharing their experiences with marketing, web accessibility, innovation, online content, security and more! Guðrun Poulsen (.fo), Session Chair PART 1: Marketing • The .ng promo experience | Edith Udeagu (.ng) • If I had a million dollars | Dana Ludviga (.lv) • Promoting .ar web accessibility | Romina Guirardo (.ar) Break PART 2: Policy, Operations & Finance • Launch of 2nd level registrations in .au | Bruce Tonkin (.au) • 3 projects to increase domain name stability & security in .RU/.РФ | Irina Danelia (.ru/.РФ) • ccTLD voluntary financial contributions | ICANN org Finance Join Zoom Meeting https://icann.zoom.us/j/96263352337?pwd=aVJKUlc2N05KVzhXQndQRzllL1ZBdz09 Thursday, 7 October 2021 | 06:00-08:00 UTC ccTLD News Session #2 Internet governance: What are the hot topics and trends across the various regions? How do they impact ccTLDs? Participate in the second ccTLD News Session and find out. This session is jointly organized by the ccNSO Meetings Programme Committee (MPC) and the ccNSO Internet Governance Liaison Committee (IGLC). Annaliese Williams (.au), Session Chair PART 1: Internet Governance • Mandy Carver (ICANN org) • Mary Uduma (African IGF) • Jordan Carter (.nz) Break PART 2: Internet Governance • Peter Koch (.de) • Oscar Robles (LACNIC) • Byron Holland (.ca) Join Zoom Meeting https://icann.zoom.us/j/92846458496?pwd=aVZlSGR5YXFNa09mQlVUMWcwOTRlQT09 Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0

The September 2021 edition of the ccNSO monthly newsletter is out now. (Issue 32)
by Joke Braeken Sept. 29, 2021

Sept. 29, 2021

Dear All, The September 2021 edition of the ccNSO monthly newsletter<https://community.icann.org/display/ccnsowkspc/ccNSO+Newsletter> is out now. Highlights from this month's edition: * Contribute to the ccNSO governance| ccNSO Council call for nominations closes soon * Save the date! Join the ccNSO webinars * Stay informed about the ccNSO Working Groups and Committees * Sneak preview ccNSO Sessions at ICANN72 * Keep your finger on the pulse: Join the ccTLD News sessions on 6 & 7 October * Interview: Meet Gudrun Poulsen, MPC Vice Chair * ccNSO Council highlights You will be able to find this month's edition, the ccNSO Newsletter Archive, and instructions on how to subscribe here: https://community.icann.org/display/ccnsowkspc/ccNSO+Newsletter . Best regards. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

1 0

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

Sept. 27, 2021

Dear Eberhard Sorry for the late response. Like you, almost everyone else, including me, has a day-time job. Thank you for recognizing the professional job of the council. We take our role very seriously and the implementation of a ccPDP is no exception. As I said in my previous emails, all steps have been taken to implement the outcome of the members vote on the ccNSO PDP on the inclusion of IDNccTLDs in the ccNSO. ICANN will conduct a public consultation. You are welcome to raise your points through that process, where they will be considered alongside any other feedback. 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 Wed, Sep 22, 2021 at 11:30 AM Eberhard Lisse via Ccnso-members < ccnso-members(a)icann.org> wrote: > Dear Alejandra, > > I do not believe that Bylaw changes should be made on the fly. Normally it > requires a formal PDP. > > I understand the bylaws not to permit a PDP to be “reviewed” by another > Working Group and to then make “recommendations” not envisioned in the PDP. > > As I wrote before, I can not recall the “further consultation”, as I have > spelled out in my previous email. > > I do not understand the bylaws to permit changes to a Developed Policy to > be made by a “drafting team”. > > I do not recall that this was presented at ICANN 71 in the context we are > considering now, and I really strongly agree with Patricio here. > > > Now 4 very experienced (I hate to say senior :-)-O) ccTLD Managers > (Stephen, Hiro, myself and Patricio (in order of experience)) raise > concerns suggestiong to step back and have another look and your > recommendation is ramming it through on purely formal grounds. > > This is a concern, and might raise issues with regard to corporate > governance under California law. > > But the question is, why would one want to do that? > > Would it not be more transparent to ventilate the issue to its conclusion? > > greetings, el > > > On 22. Sep 2021, 17:28 +0200, Alejandra Reynoso via Ccnso-members < > ccnso-members(a)icann.org>, wrote: > > 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. >>> >>> _______________________________________________ > 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

ccNSO membership : revoke draft resolution
by Joke Braeken Sept. 27, 2021

Sept. 27, 2021

Dear Councillors, Thank you all for your refinements and feedback regarding the draft resolution related to the ccNSO membership of Molddata. I would like to rescind the draft resolution circulated to Council on 23 September at 16 UTC. My email was sent too quickly, especially in light of some additional information I received in the meanwhile from IANA staff. Apologies for the inconvenience. Below I copy-pasted the additional information: This request was determined to be an administrative transfer instead of a full transfer because IP Serviciul Tehnologia Informatiei si Securitate Cibernetica (IP STISC) acquired MoldData through a merger/absorption to consolidate the main governmental IT services into a single institution. During the process, the rights and obligations of MoldData passed onto IP STISC and all of the technical staff and user support staff were transferred to IP STISC as well. IANA staff has documentation (certified translation) regarding the reorganization through absorption of the state enterprise Molddata, which states that IP STISC is the successor of rights and obligations of Molddata. When looking at the .md record in the IANA database (https://www.iana.org/domains/root/db/md.html) , you will notice that the record was last updated at the start of September 2021, but there is no transfer report, since this is merely an administrative transfer. In line with the path chosen by IANA, and the additional information we received, no further Council action is required. The Secretariat will however need to remediate the 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, and consequently adjust the ccNSO mailing list subscriptions, the ccNSO website and ccNSO membership records, to reflect this administrative update. BACKGROUND According to the ICANN Bylaws, ccNSO membership is limited to ccTLD Managers (originally Sponsoring Organisation), which are the entities listed as ccTLD Manager in the IANA TLD Delegation record. Section 10.4. MEMBERSHIP (a) The ccNSO shall have a membership consisting of ccTLD managers. Any ccTLD manager that meets the membership qualifications stated in Section 10.4(b) shall be entitled to be members of the ccNSO. For purposes of this Article 10, a ccTLD manager is the organization or entity responsible for managing an ISO 3166 country-code top-level domain, or under any later variant, for that country-code top-level domain. Thank you, and my apologies. Best regards, Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org

2 2

Monday, 27 September 2021 | Join Tomorrow: Subsequent Procedures ODP Update Webinar
by ICANN Community Digest Sept. 27, 2021

Sept. 27, 2021

Monday, 27 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 Subsequent Procedures ODP Update Webinar Information Sharing NEW: Early Successes of ICANN's DAAR Adoption in the LAC Region NEW: ICANN Launches New IMRS Activity and Incident Report Page NEW: SSAD ODP Project Update Webinar Recording Available Now REMINDER: NextGen@ICANN Application Round for ICANN73 Now Open REMINDER: ICANN Continues the Pandemic Internet Access Reimbursement Program Public Comment NEW: Proposal for Latin Script Root Zone Label Generation Rule 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 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: Early Successes of ICANN's DAAR Adoption in the LAC Region In early September, during the Latin American and Caribbean Association of ccTLDs (LACTLD) Technical Workshop, I presented the benefits of a system that ICANN has developed to tackle domain name registration and security threats across top-level domain (TLD) registries. The system is called Domain Abuse Activity Reporting (DAAR). Read More. NEW: ICANN Launches New IMRS Activity and Incident Report Page Today, the Internet Corporation for Assigned Names and Numbers (ICANN) announced the release of a new ICANN Managed Root Server (IMRS) page. The page offers a collection of public reports on activities and incidents related to the IMRS prepared by ICANN's Security and Network Engineering (SaNE) team. Read More. NEW: SSAD ODP Project Update Webinar Recording Now Available Recording of the recent SSAD ODP Project Update webinar is now available. Presentation and audio files are available. 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 NEW: Proposal for Latin Script Root Zone Label Generation Rules Open for Submissions Date: Thursday, 23 September 2021 Closed for Submissions Date: Tuesday, 23 November 2021 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 71 | Archive | Next Issue: Thursday, 30 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

Joint: ccNSO/gNSO Teleconference | 20 October at 19:00 UTC
by Kimberly Carlson Sept. 26, 2021

Sept. 26, 2021

Dear Councilors The Joint: ccNSO/gNSO Council Teleconference has is scheduled for 20 October at 19:00 UTC An agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/94218282808?pwd=MThDeEpMT0NWVmdDclh4SUxqYmk4Zz09 Webinar ID: 942 1828 2808 Passcode: 4929575289 Wiki: https://community.icann.org/x/zASHCg

1 0

ccNSO Council prep for ICANN72 teleconference | 19 October at 12:00 UTC
by Kimberly Carlson Sept. 26, 2021

Sept. 26, 2021

Dear Councilors, The ccNSO Council prep for ICANN72 teleconference is scheduled for 19 October at 12:00 UTC. An agenda will be circulated prior to the call. Please find the call details below: Join Zoom Meeting https://icann.zoom.us/j/94231768694?pwd=bHRRNDRJUitSVjI1cFlxZHBXZVhQQT09 Meeting ID: 942 3176 8694 Passcode: Council-10 Wiki: https://community.icann.org/x/hgSHCg

1 0

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