Hi Anne, To be clear, the consent agenda item is only in reference to the GNSO recommendations that are proposed to be non-adopted. Those recommendation reference the TMCH and rely upon a pre-registration notice whereas the implementation in progress relies upon a post-registration notification; this is why the pending GNSO recommendations appear no longer be necessary. The comments you’ve attributed to Jeff should not be comingled with the consent agenda item. However, in case you’re curious, Jeff’s point was that the post-registration notice will go to an affected IGO that is on the GAC list, which may be broader than what the latest EPDP defined as an IGO Complainant. Staff agrees with this assessment and has noted the point for implementation. Best, Steve From: Anne ICANN <anneicanngnso@gmail.com> Date: Thursday, July 31, 2025 at 11:19 AM To: Steve Chan <steve.chan@icann.org> Cc: Mary Wong <mary.wong@icann.org>, "council@icann.org" <council@icann.org>, GNSO-Secs <gnso-secs@icann.org> Subject: [Ext] Re: [council] Re: Meeting Invitation | GNSO Council discussion with Board Caucus on IGO Issues | Monday, 28 July 2025 Thanks Steve. Hopefully all voting Councilors have time to review this with their respective interest groups. I know Jeff Neuman made a comment that not all acronyms entered into the TMCH per the GAC request should be eligible for UDRP and URS remedies but I have no idea why and I don't know the background. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Tue, Jul 29, 2025 at 3:42 PM Steve Chan <steve.chan@icann.org<mailto:steve.chan@icann.org>> wrote: Hi Anne, Not Mary, but hopefully I can answer your question. I will take them in reverse order. The reason that Recs 3.3.5 and 3.3.7 from the PDP on Protection of IGO and INGO Identifiers in All gTLDs have been superseded can be found in today’s slides here https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/... [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/spaces...>. But in brief, the combination of the permanent post-registration notification system, plus the implementation of the Council and Board approved curative rights policy recommendations for IGOs, obviates the need for Recs 3.3.5 and 3.3.7. I have chatted with Council leadership and they believe this topic should be on the consent agenda for the August meeting in order to confirm that the Council is supportive of the Board non-adopting the two recommendations and that the Council does not intend to develop Supplemental Recommendations. This presumes of course that as Councilors check in with their appointing organizations, they are indeed supportive of this approach. Best, Steve From: Anne ICANN via council <council@icann.org<mailto:council@icann.org>> Reply-To: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Date: Monday, July 28, 2025 at 2:48 PM To: Mary Wong <mary.wong@icann.org<mailto:mary.wong@icann.org>> Cc: "council@icann.org<mailto:council@icann.org>" <council@icann.org<mailto:council@icann.org>>, GNSO-Secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Re: Meeting Invitation | GNSO Council discussion with Board Caucus on IGO Issues | Monday, 28 July 2025 Mary - can we get this on the agenda for the Council meeting and review the procedural status of the Recommendations that the Board intends to reject? Can Chris Disspain or a Council Liaison speak to this at Council in relation to the fact that these Recommendations are superseded.? Councilors may need to brief their groups in order to resolve this in August. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Mon, Jul 28, 2025 at 1:08 PM Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> wrote: Thanks Mary. On an Executive Summary level, are we saying that the 2012-13 Recommendations have been superseded by more recent policy work? (Sorry I don't have a lot of background on this one.) Does the Board have to reverse any prior Board-adopted policy Recommendations or not? Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Mon, Jul 28, 2025 at 9:33 AM Mary Wong via council <council@icann.org<mailto:council@icann.org>> wrote: Hello Susan and everyone, I realize we should have clarified the reason for this meeting earlier, I am sorry for that oversight! The purpose of the call is for the Board’s IGO Caucus Group (comprising Becky Burr, Chris Buckridge, Chris Chapman, Christian Kaufmann and Leon Sanchez – though I am not sure that they will all be on the call today) to discuss how the Board plans to close out the final few outstanding policy recommendations stemming from the very first IGO-related PDP that the GNSO conducted between 2012-2013. This is the last open item of policy work on second-level IGO protections, and given that implementation of the latest (and third) IGO-related PDP is progressing well – viz., implementation of the IGO Curative Rights policy recommendations – the Board believes it is timely to try to conclude the longstanding work on this topic. For your easy reference, the specific policy recommendations from 2013 that remain open and that will be the subject of the call today are the following: * Recommendation 3.3.5: Second-Level protections of only Exact Match, Acronym Scope 2 identifiers of the International Governmental Organizations are bulk added as a single list to the Trademark Clearinghouse (TMCH) * Recommendation 3.3.7: International Governmental Organizations Scope 2 identifiers, if added to the TMCH, allowed to participate in 90 Day Claims Notification phase of each new gTLD launch for Second-Level registrations NOTE: IGO "Scope 2 Identifiers" were defined in the PDP as meaning the acronyms in two languages of those IGOs on the GAC list as of November 2013 We have not prepared any specific background materials for the Council for this call. However, should you wish to have the background documents handy, here are some links that I hope are helpful: * Regarding the original IGO-INGO PDP (2012-2013): * PDP Final Report (November 2013), covering recommendations for top and second-level protections for the Red Cross, International Olympic Committee, IGOs and international non-governmental organizations (INGOs): https://gnso.icann.org/sites/default/files/filefield_42639/igo-ingo-final-10... [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/filefi...> * GNSO Council resolution (November 2013), adopting some of the final recommendations: https://gnso.icann.org/en/council/resolutions/1999-2019#20131120-2 [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/en/council/resolutions/199...> * Regarding the scope of the proposed post-registration-only notification system for IGOs: * Board resolution (October 2020): https://www.icann.org/en/board-activities-and-meetings/materials/approved-re... * Regarding the scope of Curative Rights protections for IGOs: * Board resolution (April 2023) adopting the GNSO policy recommendations from the second (IGO-INGO Access to Curative Rights Mechanisms) and the third GNSO PDP (EPDP on Specific Curative Rights Protections for IGOs): https://www.icann.org/en/board-activities-and-meetings/materials/approved-re... * Board resolution (May 2023) accepting GAC advice to maintain the temporary reservations for IGO acronyms at the second level until implementation of the Curative Rights policy recommendations are complete: https://www.icann.org/en/board-activities-and-meetings/materials/approved-re... * Status of and progress on the Curative Rights policy implementation: https://icann-community.atlassian.net/wiki/spaces/ICRIRT/overview [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/spaces...> We will add these links to the relevant GNSO Council wiki page for this meeting as well (https://icann-community.atlassian.net/wiki/spaces/gnsocouncilmeetings/pages/... [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/spaces...>). Thank you! Cheers Mary From: Susan Payne via council <council@icann.org<mailto:council@icann.org>> Reply-To: Susan Payne <susan.payne@comlaude.com<mailto:susan.payne@comlaude.com>> Date: Monday, July 28, 2025 at 4:50 AM To: Terri Agnew <terri.agnew@icann.org<mailto:terri.agnew@icann.org>>, "council@icann.org<mailto:council@icann.org>" <council@icann.org<mailto:council@icann.org>> Cc: GNSO-Secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Re: Meeting Invitation | GNSO Council discussion with Board Caucus on IGO Issues | Monday, 28 July 2025 Hi Terri, is there anything we should review in advance of this meeting? Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01DC0233.0CBDDF70] [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!4SdDnGtCkzfvGZJ...> Follow us on LinkedIn [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_...> and YouTube [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_...> Error! Filename not specified. From: Terri Agnew via council <council@icann.org<mailto:council@icann.org>> Sent: 22 July 2025 19:05 To: council@icann.org<mailto:council@icann.org> Cc: GNSO-Secs <gnso-secs@icann.org<mailto:gnso-secs@icann.org>> Subject: [council] Meeting Invitation | GNSO Council discussion with Board Caucus on IGO Issues | Monday, 28 July 2025 Dear all, The GNSO Council discussion with Board Caucus on IGO Issues is scheduled on Monday, 28 July 2025 at 21:00 UTC for 60 minutes. This meeting will be recorded for those who are unable to make it. Before joining the call: Please be sure you have read the Expected Standards of Behavior <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources...> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017-...> Visit the Wiki Agenda page: https://icann-community.atlassian.net/wiki/x/BwBDFw [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/BwBD...> Check your time zone: https://tinyurl.com/2v9kkjuh [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2v9kkjuh__;!!PtGJab4!4SdDnGtC...> Please click the link below to join the webinar: https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/j/91048235847?pwd=bmEHjk0uY...> Passcode: mkt7*ULa9b If joining Zoom via Zoom App the following will be required: Webinar ID: 910 4823 5847 Passcode: 9213420189 Or One tap mobile : +13462487799,,91048235847#,,,,*9213420189# US (Houston) +16699006833,,91048235847#,,,,*9213420189# US (San Jose) If you are joining via audio only: International numbers available: https://icann.zoom.us/u/a6JrPP2u5 [icann.zoom.us]<https://urldefense.com/v3/__https:/icann.zoom.us/u/a6JrPP2u5__;!!PtGJab4!4Sd...> Observers are welcome to join; they will be in a read-only and listen-only mode. Thank you. Kind regards, Terri Policy Team Supporting the GNSO ________________________________ The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company registered in England and Wales with company number 10689074 and registered office at 28 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see www.comlaude.com [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!4SdDnGtCkzfvGZJ...> _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto:council-leave@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.
