May 2026 - lac-discuss-en - lists.icann.org

[lac-discuss-es] Actualización CPWG
by lac-discuss-es＠icann.org May 17, 2026

May 17, 2026

[[-- Translated text (es -> en) --]] Dear members of the community, I'm sharing a summary of the main topics discussed at the meetings of CPWG of April 29 and May 6, 2026. For more details, they can consult the wiki pages for each session. *Links to CPWG sessions* April 29, 2026 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/1066237953/…> May 6, 2026 <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/1097728007/…> *1. Workgroup and Small Team Updates* *PDP1 on DNS Abuse Mitigation: Domain Name Verification Associates <https://icann-community.atlassian.net/wiki/spaces/alacpolicydev/pages/10324…> * Discussions covered: - Q3 What should be understood as a “reasonable investigation” by of a registrar?, seeking to define what information a registrar should review recorder, what signals should be considered and what would the steps be minimum expected during an investigation related to DNS abuse. - Use of “reasonably available” data: that the registrar should review the information reasonably available within their systems or contractual relationships, without this necessarily implying access to data that it does not possess. It was discussed that in some operating models, especially when resellers are involved, certain relevant information It can only be found in the hands of the reseller and not directly from the recorder. - Risk that an overly flexible policy will allow for non-compliance superficial. It was suggested that if the policy only requires reviewing a minimum data point (“datapoint”), a recorder could be limited to verify a single indicator and consider their obligation fulfilled research. From an at-large perspective, this could create gaps. (“loopholes”) and reduce the effectiveness of investigations against DNS abuse. - Balance between effective research and privacy protection and personal data. The discussion on Question 4 of the Charter (“Charter Question 4”) focused on how to allow the use of sufficient information to investigate abuse without the data being used for purposes other than those intended. specific to the research. - The conversation about differentiating between registers was also resumed of natural and legal persons, although it was noted that in cases related to malicious records the information used many times It may be false or compromised, which limits its practical usefulness. that differentiation within this process. *Supplementary Recommendations Team of the Standardized System of Access and Disclosure (SSAD SRT) / Data Request Service Registry (RDRS)* It was reported that the work of the Supplemental Recommendations Team of The Standardized Access and Disclosure System continues to advance and is They were expecting further meetings before ICANN86. It was also mentioned that At-Large already has a defined representation within the team. There were no substantive updates to the Data Request Service Registration during these meetings. *Other topics listed on the agenda, such as the Universal Use Working Group (UAEWG), the Policy Process on Latino Diacritics, the Second IANA Name Function Review (IFR2), the Process Expedited Domain Name Policy Development Internationalized (EPDP-IDNs), the Transfer Process of Registrars (TPR-PDP) and the Registration Data Area (RDA) remained without substantive discussion in these sessions*. *2. At-Large Policy Initiatives* *DNS Abuse* Discussions continued regarding the related At-Large strategy with mitigation of DNS abuse. Reference was made to the webinar <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/1012498450/…> done April 14th on mitigating DNS abuse and the document collaborative <https://docs.google.com/document/d/1smchQvYap04IMu7BCiAj6TWEhhxFE7wqayI8CyY…> used to gather resources, references, questions and initiatives community. The objective of this work is to gather information that will allow the development of At-Large's own agenda on DNS abuse, including possible contributions to PDP1, educational materials, awareness campaigns and Compilation of regional experiences related to phishing and fraud online and end-user protection. The community was also invited again to continue contributing materials and references to the collaborative document <https://docs.google.com/document/d/1smchQvYap04IMu7BCiAj6TWEhhxFE7wqayI8CyY…> . *3. Implementation Review Teams (IRTs)* *Privacy and Proxy Services Implementation Review Team (PPSAI IRT)* The PPSAI IRT continued discussing issues related to services Privacy and proxies, particularly the role of resellers. The conversation focused on potential gaps related to obligations contractual, data escrow, and scenarios where a reseller ceases operations without adequate mechanisms to recover the final registrant information. The possibility of extending certain obligations was also discussed. contractual to resellers through transfer mechanisms contractual obligations. *Next round of new generic top-level domains: Procedures Subsequent (SubPro), Permanent Predictability Review Team (SPIRT) and Applicant Support Program (ASP)* The opening of the application period for the 2026 round of new generic top-level domains on April 30 2026. Regarding the Applicant Support Program, it was reported that They had received 51 applications, of which 25 had already been evaluated, 22 approved and 2 withdrawn. The ASP is the program designed to support applicants who require assistance to participate in the next round. A proposal related to greater flexibility in the ASP financial eligibility assessment. Currently the threshold The reference financial threshold is USD 5 million, but ICANN proposed allowing a margin of up to 15% to account for exchange rate fluctuations, inflation and economic differences between regions. *Permanent Predictability Review Team (SPIRT)* Updates continued regarding the Permanent Review Team Predictability (SPIRT). This group was created to support the management of changes or unforeseen issues during the implementation of the next round of new gTLDs, with the aim of maintaining predictability and transparency in the process. The operation of the Guide Change Log was explained again. of the Applicant, used to document changes made to the Guide of Applicant and related documents. Changes are classified by type. Type 0 changes correspond to editorial corrections or minor adjustments; Type 1 corresponds to Minor operational changes; Type 2 corresponds to operational changes with possible material impact on applicants or processes; and Type 3 These correspond to policy changes. It was also noted that SPIRT cannot initiate cases on its own and that The issues must be submitted through the established formal mechanisms for your evaluation. *Registration Service Providers (RSPs)* A proposal (“issue submission”) related to the Registration Service Providers (RSPs), i.e., technical providers that operate registration services for new gTLDs. The discussion focused on technical requirements related to the Protocol. Extensible Provisioning (EPP). EPP is the protocol used for technical communication between registries and registrars (“registrars”). EPP extensions allow you to add functionalities additional to the protocol. Currently the Registration Service Provider Manual (“RSP”) Handbook”) and the technical tests called RST2.0 require that certain RSPs use EPP extensions registered with the Numbers Authority Assigned on the Internet (IANA). However, during the discussions of Base Registry Agreement for the next round, That limitation had been relaxed for registry operators. The concern raised is that this could create inconsistencies between different documents used in the evaluation process and limit the use of certain technical functionalities or extensions not yet formally registered with IANA. *4. Policy statements and public comments* Ratification of ALAC's comment on the Preliminary Assessment Guide for Community Priority Assessment <https://icann-community.atlassian.net/wiki/spaces/alacpolicydev/pages/99162…> (Draft Evaluation Guide for Community Priority Evaluation – CPE). Upcoming public comments related to the Rules were also mentioned. Additional Reference Label Generation <https://www.icann.org/en/public-comment/proceeding/additional-reference-lab…> (Additional Reference Label Generation Rules and Related Updates) and the Report Preliminary Review of Reviews <https://www.icann.org/en/public-comment/upcoming-proceedings> (Review of Reviews Draft Report). *5. ICANN86 and other topics* Preparation for ICANN86 was one of the recurring themes during both meetings. Possible topics for future CPWG sessions were discussed and activities related to mitigating DNS abuse, considerations linked to human rights, global public interest and protection of data, as well as proposals for the plenary meetings <https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/979173388/I…> A brief report on the Contracting Parties Summit was also shared. held in Manchester, where issues related to abuse were discussed DNS, data protection, the Uniform DNS Resolution Policy Disputes (UDRP), digital sovereignty, and other technical and regulatory aspects. The possible use of artificial intelligence tools or automated agents in meetings, particularly from an accessibility perspective and session tracking. *6. Participation of LACRALO* During this period, LACRALO maintained participation in the CPWG, including participation linked to PDP1 on DNS Abuse Mitigation already a Proposed plenary session for ICANN86. Distribution by session attendance LACRALO: April 29, 2026: Total attendees: *65 participants* Total attendees *LACRALO 4 participants (1 ALAC Member)* May 6, 2026: Total attendees *36 participants* Total attendees *LACRALO 4 participants (3 ALAC Member)* Kind regards, Eunice Alejandra Pérez Coello ALS Internet Society Mexico Chapter Member of ALAC

1 0

ACES Nomination
by Lance Hinds May 12, 2026

May 12, 2026

Dear Amrita, I also wish to nominate Krislin Goulbourne from St. Vincent for the ACES initiative. She is an ICANN fellow and a member of the St. Vincent ISOC Chapter. For your information. -- Lance Hinds Chief Technology Officer BrainStreet Group 287 'C' Albert St. Georgetown Guyanarom This message contains information that may be privileged and/or confidential and is the property of BrainStreet Technologies or BrainStreet Learning. The information contained herein is intended only for the individual or entity to whom it is addressed and others authorized to receive it . If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or take any action in reliance to the contents of this information or any part thereof and it may be unlawful to do so. If you receive this message in error, please notify the sender immediately and delete all copies of this message from your system. BrainStreet Technologies or BrainStreet Learning are neither liable for the proper and complete transmission of the information contained in this communication nor any delay in its receipt.

1 0

ACES Nomination
by Lance Hinds May 12, 2026

May 12, 2026

Dear Staff, All I would like to nominate Shay McPherson to lead the Phishing Campaign on behalf of LACRALO. Shay is an ICANN fellow from Jamaica and participates as LACRALO. She can be reached at mcphersonshanelle(a)yahoo.com. For your information and guidance -- Lance Hinds Chief Technology Officer BrainStreet Group 287 'C' Albert St. Georgetown Guyana This message contains information that may be privileged and/or confidential and is the property of BrainStreet Technologies or BrainStreet Learning. The information contained herein is intended only for the individual or entity to whom it is addressed and others authorized to receive it . If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or take any action in reliance to the contents of this information or any part thereof and it may be unlawful to do so. If you receive this message in error, please notify the sender immediately and delete all copies of this message from your system. BrainStreet Technologies or BrainStreet Learning are neither liable for the proper and complete transmission of the information contained in this communication nor any delay in its receipt.

2 1

**REMINDER - TOMORROW** Meeting invitation: At-Large Webinar: At-Large Meets ICANN Contractual Compliance and NetBeacon Institute Tuesday, 12 May 2026 at 13:00 UTC
by ICANN At-Large Staff May 11, 2026

May 11, 2026

[cid:image001.png@01DCE13E.33048B30] Dear All, You are invited to participate in this At-Large Webinar: At-Large Meets ICANN Contractual Compliance and NetBeacon Institute on Tuesday, 12 May 2026 at 13:00 UTC for 75 mins, to inform the At-Large in shaping its agenda to combat against DNS Abuse. DNS Abuse mitigation remains as a key focus area for the ALAC and At-Large community. It is generally accepted that DNS Abuse cannot be eliminated. However, it is also clear that it can be mitigated, and such mitigation efforts may take many forms and are often driven by various parties either working collaboratively or complementarily to bring about impact to protect end users against harm perpetrated by malicious domain name registrations. In prior meetings with the Security, Stability, and Resiliency team under the ICANN Office of the Chief Technology Officer (OCTO-SSR)*, the At-Large learned about the OCTO-SSR’s scope, research and tools in DNS Abuse mitigation. At this webinar, the ALAC and At-Large community will hear from ICANN Contractual Compliance and the NetBeacon Institute to understand their respective roles and work in support of DNS Abuse mitigation. It is aimed at informing a discussion on what efforts the ALAC and At-Large community should focus on in this area. Join us to learn more and to offer your input to our agenda on DNS Abuse mitigation! *The At-Large met with OCTO-SSR at – * The 26 February 2026 At-Large Meets OCTO-SSR Webinar: ICANN83 ALAC-OCTO Joint Session Recap<https://icann-community.atlassian.net/wiki/x/AgD-Mw> on an introduction to OCTO-SSR and its work; * The 11 March 2026 ALAC-OCTO Session at ICANN85, Mumbai<https://icann85.sched.com/event/2Gwml/joint-session-alac-and-octo> to further understand the work of OCTO-SSR, including some new initiatives; and – which, together with this webinar, form part of the DNS Abuse Mitigation Capacity Development Track in the FY2026 At-Large Capacity Development Initiatives<https://docs.google.com/document/d/1Hnv5EnPAOu99Narg13yTc1kOjozDArg_m6g_KQy…> Interpretation in English, French, and Spanish. For other times: Click Here [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/375ze35n__;!!PtGJab4!45hmh-V…> The agenda and call details can be found at: https://icann-community.atlassian.net/wiki/x/VgifQQ Zoom Registration: https://icann.zoom.us/meeting/register/ISQaCMwfRwiLjOdn8h_kkg#/registration You must register to join. Password: #gpif2026! Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org>

1 0

(no subject)
by Lance Hinds May 11, 2026

May 11, 2026

Dear Colleagues, By now all of you should have been notified that the election process has started and will be effect until the 15th. I urge all to participate fully in choosing the candidate from this region that can serve and serve with distinction on the ALAC. I will ask staff to provide the links for the Statements of Interest for review. It would have been helpful and encouraging for a larger turnout at the Meet the Candidates session, but again, the information about the candidates will be made available to help with the decision making process. Lance Hinds Chief Technology Officer BrainStreet Group 287 'C' Albert St. Georgetown Guyana This message contains information that may be privileged and/or confidential and is the property of BrainStreet Technologies or BrainStreet Learning. The information contained herein is intended only for the individual or entity to whom it is addressed and others authorized to receive it . If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or take any action in reliance to the contents of this information or any part thereof and it may be unlawful to do so. If you receive this message in error, please notify the sender immediately and delete all copies of this message from your system. BrainStreet Technologies or BrainStreet Learning are neither liable for the proper and complete transmission of the information contained in this communication nor any delay in its receipt.

1 0

Fwd: [At-Large] Re: [Ext] Imp: ACES Phishing Campaign: Please nominate a minimum of two RALO leads from the RALO I 8 May
by Alejandro Pisanty May 11, 2026

May 11, 2026

Hi, it seems there is some work going on of which LACRALO has not yet nominated representatives. I haven't even seen a call for volunteers or any other selection process. Please read the message from Gisella, tell us what is going on and what is needed, and get some proper action going, whoever is (supposed to be) in charge, Chair, Secretariat, whoever. It looks like dereliction of duty; it it is, it must be remedied, if it isn't, it must be explained (and remedied.) If the information and calls have been shared and I have missed them please repost. Alejandro Pisanty ---------- Forwarded message --------- From: Gisella Gruber via At-Large <at-large(a)icann.org> Date: Sat, May 9, 2026 at 2:21 AM Subject: [At-Large] Re: [Ext] Imp: ACES Phishing Campaign: Please nominate a minimum of two RALO leads from the RALO I 8 May To: Amrita Choudhury <amritachoudhury(a)ccaoi.in>, RALO Leadership < secretariat(a)atlarge-lists.icann.org>, Hadia Elminiawi <helminiawi(a)gmail.com>, Greg Shatan [ALAC] <gregshatanalac(a)gmail.com>, Frédéric Taes <ftaes(a)tsf.be>, brainstreetceo(a)gmail.com <brainstreetceo(a)gmail.com> Cc: at-large(a)icann.org <at-large(a)icann.org>, ICANN At-Large Staff < staff(a)atlarge.icann.org> Dear All, Please see volunteers so far: https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/1107394582/… NOTE – NO volunteers yet from LACRALO. Thank you. Kind regards, Gisella *From: *Amrita Choudhury <amritachoudhury(a)ccaoi.in> *Date: *Tuesday, 5 May 2026 at 11:44 *To: *RALO Leadership <secretariat(a)atlarge-lists.icann.org>, Hadia Elminiawi <helminiawi(a)gmail.com>, "Greg Shatan [ALAC]" < gregshatanalac(a)gmail.com>, Frédéric Taes <ftaes(a)tsf.be>, Lance Hinds < brainstreetceo(a)gmail.com> *Cc: *"at-large(a)icann.org" <at-large(a)icann.org>, At-Large Staff < staff(a)atlarge.icann.org> *Subject: *[Ext] Imp: ACES Phishing Campaign: Please nominate a minimum of two RALO leads from the RALO I 8 May Dear RALO Chairs, On behalf of the ALAC Community Engagement Subcommittee (ACES), we request you to nominate a minimum of two persons (maximum of five) as the RALO lead who will be responsible for leading the ACES Phishing Campaign. It is preferred that the nominated persons can understand English as the module will be rolled out in English first. The *deadline to nominate is 8 May 2026.* The ACES team will provide training and a toolkit to the nominated RALO leads, who in turn will train interested members of your RALO to organize community-level training sessions. The RALO leads will also be responsible for driving the phishing campaign at the RALO level and coordinating with the ACES team. We look forward to the nominations and will be happy to respond to any questions or queries you may have. *Please send the RALO nomination list to staff(a)atlarge.icann.org <staff(a)atlarge.icann.org> **with a copy to me and Jonathan.* Regards, Amrita _______________________________________________ At-Large mailing list -- at-large(a)icann.org To unsubscribe send an email to at-large-leave(a)icann.org At-Large Official Site: http://atlarge.icann.org _______________________________________________ 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. -- - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty Facultad de Química UNAM Av. Universidad 3000, 04510 Mexico DF Mexico +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Unete al grupo UNAM en LinkedIn, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---->> Unete a ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . .

2 4

ACTION: ALAC Objections Small Team – Membership Refresh and Call for Members to RALOs- Respond by Tuesday, 12 May at 23:00 UTC
by ICANN At-Large Staff May 10, 2026

May 10, 2026

Dear ALAC Objections Small Team Members and RALOs, As part of the ongoing work of the At-Large Small Team on the ALAC Objection Procedure<https://icann-community.atlassian.net/wiki/spaces/atlarge/pages/99700585/At…> for the Next Round, we are conducting a membership refresh and inviting new members to join the team. Current team members are kindly requested to confirm whether they wish to remain members of the Small Team. For reference, please see the current membership table included on the team’s wiki page : https://icann-community.atlassian.net/wiki/x/aU-xBQ We also invite members from all RALOs who are interested in this work to join the team. Objective and Tasks of the Team With the New gTLD Program: 2026 Round launched, the ALAC Small Team on Objections is focused on: * Updating the procedures for filing comments and objections based on changes and updated information in the 2026 Applicant Guidebook; * Developing outreach materials for the At-Large Community, including: * text encouraging participation in the At-Large gTLD Applications Review Group (gARG); and * guidance on what the At-Large Community can do during the Application Comment Period and Objection Period; * Conducting outreach during At-Large calls and at ICANN85 and ICANN86. * Note: the Objections Small Group will run through Autumn 2026 Please let us know by Tuesday, 12 May at 23:00 UTC whether: * you wish to remain a member of the team; or * you would like to join the team as a new member. Thank you very much! Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<http://atlarge.icann.org/> [signature_4211409830]

1 0

LACRALO Monthly Call
by ICANN Policy Calendar May 8, 2026

May 8, 2026

Dear All, The next LACRALO Monthly Call is scheduled for Monday, 18 May 2026 at 23:00 UTC for 90 minutes. Spanish and Portuguese interpretations will be provided (subject to availability). For other times: Click here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=LACRALO+Monthly+C…> Please note that the agenda and call details can be found at (to be updated): https://icann-community.atlassian.net/wiki/x/AQD7QQ Wiki workspace: https://community.icann.org/x/NJQi Zoom Link: https://icann.zoom.us/j/92546398435?pwd=q2Xk9GGTycd4ct7LadZR2VLwbLJIMf.1 Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org/>

1 0

Meeting Invitation: LACRALO Monthly Call on Monday, 18 May 2026 at 23:00 UTC for 90 minutes
by ICANN At-Large Staff May 8, 2026

May 8, 2026

Dear All, The next LACRALO Monthly Call is scheduled for Monday, 18 May 2026 at 23:00 UTC for 90 minutes. Spanish, French, and Portuguese interpretations will be provided (subject to availability). For other times: Click here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=LACRALO+Monthly+C…> Please note that the agenda and call details can be found at (to be updated): https://icann-community.atlassian.net/wiki/x/AQD7QQ Wiki workspace: https://community.icann.org/x/NJQi Zoom Link: https://icann.zoom.us/j/92546398435?pwd=q2Xk9GGTycd4ct7LadZR2VLwbLJIMf.1 Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org/>

1 0

LACRALO Monthly Call
by ICANN Policy Calendar May 8, 2026

May 8, 2026

Dear All, The next LACRALO Monthly Call is scheduled for Monday, 18 May 2026 at 23:00 UTC for 90 minutes. Spanish, French, and Portuguese interpretations will be provided (subject to availability). For other times: Click here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=LACRALO+Monthly+C…> Please note that the agenda and call details can be found at (to be updated): https://icann-community.atlassian.net/wiki/x/AQD7QQ Wiki workspace: https://community.icann.org/x/NJQi Zoom Link: https://icann.zoom.us/j/92546398435?pwd=q2Xk9GGTycd4ct7LadZR2VLwbLJIMf.1 Thank you. Kind Regards, ICANN Policy Staff in support of the At-Large Community www.icann.org<http://www.icann.org/>

1 0