- SubPro-IRT - lists.icann.org

ICANN80 Deck: ASP Bid Credit
by Kristy Buckley Nov. 9, 2024

Nov. 9, 2024

Greetings SubPro IRT colleagues, Elisa and Lars mentioned that there were some questions during today's IRT meeting about the Applicant Support Program bid credit. For reference, I thought it might be helpful to share the deck that was presented to the IRT during ICANN80: https://community.icann.org/download/attachments/322994373/ASP%20Bid%20Cred… We'll work with Lars and Elisa to bring this back to the IRT for discussion again soon. Kind regards, Kristy

1 0

Reserved and Blocked Names List Terminology
by Michael Karakash Nov. 9, 2024

Nov. 9, 2024

[Note: Including the SubPro IRT in this reply for transparency, as this information could be helpful to others] Dear Ashley, Thank you for your questions. We appreciate the opportunity to clarify how the new definitions of "Reserved Names" and "Blocked Names" interact with string similarity rules under the updated Applicant Guidebook. Reserved Names and Blocked Names Redefined: As you’ve noted, the terminology has been adjusted from the 2012 Guidebook. Specifically: * In the 2012 Applicant Guidebook, what was termed the “Strings Ineligible for Delegation” is now referred to as the Reserved Names List. * The list previously called the “Top-Level Reserved Names List” is now referred to as the Blocked Names List. In the most recent version of the Blocked and Reserved Names AGB draft<https://community.icann.org/download/attachments/315490346/EXT_2024-09-05_U…> which you find on the IRT Community Wiki<https://community.icann.org/display/SPIR>, you can see the clarifying language we’ve added. It states: “Note: In the 2012 Applicant Guidebook, the list called “Strings Ineligible for Delegation” is now referred to as the Reserved Names List, and the list previously called the “Top-Level Reserved Names List” is now known as the Blocked Names List.” In response to the questions in your email, the string similarity rules apply to all Reserved Names and Blocked Names listed in the table in the current AGB document. This means that: * Any applied-for gTLD string, or any of its variant strings, will not proceed if it is found to be similar to any name in the Reserved Names List or Blocked Names List. * However, there is an exception as noted in the draft String Similarity Review AGB language<https://community.icann.org/display/SPIR/1.+Working+Documents?preview=/3154…>: “If the applied-for gTLD string is a variant of a Reserved Name and the applicant is the Reserved Name entity itself, then the application can proceed with the evaluation as a variant gTLD of that Reserved Name.” As noted on the table, the only strings that are Reserved Names in the Next Round are Limited International IGO INGOs. * As a reminder, the variant of reserved name can only be applied for if the actual reserved name string is also applied for. Language in the draft IDN AGB language<https://community.icann.org/display/SPIR/1.+Working+Documents?preview=/3154…> states: “An application for an allocatable variant gTLD cannot precede an application for its primary IDN gTLD.” I hope this clarifies how the terms "Reserved Name" and "Blocked Name" are now used in the AGB and confirms the scope of string similarity evaluation for all names included in these lists. Please don’t hesitate to reach out if you have further questions or if there’s anything more we can assist with. Thank you! Best, Michael Original email: From: Ashley Roberts <ashley.roberts(a)comlaude.com<mailto:ashley.roberts@comlaude.com>> Date: Wednesday, 30 October 2024 at 11:23 To: Lars Hoffmann <lars.hoffmann(a)icann.org<mailto:lars.hoffmann@icann.org>> Subject: [Ext] Reserved Names List Dear Lars, We are already speaking to clients that are exploring applying for a TLD in the next round so we are beginning to carry out due diligence on the strings they are interested in. In going through the new string similarity rules it wasn’t clear to me what comprised the Reserved Names list referenced in point 6 on page 3 [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/policy-develo…> of the rules so I wonder if you can please clarify? In the 2012 round the only Reserved Names which were subject to string similarity (as opposed to exact match blocking) were those on the ICANN reserved list, which consisted of 34 strings (see page 60 [newgtlds.icann.org]<https://urldefense.com/v3/__https:/newgtlds.icann.org/sites/default/files/g…>). Other categories of term were blocked from application but were not subject to string similarity. This included country names, IOC and RC names, and 3 letter country codes. So something like FRANCE was blocked from registration but anything confusingly similar to that was fine. Under the new AGB language it seems as though what were termed “reserved names” and “blocked names” in 2012 have been re-categorised. According to the table in this AGB section [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/generic-names…>, the only terms which are Reserved Names are the IOC/RC/IGO names; everything else is considered a Blocked Name. Based on this categorisation, that would mean the only “reserved names” that are subject to string similarity are the IOC/RC/IGO names. However, that doesn’t seem right. Alternatively, if I assume all Reserved Names and Blocked Names in the table are subject to string similarity that would include country names and 3 letter country codes in that review, which also doesn’t seem right. This is making me wonder if there is an inconsistency with the use of the terms “reserved name” and “blocked name” across these different sections of the AGB. Can I ask you to kindly clarify: * Whether all categories in this table [itp.cdn.icann.org]<https://urldefense.com/v3/__https:/itp.cdn.icann.org/en/files/generic-names…> are subject to string similarity rules, or * Whether only some of the categories in the table are subject to string similarity rules (and if so, which categories) Apologies that I didn’t pick this up during the recent public comment period. Many thanks, Ashley Ashley Roberts Head of New TLD Consultancy [cid77860*image001.png(a)01DB2ABF.C4D62410][comlaude.com]<https://urldefense.com/v3/__https:/comlaude.com/__;!!PtGJab4!4gFLQnHfBUnOwh…> 28 Little Russell Street, London WC1A 2HN, UK T +44 (0) 20 7421 8250 Ext 264 comlaude.com [comlaude.com]<https://urldefense.com/v3/__http:/comlaude.com/__;!!PtGJab4!4gFLQnHfBUnOwhf…> Follow us on LinkedIn [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/pRkAAFJfAADD…> and YouTube [t-uk.xink.io]<https://urldefense.com/v3/__https:/t-uk.xink.io/Tracking/Index/bhkAAFJfAADD…> [cid77860*image002.png(a)01DB2ABF.C4D62410][linkedin.com]<https://urldefense.com/v3/__https:/www.linkedin.com/company/com-laude__;!!P…> [cid77860*image003.png(a)01DB2ABF.C4D62410] [twitter.com]<https://urldefense.com/v3/__https:/twitter.com/comlaude?lang=en__;!!PtGJab4…> [cid77860*image004.png(a)01DB2ABF.C4D62410] [facebook.com]<https://urldefense.com/v3/__https:/www.facebook.com/ComLaude/__;!!PtGJab4!4…> [cid77860*image005.png(a)01DB2ABF.C4D62410] [youtube.com]<https://urldefense.com/v3/__https:/www.youtube.com/@comlaude__;!!PtGJab4!4g…> [cid77860*image006.jpg(a)01DB2ABF.C4D62410] ________________________________ 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!4gFLQnHfBUnOwh…>

1 0

SubPro IRT Meeting #89 | 9 November 2024, 10:15-11:30 UTC / 13:15-14:30 TRT | ICANN81
by Next Round Policy Implementation Nov. 9, 2024

Nov. 9, 2024

Dear All, Meeting #89 of the SubPro IRT will be held in one hour on 9 November 2024 at 10:15-11:30 UTC / 13:15-14:40 TRT [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/msdzzz54__;!!PtGJab4!4ESEBMS…>] during ICANN81 in Istanbul, Turkey, in a hybrid format. Up-to-date information on the session will be published here [icann81.sched.com]<https://urldefense.com/v3/__https:/icann81.sched.com/event/1p29A/gds-subpro…>, and the agenda here<https://community.icann.org/x/AIHKFQ> . More information on ICANN81 can be found here [icann81.sched.com]<https://urldefense.com/v3/__https:/icann81.sched.com/__;!!PtGJab4!8gw61ZETf…>. Before the meeting, please ensure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>. In addition, we would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please let us know ahead of time should you be unable to attend the meeting. A recording will be made available. We remain at your disposal should you have any questions. Best regards, Renate

1 0

REMINDER | SubPro IRT Meeting #88 | 9 November 2024, 07:30-09:00 UTC / 10:30-12:00 TRT | ICANN81
by Next Round Policy Implementation Nov. 9, 2024

Nov. 9, 2024

Dear All, Meeting #88 of the SubPro IRT will be held in one hour on 9 November 2024 at 07:30-09:00 UTC / 10:30-12:00 TRT [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/bdv693th__;!!PtGJab4!7-34dnP…>] during ICANN81 in Istanbul, Turkey, in a hybrid format. Up-to-date information on the session will be published here [icann81.sched.com]<https://urldefense.com/v3/__https:/icann81.sched.com/event/1p299/gds-subpro…>, and the agenda here<https://community.icann.org/x/8oDKFQ>. More information on ICANN81 can be found here [icann81.sched.com]<https://urldefense.com/v3/__https:/icann81.sched.com/__;!!PtGJab4!8gw61ZETf…>. Before the meeting, please ensure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>. In addition, we would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please let us know ahead of time should you be unable to attend the meeting. A recording will be made available. We remain at your disposal should you have any questions. Best regards, Renate

1 0

REMINDER | SubPro IRT Meeting #87 | 9 November 2024, 06:00-07:00 UTC / 09:00-10:00 TRT | ICANN81
by Next Round Policy Implementation Nov. 9, 2024

Nov. 9, 2024

Dear All, Meeting #87 of the SubPro IRT will be held in one hour on 9 November 2024 at 06:00-07:00 UTC / 09:00-10:00 TRT [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/u8md46n9__;!!PtGJab4!8gw61ZE…>] during ICANN81 in Istanbul, Turkey, in a hybrid format. Up-to-date information on the session will be published here [icann81.sched.com]<https://urldefense.com/v3/__https:/icann81.sched.com/event/1p297/gds-subpro…>, and the agenda here [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/u8md46n9__;!!PtGJab4!8gw61ZE…>. More information on ICANN81 can be found here [icann81.sched.com]<https://urldefense.com/v3/__https:/icann81.sched.com/__;!!PtGJab4!8gw61ZETf…>. Before the meeting, please ensure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>. In addition, we would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please let us know ahead of time should you be unable to attend the meeting. A recording will be made available. We remain at your disposal should you have any questions. Best regards, Renate

1 0

Singular/Plural Notification
by Elisa Busetto Nov. 8, 2024

Nov. 8, 2024

Dear all, Please find here<https://docs.google.com/document/d/1u-2f-8sZZtH4-_T2iFuv1w4wG48CGTf4SGMseFO…> the Singular/Plural Notification language we just discussed. You can find the pdf and docx versions on the meeting page<https://community.icann.org/x/K4AUFg>. Best, Elisa

3 3

New gTLD Program: Next Round Status Update for ICANN81
by Elisa Busetto Nov. 8, 2024

Nov. 8, 2024

Dear IRT members, Please find the New gTLD Program: Next Round Status Update for ICANN81: https://go.icann.org/3YzN8VX Best regards, Elisa

1 0

Re: Language for IRT Consideration - String Contention Procedures: Replacement String (Topic 35: Auctions)
by Elisa Busetto Nov. 8, 2024

Nov. 8, 2024

Dear IRT members, We would like to inform you that we have updated the Replacement String Procedures<https://docs.google.com/document/d/14qWFuuekfFe4J_h5Hhx8uqwLK0fWWE_gkbMPOPd…> language – we will discuss the changes during Meeting #89<https://community.icann.org/x/AIHKFQ>. Best, Elisa From: Peter Eakin via SubPro-IRT <subpro-irt(a)icann.org> Reply to: Peter Eakin <peter.eakin(a)icann.org> Date: Monday, 14 October 2024 at 17:32 To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [SubPro-IRT] Language for IRT Consideration - String Contention Procedures: Replacement String (Topic 35: Auctions) Dear IRT Members, We are pleased to share a link to proposed AGB language on ‘Replacement String’ procedures (formerly known as ‘Alternate Strings’) for discussion at our meeting tomorrow, Tuesday, 15 October 2024. The link to the language can be found here [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/14qWFuuekfFe4…> and relates to issues discussed in ‘Topic 35: Auctions’ of the Final Report. This language is a subsection of AGB content on String Contention Procedures which is currently under development and expected to be shared with the IRT in the coming weeks. A high-level table of contents for this section is also included for your information. A PDF version of this document is also available on the meeting page<https://community.icann.org/pages/viewpage.action?pageId=370442261>. Should you have any questions about, or issues accessing, the above links, please let us know in advance of the meeting. Thanks and best wishes, Peter Eakin Policy Research Specialist ICANN

1 0

Re: Language for IRT Consideration - Brand TLD String Change (Topic 20: Application Change Requests)
by Elisa Busetto Nov. 8, 2024

Nov. 8, 2024

Dear all, Please note that we will discuss the updates to ‘Brand TLD String Change’<https://docs.google.com/document/d/1KmNynLD1zBGuqG3NtJt_FgTfuxFcKbaPdX-Z-GH…> language tomorrow during Meeting #89<https://community.icann.org/x/AIHKFQ>. Best, Elisa From: Peter Eakin via SubPro-IRT <subpro-irt(a)icann.org> Reply to: Peter Eakin <peter.eakin(a)icann.org> Date: Monday, 4 November 2024 at 19:11 To: "subpro-irt(a)icann.org" <subpro-irt(a)icann.org> Subject: [SubPro-IRT] Language for IRT Consideration - Brand TLD String Change (Topic 20: Application Change Requests) Dear IRT Members, We are pleased to share a link to proposed AGB language on ‘Brand TLD String Change’ procedures for discussion at our meeting tomorrow, Tuesday, 5 November 2024. The link to the language can be found here [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1KmNynLD1zBGu…> and relates to issues discussed in ‘Topic 20: Application Change Requests’ of the Final Report. A PDF version of this document is also available on the meeting page.<https://community.icann.org/pages/viewpage.action?pageId=370442253> Should you have any questions about, or issues accessing, the above links, please let us know in advance of the meeting. Thanks and best wishes, Peter Eakin Policy Research Specialist ICANN

1 0

REMINDER | SubPro IRT Meeting #89 | 9 November 2024, 10:15-11:30 UTC / 13:15-14:30 TRT | ICANN81
by Next Round Policy Implementation Nov. 7, 2024

Nov. 7, 2024

Dear All, Meeting #89 of the SubPro IRT will be held on 9 November 2024 at 10:15-11:30 UTC / 13:15-14:40 TRT [local time [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/msdzzz54__;!!PtGJab4!4ESEBMS…>] during ICANN81 in Istanbul, Turkey, in a hybrid format. Up-to-date information on the session will be published here [icann81.sched.com]<https://urldefense.com/v3/__https:/icann81.sched.com/event/1p29A/gds-subpro…>, and the agenda here<https://community.icann.org/x/AIHKFQ> . More information on ICANN81 can be found here [icann81.sched.com]<https://urldefense.com/v3/__https:/icann81.sched.com/__;!!PtGJab4!8gw61ZETf…>. Before the meeting, please ensure you have read the ICANN Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> and the ICANN Community Anti-Harassment Policy<https://www.icann.org/resources/pages/community-anti-harassment-policy-2017…>. In addition, we would like to remind participants that to ensure transparency of participation in ICANN's multistakeholder model, we ask that you sign in to Zoom sessions using your full name. For example, First Name and Last Name or Surname. You may be removed from the session if you do not sign in using your full name. Please let us know ahead of time should you be unable to attend the meeting. A recording will be made available. We remain at your disposal should you have any questions. Best regards, Renate

1 0