String Similarity Assessment of Reserved Names
Hello IRT, We have just published a paper concerning the String Similarity Assessment of Reserved Names on the wiki page of meeting #158a: https://icann-community.atlassian.net/wiki/x/AQB3Gw Sarmad will go through it during the call, but it would be appreciated if you could already review it and provide any input you may have on list. Many thanks, Elisa
Hi Elisa and Sarmad, Thanks for summarising the issue and offering two potential solutions. However, I disagree with ICANN's conclusion that we should adopt option 2, as that would be creating new policy. Option 2 proposes to: * In the case of contention between an IGO/RC/IOC applicant and a non-IGO/RC/IOC applicant, give priority to the IGO/RC/IOC applicant. This would create an entirely new method of priority for resolving contention. * Include the Reserved Names list strings in the standard string similarity review performed by the ICANN evaluators. This is a reversal of the policy from the 2012 round, when Strings Ineligible for Delegation (as Reserved Names were known at the time) were explicitly excluded from the string similarity review. The paper asserts that "...based on remaining recommendations in SubPro and IDN EPDP Phase 1, ICANN proposes to move forward with option 2...". However, I don't believe there are any policy recommendations in either SubPro or the IDN EPDP Phase 1 which allow for either of the above rules. The original policy from the 2012 round AGB states in section 2.2.1.2.3 that: "the following [strings ineligible for delegation] names are prohibited from delegation as gTLDs in the initial application round. Future application rounds may differ according to consideration of further policy advice. These names are not being placed on the Top-Level Reserved Names List, and thus are not part of the string similarity review conducted for names on that list." The SubPro final report affirmed the continuation of the 2012 rules on this topic in Affirmation 24.2: "...the Working Group affirms the standard used in the String Similarity Review from the 2012 round to determine whether an applied-for string is "similar" to any existing TLD, any other applied-for strings, Reserved Names, and in the case of 2-character IDNs, any single character or any 2-character ASCII string." Note it does not list "strings ineligible for delegation" (i.e. the IGO/RC/IOC names) as a type of string subject to string similarity review. Similarly, section 4.4.1 of the IDN EPDP phase 1 report is clear on the types of name which are subject to string similarity review and "strings ineligible for delegation" are not among them: "If an applied-for primary gTLD string or any of its variant label(s) is confusingly similar to an existing gTLD, an existing ccTLD, a New gTLD Program Reserved Name*, a two-character ASCII string, or any of the variant label(s) of the aforementioned categories of strings, the entire variant label set of the applied-for primary gTLD string will be ineligible to proceed in the application process." Thus, implementing the two above rules proposed by option 2 would be creating new policy, which is not the job of the IRT. Whereas option 2 would create new policy, the path outlined in option 1 is consistent with existing policy. Therefore, option 1 is the only viable option outlined in your paper. Please note that both the SubPro and EPDP final reports use the old definition of "Reserved Names", which is a little confusing. In those reports, the relevant term to describe the IOC/RC/IOC names is "strings ineligible for delegation". For clarity and completeness you may want to make this clear in the annex of your paper. * Definitions of New gTLD Program Reserved Names and Strings Ineligible for Delegation, used by the IDN EPDP per their Final Report: * New gTLD Program Reserved Name: A string that is reserved to maintain the exclusive rights to the names of ICANN, its bodies, or essential related functions of ICANN and IANA. For a full list of New gTLD Program Reserved Names, see Section 2.2.1.2.1 of the 2012 Applicant Guidebook. In addition, the SubPro PDP recommended adding "PTI" to the New gTLD Program Reserved Names list. * String Ineligible for Delegation: A string that is ineligible for delegation in order to provide special protections at the top-level and second-level for the names and acronyms of intergovernmental organizations (IGOs) and international non-governmental organizations (INGOs) which receive protections under treaties and statutes across multiple jurisdictions. Those organizations specifically include the Red Cross/Red Crescent Movement (RCRC) and the International Olympic Committee (IOC). I hope that makes sense. Please shout if anything in my explanation is unclear. Kind regards, Ashley Ashley Roberts Head of New TLD Consultancy Com Laude T +44 (0) 20 7421 8250 Ext 264 [cid:image001.png@01DC20EA.26D71C20] <https://comlaude.com/> Follow us on LinkedIn<https://t-uk.xink.io/Tracking/Index/pRkAAGVfAADD_RQA0> and YouTube<https://t-uk.xink.io/Tracking/Index/bhkAAGVfAADD_RQA0> From: Elisa Busetto via SubPro-IRT <subpro-irt@icann.org> Sent: 05 September 2025 12:10 To: subpro-irt@icann.org Subject: [SubPro-IRT] String Similarity Assessment of Reserved Names Hello IRT, We have just published a paper concerning the String Similarity Assessment of Reserved Names on the wiki page of meeting #158a: https://icann-community.atlassian.net/wiki/x/AQB3Gw Sarmad will go through it during the call, but it would be appreciated if you could already review it and provide any input you may have on list. Many thanks, Elisa ________________________________ 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/>
Thank you Elisa. Could you please: 1. Provide the policy Recommendation language as adopted by the Board in relation to this issue, and 2. Clarify whether there is any relevant Board-created policy on IGO names being eligible for delegation, e.g. in response to GAC Advice. Apologies for a lack of familiarity with the specifics on the policy recommendations. (I'm guessing Chris Disspain may have a good deal more background.) Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Fri, Sep 5, 2025 at 4:09 AM Elisa Busetto via SubPro-IRT < subpro-irt@icann.org> wrote:
Hello IRT,
We have just published a paper concerning the String Similarity Assessment of Reserved Names on the wiki page of meeting #158a: https://icann-community.atlassian.net/wiki/x/AQB3Gw
Sarmad will go through it during the call, but it would be appreciated if you could already review it and provide any input you may have on list.
Many thanks,
Elisa _______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to subpro-irt-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.
Hi Anne, Thank you for your questions. We are discussing internally and will have a more substantive response for the meeting on Thursday. Thanks for your patience! Best, Elisa From: Anne ICANN <anneicanngnso@gmail.com> Date: Tuesday, 9 September 2025 at 00:57 To: Elisa Busetto <elisa.busetto@icann.org> Cc: "subpro-irt@icann.org" <subpro-irt@icann.org> Subject: [Ext] Re: [SubPro-IRT] String Similarity Assessment of Reserved Names Thank you Elisa. Could you please: 1. Provide the policy Recommendation language as adopted by the Board in relation to this issue, and 2. Clarify whether there is any relevant Board-created policy on IGO names being eligible for delegation, e.g. in response to GAC Advice. Apologies for a lack of familiarity with the specifics on the policy recommendations. (I'm guessing Chris Disspain may have a good deal more background.) Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Fri, Sep 5, 2025 at 4:09 AM Elisa Busetto via SubPro-IRT <subpro-irt@icann.org<mailto:subpro-irt@icann.org>> wrote: Hello IRT, We have just published a paper concerning the String Similarity Assessment of Reserved Names on the wiki page of meeting #158a: https://icann-community.atlassian.net/wiki/x/AQB3Gw [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQB3...> Sarmad will go through it during the call, but it would be appreciated if you could already review it and provide any input you may have on list. Many thanks, Elisa _______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org<mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave@icann.org<mailto:subpro-irt-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.
Thanks Elisa. It would be helpful to have a response on Wednesday, i.e. before the Thursday meeting. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Tue, Sep 9, 2025 at 7:36 AM Elisa Busetto <elisa.busetto@icann.org> wrote:
Hi Anne,
Thank you for your questions.
We are discussing internally and will have a more substantive response for the meeting on Thursday.
Thanks for your patience!
Best,
Elisa
*From: *Anne ICANN <anneicanngnso@gmail.com> *Date: *Tuesday, 9 September 2025 at 00:57 *To: *Elisa Busetto <elisa.busetto@icann.org> *Cc: *"subpro-irt@icann.org" <subpro-irt@icann.org> *Subject: *[Ext] Re: [SubPro-IRT] String Similarity Assessment of Reserved Names
Thank you Elisa. Could you please:
1. Provide the policy Recommendation language as adopted by the Board in relation to this issue, and
2. Clarify whether there is any relevant Board-created policy on IGO names being eligible for delegation, e.g. in response to GAC Advice.
Apologies for a lack of familiarity with the specifics on the policy recommendations. (I'm guessing Chris Disspain may have a good deal more background.)
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026
anneicanngnso@gmail.com
On Fri, Sep 5, 2025 at 4:09 AM Elisa Busetto via SubPro-IRT < subpro-irt@icann.org> wrote:
Hello IRT,
We have just published a paper concerning the String Similarity Assessment of Reserved Names on the wiki page of meeting #158a: https://icann-community.atlassian.net/wiki/x/AQB3Gw [icann-community.atlassian.net] <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQB3...>
Sarmad will go through it during the call, but it would be appreciated if you could already review it and provide any input you may have on list.
Many thanks,
Elisa
_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to subpro-irt-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.
Hi Anne, As noted in the recent email I sent to the IRT mailing list, I’ve updated the paper to include the relevant Board-adopted policy recommendations in the Annex. For ease of reference, here they are once more: Relevant Recommendations from the PDP Protection of IGO and INGO Identifiers in All gTLDs: Recommendation 3.1.1: * Top-Level protections of Exact Match, Full Name Scope 1 identifiers of the Red Cross Red Crescent Movement are placed in the Applicant Guidebook section 2.2.1.2.3, Strings “Ineligible for Delegation”. Recommendation 3.1.2: * For Red Cross Red Crescent Movement identifiers, if placed in the Applicant Guidebook as ineligible for delegation at the Top-Level, an exception procedure should be created for cases where a protected organization wishes to apply for their protected string at the Top-Level. Recommendation 3.2.1: * Top-Level protections of Exact Match, Full Name Scope 1 identifiers of the International Olympic Committee are placed in the Applicant Guidebook section 2.2.1.2.3, Strings “Ineligible for Delegation”. Recommendation 3.2.2: * For International Olympic Committee Identifiers, if placed in the Applicant Guidebook as ineligible for delegation at the Top-Level, an exception procedure should be created for cases where a protected organization wishes to apply for their protected string at the Top-Level. Recommendation 3.3.1: * Top-Level protections of Exact Match, Full Name Scope 1 identifiers of the International Governmental Organizations are placed in the Applicant Guidebook section 2.2.1.2.3, Strings “Ineligible for Delegation”. Recommendation 3.3.2: * For International Governmental Organizations Identifiers, if placed in the Applicant Guidebook as ineligible for delegation at the Top-Level, an exception procedure should be created for cases where a protected organization wishes to apply for their protected string at the Top-Level. Please let me know if you have any further questions. Thank you! Best, Michael From: Anne ICANN via SubPro-IRT <subpro-irt@icann.org> Reply-To: Anne ICANN <anneicanngnso@gmail.com> Date: Monday, September 8, 2025 at 3:57 PM To: Elisa Busetto <elisa.busetto@icann.org> Cc: "subpro-irt@icann.org" <subpro-irt@icann.org> Subject: [SubPro-IRT] Re: String Similarity Assessment of Reserved Names Thank you Elisa. Could you please: 1. Provide the policy Recommendation language as adopted by the Board in relation to this issue, and 2. Clarify whether there is any relevant Board-created policy on IGO names being eligible for delegation, e.g. in response to GAC Advice. Apologies for a lack of familiarity with the specifics on the policy recommendations. (I'm guessing Chris Disspain may have a good deal more background.) Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Fri, Sep 5, 2025 at 4:09 AM Elisa Busetto via SubPro-IRT <subpro-irt@icann.org<mailto:subpro-irt@icann.org>> wrote: Hello IRT, We have just published a paper concerning the String Similarity Assessment of Reserved Names on the wiki page of meeting #158a: https://icann-community.atlassian.net/wiki/x/AQB3Gw [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQB3...> Sarmad will go through it during the call, but it would be appreciated if you could already review it and provide any input you may have on list. Many thanks, Elisa _______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org<mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave@icann.org<mailto:subpro-irt-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.
Thanks Michael. Very much appreciated. I have replied to the other email. Renate, please note my regrets for the meeting today. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Wed, Sep 10, 2025 at 4:28 PM Michael Karakash <michael.karakash@icann.org> wrote:
Hi Anne,
As noted in the recent email I sent to the IRT mailing list, I’ve updated the paper to include the relevant Board-adopted policy recommendations in the Annex. For ease of reference, here they are once more:
*Relevant Recommendations from the PDP Protection of IGO and INGO Identifiers in All gTLDs:*
*Recommendation 3.1.1: *
- *Top-Level protections of Exact Match, Full Name Scope 1 identifiers of the Red Cross Red Crescent Movement are placed in the Applicant Guidebook section 2.2.1.2.3, Strings “Ineligible for Delegation”.*
*Recommendation 3.1.2: *
- *For Red Cross Red Crescent Movement identifiers, if placed in the Applicant Guidebook as ineligible for delegation at the Top-Level, an exception procedure should be created for cases where a protected organization wishes to apply for their protected string at the Top-Level.*
*Recommendation 3.2.1: *
- *Top-Level protections of Exact Match, Full Name Scope 1 identifiers of the International Olympic Committee are placed in the Applicant Guidebook section 2.2.1.2.3, Strings “Ineligible for Delegation”.*
*Recommendation 3.2.2: *
- *For International Olympic Committee Identifiers, if placed in the Applicant Guidebook as ineligible for delegation at the Top-Level, an exception procedure should be created for cases where a protected organization wishes to apply for their protected string at the Top-Level.*
*Recommendation 3.3.1: *
- *Top-Level protections of Exact Match, Full Name Scope 1 identifiers of the International Governmental Organizations are placed in the Applicant Guidebook section 2.2.1.2.3, Strings “Ineligible for Delegation”.*
*Recommendation 3.3.2: *
- *For International Governmental Organizations Identifiers, if placed in the Applicant Guidebook as ineligible for delegation at the Top-Level, an exception procedure should be created for cases where a protected organization wishes to apply for their protected string at the Top-Level.*
Please let me know if you have any further questions.
Thank you!
Best,
Michael
*From: *Anne ICANN via SubPro-IRT <subpro-irt@icann.org> *Reply-To: *Anne ICANN <anneicanngnso@gmail.com> *Date: *Monday, September 8, 2025 at 3:57 PM *To: *Elisa Busetto <elisa.busetto@icann.org> *Cc: *"subpro-irt@icann.org" <subpro-irt@icann.org> *Subject: *[SubPro-IRT] Re: String Similarity Assessment of Reserved Names
Thank you Elisa. Could you please:
1. Provide the policy Recommendation language as adopted by the Board in relation to this issue, and
2. Clarify whether there is any relevant Board-created policy on IGO names being eligible for delegation, e.g. in response to GAC Advice.
Apologies for a lack of familiarity with the specifics on the policy recommendations. (I'm guessing Chris Disspain may have a good deal more background.)
Anne
Anne Aikman-Scalese
GNSO Councilor
NomCom Non-Voting 2022-2026
anneicanngnso@gmail.com
On Fri, Sep 5, 2025 at 4:09 AM Elisa Busetto via SubPro-IRT < subpro-irt@icann.org> wrote:
Hello IRT,
We have just published a paper concerning the String Similarity Assessment of Reserved Names on the wiki page of meeting #158a: https://icann-community.atlassian.net/wiki/x/AQB3Gw [icann-community.atlassian.net] <https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQB3...>
Sarmad will go through it during the call, but it would be appreciated if you could already review it and provide any input you may have on list.
Many thanks,
Elisa
_______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org To unsubscribe send an email to subpro-irt-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.
Apologies noted, Anne. Thank you. Best, Renate From: Anne ICANN <anneicanngnso@gmail.com> Date: Thursday, 11 September 2025 at 13:36 To: Michael Karakash <michael.karakash@icann.org>, Renate De Wulf <renate.dewulf@icann.org> Cc: Elisa Busetto <elisa.busetto@icann.org>, "subpro-irt@icann.org" <subpro-irt@icann.org> Subject: [Ext] Re: [SubPro-IRT] Re: String Similarity Assessment of Reserved Names Thanks Michael. Very much appreciated. I have replied to the other email. Renate, please note my regrets for the meeting today. Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Wed, Sep 10, 2025 at 4:28 PM Michael Karakash <michael.karakash@icann.org<mailto:michael.karakash@icann.org>> wrote: Hi Anne, As noted in the recent email I sent to the IRT mailing list, I’ve updated the paper to include the relevant Board-adopted policy recommendations in the Annex. For ease of reference, here they are once more: Relevant Recommendations from the PDP Protection of IGO and INGO Identifiers in All gTLDs: Recommendation 3.1.1: * Top-Level protections of Exact Match, Full Name Scope 1 identifiers of the Red Cross Red Crescent Movement are placed in the Applicant Guidebook section 2.2.1.2.3, Strings “Ineligible for Delegation”. Recommendation 3.1.2: * For Red Cross Red Crescent Movement identifiers, if placed in the Applicant Guidebook as ineligible for delegation at the Top-Level, an exception procedure should be created for cases where a protected organization wishes to apply for their protected string at the Top-Level. Recommendation 3.2.1: * Top-Level protections of Exact Match, Full Name Scope 1 identifiers of the International Olympic Committee are placed in the Applicant Guidebook section 2.2.1.2.3, Strings “Ineligible for Delegation”. Recommendation 3.2.2: * For International Olympic Committee Identifiers, if placed in the Applicant Guidebook as ineligible for delegation at the Top-Level, an exception procedure should be created for cases where a protected organization wishes to apply for their protected string at the Top-Level. Recommendation 3.3.1: * Top-Level protections of Exact Match, Full Name Scope 1 identifiers of the International Governmental Organizations are placed in the Applicant Guidebook section 2.2.1.2.3, Strings “Ineligible for Delegation”. Recommendation 3.3.2: * For International Governmental Organizations Identifiers, if placed in the Applicant Guidebook as ineligible for delegation at the Top-Level, an exception procedure should be created for cases where a protected organization wishes to apply for their protected string at the Top-Level. Please let me know if you have any further questions. Thank you! Best, Michael From: Anne ICANN via SubPro-IRT <subpro-irt@icann.org<mailto:subpro-irt@icann.org>> Reply-To: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Date: Monday, September 8, 2025 at 3:57 PM To: Elisa Busetto <elisa.busetto@icann.org<mailto:elisa.busetto@icann.org>> Cc: "subpro-irt@icann.org<mailto:subpro-irt@icann.org>" <subpro-irt@icann.org<mailto:subpro-irt@icann.org>> Subject: [SubPro-IRT] Re: String Similarity Assessment of Reserved Names Thank you Elisa. Could you please: 1. Provide the policy Recommendation language as adopted by the Board in relation to this issue, and 2. Clarify whether there is any relevant Board-created policy on IGO names being eligible for delegation, e.g. in response to GAC Advice. Apologies for a lack of familiarity with the specifics on the policy recommendations. (I'm guessing Chris Disspain may have a good deal more background.) Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Fri, Sep 5, 2025 at 4:09 AM Elisa Busetto via SubPro-IRT <subpro-irt@icann.org<mailto:subpro-irt@icann.org>> wrote: Hello IRT, We have just published a paper concerning the String Similarity Assessment of Reserved Names on the wiki page of meeting #158a: https://icann-community.atlassian.net/wiki/x/AQB3Gw [icann-community.atlassian.net]<https://urldefense.com/v3/__https:/icann-community.atlassian.net/wiki/x/AQB3...> Sarmad will go through it during the call, but it would be appreciated if you could already review it and provide any input you may have on list. Many thanks, Elisa _______________________________________________ SubPro-IRT mailing list -- subpro-irt@icann.org<mailto:subpro-irt@icann.org> To unsubscribe send an email to subpro-irt-leave@icann.org<mailto:subpro-irt-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.
participants (5)
-
Anne ICANN -
Ashley Roberts -
Elisa Busetto -
Michael Karakash -
Renate De Wulf