- ALAC - lists.icann.org

ccNSO News
by Laura Margolis May 27, 2024

May 27, 2024

Dear All: Hope you are doing well. I would like to inform you some news regarding the ccNSO World: 1. ICANN80 Pre-Week - Learning Session 2. DASC (DNS Abuse Standing Committee) News 3. ICANN80 Schedule and highlighted sessions *1) Learn about ccNSO - ICANN Preweek - Tuesday 28th., May at noon UTC* If you want to learn more about ccNSO or you know colleagues or peers who would benefit from an introductory session to the ccNSO, Join ccNSO Council Vice Chair Biyi Oladipo (.ng) for a 1-hour ccTLD Webinar for newcomers. Biyi will help you to gain an understanding of the work of the ccNSO, what to expect from the ccNSO at the ICANN80 Policy Forum, as well as how ccTLD community representatives can participate in the important work that affects you and your region. *When?* Tuesday, 28 May 2024 | noon UTC *How to participate?* Register in advance for this meeting: https://icann.zoom.us/meeting/register/tJUvdeurrzssHtWltV34uFKz82i_PwEy3WjE After registering, you will receive a confirmation email containing information about joining the meeting. Recordings will become available here: https://community.icann.org/x/ooNJD *2) DASC - DNS Abuse Standing Committee* The *ccNSO DNS Abuse Standing Committee’s (DASC) Repository Subgroup* announced the availability of a repository of useful links for ccTLD managers as they seek information in addressing DNS Abuse. The purpose of the repository is to provide access to information relevant to the topic of DNS abuse that would be useful for ccTLD managers to identify, understand, and/or plan to take action with respect to such abuse that they may encounter. You can see the repository here <https://community.icann.org/x/Ege7Cg>, where the links are currently organized under four headings: · Presentations and reports. · Articles/commentaries. · Tools; and · Definitions/policies. The repository, which will be open and generally available, will be managed by an ‘editorial board’ which for the present will be the Repository Subgroup. The terms of reference for the repository and the editorial board can be seen here <https://community.icann.org/display/ccnsowkspc/ccNSO+and+DNS+Abuse+Mitigati…> . The initial links that you will see there have been inserted by the Subgroup. The idea is, that the ccNSO community will contribute suggestions for further inclusion – we hope to maintain this as a current and widely used resource that benefits members and ccTLD managers in maintaining safe and effective TLDs. If you want to learn more about DNS Abuse within ccTLDS, you’re invited to learn more during the DASC session at *ICANN80 Tuesday, 11 June 13:45-15:00 CAT (11:45-13:00 UTC).* *3) ICANN80 ccNSO Schedule and Links to Bookmark * If you would like to attend any of the ccNSO Meetings during ICANN80, here you have the links to the Schedule, Session Highlights and Tech Day ccNSO Schedule https://community.icann.org/x/GQBkEw ccNSO Session Highlights https://community.icann.org/x/wYCfEw Tech Day https://community.icann.org/x/OgBkEw I would like to recommend you some sessions to attend: *ccTLD News Part 1* When: Tuesday 11th. Time: 9:00 - 10:15 local time (7:00 - 8:15 UTC) Session chair: Everton T. Rodrigues (.br) - Collaboration and Partnerships in the ccTLD Landscape, Hildah Maina (.ke) - Introducing "A Technical Community Coalition for Multistakeholderism”, Jodi Anderson (.nz) *ccTLD News Part 2* When: Tuesday 11th. Time: 10:45 to 12:15 local time (8:45 - 10:15 UTC) Session chair: Joel Karubiu (AFTLD) - Digitization of South African Public Schools with school.za 2nd level domains, Plantina Tsholofelo Mokone (.za) - Large scale of community projects of a small registry, Dejan Djukic (.rs .срб) - Driving Digital Innovation: .ng ccTLD Registry Initiatives, Busayo Balogun (.ng) - Ten years of broadband measurement: lessons from Canada, Charles Noir (.ca) - New registrar requirements, Kristian Ørmen (.se, .nu) *ccNSO Internet Governance Liaison Committee (IGLC)* How ccTLDs contribute to a better world (UN Sustainable Development Goals) When: Wednesday 12th. Time: 13:45 - 15:00 local time (11:45 - 13:00 UTC) Hope you have a nice week. Thank you! Best Regards, *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com +59899690992 skype: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

1 0

About Justine Chow and her visit to LACRALO
by Sergio Salinas Porto May 21, 2024

May 21, 2024

Dear friends, Yesterday at the monthly LACRALO meeting, Juntine Chow visited us to talk about the activities of the GNSO and Progress in implementing the next Round, it was a very good activity where what was planned to be only a 30 minute meeting, was prolonged for space 45 minutes (even though Justine had other obligations to fulfill and had to leave on time). The topic discussed sparked a series of comments and contributions, the product of a tight and in-depth presentation that Justine made. I really must thank Justine for her invaluable contribution to the policy debates, in this case my colleagues who do not usually listen to her were amazed by her. What I do in a personal capacity, I know from comments I received after the meeting that reflect the collective feeling of the region. I am very happy for the quality of colleagues we have in ALAC. A big hug to everyone! *Sergio Salinas Porto**Presidente Internauta Argentina - LACRALO/ICANN <https://atlarge.icann.org/ralos/lacralo>**Asociación Argentina de Usuarios de Internet <http://www.internauta.org.ar/>/FeTIA <http://www.fetia.org.ar/>**FUILAC- Federación de Usuarios de Internet de LAC <https://fuilac.org>**facebook: salinasporto <http://www.facebook.com/salinasporto> **twitter: sergiosalinas <http://twitter.com/sergiosalinas>**Mobi:+54 9 223 5 215819**"Ojalá podamos ser desobedientes, cada vez que recibimos órdenes que humillan nuestra * * conciencia o violan nuestro sentido común" Eduardo Galeano*

1 0

The SSAC has published SAC125
by Matthias M. Hudobnik May 18, 2024

May 18, 2024

Hi colleagues, the SSAC has published SAC125. ### SSAC Report on Registrar Nameserver Management (SAC125): The report focuses on a specific type of sacrificial nameserver where the parent domains of the renamed host objects are considered unsafe because they are registrable. This introduces a new attack surface for domain resolution hijacking, as malicious actors can exploit these unsafe sacrificial nameservers to gain unauthorized control over dependent domains, leading to manipulation or disruption. As of September 2020, this practice had inadvertently exposed over 500,000 domains within generic top-level domains (gTLDs) to resolution hijacking risk, resulting in over 163,000 domains falling under unauthorized control. The report explores potential solutions to remediate exposed domains and prevent the creation of new unsafe sacrificial nameservers. Remediating exposed domains involves registrants, registrars, and registries, but coordination efforts face challenges like awareness, technical capability, and liability concerns. To prevent the risk, two primary categories of solutions are examined: 1) granting registrars more flexibility to delete host objects of expired domains, eliminating the need for sacrificial nameservers altogether, or 2) standardized renaming methods for sacrificial nameservers so their parent domains are not registrable. Recognizing the need for balance between operational efficiency, security, and minimization of unintended consequences, the SSAC recommends a multifaceted approach: · Recommendation 1: The registry and registrar communities should collaborate to develop and implement a comprehensive code of conduct to mitigate the risks associated with registrable sacrificial nameservers. · Recommendation 2: ICANN org should design, develop, and regularly publish aggregated statistics on the prevalence of unsafe sacrificial nameservers and the effectiveness of mitigation measures. · Recommendation 3: ICANN org should directly engage with registries and registrars to assist in mitigation and prevention efforts based on the insights from Recommendation 2. Link to the report: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe…. Have a nice day! Best, Matthias ______________________________ Ing. Mag. Matthias M. Hudobnik FIP • CIPP/E • CIPT • DPO • CIS LA matthias(a)hudobnik.at http://www.hudobnik.at @mhudobnik

1 0

ccNSO Council meeting #205
by Laura Margolis May 18, 2024

May 18, 2024

Dear All: Hope you are doing fine. I would like to inform you that the ccNSOCouncil meeting #205 was held yesterday May 16th. At 21:00 UTC. All the meeting related documents are uploaded in the *ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>* Agenda <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> , Notes <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> , Working Group and Committees written updates and other documents <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> I am attaching the draft Agenda and Notes, but I would like to *highlight* some of the topics: *Letter from Larisa Gurnick from ICANN Org on PHR (Pilot Holistic Review)* The letter is about what would be the next steps on the Pilot Holistic Review (PHR) and deferral of ATRT4 until next April. Timeline is as follows: A call for volunteers will be made on May 23rd. until June 19th. Then, SO/AC will review the list of applicants and determine their respective nominations from June 20th. till August 2nd. After, ICANN Org posts a list of all SO/AC nominated applicants on the PHR wiki and produces a skill and diversity analysis of nominated candidates from August 5th., till August 9th. The chairs of the SO/AC participating in the applicable review shall select a group of up to 21 review team members from among the prospective members nominated by the Supporting Organizations and Advisory Committees, balanced for diversity and skill. SO/AC Chairs select the Review Team members and identify review leadership from a list of nominated applicants from August 12th till September 6th. SO/AC Chairs inform ICANN of selected Review Team members on September 9th. *Progress GAP Analysis & Response ccPDP3 RM questions* On the Policy Gaps, a new WG Charter will be proposed to the Council and the Community during ICANN80. The WG will look for GAPS and identify which one needs to be addressed first and how. It will work on the overview of policies and guidance to be presented during ICANN81 in Istanbul. The tasks of the new WG will be to reflect IANA’s work and the GAPS, the way to address the GAPS. Study group, formal PDP Process, guidance for information, overview of all the components of the ccNSO policies. The small group on the caucus questions will have its first meeting May 21st. and will go over the questions. Group now includes 8 members of the WG and 3 Councilors who were not part of the WG. *Results Members vote ccPDP4* 1) Voting report for adoption, there was a detailed summary regarding the voting process 2) Next step: Board report, that will have a Public Comment period and GAC will be formally requested for advice. 3) Final step will be the adoption of the Board report. *3rd CSC Review: preliminary discussion how to handle the review* *For discussion:* According to the ICANN Bylaws and Charter of the Customer Standing Committee, the 3rd CSC effectiveness review is expected to start around 1 October 2024. The 2nd Review was concluded in June 2022, and one of the recommendations was to amend the ICANN Bylaws (and Charter of the CSC) to expand the duration between the reviews to five years after the previous review was concluded. Amending section 17.3 is a Fundamental Bylaw change. Further, according to section 17.3 (b) the method of review will be determined by the ccNSO and GNSO and the findings of the review will be published on the Website. *Agenda of ccTLD News during ICANN80 (will send it in a separate email when final schedule is out) * *PART 1* Session chair: Everton T. Rodrigues (.br) Collaboration and Partnerships in the ccTLD Landscape, Hildah Maina (.ke) Introducing "A Technical Community Coalition for Multistakeholderism”, Jodi Anderson (.nz) *PART 2* Session chair: Joel Karubiu (AFTLD) Digitization of South African Public Schools with school.za 2nd level domains, Plantina Tsholofelo Mokone (.za) Large scale of community projects of a small registry, Dejan Djukic (.rs .срб) Driving Digital Innovation: .ng ccTLD Registry Initiatives, Busayo Balogun (.ng) Ten years of broadband measurement: lessons from Canada, Charles Noir (.ca) Opening up the .eu Abuse Prevention and Early Warning System to the ccTLD community, Hans Seeuws (.eu) Agenda <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> , Notes <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> , Working Group and Committees written updates and other documents <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…> *AGENDA Council meeting # 206* *Draft Agenda* *ccNSO Council Meeting 205* 16 May 2024, 21.00 UTC 1. *Welcome and roll call* 1. *Establish whether meeting is Quorate* 2. *Update Statement of Interest* For information <https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-2…> Guideline <https://ccnso.icann.org/en/about/ccnso-internal-procedure-general-soi-coi-2…> & <https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> Template <https://docs.google.com/forms/d/e/1FAIpQLSfRpehiCw2ty2PYRiaPG0K3lZSKk9LrLPQ…> *Administrative matters* 2. *Relevant Correspondence* <https://ccnso.icann.org/en/about/statements.htm> 1. Letter from Katrina Sataki, chair of the Board Caucus ccPDP3 RM (Letter dated 2 March 2024) to be discussed under item 12. 3. *Minutes & Action Items* 1. *Minutes Meeting 204**: *Circulated 6 May 2024 2. *Action items* *Action Item 204-01:* Council to discuss with the registry stakeholder group (agenda item) the third CSC review. *Action Item 204-02:* Secretariat to adjust Purpose and Goals statement approval date (to April 2024) (Completed and posted) *Action Item 204-03:* ccNSO Council and Triage committee to jointly plan a resource capacity workshop prior to ICANN80 (Completed, scheduled 30 May 2024) *Action Item 204-04:* Post ICANN80, Council to decide whether to keep the policy gap analysis group ad-hoc or create a fully mandated working group (Pending, TBD post ICANN80) *Action Item 204-05:* Secretariat to inform DASC and IGLC leadership of Federica Tortorella oof appointment to both groups (Completed) *Action Item 204-06:* Chair to inform ISOC.LB <http://isoc.lb/> and ccNSO membership (Completed) *Action Item 204-06:* Secretariat assist drafting response (Google Doc) to Tripti Sinha’s letter on amendment recommendation 7 on CCWG Auction Proceeds. Small group of Councilors to draft response (Alejandra, Chris, Olga, Jenifer) (Completed) *Action Item 204-07:* Secretariat to suggest new Terms of Reference for OISC by meeting 205 of the ccNSO Council (May 2024). *Action Item 204-08:* Secretariat to send call for volunteers: small group to review World Café outcomes (no response) *Action Item 204-09:* Chair to send email to Council re preference to have an extraordinary Council meeting or wait until May call to discuss questions received from the Board on ccPDP RM (Completed, scheduled 7 May 2024) 4. *Intermeeting Decisions (since meeting 203, March 2024)* 1. *203-A* 2. *2023-B* 5. *Intermeeting decisions Triage Committee* The Triage Committee has made no decisions since meeting 202. *Updates* 6. *Update ECA, IFRT & CSC* 7. *Update WGs *(written updates or taken from the meeting) 1. *IGLC* 2. *GRC* 3. *SOPC* 4. *OISC **(no meetings pending update charter)* 5. *TLD-OPS* 6. *DASC* 7. *Technical WG* 8. *MPC* 9. *UAC* 10. *Registrant capacity ad-hoc group* 11. *IRP Panel selection* 12. *CCG WS 2 Implementation* 13. *New: CIP-CCG* 14. *Prioritization Framework group* 8. *Update liaisons* (written updates) 1. *Update ALAC Liaison* 2. *Update GNSO Liaison* 3. *Update UASG Liaison* 9. *Update ccNSO Website redesign* Informational *10. **Update Triage Committee: Monitor portfolio of Activities 2024-2025* 11. *Update Chair, Vice-Chairs, Councillors, RO’s and Secretariat* 1. *1-on-1 ICANN CEO and ccNSO leadership* 12. *Progress GAP Analysis & Response ccPDP3 RM questions* *Administrative Matters & Decisions* 13. *Results Members Vote ccPDP4* *a. **Voting Report for adoption* *Draft resolution* *Background* In accordance with the ccNSO Policy Development Procedure (Annex B to the ICANN Bylaws), the ccNSO Council Recommendation to adopt the proposed policy on the (de-)selection of IDN ccTLD strings, was put to a vote by the ccNSO Membership. The voting ran from Wednesday, 27 March 2024 (00:01 UTC) and closed Wednesday, 17 April 2024 (23:59 UTC). The vote passed: At the closure of the vote, 56% of the Emissaries (97 out of 174 Emissaries) cast their vote. 97% of the votes cast were in support of the ccNSO Council recommendation to adopt the proposed ccPDP4-IDN policy. The Bylaw requirements for a valid vote in support of the policy were met: at least 50% of the emissaries are required to lodge their vote and the 66 % of the votes cast need to be in favor. The Voting Process Manager submitted her report as required, and made 4 observations, however did not report any incidents. *Decision* *The ccNSO adopts the voting report as submitted by the Voting Process Manager, notes the observations and requests the ccPDP4 Issue Manager to include a reference in the forthcoming Board Report. By adopting the Voting Report, the voting process is formally concluded. The ccNSO Council thanks Joke Braeken wholeheartedly for her managing the voting process. This resolution becomes effective upon publication. * *b. **Next Step: Board Report* 14. *Appointment Members to Committees and Working Groups, if any* No appointments for this meeting 15. *Update OMC (was: OISC) Terms of Reference* *Substantive Matters & Decisions* 16. *Review External appointments: next steps* 17. *3rd CSC Review: preliminary discussion how to handle the review* For discussion According to the ICANN Bylaws and Charter of the Customer Standing Committee, the 3rd CSC effectiveness review is expected to start around 1 October 2024. The 2nd Review was concluded in June 2022, and one of the recommendations was to amend the ICANN Bylaws (and Charter of the CSC) to expand the duration between the reviews to five years after the previous review was concluded. Amending section 17.3 is a Fundamental Bylaw change. Further, according to section 17.3 (b) the method of review will be determined by the ccNSO and GNSO and the findings of the review will be published on the Website. 18. *Discussion and decision on next steps outcome world cafés on keeping the ccNSO relevant next 7 years* For Information & discussion 19. *ccNSO relevant meetings ICANN80 ( 10 – 13 June 2024)* 1. *Prep week ICANN80: 28 -30 May 2024* 2. *Prep Council meeting* 1. *Working session (conference call)* 2. *Prep session* 3. *Joint Meetings* 1. *Virtual meeting GNSO Council - 11 July 2024 13:00 UTC* 4. *Special Event: Tuesday 11 June 2024- block 5* 5. *Tentative Block Schedule* 20. *AOB* 21. *Next Council Meetings* ● June 13 @ICANN80 (206) – time TBD ● July 18 – 12:00 UTC (207) ● August 22 (208) – 18.00 UTC (208), may be deferred ● September 19 – 12:00 UTC (209) ● October 17 – 21:00 UTC (210) ● November 14 @ICANN80 – (211) – time TBD ● December 12 – 12:00 UTC (212) ● January 16, '25 - 18:00 UTC (213) ● February 13, '25 - 12:00 UTC (214 22. *Adjourn* Thank you for your attention and if you have any questions or topics you would like to deep dive more, please let me know. Kindest Regards, -- *Laura Margolis* ALAC Liaison to ccNSO margolisl(a)gmail.com +59899690992 skype: lauri.margolis ccNSO Liaison Workspace <https://community.icann.org/display/atlarge/ALAC+Liaison+to+the+ccNSO+Repor…>

2 1

Summary Report for GNSO Council 16 May 2024 meeting
by Justine Chew May 17, 2024

May 17, 2024

Dear all, Here is my report of the GNSO Council's 16 May 2024 meeting. Council discussed some issues at length, but the most important decision for us is their resolution to request for an Issues Report for Diacritics in Latin Script and the direction to GNSO staff to create the Report. There were also a couple of amendments to the agenda <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> under AOB but I have concentrated on what I think are the key matters of interest to us. You can also read this report posted at the ALAC Liaison to the GNSO workspace <https://community.icann.org/x/mQK7Cg>, or simply using the links included below to navigate to the May 2024 entry. *Special Summary Report of 16 May 2024 Meeting to ALAC <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…>* For brevity, I will just highlight a few things here. For some of the issues, you can glean a wider perspective from GNSO Council May 2024 Matters of Interest <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> and/or from GNSO Council May 2024 Meeting Records <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> . *1. Consent Agenda* - Council resolved <https://gnso.icann.org/en/council/resolutions/2020-current#202405> to adopt the revised Description of the role of GNSO Liaison to the Governmental Advisory Committee <https://gnso.icann.org/sites/default/files/policy/2024/draft/final-gnso-lia…> . - Council resolved <https://gnso.icann.org/en/council/resolutions/2020-current#202405> to approved the ICANN Board’s Proposed Amendment to remove the phrase “from the Independent Project Applications Panel” from the Cross-Community Working Group on Auction Proceeds Recommendation 7. *2. Diacritics in Latin Script* - The issue of diacritics in Latin script is not a new one. It first originated, resulting from the 2012 Round, when the registry operator for .Quebec opted to apply for the non-diacritic .quebec label in favour of the label with diacritic “.québec”, but they did not pursue any "formal" remedy to the challenge of also obtaining the “.québec” TLD until more recently, when 4 public comments were submitted in response to the GNSO Call for Public Comments to the Phase 1 Initial Report of the IDNs EPDP <https://www.icann.org/en/public-comment/proceeding/phase-1-initial-report-o…> in Apr 2023. - In Jul 2023, GNSO Leadership received a communication <https://mm.icann.org/pipermail/gnso-epdp-idn-team/2023-August/001073.html> from the IDNs-EPDP Chair regarding 4 public comments related to creating an exceptional process by which the existing registry operator for .quebec could apply “.québec” in a future gTLD round ("the .québec issue") being out of scope of the IDNs-EPDP and its Charter, and referred the comments to the GNSO Council for consideration and action as determined appropriate. - On 17 Aug 2023, GNSO Leadership circulated the 22 Jun 2023 letter <https://gnso.icann.org/sites/default/files/policy/2023/correspondence/zuck-…> from ALAC Chair to the GNSO Chair regarding the Latin script LGR and .québec issue. - On 24 Aug 2023, Council discussed this issue and, the then GNSO Chair essentially concluded that the issue of .quebec (TLD) not being a variant of “.québec” did not require an immediate resolution and one that did not squarely sit in the remit of the IDNs-EPDP. - On 23 Sep 2023, the then Council Chair again addressed the issue of accents and diacritics in Latin languages that could be deemed confusingly similar to existing strings or other applications, and suggested chartering something with a narrow scope to ensure that this topic does not slide elsewhere into the string similarity discussion and ensure that solutions are found that match requirements imposed on variants. ICANN org staff clarified that next steps from the staff perspective would be for Council to request an Issues Report. - On 25 Oct 2023, Council received a detailed briefing on this issue and agreed to request a study from ICANN org to help inform the GNSO Council on the issue of diacritics in Latin Script. Prior to the request being made to ICANN org, the org volunteered to investigate what mechanism or mechanisms might be appropriate to address this issue. Since then, Council had for several months deferred discussing a way forward to address the issue as GNSO support staff had indicated that a proposal for a solution was being worked on which might alleviate the need for a study request which Council had been mooting earlier. - The issue finally returned to Council's agenda in Apr 2024, where after much discussion, Council concluded that GNSO support staff's suggested way forward was neither feasible nor desirable (see my Apr 2024 report <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…>), and as a result, Council reinforced its agreement <https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso…> to request an Issue Report on diacritics in Latin script. Since this could only be actioned through a Council resolution, it was agreed that Council would vote on such a motion in its May 2024 meeting. - Hence at this meeting, Council resolved <https://gnso.icann.org/en/council/resolutions/2020-current#202405> to adopt the request for an an Issues Report, and directs staff to create the Report. *3**. IPC's Request for Reconsideration (RfR) on the Board's Proposed Bylaws Updates to Limit Access to Accountability Mechanisms* - This is regarding the Board Accountability Mechanisms Committee's (BAMC) dismissal of IPC's RfR on the basis that IPC was not a party harmed by the Board's Proposed Bylaws Updates to Limit Access to Accountability Mechanisms <https://www.icann.org/en/public-comment/proceeding/proposed-bylaws-updates-…> . - NOTE: While the GNSO Council did not support <https://www.icann.org/en/public-comment/proceeding/proposed-bylaws-updates-…> the Board's proposal but the ALAC did <https://www.icann.org/en/public-comment/proceeding/proposed-bylaws-updates-…>, the issue being contended here, is the principle that an ICANN community group can be found to have no standing (i.e. has been unable to show harm suffered) for something that has yet to be implemented. - Council discussed possible next steps to counter the BAMC dismissal, noting that the gravity and implications of grounds for this dismissal, including the possibility of involving other members of the ICANN Community in next steps. *4. Deferral of Policy Status Report Request - Expiration Policies* - Council previously considered when to request a Policy Status Report (“PSR”) for the purpose of conducting a review of the two Expiration Policies, the Expired Domain Name Deletion Policy (“EDDP”) and the Expired Registration Recovery Policy (“ERRP”). In November 2020, given concerns about its capacity and no known issues with the policies, the Council agreed to delay the request for the Policy Status Report (PSR) for a period of 24 months. After 24 months had passed, the Council reconsidered whether it was an appropriate time to request a PSR. - In July 2022, Council agreed that it would be helpful to consult with both registrars and ICANN org to help determine if there are any known issues or concerns with either of the two Expiration Policies which could warrant requesting a PSR. - In making its decision whether to request to a PSR at this time, Council consulted: 1. Registrars, who were asked to flag substantial issues with the policies that would warrant a near-term request for PSR and did not note any issues 2. ICANN Compliance, who provided a write-up <https://mm.icann.org/pipermail/council/2022-November/026164.html>, noting confusion with key terms in the policy and persistent registrant confusion with the auto-renew grace period and aftermarket activities, et al. 3. ICANN org Registrant Program, which provided a catalog of the available educational resources on domain name expiration and renewal (Brian Gutterman’s update at Council) - Council then determined that the EDDP and ERRP seem to have been implemented as intended and imminent policy work is not needed at this time, and so, considered to pursue a PSR on the Expiration Policies in two years' time, or earlier, if a need is determined and it is requested. - Primarily at an IPC Councilor's request, this decision for a deferral of the PSR was deferred yet again, to Council's Jun 2024 meeting. IPC's belief that the request for a PSR should proceed now since it would take some time for it to be actioned by ICANN org staff, and IPC wanted a bit more time to shore up its representation on this issue. There was no objection to deferring the vote to Council's next meeting. Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> On Sat, 4 May 2024 at 17:44, Justine Chew <justine.chew.icann(a)gmail.com> wrote: > Dear all, > > Just a note to inform you that the agenda for the GNSO Council meeting of > 16 May 2024 is out. > > For a curated version of the highlighted agenda item, please visit this > link > <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> > . > > *GNSO Council Meeting #5 of 2024 held on 16 May 2024 * > > *Full Agenda <https://community.icann.org/x/BYDyEg> | Documents > <https://community.icann.org/x/tQJyEw> | Motions > <https://community.icann.org/x/tAJyEw>* > > - *Item 1: Administrative Matters* > - Item 2: Opening Remarks / Review of Projects List > <https://gnso.icann.org/en/council/project> and Action Item List > <https://community.icann.org/x/RgZlAg> > - Item 3: Consent Agenda > - GNSO Liaison to the Governmental Advisory Committee > - Council Response to Board Letter on CCWG Auction Proceeds > Recommendation 7 > - *Item 4: COUNCIL VOTE - Deferral of Policy Status Report Request - > Expiration Policies* > - *Item 5: COUNCIL VOTE - Request for Preliminary Issue Report for > Diacritics in Latin Script* > - Item 6: COUNCIL DISCUSSION - GNSO Council Committee for Overseeing > and Implementing Continuous Improvement (“CCOICI”) Pilot Survey Results > - *Item 7: COUNCIL DISCUSSION - Intellectual Property Constituency > Request for Reconsideration* > - Item 8: COUNCIL DISCUSSION - Review of Action Decision Radar > - Item 9: GNSO Council Aspirational Statement > - > > *Item 10: Any Other Business* > - > > 10.1 - Update on ICANN80 planning and GNSO Draft schedule > - > > 10.2 - ccNSO & GAC Liaison updates (every three months) > - > > 10.3 - SPS Action Item Updates: Recommendation Reports and GNSO > Liaisons to WGs > - *10.4 - Call for Volunteers > <https://lists.icann.org/hyperkitty/list/council@icann.org/thread/FSVAED2EID…>- > Privacy and Proxy Services Accreditation Implementation Review Team (PPSAI)* > > > As usual, Council meetings are open to observers both on-site and remotely > in listen-only mode. If you would like to observe the meeting, please check this > link > <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> for > details. > > Thanks for reading / considering. > > Justine Chew > ALAC Liaison to the GNSO > GNSO Liaison Report Workspace > <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> > ------ > >

1 0

The SSAC has published SAC124
by Matthias M. Hudobnik May 7, 2024

May 7, 2024

Hi colleagues, the SSAC has published SAC124. ### SSAC Advice on Name Collision Analysis (SAC124): The SSAC provides its advice on name collision analysis based on the NCAP Study Two report. The SSAC fully endorses the findings and recommendations presented in the report and recommends the ICANN Board adopt and implement these recommendations. The SSAC supports the centralized and coordinated approach proposed by Study Two. This approach is essential for implementing effective measures to mitigate the two data-access-related risks associated with name collisions: · Delegation Risk: Privacy and risks to users and end systems from name collisions associated with the delegation of a TLD. · Assessment Risk: Privacy risks associated with the execution of data collection methods in the proposed Name Collision Risk Assessment Framework. While acknowledging ICANN org's privacy concerns around the proposed data collection methods, the SSAC offers three considerations: · Privacy risks are inherent in managing name collision risk due to ICANN's role in coordinating gTLD allocation and assignment. · Avoiding data collection does not resolve delegation privacy risks, but rather transfers these risks to third parties, potentially amplifying harm. · Effective management of security, stability and resiliency risks requires a proactive approach to name collision identification and mitigation. Based on these, the SSAC recommends prioritizing solutions that allow sufficient data collection and analysis to properly inform name collision mitigation strategies. Failing to mitigate delegation risks due to assessment risk concerns would threaten DNS security/stability and end-user privacy. The SSAC's recommendations are: · Adopt and implement all recommendations in NCAP Study Two. · Prioritize finding appropriate solutions within the proposed framework that enable sufficient data collection and analysis for mitigation. · The SSAC welcomes engagement from ICANN org and offers its expertise. The SSAC acknowledges more work is needed on privacy aspects and looks forward to collaborating with ICANN org and privacy experts. Link to the report: https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe…. Have a nice day! Best, Matthias ______________________________ Ing. Mag. Matthias M. Hudobnik FIP • CIPP/E • CIPT • DPO • CIS LA matthias(a)hudobnik.at http://www.hudobnik.at @mhudobnik

1 0

GNSO Council 16 May 2024 meeting agenda is out
by Justine Chew May 4, 2024

May 4, 2024

Dear all, Just a note to inform you that the agenda for the GNSO Council meeting of 16 May 2024 is out. For a curated version of the highlighted agenda item, please visit this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> . *GNSO Council Meeting #5 of 2024 held on 16 May 2024 * *Full Agenda <https://community.icann.org/x/BYDyEg> | Documents <https://community.icann.org/x/tQJyEw> | Motions <https://community.icann.org/x/tAJyEw>* - *Item 1: Administrative Matters* - Item 2: Opening Remarks / Review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List <https://community.icann.org/x/RgZlAg> - Item 3: Consent Agenda - GNSO Liaison to the Governmental Advisory Committee - Council Response to Board Letter on CCWG Auction Proceeds Recommendation 7 - *Item 4: COUNCIL VOTE - Deferral of Policy Status Report Request - Expiration Policies* - *Item 5: COUNCIL VOTE - Request for Preliminary Issue Report for Diacritics in Latin Script* - Item 6: COUNCIL DISCUSSION - GNSO Council Committee for Overseeing and Implementing Continuous Improvement (“CCOICI”) Pilot Survey Results - *Item 7: COUNCIL DISCUSSION - Intellectual Property Constituency Request for Reconsideration* - Item 8: COUNCIL DISCUSSION - Review of Action Decision Radar - Item 9: GNSO Council Aspirational Statement - *Item 10: Any Other Business* - 10.1 - Update on ICANN80 planning and GNSO Draft schedule - 10.2 - ccNSO & GAC Liaison updates (every three months) - 10.3 - SPS Action Item Updates: Recommendation Reports and GNSO Liaisons to WGs - - *10.4 - Call for Volunteers <https://lists.icann.org/hyperkitty/list/council@icann.org/thread/FSVAED2EID…>- Privacy and Proxy Services Accreditation Implementation Review Team (PPSAI)* As usual, Council meetings are open to observers both on-site and remotely in listen-only mode. If you would like to observe the meeting, please check this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> for details. Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> ------

1 0

GAC Liaison Report on Intersessional Work / ALAC-GAC Joint Communication on Applicant Support
by Joanna Kulesza April 30, 2024

April 30, 2024

Dear all, I am pleased to provide you with a report on the bilateral engagement between the GAC and the ALAC, emphasizing the significant focus on developing the joint communication regarding the Applicant Support Program, following the ALAC-GAC meeting at the ICANN79 Community Forum in San Juan, Puerto Rico. 1. Background and Context: The joint communication aims to consolidate the input and perspectives of both ALAC and GAC on the ASP, reflecting the discussions and agreements reached during our bilateral meeting at ICANN79. 2. Content Development: Since our meeting in San Juan, the working group composed of representatives from both ALAC and GAC has diligently worked on drafting the joint communication. They have incorporated key points and recommendations outlined in the draft statement you provided, which articulates our collective stance on the ASP. The drafting work is being excellently spearheaded by Justine Chew, ALAC VC, on behalf of the At-Large Community. 3. Alignment with Community Feedback: The content of the joint communication has been informed by various sources, including recent GAC communiques, public comments, and contributions from working group members. We have strived to ensure that the communication accurately reflects the diverse perspectives and priorities of the ICANN community. 4. Key Themes and Recommendations: The joint communication emphasizes several core principles and recommendations, including: - Alleviating the financial burden on ASP applicants to the maximum extent possible. - Prioritizing outreach to applicants from underserved regions. - Applying a holistic approach to support ASP applicants throughout the application lifecycle. - Supporting the longer-term success of ASP-qualified applicants beyond the application phase. 5. Incorporating ALAC and GAC Feedback: The draft communication has undergone iterative review and revision by both ALAC and GAC representatives to ensure consensus and coherence. Feedback provided by working group members has been carefully considered and integrated into the final draft. 6. Annexes and Supporting Documentation: The joint communication will be supplemented by annexes, including the ICANN79 GAC Communique and the ALAC Proposal on the implementation of Subsequent Procedures Recommendation 17.2. These annexes provide additional context and background information to support our recommendations. 7. Next Steps: The finalized joint communication will be presented for discussion and approval during our upcoming bilateral meeting in Kigali, Rwanda. We anticipate productive input for the ICANN Board members and stakeholders to further refine our recommendations and ensure their alignment with ICANN's objectives. A draft agenda for the bilateral session in Kigali is included below for your kind consideration: Proposed Agenda for ALAC-GAC Joint Bilateral Session in Kigali Date: Wednesday, June 12, 2024 Time: 07:00 - 08:15 UTC (75 minutes) 1. 07:00 - 07:10 UTC Introduction and welcome by GAC/ALAC Chairs - Jonathan Zuck, ALAC Chair - Nico Caballo, GAC Chair 2. Presentation of Joint Position Paper - (07:10 - 07:25 UTC) Presentation of joint position paper by ALAC representative - (07:25 - 07:40 UTC) Presentation of joint position paper by GAC representative 3. Moderated Q&A Session - (07:40 - 08:00 UTC) 4. Closing remarks and next steps (08:00 - 08:15 UTC) Please allow me to take this opportunity to express my appreciation for the collaborative spirit and dedication demonstrated by both ALAC and GAC members throughout this process. Our joint communication reflects our shared commitment to advancing the ASP and fostering diversity and inclusivity within the domain name ecosystem. Thank you for your attention to this report. Your feedback and any additional input are highly valued. Please feel free to share your thoughts or suggestions. -- Kind regards, Joanna Kulesza ------------------- Joanna Kulesza, PhD Professor of International Law Lodz Cyber Hub / University of Lodz Law School / Poland www.cyber.uni.lodz.pl (EURALO ALS 341) ALAC / EURALO / ALAC Liaison to the GAC

4 3

GNSO Council 18 April 2024 meeting agenda is out
by Justine Chew April 30, 2024

April 30, 2024

Dear all, Just a note to inform you that the agenda for the GNSO Council meeting of 18 Apr 2024 is out. For a curated version of the highlighted agenda item, please visit this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> . *GNSO Council Meeting #4 of 2024 held on 18 Apr 2024 * *Full Agenda <https://community.icann.org/x/_oAvEQ> | Documents <https://community.icann.org/x/A4DyEg> | Motions <https://community.icann.org/x/AYDyEg>* - *Item 1: Administrative Matters* - Item 2: Opening Remarks / Review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg> - *Item 3: Consent Agenda* - GNSO Council Review of the GAC Communiqué <https://gnso.icann.org/sites/default/files/policy/2024/correspondence/dibia…> - GNSO Council Small Team Guidance Document <https://gnso.icann.org/sites/default/files/policy/2024/draft/updated-small-…> - *Confirmation of Standing Predictability Implementation Review Team (SPIRT) Charter Drafting Team Leadership *(Chair - Nitan Walia; Vice-chair - Alan Greenberg; GNSO Council liaison - Anne Aikman-Scalese) - *Item 4: COUNCIL VOTE - Deferral of Policy Status Report Request - Expiration Policies* - *Item 5: COUNCIL DISCUSSION - Diacritics in Latin Script* - *Item 6: COUNCIL VOTE - SubPro Supplemental Recommendations* - *Item 7: COUNCIL DISCUSSION - New gTLD Auction Proceeds Cross Community Working Group - Auction Proceeds (CCWG-AP) - Proposed Update to Recommendation 7* - Item 8: COUNCIL DISCUSSION - Review of Action Decision Radar - *Item 9: Update on Status of Privacy and Proxy Services Accreditation Implementation* - *Item 10: ANY OTHER BUSINESS* - 10.1 - Update on ICANN80 planning and GNSO Draft schedule <https://gnso.icann.org/sites/default/files/policy/2024/draft/icann80-gnso-d…> - 10.2 - Replacement of Council representative to the Continuous Improvement Program Community Coordination Group (CIP-CCG) - *10.3 - Upcoming Sessions/Updates on the Registration Data Request System (RDRS) * As usual, Council meetings are open to observers both on-site and remotely in listen-only mode. If you would like to observe the meeting, please check this link <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> for details. Thanks for reading / considering. Justine Chew ALAC Liaison to the GNSO GNSO Liaison Report Workspace <https://community.icann.org/display/atlarge/GNSO+Liaison+Report%2C+post-Oct…> ------

3 5

At-Large Travel Fresh Start
by Jonathan Zuck April 29, 2024

April 29, 2024

Dear All, Thank you again for your feedback on the At-Large travel policy. I want you to know that we have heard your concerns regarding the proposed At-Large travel policy and we want to keep discussing it with you. The need for an objective, utilitarian and flexible travel policy still exits to ensure that those actively engaged in ICANN work are in the best position to participate and we are actively planning for the future. For ICANN80, we propose to revert to the allocation of 15 slots to the ALAC, 10 to the five RALOs and 3 for ALAC Liaisons and one for the ALAC Chair. Given that 3 ALAC members are unable to travel to Kigali, we would like to offer them to AFRALO to allocate as they wish. These 3 slots are unused ALAC slots so they are not drawn from expected slots. For ICANN81, as this is the Annual General Meeting, we will also use the allocation which also supports the travel for outgoing, incoming, and continuing ALAC and Regional Leaders, according to their regional rotations For the longer-term development of an At-Large travel policy, starting as early as May 2024, we suggest engaging in regional listening sessions where everyone has the opportunity to share their views and explain any concerns in a structured manner. Should you agree, we've asked Melissa Allgood, a member of ICANN org specializing in conflict resolution, to lead these discussions as a neutral facilitator. Melissa will not act as a representative of ICANN org, but rather will structure our dialogue to ensure that all participants are heard and their views considered. We will work with RALO leaders to include these listening sessions at a time that best meets the needs of each region, perhaps during scheduled monthly calls. The development of a formal At-Large travel policy will take some time and we would like for all voices to be heard and considered. Ideally, we would like to work jointly with you - - in eliminating subjective answers with agreed, objective metrics that meet well crafted expectations of volunteers in performing the role of the ALAC as tasked under the ICANN Bylaws. Such a policy should be reflective of the values of the bottom-up multi-stakeholder model. Let us move forward in an inclusive, constructive, transparent, and respectful manner within our community. Jonathan Jonathan Zuck | Director, Future of Work Project | Innovators Network jzuck(a)innovatorsnetwork.org<mailto:jzuck@innovatorsnetwork.org> | O 202.827.7594 | D 202.420.7483 [See the source image]Jonathan-zuck<https://www.linkedin.com/in/jonathan-zuck/> | [See the source image] jvzuck<https://twitter.com/Jvzuck> | [See the source image] jonathanzuck<https://www.instagram.com/jonathanzuck/> | [See the source image] Jonathan.zuck<https://www.facebook.com/jonathan.zuck/> [signature_1023473624]

15 23