Reminder: Updated Recommendation Text for IDN Table Harmonization, Domain Name Query & IDN Implementation Guidelines
![](https://secure.gravatar.com/avatar/43effdcf0b64db8cc8772c60ab7b4bf6.jpg?s=120&d=mm&r=g)
Dear EPDP-IDNs Team, We hope the ICANN79 Community Forum is going smoothly for you all. It was great seeing you all on Saturday for the first session. While we wait to finalize the IDN Table harmonization mechanism topic, the leadership and staff would like to draw your attention again to the following revised languages related to domain name query and IDN Implementation Guidelines, as Ariel had shared last Wednesday, 28 Feb: https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vs... [docs.google.com]<https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vslv8/edit?pli=1%20%5bdocs.google.com%5d> * New Rec 12 & IG 17: pp.33-35 * New Rec 19: p.38, and rationale on p.43 (New Rec 14 and New IG 18 unchanged from last call) If no concerns with the above updates by Wednesday, 6 March, 16:00 UTC, we intend to move forward with the proposed language in the initial report. We look forward to your kind cooperation. Much appreciated, Ariel, Steve, Dan, and Saewon. From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces@icann.org> on behalf of Ariel Liang <ariel.liang@icann.org> Date: Wednesday, February 28, 2024 at 5:19 PM To: "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Subject: [Gnso-epdp-idn-team] Updated Recommendation Text for IDN Table Harmonization, Domain Name Query & IDN Implementation Guidelines Dear All, In preparation for the EPDP-IDNs Team meeting in ICANN79 San Juan, please find the updated recommendation text that will be discussed during the session on Saturday, 2 March at 9:00-10:00 Local time: For updated language related to domain name query and IDN Implementation Guidelines, please see here: https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vs... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vslv8/edit?pli=1__;!!PtGJab4!9-pc9rvSeGqInad4d2uvr08a8ox-OmmMk7V3Bwkv794q1D5YMiDWW0PfXRftaqIHf-qy9rKzHzRjD5Qng6EGa4fkvjWy$> * New Rec 12 & IG 17: pp.33-35 * New Rec 19: p.38, and rationale on p.43 (New Rec 14 and New IG 18 unchanged from last call) For the IDN Table harmonization mechanism topic, please find the leadership suggested recommendation text on pp.2 here: https://docs.google.com/document/d/1DUl7DkbCtncgw2__5NZku-GUj6zAt2UYyZA9FPBm... - heading=h.f5zexghzu33o [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DUl7DkbCtncgw2__5NZku-GUj6zAt2UYyZA9FPBmB58/edit*heading=h.f5zexghzu33o__;Iw!!PtGJab4!9-pc9rvSeGqInad4d2uvr08a8ox-OmmMk7V3Bwkv794q1D5YMiDWW0PfXRftaqIHf-qy9rKzHzRjD5Qng6EGa3hOyK3I$> * Note: page 1 contains previously agreed charter question C5 response and RySG input provided during the last call; rationale will be added after EPDP Team’s agreement on the recommendation text The suggested agenda for the session is the following: 1. Roll Call and SOI Updates (2 min) 2. Welcome and Chair Updates (3 min) 3. Proposed Draft Recommendations for C5 - IDN Table Harmonization Mechanism (30 min) 4. Close Loop on Updated Preliminary Recommendations on UDRP and IDN Implementation Guidelines (20 min) 5. Next Steps (2 min) 6. AOB (3 min) Safe travels to those who will attend ICANN79 in person, and look forward to seeing others online as well. Best Regards, Ariel
![](https://secure.gravatar.com/avatar/22b938c86873c8b76b126d353834a19d.jpg?s=120&d=mm&r=g)
Hi Saewon, thank you for your e-mail. I just reviewed the text and I found one issue, that I didn't think of before (sorry for commenting this so late). Regarding Rec 12 about RDDS responses, we write: "This desired scenario applies to the returned response to a query for both an allocated domain name and an unallocated domain name." I added a comment in the document stating: The answer when querying unallocated domain names can only be provided by Registries, but not by Registrars. In order to find out, whether a non-existing domain belongs to an existing variant set, the (2nd level) IDN table rules need to be consulted. These rules, however, are not available to registrars, but only to registries. Hence, it's nearly impossible for registrars to provide this information. I thus suggest for registrars to only require returning data when *existing" domain names are queried. 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
![](https://secure.gravatar.com/avatar/ee825a152e293ed1aeaf6ec3df1b5ab3.jpg?s=120&d=mm&r=g)
Hi Saewon, et al Apologies for the delayed response. The RySG support team deliberated Rec 12 and Implementation Guidance 17 and would like to provide the following observations: 1. We appreciate IG 17 replaced RDAP with RDDS. RDDS is more of an appropriate reference because it refers to the service and not the protocol. 2. RDDS in its current form (RDAP and WHOIS) is designed to return information on existing objects (i.e., an allocated domain name). This should be considered as a minimum requirement. A registry operator may want to expand the utility of RDDS if they so choose to. 3. We would like to move away from using the term “query” as this word has meaning in our registry agreements related to SLAs. We strongly prefer to not open an SLA conversation to enable a search function for variant domain names. We suggest call it a “service”. 4. Rec 12 does not reference a specific solution (e.g., RDDS); we like this because it allows for the solution set to consider other functions. Therefore, we would like to suggest expanding IG17 to include other alternatives in addition to RDDS. For your consideration we provide suggested revisions to Rec 12 and IG 17. Suggested Rec 12: Enable a service to discover the allocated variant domain names for a given domain name string, including an indication of the primary domain name(s) of the variant set. Suggested IG 17: Rec 12 is intended as a minimum requirement. Registry or registrar may choose to enhance the behavior of the service (RDDS or other alternative) to provide additional information or enable other methods to provide the information (e.g., bulk services). We are happy to discuss. Best, Dennis, on behalf the RySG reps From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces@icann.org> on behalf of Saewon Lee <saewon.lee@icann.org> Date: Monday, March 4, 2024 at 1:14 AM To: "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Subject: [EXTERNAL] [Gnso-epdp-idn-team] Reminder: Updated Recommendation Text for IDN Table Harmonization, Domain Name Query & IDN Implementation Guidelines Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Dear EPDP-IDNs Team, We hope the ICANN79 Community Forum is going smoothly for you all. It was great seeing you all on Saturday for the first session. While we wait to finalize the IDN Table harmonization mechanism topic, the leadership and staff would like to draw your attention again to the following revised languages related to domain name query and IDN Implementation Guidelines, as Ariel had shared last Wednesday, 28 Feb: https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vs... [docs.google.com]<https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vslv8/edit?pli=1%20%5bdocs.google.com%5d> * New Rec 12 & IG 17: pp.33-35 * New Rec 19: p.38, and rationale on p.43 (New Rec 14 and New IG 18 unchanged from last call) If no concerns with the above updates by Wednesday, 6 March, 16:00 UTC, we intend to move forward with the proposed language in the initial report. We look forward to your kind cooperation. Much appreciated, Ariel, Steve, Dan, and Saewon. From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces@icann.org> on behalf of Ariel Liang <ariel.liang@icann.org> Date: Wednesday, February 28, 2024 at 5:19 PM To: "gnso-epdp-idn-team@icann.org" <gnso-epdp-idn-team@icann.org> Subject: [Gnso-epdp-idn-team] Updated Recommendation Text for IDN Table Harmonization, Domain Name Query & IDN Implementation Guidelines Dear All, In preparation for the EPDP-IDNs Team meeting in ICANN79 San Juan, please find the updated recommendation text that will be discussed during the session on Saturday, 2 March at 9:00-10:00 Local time: For updated language related to domain name query and IDN Implementation Guidelines, please see here: https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vs... [docs.google.com]<https://secure-web.cisco.com/1QkgKPPAe7eMd-L2RFuf5HNCHHtZl914-Z11pdiV0zvw9XBJxrbH0O61OtVxWM6iNpDjBreuLzCxRcs8Cv3yb0BZhYvFWwdf9ooSZlyH0JgWFELBQ3qJDlmk2cp5W2ObRNaOZBuvUNmWMqur-x1wtR5q2myM9d_UOBsR39A3CvtOicXEfV1E-I_c9c-Lg5na_7XuzkMf8QtsphOj0xMRow8A9kwAk-idH0YflOUG6vo3csSUDR9OGsLD10qcaNacCQ7lTwcnuqqWtl0xjvjpHfgUFrODWJViBXqiIbH8ImFw/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fdocs.google.com%2Fdocument%2Fd%2F1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vslv8%2Fedit%3Fpli%3D1__%3B%21%21PtGJab4%219-pc9rvSeGqInad4d2uvr08a8ox-OmmMk7V3Bwkv794q1D5YMiDWW0PfXRftaqIHf-qy9rKzHzRjD5Qng6EGa4fkvjWy%24> * New Rec 12 & IG 17: pp.33-35 * New Rec 19: p.38, and rationale on p.43 (New Rec 14 and New IG 18 unchanged from last call) For the IDN Table harmonization mechanism topic, please find the leadership suggested recommendation text on pp.2 here: https://docs.google.com/document/d/1DUl7DkbCtncgw2__5NZku-GUj6zAt2UYyZA9FPBm... - heading=h.f5zexghzu33o [docs.google.com]<https://secure-web.cisco.com/1TlCeG7wfOWWZbM4as5Xi-jSBOtqEln689hwzsLpROXpYWK3gzN15Ku1HwkKuiT-nT0Es9tQq9bIUhUwoQQLvw-wLkIDWr58nfm-2qvYzr04Ddx0Sp10FGPqW0YLqWTdaRX96iOcu-c1QLOuveJUlm5j_j0m8OtNIHabsPmHkd2yI9w8_HCxH2dntyCMGb9H9J9-ia3JU6QnsNiDZEwDbl5Xrmgb-X3iVYDfIXn0guOBp8BzaAgMwwqwxzjEjc9D-dioND_Gc-XYir_htrmZP7AKlv-PyUmIg0N47tbF569E/https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2Fdocs.google.com%2Fdocument%2Fd%2F1DUl7DkbCtncgw2__5NZku-GUj6zAt2UYyZA9FPBmB58%2Fedit%2Aheading%3Dh.f5zexghzu33o__%3BIw%21%21PtGJab4%219-pc9rvSeGqInad4d2uvr08a8ox-OmmMk7V3Bwkv794q1D5YMiDWW0PfXRftaqIHf-qy9rKzHzRjD5Qng6EGa3hOyK3I%24> * Note: page 1 contains previously agreed charter question C5 response and RySG input provided during the last call; rationale will be added after EPDP Team’s agreement on the recommendation text The suggested agenda for the session is the following: 1. Roll Call and SOI Updates (2 min) 2. Welcome and Chair Updates (3 min) 3. Proposed Draft Recommendations for C5 - IDN Table Harmonization Mechanism (30 min) 4. Close Loop on Updated Preliminary Recommendations on UDRP and IDN Implementation Guidelines (20 min) 5. Next Steps (2 min) 6. AOB (3 min) Safe travels to those who will attend ICANN79 in person, and look forward to seeing others online as well. Best Regards, Ariel
![](https://secure.gravatar.com/avatar/dc8a4226179d0cece742a2c28d0532b7.jpg?s=120&d=mm&r=g)
Colleagues Good morning; to confirm that the GAC is delighted to confirm that we are happy to move ahead with the proposed language; Best Nigel From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces@icann.org> On Behalf Of Saewon Lee Sent: Monday, March 4, 2024 5:14 AM To: gnso-epdp-idn-team@icann.org Subject: [Gnso-epdp-idn-team] Reminder: Updated Recommendation Text for IDN Table Harmonization, Domain Name Query & IDN Implementation Guidelines Dear EPDP-IDNs Team, We hope the ICANN79 Community Forum is going smoothly for you all. It was great seeing you all on Saturday for the first session. While we wait to finalize the IDN Table harmonization mechanism topic, the leadership and staff would like to draw your attention again to the following revised languages related to domain name query and IDN Implementation Guidelines, as Ariel had shared last Wednesday, 28 Feb: https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vs... [docs.google.com]<https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vslv8/edit?pli=1%20%5bdocs.google.com%5d> * New Rec 12 & IG 17: pp.33-35 * New Rec 19: p.38, and rationale on p.43 (New Rec 14 and New IG 18 unchanged from last call) If no concerns with the above updates by Wednesday, 6 March, 16:00 UTC, we intend to move forward with the proposed language in the initial report. We look forward to your kind cooperation. Much appreciated, Ariel, Steve, Dan, and Saewon. From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces@icann.org<mailto:gnso-epdp-idn-team-bounces@icann.org>> on behalf of Ariel Liang <ariel.liang@icann.org<mailto:ariel.liang@icann.org>> Date: Wednesday, February 28, 2024 at 5:19 PM To: "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: [Gnso-epdp-idn-team] Updated Recommendation Text for IDN Table Harmonization, Domain Name Query & IDN Implementation Guidelines Dear All, In preparation for the EPDP-IDNs Team meeting in ICANN79 San Juan, please find the updated recommendation text that will be discussed during the session on Saturday, 2 March at 9:00-10:00 Local time: For updated language related to domain name query and IDN Implementation Guidelines, please see here: https://docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vs... [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1UrrckzbPNL1Z8fUtH5Q5WqUWglxbD-SbihX8o8Vslv8/edit?pli=1__;!!PtGJab4!9-pc9rvSeGqInad4d2uvr08a8ox-OmmMk7V3Bwkv794q1D5YMiDWW0PfXRftaqIHf-qy9rKzHzRjD5Qng6EGa4fkvjWy$> * New Rec 12 & IG 17: pp.33-35 * New Rec 19: p.38, and rationale on p.43 (New Rec 14 and New IG 18 unchanged from last call) For the IDN Table harmonization mechanism topic, please find the leadership suggested recommendation text on pp.2 here: https://docs.google.com/document/d/1DUl7DkbCtncgw2__5NZku-GUj6zAt2UYyZA9FPBm... - heading=h.f5zexghzu33o [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DUl7DkbCtncgw2__5NZku-GUj6zAt2UYyZA9FPBmB58/edit*heading=h.f5zexghzu33o__;Iw!!PtGJab4!9-pc9rvSeGqInad4d2uvr08a8ox-OmmMk7V3Bwkv794q1D5YMiDWW0PfXRftaqIHf-qy9rKzHzRjD5Qng6EGa3hOyK3I$> * Note: page 1 contains previously agreed charter question C5 response and RySG input provided during the last call; rationale will be added after EPDP Team’s agreement on the recommendation text The suggested agenda for the session is the following: 1. Roll Call and SOI Updates (2 min) 2. Welcome and Chair Updates (3 min) 3. Proposed Draft Recommendations for C5 - IDN Table Harmonization Mechanism (30 min) 4. Close Loop on Updated Preliminary Recommendations on UDRP and IDN Implementation Guidelines (20 min) 5. Next Steps (2 min) 6. AOB (3 min) Safe travels to those who will attend ICANN79 in person, and look forward to seeing others online as well. Best Regards, Ariel
participants (4)
-
Hickson, Nigel (DSIT)
-
Michael Bauland
-
Saewon Lee
-
Tan Tanaka, Dennis