Thank you for the questions, Satish and Nigel. Again, please refer to the response below based on Staff’s understanding: Implementation Guidance 15 was suggested to resolve the end-users’ needs to be able to determine what the allocated variant domain names are (e.g., interest in registering a domain name or filing a URS complaint). However, in order to mitigate any data privacy risks, per ICANN Legal Function’s advice, the proposed language was left at registrars’ discretion to accept and consider whether the disclosure of such information should be granted, balancing the interest of the requestor with those of the data subject. In contrast, Recommendation 14 is about the contracted parties having a technically feasible solution to be able to communicate with each other regarding variant domain names. The solution developed through Rec. 14 would likely be the manner in which a registrar would retrieve the requested information (e.g., one of the questions that RrSG posed for Rec.1 through the Public Comment review process<https://docs.google.com/spreadsheets/d/1oFX0h_czrJtV0Z_q9haGuVHjnhy4lZyyee-I...> – possibly a technical solution such as an EPP extension?). I hope this readdresses Michael’s concerns and reduces the burden for registrars. Sharing with you all below the drafted language for Outputs 14 and 15 again, for your convenience: Draft Final Recommendation 14: “To account for the "same entity" principle and its implications for variant domain names, gTLD registry operators should work with ICANN-accredited registrars to provide information on the allocated variant domain names for a given domain name, including an indication of the source domain name(s) and initial source domain name of the variant domain set. The grandfathered variant domain names pursuant to Final Recommendation 3 are exempt from this requirement.” Draft Final Implementation Guidance 15: “In order to allow an end user to discover the allocated variant domain names for a given domain name, registrars should accept and consider whether disclosure of this information should be granted. In considering whether to disclose the information, the registrar should balance the interest of the requestor with those of the data subject, where such balancing is required by applicable law.” Kind regards, EPDP-IDNs Team Support Staff. From: Satish Babu <sbabu@ieee.org> Date: Wednesday, September 4, 2024 at 4:50 AM To: "Hickson, Nigel (DSIT)" <nigel.hickson@dsit.gov.uk> Cc: Saewon Lee <saewon.lee@icann.org>, Michael Bauland <Michael.Bauland@knipp.de>, "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Subject: [Ext] Re: [Gnso-epdp-idn-team] Re: Action Item 1: Feedback Request for Outputs 14-15 Thanks Nigel, Saewon and all. We also would also like to have the answer to Nigel's question, as ALAC's response to the public comment had proposed a mechanism by which any one--including registrants, security researchers or end users--could have access to non-private information regarding the variant set. With kind regards satish On Wed, Sep 4, 2024 at 2:04 PM Hickson, Nigel (DSIT) via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> wrote: Seawon cc as above Good morning; thanks for Micheal rising and for your reply. Can I confirm, however, my understanding that whatever arrangements the Registries and Registrars make the information HAS to be provided for registrants to see. Best Nigel -----Original Message----- From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> Sent: 03 September 2024 23:03 To: Michael Bauland <Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de>>; gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> Subject: [Gnso-epdp-idn-team] Re: Action Item 1: Feedback Request for Outputs 14-15 Dear Michael, Thank you for your questions. Please refer to the responses below and kindly note that these are Staff's understanding of your questions (sorry that I could not mark the responses in a different color or highlight them as the rich text format is not allowed here): 1. We are not actually prescribing *who* is going to provide that information, nor *how* it is provided. Only that it's up to registries or registrars to sort out these questions. --> 'How' the information would be provided is not prescribed. However, 'who' will be involved in these discussions and providing the information is prescribed, namely, at a minimum, gTLD registry operators and ICANN-accredited registrars (i.e., the contracted parties). ***Staff is still trying to determine with GTS ICANN org's role in this situation. 2. Is this on a per TLD (incl. variants) basis? So should registry X work with all their registrars to find a solution how to provide this information and should registry Y do the same with their registrars? Or should there be some more global working group of all registries and registrars to find a solution that should then be applied to all TLDs. --> Similar to the rationale provided in Final Recommendation 6 and the responses to charter questions C3 and C3a, the solution should be uniform, to the extent possible, where a single mechanism is agreed upon and used to identify the appropriate information to satisfy the "same entity" principle. The method should be of their own choosing, but this single method should be determined together by all registries and registrars that should be applied to all TLDs. However, as the suggested IG 15 states, allowing an end user/registrant to discover the information (allocated variant domain names for a given domain name) is at each registrar's discretion based on the interest of the requestor and the applicable law that does not compromise data privacy. I hope this satisfies your confusion. Warm regards, EPDP-IDNs Team Staff Support. On 9/3/24, 2:44 AM, "Michael Bauland via Gnso-epdp-idn-team" <gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>>> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>>>>> wrote: Hi Saewon, hi team, thanks to Saewon for compiling all this in a succinct format, that's very helpful. I do have a question regarding the new Rec 14:
*(New Draft) _Final Recommendation 14_:* /“To account for the "same entity" principle and its implications for variant domain names, gTLD registry operators should work with ICANN-accredited registrars to provide information [...]
I'm not sure I understand this recommendation correctly. So I'll ask some clarification questions or write down, what I understand and would like you to confirm or correct me, please. (All following references to TLDs, registries and registrars are of course meant to be gTLD/ICANN accredited.) 1. We are not actually prescribing *who* is going to provide that information, nor *how* it is provided. Only that it's up to registries or registrars to sort out these questions. 2. Is this on a per TLD (incl. variants) basis? So should registry X work with all their registrars to find a solution how to provide this information and should registry Y do the same with their registrars? Or should there be some more global working group of all registries and registrars to find a solution that should then be applied to all TLDs. 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<mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de>> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de>>> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de>> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de>>>> Software Development E-mail: Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de>> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de>>> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de>> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de> <mailto:Michael.Bauland@knipp.de<mailto:Michael.Bauland@knipp.de>>>> Register Court: Amtsgericht Dortmund, HRB 13728 Chief Executive Officers: Dietmar Knipp, Elmar Knipp Certified according DIN ISO/IEC 27001:2017 _______________________________________________ Gnso-epdp-idn-team mailing list -- gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>>> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> <mailto:gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org>>>> To unsubscribe send an email to gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org> <mailto:gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org>> <mailto:gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org> <mailto:gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org>>> <mailto:gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org> <mailto:gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org>> <mailto:gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org> <mailto:gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org>>>> %(web_page_url)slistinfo/%(_internal_name)s _______________________________________________ Gnso-epdp-idn-team mailing list -- gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> To unsubscribe send an email to gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org> %(web_page_url)slistinfo/%(_internal_name)s _______________________________________________ Gnso-epdp-idn-team mailing list -- gnso-epdp-idn-team@icann.org<mailto:gnso-epdp-idn-team@icann.org> To unsubscribe send an email to gnso-epdp-idn-team-leave@icann.org<mailto:gnso-epdp-idn-team-leave@icann.org> %(web_page_url)slistinfo/%(_internal_name)s