June 2022 - Gnso-epdp-idn-team

Draft Outcome: Group 2 Charter Questions Related to "Same Entity" Principle at Top-Level
by Ariel Liang July 7, 2022

July 7, 2022

Dear All Please find the draft outcome language for Group 2 charter questions related to “same entity” principle at the top-level, which are: * B1, B2, B3, B5: https://docs.google.com/document/d/15YGISgNQYL_VfcVVZ6E97qbo42GPziP6x089bR3… * D1a, D1b (Part 2): https://docs.google.com/document/d/1C6xKX87w2LtN4Is0mehuRgc1GqjKmbbhT14KbvU… Both documents are also posted on the wiki page here: https://community.icann.org/x/XwyHCg. Following the agreed format, the draft outcome language includes the following components: * Brief answer to the charter question * Recommendations and implementation guidance * Rationale for recommendations and implementation guidance Please note that for charter question D1b Part 1 (related to the process by which an existing TLD registry operator seeks to activate variants) has not be addressed; it depends on the survey responses from the Arabic/Chinese TLD ROs. Please provide any input/suggestion for the draft outcome language on the mailing list by Friday, 8 July. Best Regards, Steve, Emily, Ariel

2 4

Notes and action items - IDNs EPDP Meeting #40 - 30 June 2022
by Emily Barabas June 30, 2022

June 30, 2022

Dear all, Please find below the notes and action items from today’s meeting on Thursday, 30 June 2022 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily Action Items: Action Item 1: Staff to develop graphics to demonstrate scenarios for C1. Notes – IDNs EPDP Call – 30 June 2022 Welcome & Chair Updates * Survey was sent out to Chinese and Arabic TLD ROs to get a sense of their interest in activating variants. For Chinese TLDs, 23 responses were received. For Arabic TLDs, 2 responses were received. * It was noted that there might have been some confusion among ROs about the purpose of the survey because it was sent by GDS. * Leadership team will process survey results and bring back to the group for consideration. * Reminder to read draft responses to charter questions and recommendations out for review: Deadline 8 July. Review Charter Questions a7 and a10 * The Team will do a second reading of revised language for a7 and a10 and tidy up the language where needed: https://docs.google.com/document/d/1Bt0LT45UaLynFNverh1nJhyvq6q6NxgSFAOnOp2…<Welcome%20&%20Chair%20Updates%20%20%20•Communication%20was%20sent%20out%20t…> * Agreement that the first sentence of Recommendation 1.11 should read: “Single character gTLDs may only be allowed for limited scripts and languages where a character is an ideograph.” (“script” and “language” are to be pluralized) * Additional transitions added to 1.13 that were missing in the original text to improve accuracy of the language – transition #2 from “withheld-same-entity” to “blocked” covers cases where the RZ-LGR is not fully backwards compatible; transition #5 from “allocated” to “withheld-same-entity”covers intentional retirement or removal of TLD from the root zone. If a gTLD is terminated the same RO can re-apply. If it’s a brand, the RO has to wait two years to re-apply. * Text from the graphic originating in the staff paper has been moved to rationale. Rationale also now includes description of the two newly added transitions. * Text added to the rationale explaining why the EPDP Team disagrees with the explanatory remarks in the Staff Paper that the transition from “rejected” to “withheld-same-entity” is automatic. * Support expressed for the revised language. Charter Question C1 * Dennis Tan has suggested that questions C1 and C2 are considered in tandem. Explanation: The charter drafting team wanted to acknowledge the structure of the Staff Paper. The intention was to look at this in a vacuum and break the conversation down piecemeal – first, look at what the same entity principle means, then define what the same entity is. Second level variants exist today and the same entity principle is applied to those as a concept. C1 speaks to just the definition of the concept, C2 goes into what that means in practice, including for existing gTLD operators. It would be beneficial to look at the same entity principle means as a registrant (C2), holistically with C1, because there are real-world implications. In the existing Registry Agreement the same entity is the sponsoring registrar as opposed to the registrant. * Summary: C2 assumes that the registrant is the “same entity”, but in C1, there is no definition of same entity. The current situation at the second level is that the same entity is not the registrant. * Review of charter question C2 – Slide 10 * Context: Definition of “Same Entity” at Second-Level – Slide 11 * Clarification of staff paper recommendation 3: “. . . or else withheld for possible allocation only to that entity.” The concept in the staff paper was that the registrant is the same entity. * Charter question C1 – Slide 4 * Comment: definition of “same entity” should be defined further. * Context for Scenario 1 & Discussion – Slide 5 * Discussion question: should a future second-level label under any allocatable variant label of an existing TLD (i.e., Chinese or Arabic gTLD) be only allocated to the same entity, or else withheld for possible allocation only to that same entity? * Example: sld.variantTLD1 and sld.variantTLD2 are two distinct DNS records, each one in its respective zones. Should they have the same registrant? * Question: What is the downside of it not being the same entity? * Response: Variant labels are by definition considered the same by the users from various points of view, for example they may be visually identical (but different code points). If they are registered to different registrants, a user may think they are going to one website but they are going to a different website (misconnection). If the same entity principle is followed, you don’t have the risk of misconnection, so the security concern is addressed. * Question: Can we define same entity as the same registrant and same registry, but the registrar can be different? * Response: This becomes tricky in the implementation if there is not a connection that requires the same registrar. * Comment: We need to be mindful of relationships. The registry has a relationship with the registrar. The registrar has a relationship with the registrant or the registrar may have a relationship with the reseller who has a relationship with the registrant. The way the data flows upstream currently needs to be taken into account. If/when information flows from the registrant to the registry, this is limited. It is difficult to picture how a registry would manage this situation without having the registrar in the middle. * Additional comment: During the course of a domain registration, the registrant can change its registrar. The registrar is changeable. The registry and the registrant are the key players. * Comment: In response to question about whether a registry could check that it is same registrant. Technically this is possible because it is possible to have shared contact/registrant handle between registrars. But allowing different registrars would likely be complex to manage. * Comment: While technically feasible, it is very impractical to operate and scale. * Comment: If the registrant changes the registrar, it can do so for the variant labels, as well. * Comment: Once you have a variant set “package”, the set must move together. If this principle is followed, there is not a way to separate into different registrars. * Comment: When the variant TLD is activated, the registrant should activate the variant at the same registrar as the primary. * Summary: Support for the same entity being the registrant. Question: How do we put this into policy? Can we put a requirement on the registrant that if they register a name at the second level that they use the same registrar when they want more than one label in a “package”? * Comment: We need to keep in mind why we are doing this PDP. We want more IDNs. As we issue recommendations about how the relationships need to be implemented, what will be required of registries and registrars, and how it will be enforced, we need to think about the technical complexity and make it implementable for the contracted parties. * Comment: Currently there is no technical standard solutions for making two TLDs operate in the same way. At the end of the day, if no contracted parties are willing to do the work, there will be no supply. If there is no supply, there will be no demand. Action Item 1: Staff to develop graphics to demonstrate scenarios for C1.

1 0

Post Call | IDNs EPDP Team call | Thursday, 30 June 2022
by Julie Bisland June 30, 2022

June 30, 2022

Dear all, All recordings for the IDNs EPDP Team call held on Thursday, 30 June 2022 can be found on the agenda wiki page <https://community.icann.org/x/tQD5Cw> (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 chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-epdp-idn-team/> and the main wiki page<https://community.icann.org/x/uAPpCQ>. Thank you! Kind Regards, Julie

1 0

July-August-September 2022 | IDNs EPDP Team
by Julie Bisland June 30, 2022

June 30, 2022

Dear all, Please find the .ics attachment for the series of IDNs EPDP Team calls taking place in July, August, and September 2022. The .ics file is a recurring order to take place every Thursday at 13:30 UTC. Please be sure to download it as “recurring” vs. a one-time event to ensure all the dates show up on your calendar. * 07 July 2022 (invite has already been sent) * 14 July 2022 * 21 July 2022 * 28 July 2022 * 04 August 2022 * 11 August 2022 * 18 August 2022 * 25 August 2022 (conflicts with GNSO Council Meeting, may be rescheduled) * 01 September 2022 * 08 September 2022 * 15 September 2022 The next call takes place on 07 July 2022 and the invitation has been sent out. Thank you. Kind regards, Julie

1 0

Meeting Invitation | IDNs EPDP Team | Thursday, 07 July 2022 at 13:30 UTC
by Julie Bisland June 30, 2022

June 30, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 07 July 2022 at 13:30 UTC for 90 minutes. 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 Wiki agenda page: https://community.icann.org/x/IAYVD * Check your time zone: https://tinyurl.com/2p8erc7a 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, Julie

1 0

**ON NOW** Meeting Invitation | IDNs EPDP Team | Thursday, 30 June 2022 at 13:30 UTC
by Julie Bisland June 30, 2022

June 30, 2022

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 30 June 2022 at 13:30 UTC for 90 minutes. 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 Wiki agenda page: https://community.icann.org/x/tQD5Cw * Check your time zone: https://tinyurl.com/5n7d3vxh [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5n7d3vxh__;!!PtGJab4!-XAqAiq…> 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

1 0

**STARTS IN 20 MINUTES** Meeting Invitation | IDNs EPDP Team | Thursday, 30 June 2022 at 13:30 UTC
by Julie Bisland June 30, 2022

June 30, 2022

**STARTS IN 20 MINUTES** Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 30 June 2022 at 13:30 UTC for 90 minutes. 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 Wiki agenda page: https://community.icann.org/x/tQD5Cw * Check your time zone: https://tinyurl.com/5n7d3vxh [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/5n7d3vxh__;!!PtGJab4!-XAqAiq…> 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

1 0

Re: [Gnso-epdp-idn-team] Proposed Agenda - IDN EPDP Meeting #40 - Thursday 30 June 2022 at 13:30 UTC
by Tan Tanaka, Dennis June 30, 2022

June 30, 2022

Hello — C1 and C2 are very closely related. In my opinion they should be discussed in tandem since C2 defines what the same entity is for C1. Given that we are allocating 50 mins to the topic, would you consider expanding the scope of the discussion? Thanks, Dennis From: Gnso-epdp-idn-team <gnso-epdp-idn-team-bounces(a)icann.org> on behalf of Emily Barabas <emily.barabas(a)icann.org> Date: Tuesday, June 28, 2022 at 3:16 AM To: "gnso-epdp-idn-team(a)icann.org" <gnso-epdp-idn-team(a)icann.org> Subject: [EXTERNAL] [Gnso-epdp-idn-team] Proposed Agenda - IDN EPDP Meeting #40 - Thursday 30 June 2022 at 13:30 UTC 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 all, Please find below the proposed agenda for our meeting on Thursday 30 June 2022 at 13:30 UTC. Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #40 Proposed Agenda 1. Roll Call & SOI (2 minutes) 2. Welcome & Chair Updates (5 mins) · Update on Chinese and Arabic TLD RO survey 3. Review Charter Questions a7 and a10 (30 mins) 4. Charter Question C1 (50 mins) 5. AOB (3 mins)

3 3

IDNs EPDP Team meeting
by ICANN Policy Calendar June 29, 2022

June 29, 2022

Meeting: IDNs EPDP Team meeting Pattern: Weekly on Thursdays, 07 July – 15 September 2022 at 13:30 UTC for 90 minutes Please click the link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 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 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 (07 July): https://community.icann.org/x/IAYVD * For other places see: https://tinyurl.com/39m2e7cs 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

IDNs EPDP Team meeting
by ICANN Policy Calendar June 29, 2022

June 29, 2022

Meeting: IDNs EPDP Team meeting Pattern: Weekly on Thursday’s 30 June – 15 September 2022 at 13:30 UTC for 90 minutes Please click the link to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 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 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/tQD5Cw * For other places see: https://tinyurl.com/5n7d3vxh 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