August 2024 - Gnso-epdp-idn-team

Action Item 1: Feedback Request for Outputs 14-15
by Saewon Lee Sept. 4, 2024

Sept. 4, 2024

Dear EPDP-IDNs Team, Per our Team discussion, leadership/staff would like to share the proposed language for Outputs 14-15 with the respective rationales again for your review and feedback. Kindly review the proposal together with your respective groups and provide feedback either through the mailing list or during the next Team meeting (5 September), if possible. Leadership/staff envisions the finalization of these Outputs by Thursday, 12 September, at 12:00 UTC. * Output 14 Recommendation 14: Rationale for change After EPDP Team deliberations, it became apparent that two concepts were being combined in PR 14 and IG 15. Firstly, registries and registrars need a mechanism to communicate between themselves, to determine what the allocated and allocatable variant domain names are for a given domain name, for a variety of reasons, but principally, to ensure that the same entity requirement is adhered to. Secondarily, an end user 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). Because of these two distinct purposes, it likely makes sense to delineate them into a separate recommendation and implementation guidance. (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 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.” (Current Language within the Working Doc.) Final Recommendation 14: “To account for the “same entity” principle and its implications for variant domain names, ICANN org should work with relevant stakeholders to develop and enable a service to discover 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 Preliminary Recommendation 3 are exempt from this requirement.” * Output 15 Implementation Guidance 15: Rationale for change Support staff reached out to ICANN Legal, to determine whether there may be data privacy concerns from disclosing the allocated variant domain names of a given domain name. Though the disclosure of allocated variant domain names may not directly expose personal data, it could reveal details about the registrant that may unintentionally compromise their privacy. As such, the recommendation from legal is to restrict public access to this information or avoid disclosure altogether. However, there are reasons that an end user may need this information. (New 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.” (Current Language within the Working Doc.) Implementation Guidance 15 “Final Recommendation 14 is intended as a minimum requirement. A registry or a registrar may choose to enhance the behavior of the service to provide additional information or enable other methods to provide the following information (e.g., bulk services): 15.1 the required data elements for the given domain name in accordance with the Registration Data Policy; 15.2 all the other allocated variant domain name(s) under a given gTLD and its delegated gTLD variant label(s), if any; and 15.3 the source domain name used to calculate the variant domain set.” Thank you for your kind cooperation. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Wednesday, August 28, 2024 at 8:00 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-epdp-idn-team] Re: Review Request and New Language for Outputs 14-15 Dear EPDP-IDNs Team, Adding on to the long list of homework, kindly find the updates to pp.39-47 in Section 4 for “Charter Questions with No Outputs”: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> We look forward to your kind review and feedback by Wednesday, 4 September, 2024, at 21:00 UTC. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Tuesday, August 27, 2024 at 11:01 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-epdp-idn-team] Review Request and New Language for Outputs 14-15 Dear EPDP-IDNs Team, As we prepare for our next meeting on Thursday, 29 August at 12:00 UTC, this is a friendly reminder for the Team to review and provide feedback for “grandfathered” suggestions, Section 3 (Glossary), and Section 4 (Outputs 1-20, excluding 14-15, 17). The links to these documents are shared for your convenience again below: * Grandfathered suggestions: https://docs.google.com/spreadsheets/d/1EJdmbLg-mAst_ajV-P3DFRhzyE8O4vDKWdZ… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1EJdmbLg-…> * Section 3 (Glossary): https://docs.google.com/document/d/1DPjKUkbD6OUJ3iHkh3UZyEKFhVi-oGFdcG-7dfg… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DPjKUkbD6OUJ…> * Section 4 (Outputs 1-20): https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> As for the Outputs 14-15, please see below the suggested new language and the reason behind each one, based on the Public Comment and Team’s discussions, for your review. The current language within the working document is also presented for you below. This item will be discussed during our meeting this Thursday and the new language will only be incorporated into the working document once the Team reaches an agreement: * Output 14 Recommendation 14: Rationale for change After EPDP Team deliberations, it became apparent that two concepts were being combined in PR 14 and IG 15. Firstly, registries and registrars need a mechanism to communicate between themselves, to determine what the allocated and allocatable variant domain names are for a given domain name, for a variety of reasons, but principally, to ensure that the same entity requirement is adhered to. Secondarily, an end user 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). Because of these two distinct purposes, it likely makes sense to delineate them into a separate recommendation and implementation guidance. (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 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.” (Current Language within the Working Doc.) Final Recommendation 14: “To account for the “same entity” principle and its implications for variant domain names, ICANN org should work with relevant stakeholders to develop and enable a service to discover 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 Preliminary Recommendation 3 are exempt from this requirement.” * Output 15 Implementation Guidance 15: Rationale for change Support staff reached out to ICANN Legal, to determine whether there may be data privacy concerns from disclosing the allocated variant domain names of a given domain name. Though the disclosure of allocated variant domain names may not directly expose personal data, it could reveal details about the registrant that may unintentionally compromise their privacy. As such, the recommendation from legal is to restrict public access to this information or avoid disclosure altogether. However, there are reasons that an end user may need this information. (New 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.” (Current Language within the Working Doc.) Implementation Guidance 15 “Final Recommendation 14 is intended as a minimum requirement. A registry or a registrar may choose to enhance the behavior of the service to provide additional information or enable other methods to provide the following information (e.g., bulk services): 15.1 the required data elements for the given domain name in accordance with the Registration Data Policy; 15.2 all the other allocated variant domain name(s) under a given gTLD and its delegated gTLD variant label(s), if any; and 15.3 the source domain name used to calculate the variant domain set.” Thank you for your kind consideration and we look forward to the discussions soon. Warm regards, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Wednesday, August 21, 2024 at 6:58 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-epdp-idn-team] Meeting to Resume 29 August (Usual Meeting Time) Dear EPDP-IDNs Team, We hope you are having a great 2-week break from the EPDP-IDNs! Based on the result of the doodle poll as well as re-evaluating the progress of the remaining work, the Team Meeting will resume on Thursday, 29 August, at 12:00 UTC on the usual meeting time. As previously announced, if the Team needs extra time for further discussions, this will be scheduled for another week in September. In addition, please review the updated language within Outputs 10-13, 16, 18-20 (pp.20-27, 29, 31-37). Kindly note that Outputs 14-15, and 17 are still a work in progress and will be flagged for review at a later date. Also, the Leadership will be reviewing the updated language in parallel with the Team: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> As a reminder, kindly also review and provide feedback to the other requests below, including “grandfathered” suggestions, Section 3 (Glossary), and Section 4 (Outputs 1-9), for a fruitful meeting when we resume. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Wednesday, August 14, 2024 at 7:48 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] Meeting to Resume End of August (Week of 26 August) Dear EPDP-IDNs Team, Sincere apologies for the abrupt announcement, but due to unforeseen circumstances which involve the absence of Leadership/several Team members, the EPDP-IDNs Team Meeting for this week and next (15 and 22 August) will be canceled, only to resume during the last week of August (Week of 26 August). The Leadership suggests that, if possible, the Team holds 2 meetings during the last week of August (possibly Tuesday, 27 August and the usual Thursday, 29 August), to not only pick up where we left off but to hopefully conclude the review of comments within the working document for all outputs and other public comment inputs. A doodle poll will be sent out for another meeting during the last week, and if not possible to find the extra time, our meeting will still proceed on Thursday, 29 August. Further scheduling for September (if any more to be scheduled beyond 5 September, other than the Final Consensus Call) will be discussed on 29 August. As another reminder, the updates for Recs.10-20 will be shared soon. In the meantime, please review and provide feedback to the requests below (as none have been provided yet), including “grandfathered” suggestions, Section 3 (Glossary), and Section 4 (Outputs 1-9), for a fruitful meeting when we resume. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Tuesday, August 13, 2024 at 10:44 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] "Grandfathering" for Review Dear EPDP-IDNs Team, As briefly mentioned via our last Team Meeting on 8 August, kindly find in the link ICANN org’s suggested updates to the term, “grandfathered” for your review: https://docs.google.com/spreadsheets/d/1EJdmbLg-mAst_ajV-P3DFRhzyE8O4vDKWdZ… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1EJdmbLg-…> The columns are arranged as follows: * Column A: Relevant Output/Rationale (name/number) where the term is included * Column B: Particular sentence/paragraph including the term(s) * Column C: Replaced term(s) * Column D: Revised sentence/paragraph * Column E: Full text of the Output/Rationale to understand the context * Column F: Notes Upon Leadership/Staff’s revision of ICANN org’s suggested text(s), the Leadership has drawn the conclusion that ICANN org’s approach is the simplest and least disruptive in addressing org’s concerns about using the term, “grandfathered,” in our report. As you can see within the spreadsheet, the general term that was used to replace “grandfathered” was “exempted” (or in some cases, “excluded,” if duplicated within one sentence), which does seem to adequately convey the meaning or intent of the recommendations as drafted. As a reminder, the terms instead of “grandfathered,” that were suggested from ICANN org and the Team via discussions were: * Pre-existing domains * Exempted domains * Domains created before a certain date * Right of Continuance * Transitional exceptions Also as a reminder, please review Section 3 and Section 4 (Outputs 1-9) within the working docs as requested in the emails below. The links are shared with you again for your convenience: * Section 3 (Glossary) pp.8, 11-15: https://docs.google.com/document/d/1DPjKUkbD6OUJ3iHkh3UZyEKFhVi-oGFdcG-7dfg… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DPjKUkbD6OUJ…> * Section 4 (Outputs 1-9) pp.3-20: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> The updates for 10-20 and other general comments will be notified soon. We look forward to your kind review and further discussions related to the terms and Outputs during our next Team meeting. Kind regards, Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Tuesday, August 6, 2024 at 3:31 PM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] Working Doc (Section 3) for Review Dear EPDP-IDNs Team, Following Section 4, please find the updated language for Section 3 (Glossary) based on the public comments received; https://docs.google.com/document/d/1DPjKUkbD6OUJ3iHkh3UZyEKFhVi-oGFdcG-7dfg… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DPjKUkbD6OUJ…> The pages to focus on are pp.8, 11-15; Once again, please provide your feedback (sidebar comments only) mainly on the aforementioned parts to review together on Thursday, 15 August, during our Team Meeting. Updates for other parts of the section (or overall) will occur at a later date. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee <saewon.lee(a)icann.org> Date: Monday, August 5, 2024 at 6:32 PM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: Working Doc (Section 4) for Review Dear EPDP-IDNs Team, We hope this email finds you well. Please find the updated language for Outputs 1-9 so far in the working doc., based on the discussions from the Public Comment Review; https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> The pages to focus on are pp.3-19; please provide your feedback (sidebar comments only) to the aforementioned parts only to review together on Thursday, 15 August, during our Team Meeting. Please also note that more updates will occur post Rys’ feedback (post Tuesday, 6 August) and Section 3 updates will also be shared soon. Updates for other parts of the section will occur at a later date. Much appreciated, Steve, Dan, and Saewon.

4 7

Action Item 2: Feedback Request for Outputs 18 and 20
by Saewon Lee Aug. 30, 2024

Aug. 30, 2024

Dear EPDP-IDNs Team, For the next item, leadership/staff would like to share the proposed language for Final Recommendations 18 and 20 with the respective rationales for your review and feedback. Again, kindly review the proposal together with your respective groups and provide feedback either through the mailing list or during the next Team meeting (5 September), if possible. Leadership/staff envisions the finalization of these Outputs by Thursday, 5 September, at 12:00 UTC. * Output 18 Recommendation 18: Rationale for change (Excerpt from Section 4 – Please note that the rationale portion was too long to share via email, thus only the relevant part has been extracted here for review. For further details, please see the working document via pp.34-37: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj…) “However, in accordance with the Public Comment input, the EPDP Team decided that the ICANN Board will have the ultimate oversight responsibility and be charged with developing and updating the IDN Implementation Guidelines, rather than through its subset or its relevant successor, in consultation with the ICANN community. Moreover, the documented process must be conducted in consultation with the GNSO Council and the ccNSO Council.” (Proposal) Final Recommendation 18: “The existing process for developing and updating the IDN Implementation Guidelines, that includes establishing a working group of community experts and ICANN org staff, under the governance of ICANN Board, must be maintained. The process for developing and updating the IDN Implementation Guidelines must be formalized and documented to enhance its predictability, transparency, rigor, efficiency, and effectiveness. The ICANN Board will be responsible for documenting the process, in consultation with the ICANN community. The documented process must be approved by the ICANN Board, in consultation with the GNSO Council and ccNSO Council.” (Current Language within the Working Doc.) Final Recommendation 18: (Again, only extracted the line in question here) “The documented process must be approved by the GNSO Council, the ccNSO Council, and the ICANN Board..” * Output 20 Recommendation 20: Rationale for change “Though the ICANN Board has ownership of the documented process for developing and updating the IDN Implementation Guidelines, as set out in Final Recommendation 18, the EPDP Team agreed that moving forward, any future versions of the Guidelines must be approved by the GNSO Council prior to consideration by the ICANN Board. This is a significant procedural change from the existing practice. As the Guidelines is a compulsory document for ICANN contracted parties (gTLD registries and registrars offering IDN registration) and contains contractual obligations, seeking GNSO Council’s approval of any new future version prior to the ICANN Board consideration is of critical importance. This will also help mitigate the challenging situation incurred when the final version of the proposed draft 4.0 was published for Board consideration, as explained in the rationale for Final Recommendation 18. Further, while ccTLD managers are not contractually required to adhere to the Guidelines, they are expected to be guided by it. Thus, seeking ccNSO Council's consideration during the approval process will also ensure that the other impacted party aligns with the proposed changes or updates in the future versions prior to Board consideration, ultimately ensuring consistency at the second-level.” (Proposal) Final Recommendation 20: “Any future versions of the IDN Implementation Guidelines must be approved by the GNSO Council prior to consideration by the ICANN Board.” (Current Language within the Working Doc.) Final Recommendation 20: “Any future versions of the IDN Implementation Guidelines must be approved by the GNSO Council and the ccNSO Council prior to consideration and approval by the ICANN Board.” Thank you for your kind cooperation. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Friday, August 30, 2024 at 12:45 PM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-epdp-idn-team] Action Item 1: Feedback Request for Outputs 14-15 Dear EPDP-IDNs Team, Per our Team discussion, leadership/staff would like to share the proposed language for Outputs 14-15 with the respective rationales again for your review and feedback. Kindly review the proposal together with your respective groups and provide feedback either through the mailing list or during the next Team meeting (5 September), if possible. Leadership/staff envisions the finalization of these Outputs by Thursday, 12 September, at 12:00 UTC. * Output 14 Recommendation 14: Rationale for change After EPDP Team deliberations, it became apparent that two concepts were being combined in PR 14 and IG 15. Firstly, registries and registrars need a mechanism to communicate between themselves, to determine what the allocated and allocatable variant domain names are for a given domain name, for a variety of reasons, but principally, to ensure that the same entity requirement is adhered to. Secondarily, an end user 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). Because of these two distinct purposes, it likely makes sense to delineate them into a separate recommendation and implementation guidance. (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 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.” (Current Language within the Working Doc.) Final Recommendation 14: “To account for the “same entity” principle and its implications for variant domain names, ICANN org should work with relevant stakeholders to develop and enable a service to discover 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 Preliminary Recommendation 3 are exempt from this requirement.” * Output 15 Implementation Guidance 15: Rationale for change Support staff reached out to ICANN Legal, to determine whether there may be data privacy concerns from disclosing the allocated variant domain names of a given domain name. Though the disclosure of allocated variant domain names may not directly expose personal data, it could reveal details about the registrant that may unintentionally compromise their privacy. As such, the recommendation from legal is to restrict public access to this information or avoid disclosure altogether. However, there are reasons that an end user may need this information. (New 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.” (Current Language within the Working Doc.) Implementation Guidance 15 “Final Recommendation 14 is intended as a minimum requirement. A registry or a registrar may choose to enhance the behavior of the service to provide additional information or enable other methods to provide the following information (e.g., bulk services): 15.1 the required data elements for the given domain name in accordance with the Registration Data Policy; 15.2 all the other allocated variant domain name(s) under a given gTLD and its delegated gTLD variant label(s), if any; and 15.3 the source domain name used to calculate the variant domain set.” Thank you for your kind cooperation. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Wednesday, August 28, 2024 at 8:00 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-epdp-idn-team] Re: Review Request and New Language for Outputs 14-15 Dear EPDP-IDNs Team, Adding on to the long list of homework, kindly find the updates to pp.39-47 in Section 4 for “Charter Questions with No Outputs”: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> We look forward to your kind review and feedback by Wednesday, 4 September, 2024, at 21:00 UTC. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Tuesday, August 27, 2024 at 11:01 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-epdp-idn-team] Review Request and New Language for Outputs 14-15 Dear EPDP-IDNs Team, As we prepare for our next meeting on Thursday, 29 August at 12:00 UTC, this is a friendly reminder for the Team to review and provide feedback for “grandfathered” suggestions, Section 3 (Glossary), and Section 4 (Outputs 1-20, excluding 14-15, 17). The links to these documents are shared for your convenience again below: * Grandfathered suggestions: https://docs.google.com/spreadsheets/d/1EJdmbLg-mAst_ajV-P3DFRhzyE8O4vDKWdZ… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1EJdmbLg-…> * Section 3 (Glossary): https://docs.google.com/document/d/1DPjKUkbD6OUJ3iHkh3UZyEKFhVi-oGFdcG-7dfg… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DPjKUkbD6OUJ…> * Section 4 (Outputs 1-20): https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> As for the Outputs 14-15, please see below the suggested new language and the reason behind each one, based on the Public Comment and Team’s discussions, for your review. The current language within the working document is also presented for you below. This item will be discussed during our meeting this Thursday and the new language will only be incorporated into the working document once the Team reaches an agreement: * Output 14 Recommendation 14: Rationale for change After EPDP Team deliberations, it became apparent that two concepts were being combined in PR 14 and IG 15. Firstly, registries and registrars need a mechanism to communicate between themselves, to determine what the allocated and allocatable variant domain names are for a given domain name, for a variety of reasons, but principally, to ensure that the same entity requirement is adhered to. Secondarily, an end user 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). Because of these two distinct purposes, it likely makes sense to delineate them into a separate recommendation and implementation guidance. (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 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.” (Current Language within the Working Doc.) Final Recommendation 14: “To account for the “same entity” principle and its implications for variant domain names, ICANN org should work with relevant stakeholders to develop and enable a service to discover 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 Preliminary Recommendation 3 are exempt from this requirement.” * Output 15 Implementation Guidance 15: Rationale for change Support staff reached out to ICANN Legal, to determine whether there may be data privacy concerns from disclosing the allocated variant domain names of a given domain name. Though the disclosure of allocated variant domain names may not directly expose personal data, it could reveal details about the registrant that may unintentionally compromise their privacy. As such, the recommendation from legal is to restrict public access to this information or avoid disclosure altogether. However, there are reasons that an end user may need this information. (New 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.” (Current Language within the Working Doc.) Implementation Guidance 15 “Final Recommendation 14 is intended as a minimum requirement. A registry or a registrar may choose to enhance the behavior of the service to provide additional information or enable other methods to provide the following information (e.g., bulk services): 15.1 the required data elements for the given domain name in accordance with the Registration Data Policy; 15.2 all the other allocated variant domain name(s) under a given gTLD and its delegated gTLD variant label(s), if any; and 15.3 the source domain name used to calculate the variant domain set.” Thank you for your kind consideration and we look forward to the discussions soon. Warm regards, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Wednesday, August 21, 2024 at 6:58 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-epdp-idn-team] Meeting to Resume 29 August (Usual Meeting Time) Dear EPDP-IDNs Team, We hope you are having a great 2-week break from the EPDP-IDNs! Based on the result of the doodle poll as well as re-evaluating the progress of the remaining work, the Team Meeting will resume on Thursday, 29 August, at 12:00 UTC on the usual meeting time. As previously announced, if the Team needs extra time for further discussions, this will be scheduled for another week in September. In addition, please review the updated language within Outputs 10-13, 16, 18-20 (pp.20-27, 29, 31-37). Kindly note that Outputs 14-15, and 17 are still a work in progress and will be flagged for review at a later date. Also, the Leadership will be reviewing the updated language in parallel with the Team: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> As a reminder, kindly also review and provide feedback to the other requests below, including “grandfathered” suggestions, Section 3 (Glossary), and Section 4 (Outputs 1-9), for a fruitful meeting when we resume. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Wednesday, August 14, 2024 at 7:48 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] Meeting to Resume End of August (Week of 26 August) Dear EPDP-IDNs Team, Sincere apologies for the abrupt announcement, but due to unforeseen circumstances which involve the absence of Leadership/several Team members, the EPDP-IDNs Team Meeting for this week and next (15 and 22 August) will be canceled, only to resume during the last week of August (Week of 26 August). The Leadership suggests that, if possible, the Team holds 2 meetings during the last week of August (possibly Tuesday, 27 August and the usual Thursday, 29 August), to not only pick up where we left off but to hopefully conclude the review of comments within the working document for all outputs and other public comment inputs. A doodle poll will be sent out for another meeting during the last week, and if not possible to find the extra time, our meeting will still proceed on Thursday, 29 August. Further scheduling for September (if any more to be scheduled beyond 5 September, other than the Final Consensus Call) will be discussed on 29 August. As another reminder, the updates for Recs.10-20 will be shared soon. In the meantime, please review and provide feedback to the requests below (as none have been provided yet), including “grandfathered” suggestions, Section 3 (Glossary), and Section 4 (Outputs 1-9), for a fruitful meeting when we resume. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Tuesday, August 13, 2024 at 10:44 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] "Grandfathering" for Review Dear EPDP-IDNs Team, As briefly mentioned via our last Team Meeting on 8 August, kindly find in the link ICANN org’s suggested updates to the term, “grandfathered” for your review: https://docs.google.com/spreadsheets/d/1EJdmbLg-mAst_ajV-P3DFRhzyE8O4vDKWdZ… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1EJdmbLg-…> The columns are arranged as follows: * Column A: Relevant Output/Rationale (name/number) where the term is included * Column B: Particular sentence/paragraph including the term(s) * Column C: Replaced term(s) * Column D: Revised sentence/paragraph * Column E: Full text of the Output/Rationale to understand the context * Column F: Notes Upon Leadership/Staff’s revision of ICANN org’s suggested text(s), the Leadership has drawn the conclusion that ICANN org’s approach is the simplest and least disruptive in addressing org’s concerns about using the term, “grandfathered,” in our report. As you can see within the spreadsheet, the general term that was used to replace “grandfathered” was “exempted” (or in some cases, “excluded,” if duplicated within one sentence), which does seem to adequately convey the meaning or intent of the recommendations as drafted. As a reminder, the terms instead of “grandfathered,” that were suggested from ICANN org and the Team via discussions were: * Pre-existing domains * Exempted domains * Domains created before a certain date * Right of Continuance * Transitional exceptions Also as a reminder, please review Section 3 and Section 4 (Outputs 1-9) within the working docs as requested in the emails below. The links are shared with you again for your convenience: * Section 3 (Glossary) pp.8, 11-15: https://docs.google.com/document/d/1DPjKUkbD6OUJ3iHkh3UZyEKFhVi-oGFdcG-7dfg… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DPjKUkbD6OUJ…> * Section 4 (Outputs 1-9) pp.3-20: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> The updates for 10-20 and other general comments will be notified soon. We look forward to your kind review and further discussions related to the terms and Outputs during our next Team meeting. Kind regards, Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Tuesday, August 6, 2024 at 3:31 PM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] Working Doc (Section 3) for Review Dear EPDP-IDNs Team, Following Section 4, please find the updated language for Section 3 (Glossary) based on the public comments received; https://docs.google.com/document/d/1DPjKUkbD6OUJ3iHkh3UZyEKFhVi-oGFdcG-7dfg… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DPjKUkbD6OUJ…> The pages to focus on are pp.8, 11-15; Once again, please provide your feedback (sidebar comments only) mainly on the aforementioned parts to review together on Thursday, 15 August, during our Team Meeting. Updates for other parts of the section (or overall) will occur at a later date. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee <saewon.lee(a)icann.org> Date: Monday, August 5, 2024 at 6:32 PM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: Working Doc (Section 4) for Review Dear EPDP-IDNs Team, We hope this email finds you well. Please find the updated language for Outputs 1-9 so far in the working doc., based on the discussions from the Public Comment Review; https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> The pages to focus on are pp.3-19; please provide your feedback (sidebar comments only) to the aforementioned parts only to review together on Thursday, 15 August, during our Team Meeting. Please also note that more updates will occur post Rys’ feedback (post Tuesday, 6 August) and Section 3 updates will also be shared soon. Updates for other parts of the section will occur at a later date. Much appreciated, Steve, Dan, and Saewon.

1 0

FW: Request for IDN EPDP Leadership Team
by Saewon Lee Aug. 30, 2024

Aug. 30, 2024

Dear EPDP-IDNs Team, Please find below the email from Sarmad withdrawing the request associated with Recommendation 6 in response to Charter Question C5. Kind regards, EPDP-IDNs Support Staff on behalf of EPDP-IDNs Leadership Team From: Saewon Lee <saewon.lee(a)icann.org> Date: Thursday, August 29, 2024 at 11:55 AM To: "DonnaAustin605(a)hotmail.com" <DonnaAustin605(a)hotmail.com>, "farell(a)benin2point0.org" <farell(a)benin2point0.org>, Manju Chen <manju(a)nii.org.tw> Cc: Steve Chan <steve.chan(a)icann.org>, Daniel Gluck <daniel.gluck(a)icann.org> Subject: FW: Request for IDN EPDP Leadership Team Dear EPDP-IDNs Leadership Team, Please see the message below from ICANN org (Sarmad and team), as requested. Kind regards, Steve, Dan, and Saewon. From: Sarmad Hussain <sarmad.hussain(a)icann.org> Date: Thursday, August 29, 2024 at 11:42 AM To: Steve Chan <steve.chan(a)icann.org>, Saewon Lee <saewon.lee(a)icann.org> Cc: Pitinan Kooarmornpatana <pitinan.koo(a)icann.org>, Michael Karakash <michael.karakash(a)icann.org> Subject: Request for IDN EPDP Leadership Team Dear Steve and Saewon, Following IDN EPDP and our discussions, may I request you to pass on the following message to the IDN EPDP Leadership Team. Regards, Sarmad ===== Dear IDN EPDP Leadership Team, Thank you for considering our request on stabilizing the IDN Table harmonization related recommendations in IDN EPDP Phase 2, and exploring ways to expedite the process. The preparatory work for these recommendations would have served as an input for ICANN org for the RSP Evaluation Program. However, we also recognize the concerns that derive from the fact that the corresponding policy recommendations are not yet considered by the GNSO and the ICANN Board. Therefore, we are writing to withdraw the request and will find a solution which works within the existing framework. Once again, we greatly appreciate your kind consideration of this matter and look forward to the final IDN EPDP Phase 2 recommendations. Sincerely, Sarmad

1 0

Post Call | IDNs EPDP Team call | Thursday, 29 August 2024
by Devan Reed Aug. 29, 2024

Aug. 29, 2024

Dear all, All recordings for the IDNs EPDP Team call held on Thursday, 29 August 2024 can be found on the agenda wiki page <https://community.icann.org/x/I4BFF> (attendance included) and the GNSO Master Calendar<https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…>. These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom recording (including audio, visual, rough transcript, chat) * Transcript * Agenda & Notes/Action Items (if applicable) For additional information, you may consult the mailing list archives <https://urldefense.com/v3/__https:/lists.icann.org/hyperkitty/list/gnso-epd…> and the main wiki page<https://community.icann.org/x/uAPpCQ>. Thank you! Kind Regards, Devan

1 0

IDNs EPDP Team meeting
by ICANN Policy Calendar Aug. 29, 2024

Aug. 29, 2024

Meeting: IDNs EPDP Team meeting Date/Time: Thursday, 12 September 2024 at 12:00 UTC for 2 hours Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the 2024 Wiki pages: https://community.icann.org/x/vgGWEQ * Check your time zone: https://tinyurl.com/27due68j ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands.

1 0

Meeting Invitation | IDNs EPDP Team | Thursday, 05 September 2024 at 12:00 UTC
by Devan Reed Aug. 29, 2024

Aug. 29, 2024

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 05 September 2024 at 12:00 UTC for 2 hours. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the agenda Wiki page: https://community.icann.org/x/JYBFF * Check your time zone: https://tinyurl.com/2hswjm3c ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Devan Policy Team Supporting the GNSO

1 0

FW: [GNSO-TPR] Re: Internationalized Domain Names (IDNs) EPDP recommendations related to the Transfer Policy
by Steve Chan Aug. 29, 2024

Aug. 29, 2024

Dear EPDP Team members, Please see the email sent to the Transfer Policy Review PDP. As you can see below, the Transfer Policy Review PDP “Leadership and Support Staff have discussed this, and we do not think these recommendations should affect this group’s work or timeline. In short, the implementation of these recommendations may require updates to the Transfer Policy, but the recommendations do not conflict or affect any of the current policy recommendations in our Initial Report.” You can also see the limited feedback received to date from the PDP members. Best, Steve From: Steinar Grøtterød via GNSO-TPR <gnso-tpr(a)icann.org> Reply-To: Steinar Grøtterød <steinar(a)recito.no> Date: Thursday, August 22, 2024 at 12:55 PM To: "gnso-tpr(a)icann.org" <gnso-tpr(a)icann.org> Subject: [GNSO-TPR] Re: Internationalized Domain Names (IDNs) EPDP recommendations related to the Transfer Policy Dear all, I have received the following from Satish Babu. At-Large representative in the EPDP: PR 10-12 are the direct consequence of the "Same Entity" principle that was first formulated during the Phase 1 stage of the EPDP, and has continued into Phase 2 as well. At the second level, when we enumerate the variants of existing domain names, it is possible that two active domain names, belonging to different applicants, turn out to be variants of each other. This would be a violation of the "Same Entity" principle, and therefore we need a special process to handle this, which is grandfathering. As pointed out in the mail, these recommendations are unlikely to conflict with the TRP recommendations, and may only require some update to the language. Regards, Steinar Grøtterød At-Large From: rcarney--- via GNSO-TPR <gnso-tpr(a)icann.org> Date: Thursday, 22 August 2024 at 21:35 To: gnso-tpr(a)icann.org <gnso-tpr(a)icann.org> Subject: [GNSO-TPR] Re: Internationalized Domain Names (IDNs) EPDP recommendations related to the Transfer Policy Good Afternoon, Just a quick reminder to review the items below and if you have concerns with the recommendations as written by the IDN WG, you may wish to reach out to your SG/C representatives in the EPDP Team as soon as possible to ensure the EPDP Team can consider concerns (if any) Thanks Roger ________________________________ From: Caitlin Tubergen via GNSO-TPR <gnso-tpr(a)icann.org> Sent: Thursday, August 15, 2024 5:43 PM To: gnso-tpr(a)icann.org <gnso-tpr(a)icann.org> Subject: [GNSO-TPR] Internationalized Domain Names (IDNs) EPDP recommendations related to the Transfer Policy Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Dear TPR Working Group Members, We hope you are enjoying your well-deserved break. We do not mean to disrupt your break, but did want to inform you that the Internationalized Domain Name (IDN) EPDP Team is working to complete its Phase 2 Final Report over the next several weeks. Why does this matter to the TPR WG? The Phase 2 Final Report has three recommendations which directly or indirectly reference the Transfer Policy. These are explained in more detail later in this message. I see that the Transfer Policy is referenced, but does this affect our timeline or Final Report? Leadership and Support Staff have discussed this, and we do not think these recommendations should affect this group’s work or timeline. In short, the implementation of these recommendations may require updates to the Transfer Policy, but the recommendations do not conflict or affect any of the current policy recommendations in our Initial Report. Why are you telling me this now? The short answer is that the EPDP on IDNs Phase 2 is finalizing its Final Report and seeks assurance that these particular recommendations will not have an impact on or contradict the work of the TPR WG, so if you have concerns with the recommendations as written, you may wish to reach out to your SG/C representatives in the EPDP Team as soon as possible to ensure the EPDP Team can consider concerns (if any). It is worth noting, though, that the ALAC, BC, NCSG, RrSG, and RySG all participated in the Public Comment period. In other words, some concerns have already been expressed to the IDN EPDP Team in the public comments, and the EPDP Team is in the process of reviewing all public comments received; this outreach is in fact in response to the public comment review process. What do these IDN Phase 2 Recommendations say? * Preliminary Recommendation 10: In the event an inter-registrar transfer process is initiated for a domain name, which is a member of a variant domain set, the process must encompass all of its allocated variant domain names, if any, together. The grandfathered variant domain names pursuant to Preliminary Recommendation 3 are exempt from this requirement. [TPR Leadership note: This will likely require an update to the Transfer Policy as part of implementation, but does not conflict with the TPR WG’s recommendations.] * Preliminary Recommendation 11: In the event a domain name is ordered to be transferred as a result of a Uniform Domain Name Dispute Resolution Policy (UDRP) administrative proceeding, the transfer process must include the domain name and all of its allocated variant domain names, if any, together. The grandfathered variant domain names pursuant to Preliminary Recommendation 3 are exempt from this requirement. [TPR Leadership note: This will likely require an update to the UDRP Rules as part of implementation, but does not conflict with the TPR WG’s recommendations.] * Implementation Guidance 12: A Uniform Rapid Suspension System (URS) complainant is responsible for deciding whether to include allocated variant domain names, if any, of a disputed domain name as part of their URS complaint. [TPR Leadership Note: This recommendation may require an update to the URS Rules as part of implementation, but does not conflict with the TPR WG recommendations.] As noted above, if you have concerns with these recommendations that were not raised as part of your group’s public comment submission, we would recommend that you reach out to your designated EPDP representatives<https://community.icann.org/display/epdpidn/5.+PDP+Members+and+mailing+list…> as soon as possible so they can be discussed with the IDN EPDP Team (expected timeline: 5 September) prior to its submission of its Final Report to the GNSO Council (expected due date: 7 October). Thank you, and we hope you enjoy the rest of your break. Best regards, Caitlin on behalf of the TPR Staff Support Team

1 0

15 MINUTES REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 29 August 2024 at 12:00 UTC
by Devan Reed Aug. 29, 2024

Aug. 29, 2024

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 29 August 2024 at 12:00 UTC for 2 hours. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the agenda Wiki page: https://community.icann.org/x/HYBFF * Check your time zone: https://tinyurl.com/ftjcxx7f ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

REMINDER | Meeting Invitation | IDNs EPDP Team | Thursday, 29 August 2024 at 12:00 UTC
by Terri Agnew Aug. 28, 2024

Aug. 28, 2024

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 29 August 2024 at 12:00 UTC for 2 hours. Please click link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94276275950?pwd=dG5hanFz…> Passcode: !!0tV0Wh&K For Audio only: One tap mobile : US: +13017158592,,94276275950#,,,,*5259149775# or +13126266799,,94276275950#,,,,*5259149775# Webinar ID: 942 7627 5950 Passcode: 5259149775 International numbers available: https://icann.zoom.us/u/adP1jJ0gRH <https://urldefense.com/v3/__https:/icann.zoom.us/u/adP1jJ0gRH__;!!PtGJab4!v…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> Members, participants, and observers all have different access and participation directions, please read below! ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior <https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the agenda Wiki page: https://community.icann.org/x/HYBFF * Check your time zone: https://tinyurl.com/ftjcxx7f ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Everyone, when posting to the chat in order for everyone to see and to be captured afterwards. Only for Observers: * Observers will have ability to view member chat and information shared in the zoom webinar room. * Observers will not be able to use chat or raise hands. Thank you. Kind regards, Terri Policy Team Supporting the GNSO

1 0

Re: Review Request and New Language for Outputs 14-15
by Saewon Lee Aug. 28, 2024

Aug. 28, 2024

Dear EPDP-IDNs Team, Adding on to the long list of homework, kindly find the updates to pp.39-47 in Section 4 for “Charter Questions with No Outputs”: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… We look forward to your kind review and feedback by Wednesday, 4 September, 2024, at 21:00 UTC. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Tuesday, August 27, 2024 at 11:01 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-epdp-idn-team] Review Request and New Language for Outputs 14-15 Dear EPDP-IDNs Team, As we prepare for our next meeting on Thursday, 29 August at 12:00 UTC, this is a friendly reminder for the Team to review and provide feedback for “grandfathered” suggestions, Section 3 (Glossary), and Section 4 (Outputs 1-20, excluding 14-15, 17). The links to these documents are shared for your convenience again below: * Grandfathered suggestions: https://docs.google.com/spreadsheets/d/1EJdmbLg-mAst_ajV-P3DFRhzyE8O4vDKWdZ… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1EJdmbLg-…> * Section 3 (Glossary): https://docs.google.com/document/d/1DPjKUkbD6OUJ3iHkh3UZyEKFhVi-oGFdcG-7dfg… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DPjKUkbD6OUJ…> * Section 4 (Outputs 1-20): https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> As for the Outputs 14-15, please see below the suggested new language and the reason behind each one, based on the Public Comment and Team’s discussions, for your review. The current language within the working document is also presented for you below. This item will be discussed during our meeting this Thursday and the new language will only be incorporated into the working document once the Team reaches an agreement: * Output 14 Recommendation 14: Rationale for change After EPDP Team deliberations, it became apparent that two concepts were being combined in PR 14 and IG 15. Firstly, registries and registrars need a mechanism to communicate between themselves, to determine what the allocated and allocatable variant domain names are for a given domain name, for a variety of reasons, but principally, to ensure that the same entity requirement is adhered to. Secondarily, an end user 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). Because of these two distinct purposes, it likely makes sense to delineate them into a separate recommendation and implementation guidance. (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 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.” (Current Language within the Working Doc.) Final Recommendation 14: “To account for the “same entity” principle and its implications for variant domain names, ICANN org should work with relevant stakeholders to develop and enable a service to discover 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 Preliminary Recommendation 3 are exempt from this requirement.” * Output 15 Implementation Guidance 15: Rationale for change Support staff reached out to ICANN Legal, to determine whether there may be data privacy concerns from disclosing the allocated variant domain names of a given domain name. Though the disclosure of allocated variant domain names may not directly expose personal data, it could reveal details about the registrant that may unintentionally compromise their privacy. As such, the recommendation from legal is to restrict public access to this information or avoid disclosure altogether. However, there are reasons that an end user may need this information. (New 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.” (Current Language within the Working Doc.) Implementation Guidance 15 “Final Recommendation 14 is intended as a minimum requirement. A registry or a registrar may choose to enhance the behavior of the service to provide additional information or enable other methods to provide the following information (e.g., bulk services): 15.1 the required data elements for the given domain name in accordance with the Registration Data Policy; 15.2 all the other allocated variant domain name(s) under a given gTLD and its delegated gTLD variant label(s), if any; and 15.3 the source domain name used to calculate the variant domain set.” Thank you for your kind consideration and we look forward to the discussions soon. Warm regards, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Wednesday, August 21, 2024 at 6:58 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Cc: GNSO-Secs <gnso-secs(a)icann.org> Subject: [Gnso-epdp-idn-team] Meeting to Resume 29 August (Usual Meeting Time) Dear EPDP-IDNs Team, We hope you are having a great 2-week break from the EPDP-IDNs! Based on the result of the doodle poll as well as re-evaluating the progress of the remaining work, the Team Meeting will resume on Thursday, 29 August, at 12:00 UTC on the usual meeting time. As previously announced, if the Team needs extra time for further discussions, this will be scheduled for another week in September. In addition, please review the updated language within Outputs 10-13, 16, 18-20 (pp.20-27, 29, 31-37). Kindly note that Outputs 14-15, and 17 are still a work in progress and will be flagged for review at a later date. Also, the Leadership will be reviewing the updated language in parallel with the Team: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> As a reminder, kindly also review and provide feedback to the other requests below, including “grandfathered” suggestions, Section 3 (Glossary), and Section 4 (Outputs 1-9), for a fruitful meeting when we resume. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Wednesday, August 14, 2024 at 7:48 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] Meeting to Resume End of August (Week of 26 August) Dear EPDP-IDNs Team, Sincere apologies for the abrupt announcement, but due to unforeseen circumstances which involve the absence of Leadership/several Team members, the EPDP-IDNs Team Meeting for this week and next (15 and 22 August) will be canceled, only to resume during the last week of August (Week of 26 August). The Leadership suggests that, if possible, the Team holds 2 meetings during the last week of August (possibly Tuesday, 27 August and the usual Thursday, 29 August), to not only pick up where we left off but to hopefully conclude the review of comments within the working document for all outputs and other public comment inputs. A doodle poll will be sent out for another meeting during the last week, and if not possible to find the extra time, our meeting will still proceed on Thursday, 29 August. Further scheduling for September (if any more to be scheduled beyond 5 September, other than the Final Consensus Call) will be discussed on 29 August. As another reminder, the updates for Recs.10-20 will be shared soon. In the meantime, please review and provide feedback to the requests below (as none have been provided yet), including “grandfathered” suggestions, Section 3 (Glossary), and Section 4 (Outputs 1-9), for a fruitful meeting when we resume. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Tuesday, August 13, 2024 at 10:44 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] "Grandfathering" for Review Dear EPDP-IDNs Team, As briefly mentioned via our last Team Meeting on 8 August, kindly find in the link ICANN org’s suggested updates to the term, “grandfathered” for your review: https://docs.google.com/spreadsheets/d/1EJdmbLg-mAst_ajV-P3DFRhzyE8O4vDKWdZ… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1EJdmbLg-…> The columns are arranged as follows: * Column A: Relevant Output/Rationale (name/number) where the term is included * Column B: Particular sentence/paragraph including the term(s) * Column C: Replaced term(s) * Column D: Revised sentence/paragraph * Column E: Full text of the Output/Rationale to understand the context * Column F: Notes Upon Leadership/Staff’s revision of ICANN org’s suggested text(s), the Leadership has drawn the conclusion that ICANN org’s approach is the simplest and least disruptive in addressing org’s concerns about using the term, “grandfathered,” in our report. As you can see within the spreadsheet, the general term that was used to replace “grandfathered” was “exempted” (or in some cases, “excluded,” if duplicated within one sentence), which does seem to adequately convey the meaning or intent of the recommendations as drafted. As a reminder, the terms instead of “grandfathered,” that were suggested from ICANN org and the Team via discussions were: * Pre-existing domains * Exempted domains * Domains created before a certain date * Right of Continuance * Transitional exceptions Also as a reminder, please review Section 3 and Section 4 (Outputs 1-9) within the working docs as requested in the emails below. The links are shared with you again for your convenience: * Section 3 (Glossary) pp.8, 11-15: https://docs.google.com/document/d/1DPjKUkbD6OUJ3iHkh3UZyEKFhVi-oGFdcG-7dfg… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DPjKUkbD6OUJ…> * Section 4 (Outputs 1-9) pp.3-20: https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> The updates for 10-20 and other general comments will be notified soon. We look forward to your kind review and further discussions related to the terms and Outputs during our next Team meeting. Kind regards, Saewon. From: Saewon Lee via Gnso-epdp-idn-team <gnso-epdp-idn-team(a)icann.org> Reply-To: Saewon Lee <saewon.lee(a)icann.org> Date: Tuesday, August 6, 2024 at 3:31 PM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [Gnso-epdp-idn-team] Working Doc (Section 3) for Review Dear EPDP-IDNs Team, Following Section 4, please find the updated language for Section 3 (Glossary) based on the public comments received; https://docs.google.com/document/d/1DPjKUkbD6OUJ3iHkh3UZyEKFhVi-oGFdcG-7dfg… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1DPjKUkbD6OUJ…> The pages to focus on are pp.8, 11-15; Once again, please provide your feedback (sidebar comments only) mainly on the aforementioned parts to review together on Thursday, 15 August, during our Team Meeting. Updates for other parts of the section (or overall) will occur at a later date. Much appreciated, Steve, Dan, and Saewon. From: Saewon Lee <saewon.lee(a)icann.org> Date: Monday, August 5, 2024 at 6:32 PM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: Working Doc (Section 4) for Review Dear EPDP-IDNs Team, We hope this email finds you well. Please find the updated language for Outputs 1-9 so far in the working doc., based on the discussions from the Public Comment Review; https://docs.google.com/document/d/1vVbsKNfzHoqmuBH6VF1jF73Xr4A_UK7ZXiGmRJj… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1vVbsKNfzHoqm…> The pages to focus on are pp.3-19; please provide your feedback (sidebar comments only) to the aforementioned parts only to review together on Thursday, 15 August, during our Team Meeting. Please also note that more updates will occur post Rys’ feedback (post Tuesday, 6 August) and Section 3 updates will also be shared soon. Updates for other parts of the section will occur at a later date. Much appreciated, Steve, Dan, and Saewon.

1 0