Reminder: Share Current Views on String Similarity Review Hybrid Model
Dear All, In the upcoming meeting on Thursday, 13 October, the team is expected to discuss the String Similarity Review topic and the hybrid model proposed by the small group. During the meeting yesterday, several members provided a preview of their groups’ positions on the hybrid model. To facilitate an effective discussion next week, the leadership team is requesting members, especially those who could not make it to yesterday’s call, to circulate your groups’ current views on the hybrid model on the mailing list by EOB Tuesday, 11 October. Please also share the rationale, caveats, and other considerations (if any). Thank you, Steve, Emily, Ariel
Dear all The ALAC Team supports the proposed Hybrid Model for String Similarity Review on the basis that: 1. There is a need to adopt a cautious and conservative approach for the String Similarity review process. 2. The proposed Hybrid Model reflects a conservative approach that can help mitigate the two types of failure modes (denial of service and misconnection), and thereby promotes good user experience; yet does not call for excessive computational and evaluative complexity (by not comparing blocked variants of one TLD with the blocked variants of another). We are, however, open to considering refinements that would help reduce complexity in computation/ evaluation without diminishing the mitigatory goal of the Hybrid Model. With kind regards satish On Fri, Oct 7, 2022 at 7:18 PM Ariel Liang <ariel.liang@icann.org> wrote:
Dear All,
In the upcoming meeting on Thursday, 13 October, the team is expected to discuss the String Similarity Review topic and the hybrid model proposed by the small group. During the meeting yesterday, several members provided a preview of their groups’ positions on the hybrid model. To facilitate an effective discussion next week, the leadership team is requesting members, especially those who could not make it to yesterday’s call, to circulate your groups’ current views on the hybrid model on the mailing list by *EOB Tuesday, 11 October*. Please also share the rationale, caveats, and other considerations (if any).
Thank you,
Steve, Emily, Ariel _______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team
Dear all, See below the NCSG’s position regarding IDN EPDP Small Group Hybrid Model Recommendation on String Similarity Basis for Comparison for gTLD labels and corresponding variant labels *1- We think that the proposal of the small group is a practical one and backed by fact. 2- The findings clearly shows that there is a real possibility to miss confusable strings if the applied for TLD was not compared against (a) its blocked variants (b) existing TLDs and their allocatable and blocked variants (c) other applied for TLDs and their allocatable and blocked variants.3- A blocked variant of the request for TLD cannot be allocated, therefore we agree with the group's recommendation that it should not be used to compare against blocked variants of other TLDs. Only applied for and allocatable strings should be used.* Looking forward to reading recommendations from other stakeholder groups at the upcoming meeting. King regards, Emmanuel Vitus Le lun. 10 oct. 2022 à 15:38, Satish Babu via Gnso-epdp-idn-team < gnso-epdp-idn-team@icann.org> a écrit :
Dear all
The ALAC Team supports the proposed Hybrid Model for String Similarity Review on the basis that:
1. There is a need to adopt a cautious and conservative approach for the String Similarity review process. 2. The proposed Hybrid Model reflects a conservative approach that can help mitigate the two types of failure modes (denial of service and misconnection), and thereby promotes good user experience; yet does not call for excessive computational and evaluative complexity (by not comparing blocked variants of one TLD with the blocked variants of another).
We are, however, open to considering refinements that would help reduce complexity in computation/ evaluation without diminishing the mitigatory goal of the Hybrid Model.
With kind regards
satish
On Fri, Oct 7, 2022 at 7:18 PM Ariel Liang <ariel.liang@icann.org> wrote:
Dear All,
In the upcoming meeting on Thursday, 13 October, the team is expected to discuss the String Similarity Review topic and the hybrid model proposed by the small group. During the meeting yesterday, several members provided a preview of their groups’ positions on the hybrid model. To facilitate an effective discussion next week, the leadership team is requesting members, especially those who could not make it to yesterday’s call, to circulate your groups’ current views on the hybrid model on the mailing list by *EOB Tuesday, 11 October*. Please also share the rationale, caveats, and other considerations (if any).
Thank you,
Steve, Emily, Ariel _______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team
_______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team
Ariel and colleagues Good morning and apologies for being late on deploying GAC views on this important issue. In general we are supportive, like other constituencies, of the Hybrid Model for String Similarity. While we take, perhaps, a less conservative position than some, looking for maximum opportunities for variant use, we appreciate the need to mitigate failures; not least through denial or service or misconnection. We note that neither of these failure modes would be beneficial to users. We look forward to further work in the wider group on taking this forward. Finally, we would like to thank the Small Group for all their work on this; best Nigel Mon, 10 Oct 2022 at 14:38, Satish Babu via Gnso-epdp-idn-team < gnso-epdp-idn-team@icann.org> wrote:
Dear all
The ALAC Team supports the proposed Hybrid Model for String Similarity Review on the basis that:
1. There is a need to adopt a cautious and conservative approach for the String Similarity review process. 2. The proposed Hybrid Model reflects a conservative approach that can help mitigate the two types of failure modes (denial of service and misconnection), and thereby promotes good user experience; yet does not call for excessive computational and evaluative complexity (by not comparing blocked variants of one TLD with the blocked variants of another).
We are, however, open to considering refinements that would help reduce complexity in computation/ evaluation without diminishing the mitigatory goal of the Hybrid Model.
With kind regards
satish
On Fri, Oct 7, 2022 at 7:18 PM Ariel Liang <ariel.liang@icann.org> wrote:
Dear All,
In the upcoming meeting on Thursday, 13 October, the team is expected to discuss the String Similarity Review topic and the hybrid model proposed by the small group. During the meeting yesterday, several members provided a preview of their groups’ positions on the hybrid model. To facilitate an effective discussion next week, the leadership team is requesting members, especially those who could not make it to yesterday’s call, to circulate your groups’ current views on the hybrid model on the mailing list by *EOB Tuesday, 11 October*. Please also share the rationale, caveats, and other considerations (if any).
Thank you,
Steve, Emily, Ariel _______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team
_______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team
Thank you Satish, Dennis, Emmanuel, and Nigel for sharing the positions from your groups. We look forward to the continued discussion of the hybrid model during tomorrow’s meeting. Best Regards, Ariel From: Nigel Hickson <nigel.hickson@dcms.gov.uk> Date: Tuesday, October 11, 2022 at 3:35 AM To: Ariel Liang <ariel.liang@icann.org> Cc: "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Subject: [Ext] Re: [Gnso-epdp-idn-team] Reminder: Share Current Views on String Similarity Review Hybrid Model Ariel and colleagues Good morning and apologies for being late on deploying GAC views on this important issue. In general we are supportive, like other constituencies, of the Hybrid Model for String Similarity. While we take, perhaps, a less conservative position than some, looking for maximum opportunities for variant use, we appreciate the need to mitigate failures; not least through denial or service or misconnection. We note that neither of these failure modes would be beneficial to users. We look forward to further work in the wider group on taking this forward. Finally, we would like to thank the Small Group for all their work on this; best Nigel Mon, 10 Oct 2022 at 14:38, Satish Babu via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> wrote: Dear all The ALAC Team supports the proposed Hybrid Model for String Similarity Review on the basis that: 1. There is a need to adopt a cautious and conservative approach for the String Similarity review process. 2. The proposed Hybrid Model reflects a conservative approach that can help mitigate the two types of failure modes (denial of service and misconnection), and thereby promotes good user experience; yet does not call for excessive computational and evaluative complexity (by not comparing blocked variants of one TLD with the blocked variants of another). We are, however, open to considering refinements that would help reduce complexity in computation/ evaluation without diminishing the mitigatory goal of the Hybrid Model. With kind regards satish On Fri, Oct 7, 2022 at 7:18 PM Ariel Liang <ariel.liang@icann.org<mailto:ariel.liang@icann.org>> wrote: Dear All, In the upcoming meeting on Thursday, 13 October, the team is expected to discuss the String Similarity Review topic and the hybrid model proposed by the small group. During the meeting yesterday, several members provided a preview of their groups’ positions on the hybrid model. To facilitate an effective discussion next week, the leadership team is requesting members, especially those who could not make it to yesterday’s call, to circulate your groups’ current views on the hybrid model on the mailing list by EOB Tuesday, 11 October. Please also share the rationale, caveats, and other considerations (if any). Thank you, Steve, Emily, Ariel _______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org<mailto:Gnso-epdp-idn-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team _______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org<mailto:Gnso-epdp-idn-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team
With respect to the IPC view, we have not yet been able as a group to discuss this completely, but the IPC is concerned that the Hybrid Model needs to have an exception process. For example, if there is a Brand that has a name which happens to be a non-allocatable variant of another string that has been delegated, then we believe that new Brand should be able to overcome any potential string similarity review of string confusion objection. we believe that the risk of “misconnection” in such a case is extremely low in such a case. Any model that does not allow for exceptions in our view would be unacceptable to the IPC. Sincerely, Jeff [cid:image001.png@01D8DE2E.FDD29D50] Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com<mailto:jeff@jjnsolutions.com> http://jjnsolutions.com From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces@icann.org> On Behalf Of Ariel Liang Sent: Wednesday, October 12, 2022 10:27 AM To: Nigel Hickson <nigel.hickson@dcms.gov.uk> Cc: gnso-epdp-idn-team@icann.org Subject: Re: [Gnso-epdp-idn-team] [Ext] Re: Reminder: Share Current Views on String Similarity Review Hybrid Model Thank you Satish, Dennis, Emmanuel, and Nigel for sharing the positions from your groups. We look forward to the continued discussion of the hybrid model during tomorrow’s meeting. Best Regards, Ariel From: Nigel Hickson <nigel.hickson@dcms.gov.uk<mailto:nigel.hickson@dcms.gov.uk>> Date: Tuesday, October 11, 2022 at 3:35 AM To: Ariel Liang <ariel.liang@icann.org<mailto:ariel.liang@icann.org>> Cc: "gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>" <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> Subject: [Ext] Re: [Gnso-epdp-idn-team] Reminder: Share Current Views on String Similarity Review Hybrid Model Ariel and colleagues Good morning and apologies for being late on deploying GAC views on this important issue. In general we are supportive, like other constituencies, of the Hybrid Model for String Similarity. While we take, perhaps, a less conservative position than some, looking for maximum opportunities for variant use, we appreciate the need to mitigate failures; not least through denial or service or misconnection. We note that neither of these failure modes would be beneficial to users. We look forward to further work in the wider group on taking this forward. Finally, we would like to thank the Small Group for all their work on this; best Nigel Mon, 10 Oct 2022 at 14:38, Satish Babu via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> wrote: Dear all The ALAC Team supports the proposed Hybrid Model for String Similarity Review on the basis that: 1. There is a need to adopt a cautious and conservative approach for the String Similarity review process. 2. The proposed Hybrid Model reflects a conservative approach that can help mitigate the two types of failure modes (denial of service and misconnection), and thereby promotes good user experience; yet does not call for excessive computational and evaluative complexity (by not comparing blocked variants of one TLD with the blocked variants of another). We are, however, open to considering refinements that would help reduce complexity in computation/ evaluation without diminishing the mitigatory goal of the Hybrid Model. With kind regards satish On Fri, Oct 7, 2022 at 7:18 PM Ariel Liang <ariel.liang@icann.org<mailto:ariel.liang@icann.org>> wrote: Dear All, In the upcoming meeting on Thursday, 13 October, the team is expected to discuss the String Similarity Review topic and the hybrid model proposed by the small group. During the meeting yesterday, several members provided a preview of their groups’ positions on the hybrid model. To facilitate an effective discussion next week, the leadership team is requesting members, especially those who could not make it to yesterday’s call, to circulate your groups’ current views on the hybrid model on the mailing list by EOB Tuesday, 11 October. Please also share the rationale, caveats, and other considerations (if any). Thank you, Steve, Emily, Ariel _______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org<mailto:Gnso-epdp-idn-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team _______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org<mailto:Gnso-epdp-idn-team@icann.org> https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team
Hi Jeff, On 12.10.2022 17:37, Jeff Neuman wrote:
With respect to the IPC view, we have not yet been able as a group to discuss this completely, but the IPC is concerned that the Hybrid Model needs to have an exception process. For example, if there is a Brand that has a name which happens to be a non-allocatable variant of another string that has been delegated
I assume you mean "if there is a Brand that has a name which is (confusingly) similar to a non-allocatable variant of another string that has been delegated". Sorry to be a nitpicker, but if the brand's name actually *is* a variant of a delegate string, then there is no way that the brand will be able to get their string while the already delegated string remains. Cheers, Michael -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Dipl.-Informatiker Fon: +49 231 9703-0 Fax: +49 231 9703-200 Dr. Michael Bauland SIP: Michael.Bauland@knipp.de Software Development E-mail: Michael.Bauland@knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp
Thanks Michael and yes this is indeed what I meant. Jeffrey J. Neuman Founder & CEO JJN Solutions, LLC p: +1.202.549.5079 E: jeff@jjnsolutions.com http://jjnsolutions.com -----Original Message----- From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces@icann.org> On Behalf Of Michael Bauland Sent: Thursday, October 13, 2022 9:38 AM To: gnso-epdp-idn-team@icann.org Subject: Re: [Gnso-epdp-idn-team] [Ext] Re: Reminder: Share Current Views on String Similarity Review Hybrid Model Hi Jeff, On 12.10.2022 17:37, Jeff Neuman wrote:
With respect to the IPC view, we have not yet been able as a group to discuss this completely, but the IPC is concerned that the Hybrid Model needs to have an exception process. For example, if there is a Brand that has a name which happens to be a non-allocatable variant of another string that has been delegated
I assume you mean "if there is a Brand that has a name which is (confusingly) similar to a non-allocatable variant of another string that has been delegated". Sorry to be a nitpicker, but if the brand's name actually *is* a variant of a delegate string, then there is no way that the brand will be able to get their string while the already delegated string remains. Cheers, Michael -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeisser-Weg 9 44227 Dortmund Germany Dipl.-Informatiker Fon: +49 231 9703-0 Fax: +49 231 9703-200 Dr. Michael Bauland SIP: Michael.Bauland@knipp.de Software Development E-mail: Michael.Bauland@knipp.de Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp _______________________________________________ Gnso-epdp-idn-team mailing list Gnso-epdp-idn-team@icann.org https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team
participants (6)
-
Ariel Liang -
Emmanuel Vitus -
Jeff Neuman -
Michael Bauland -
Nigel Hickson -
Satish Babu