Dear Ariel and All,

Our preferred string similarity review levels is Level 2  

  1. Why do you believe your preferred level of review is the most appropriate? 

Choosing between Level1 and Level 2 depends on some other elements. This would include cost associated with each string applied for as well as when the applicant could apply for a string.

Level 1: allows entities to ensure strings that they would either use now or intend to use in the future while giving room to future labels that could have been blocked due to similarity/confusability with some of the variants that the entity would have never used anyway. This option entails the least similarity work and cost.

 

Level 2: Allows entities to ensure all their allocatable strings and all other possible future similar strings would be blocked. This option gives full future predictability and entails less similarity costs and work than level 3.  

 

Level 3: Would unnecessary block future strings that are similar to blocked strings. Blocked strings will in all cases never be  delegated. Therefore, unnecessary blocking possible future TLDs and entailing unnecessary similarity review work and costs.   

 

  1. Based on your preferred level of review, what would be the string similarity review’s impact on preventing user confusion and security/stability issues in the DNS? In other words, how effective would string similarity review be in preventing delegation of similar strings? 

String similarity review work would be effective in preventing delegation of similar strings in all three levels. Level 3 would require unnecessary string similarity review work. As it would check for similarity with blocked strings that are never going to be delegated. Level 2 would provide full future predictability, while entailing less similarity work and costs than level 3.

  1. Have you considered the feasibility of implementing the string similarity review based on your preferred level? For example, the complexity and costs involved to conduct the resulting review. 

Level 3 entails unjustified complex and costly string similarity work. Level 2 is a middle ground it is associated with more costs and work than level 1 but provides full future predictability.  

Kind regards

Hadia El Miniawi (On behalf of ALAC)

From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces@icann.org> On Behalf Of Ariel Liang
Sent: Tuesday, April 26, 2022 2:29 PM
To: gnso-epdp-idn-team@icann.org
Subject: [Gnso-epdp-idn-team] REMINDER - Your Input Requested: String Similarity Review Level & Rationale

 

Dear EPDP Team,

 

This is a reminder to provide your input on the string similarity review levels.

 

Thanks very much to Michael and Anil for the input on list. Please be so kind to provide rationale for your preferred level and responses to the three questions as well.

 

Best Regards,

Ariel

 

From: Ariel Liang <ariel.liang@icann.org>
Date: Wednesday, April 20, 2022 at 1:59 PM
To: "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org>
Subject: Your Input Requested: String Similarity Review Level & Rationale

 

Dear EPDP Team, 

 

Thank you for the discussions to date on the string similarity review topic (charter questions E3, E1 (part1) and E3a). The leadership team appreciates that this is a difficult topic and that a range of views are evident across the Team, particularly on the three levels of string similarity review.

 

In order to facilitate the continued deliberation of this topic, the Leadership Team requests members to consider the three levels of string similarity review and indicate your preferred level of review, along with the reasons why this is your preferred level, on the list by Wednesday, 27 April 2022. 

 

When sharing your preference, please include responses to the following questions: 

 

  1. Why do you believe your preferred level of review is the most appropriate? 
  2. Based on your preferred level of review, what would be the string similarity review’s impact on preventing user confusion and security/stability issues in the DNS? In other words, how effective would string similarity review be in preventing delegation of similar strings? 
  3. Have you considered the feasibility of implementing the string similarity review based on your preferred level? For example, the complexity and costs involved to conduct the resulting review. 

 

The string similarity review topic is expected to be discussed again during the EPDP Team meeting next week (28 April 2022) and members and participants will be invited to speak to their respective preferences and rationales. As a reminder, the three levels are as follows (please see details in the slide deck): 

Thank you for your contribution!

 

Best Regards,

Steve, Emily, Ariel