friendly amendment to the Option 4 IGO/INGO
Dear Councillors In conversation with some of you I have expressed some unease about the TLD applicant not seeing displayed properly warnings about the existence of the Reserved list, whilst filling in the application form. Links may not be visible enough. I like to propose a small friendly amendment to the Option 4 text, under a) - The application process must prominently display and clearly communicate this List so that TLD applicants are fully aware of its existence and implications prior to filing its choice of the TLD string. b) That Org should contact the relevant protected organizations after String Confirmation Day to ensure they are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, and are aware of their options for bringing formal Objection or seeking support of the GAC. c) That Org should also contact the GAC after String Confirmation Day to ensure that the GAC are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, in order that GAC members may consider whether any Early Warning(s) or GAC Consensus Advice would be appropriate. d) We also would encourage the GAC to contact the relevant protected organizations to ensure that they are aware of the applied-for strings and can decide whether to utilize any challenge methods outlined in the AGB. e) That Org should also notify the applicant of the confusingly similar string, and give them the option to withdraw for an appropriate refund. f) The GNSO Council encourages the Board to ensure that Org puts appropriate mechanisms in place to safeguard the strings on the Reserved Names List, pending the conclusion of the Objection period, the outcome of any filed Objection, the outcome of any GAC Consensus Advice against a confusingly similar string, or confirmation from the GAC that it does not intend to issue Consensus Advice. Such an appropriate mechanism might include placing any confusingly similar application on hold, pending such resolution. Hope this is an acceptable friendly amendment. best Desiree — NCA CPH Councillor
Thanks Desiree. I hope the amendment is accepted. The inclusion of “Such an appropriate mechanism might include placing any confusingly similar application on hold, pending such resolution” will allow me to vote yes. Best, Paul From: desiree-me via council <council@icann.org> Sent: Tuesday, October 28, 2025 1:05 PM To: council@gnso icann. org <council@gnso.icann.org> Subject: [council] friendly amendment to the Option 4 IGO/INGO Dear Councillors In conversation with some of you I have expressed some unease about the TLD applicant not seeing displayed properly warnings about the existence of the Reserved list, whilst filling in the application form. Links may not be visible enough. I like to propose a small friendly amendment to the Option 4 text, under a) 1. The application process must prominently display and clearly communicate this List so that TLD applicants are fully aware of its existence and implications prior to filing its choice of the TLD string. b) That Org should contact the relevant protected organizations after String Confirmation Day to ensure they are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, and are aware of their options for bringing formal Objection or seeking support of the GAC. c) That Org should also contact the GAC after String Confirmation Day to ensure that the GAC are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, in order that GAC members may consider whether any Early Warning(s) or GAC Consensus Advice would be appropriate. d) We also would encourage the GAC to contact the relevant protected organizations to ensure that they are aware of the applied-for strings and can decide whether to utilize any challenge methods outlined in the AGB. e) That Org should also notify the applicant of the confusingly similar string, and give them the option to withdraw for an appropriate refund. f) The GNSO Council encourages the Board to ensure that Org puts appropriate mechanisms in place to safeguard the strings on the Reserved Names List, pending the conclusion of the Objection period, the outcome of any filed Objection, the outcome of any GAC Consensus Advice against a confusingly similar string, or confirmation from the GAC that it does not intend to issue Consensus Advice. Such an appropriate mechanism might include placing any confusingly similar application on hold, pending such resolution. Hope this is an acceptable friendly amendment. best Desiree — NCA CPH Councillor This email originated from outside the firm. Please use caution.
Thank you for your thoughtful suggestion Desiree. I can happily accept that as friendly. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:ignored-in-diff-414B7E92-CF56-47B5-B28E-CD55E9601FCB] <https://comlaude.com> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0> ________________________________ From: desiree-me via council <council@icann.org> Sent: Tuesday, October 28, 2025 6:04:40 PM To: council@gnso icann. org <council@gnso.icann.org> Subject: [council] friendly amendment to the Option 4 IGO/INGO Dear Councillors In conversation with some of you I have expressed some unease about the TLD applicant not seeing displayed properly warnings about the existence of the Reserved list, whilst filling in the application form. Links may not be visible enough. I like to propose a small friendly amendment to the Option 4 text, under a) 1. The application process must prominently display and clearly communicate this List so that TLD applicants are fully aware of its existence and implications prior to filing its choice of the TLD string. b) That Org should contact the relevant protected organizations after String Confirmation Day to ensure they are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, and are aware of their options for bringing formal Objection or seeking support of the GAC. c) That Org should also contact the GAC after String Confirmation Day to ensure that the GAC are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, in order that GAC members may consider whether any Early Warning(s) or GAC Consensus Advice would be appropriate. d) We also would encourage the GAC to contact the relevant protected organizations to ensure that they are aware of the applied-for strings and can decide whether to utilize any challenge methods outlined in the AGB. e) That Org should also notify the applicant of the confusingly similar string, and give them the option to withdraw for an appropriate refund. f) The GNSO Council encourages the Board to ensure that Org puts appropriate mechanisms in place to safeguard the strings on the Reserved Names List, pending the conclusion of the Objection period, the outcome of any filed Objection, the outcome of any GAC Consensus Advice against a confusingly similar string, or confirmation from the GAC that it does not intend to issue Consensus Advice. Such an appropriate mechanism might include placing any confusingly similar application on hold, pending such resolution. Hope this is an acceptable friendly amendment. best Desiree — NCA CPH Councillor ________________________________ 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<https://comlaude.com>
Great work, Desiree! Best, Thomas Sent from my mobile device. Please excuse typos and brevity. ________________________________ Von: Susan Payne via council <council@icann.org> Gesendet: Tuesday, October 28, 2025 6:59:16 PM An: desiree-me <desiree-me@protonmail.com>; council@gnso icann. org <council@gnso.icann.org> Betreff: [council] Re: friendly amendment to the Option 4 IGO/INGO Thank you for your thoughtful suggestion Desiree. I can happily accept that as friendly. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:ignored-in-diff-414B7E92-CF56-47B5-B28E-CD55E9601FCB] <https://comlaude.com> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADw_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADw_RQA0> ________________________________ From: desiree-me via council <council@icann.org> Sent: Tuesday, October 28, 2025 6:04:40 PM To: council@gnso icann. org <council@gnso.icann.org> Subject: [council] friendly amendment to the Option 4 IGO/INGO Dear Councillors In conversation with some of you I have expressed some unease about the TLD applicant not seeing displayed properly warnings about the existence of the Reserved list, whilst filling in the application form. Links may not be visible enough. I like to propose a small friendly amendment to the Option 4 text, under a) 1. The application process must prominently display and clearly communicate this List so that TLD applicants are fully aware of its existence and implications prior to filing its choice of the TLD string. b) That Org should contact the relevant protected organizations after String Confirmation Day to ensure they are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, and are aware of their options for bringing formal Objection or seeking support of the GAC. c) That Org should also contact the GAC after String Confirmation Day to ensure that the GAC are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, in order that GAC members may consider whether any Early Warning(s) or GAC Consensus Advice would be appropriate. d) We also would encourage the GAC to contact the relevant protected organizations to ensure that they are aware of the applied-for strings and can decide whether to utilize any challenge methods outlined in the AGB. e) That Org should also notify the applicant of the confusingly similar string, and give them the option to withdraw for an appropriate refund. f) The GNSO Council encourages the Board to ensure that Org puts appropriate mechanisms in place to safeguard the strings on the Reserved Names List, pending the conclusion of the Objection period, the outcome of any filed Objection, the outcome of any GAC Consensus Advice against a confusingly similar string, or confirmation from the GAC that it does not intend to issue Consensus Advice. Such an appropriate mechanism might include placing any confusingly similar application on hold, pending such resolution. Hope this is an acceptable friendly amendment. best Desiree — NCA CPH Councillor ________________________________ 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<https://comlaude.com>
Hello all, Since Nacho seconded this, he will also need to accept. Thank you. Kind regards, Terri Policy Team Supporting the GNSO From: Susan Payne via council <council@icann.org> Reply-To: Susan Payne <susan.payne@comlaude.com> Date: Tuesday, October 28, 2025 at 8:23 PM To: desiree-me <desiree-me@protonmail.com>, "council@gnso icann. org" <council@gnso.icann.org> Subject: [council] Re: friendly amendment to the Option 4 IGO/INGO Thank you for your thoughtful suggestion Desiree. I can happily accept that as friendly. Susan Susan Payne Head of Legal Policy Com Laude T +44 (0) 20 7421 8250 Ext 255 [cid:image001.png@01DC485A.942F8130] [comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com__;!!PtGJab4!8aZzVsJjdmGZN62K...> 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_...> ________________________________ From: desiree-me via council <council@icann.org> Sent: Tuesday, October 28, 2025 6:04:40 PM To: council@gnso icann. org <council@gnso.icann.org> Subject: [council] friendly amendment to the Option 4 IGO/INGO Dear Councillors In conversation with some of you I have expressed some unease about the TLD applicant not seeing displayed properly warnings about the existence of the Reserved list, whilst filling in the application form. Links may not be visible enough. I like to propose a small friendly amendment to the Option 4 text, under a) 1. The application process must prominently display and clearly communicate this List so that TLD applicants are fully aware of its existence and implications prior to filing its choice of the TLD string. b) That Org should contact the relevant protected organizations after String Confirmation Day to ensure they are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, and are aware of their options for bringing formal Objection or seeking support of the GAC. c) That Org should also contact the GAC after String Confirmation Day to ensure that the GAC are aware of any applied-for strings that could be considered confusingly similar to those on the Reserved Names list, in order that GAC members may consider whether any Early Warning(s) or GAC Consensus Advice would be appropriate. d) We also would encourage the GAC to contact the relevant protected organizations to ensure that they are aware of the applied-for strings and can decide whether to utilize any challenge methods outlined in the AGB. e) That Org should also notify the applicant of the confusingly similar string, and give them the option to withdraw for an appropriate refund. f) The GNSO Council encourages the Board to ensure that Org puts appropriate mechanisms in place to safeguard the strings on the Reserved Names List, pending the conclusion of the Objection period, the outcome of any filed Objection, the outcome of any GAC Consensus Advice against a confusingly similar string, or confirmation from the GAC that it does not intend to issue Consensus Advice. Such an appropriate mechanism might include placing any confusingly similar application on hold, pending such resolution. Hope this is an acceptable friendly amendment. best Desiree — NCA CPH Councillor ________________________________ 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!8aZzVsJjdmGZN62K...>
participants (6)
-
desiree-me -
Nacho Amadoz -
Paul McGrady -
Susan Payne -
Terri Agnew -
Thomas Rickert | rickert.law