March 2022 - Gnso-epdp-idn-team

Meeting Invitation | IDNs EPDP Team | Thursday, 17 March 2022 at 13:30 UTC
by Devan Reed 14 Mar '22

14 Mar '22

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 17 March 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/YwB1Cw * Check your time zone: https://tinyurl.com/ut5dt3wd 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

IDNs EPDP Team meeting
by ICANN Policy Calendar 14 Mar '22

14 Mar '22

Meeting: IDNs EPDP Team meeting Date/time: Every Thursday at 13:30 UTC for 90 minutes, beginning 17 March 2021 through 09 June 2021 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/YwB1Cw (17 March, see future dates on the left side) * For other places see: https://tinyurl.com/ut5dt3wd 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

Notes and action items - IDNs EPDP ICANN 73, Meeting #26 - 9 March 2022
by Steve Chan 14 Mar '22

14 Mar '22

Dear all, Please find below the notes from today’s meeting at ICANN73 on Wednesday, 9 March 2022 at 18:30 UTC. Best, Ariel, Emily, Steve Action Items: Action Item: Develop questionnaire to survey existing IDN gTLD registry operators (Chinese and Arabic only) for EPDP Team review. Propose timing for responses from ROs. Notes – IDNs EPDP Call ICANN73 – 9 March 2022 Welcome & Chair Updates * Reminder to review draft language for A5 and A6 * A7 – input received from the NCSG that there should be consultation with the CJK GPs. Staff is tasked with developing a streamlined request * Daylight savings impact. Likely to suggest maintaining the same UTC time of 13:30 * During CPH/Board discussion, the need to ensure implementable recommendations was raised. It’s a good reminder for this group as it develops its recommendations. * Discussion on the Board liaison role as well – they should have their Board hats on to consider best interests concerns and that recommendations are implementable, so such things can potentially be identified earlier in the process. * Input may not be in real time as Board discussion may be warranted. Continue discussion on Charter Questions D1b and B4 & begin discussion on Charter Questions B4a and B5 D1b * Question is about existing and new ROs applying for variant labels, as well as associated fees. * Part 1 (new applicant and allocatable variants) – desire to have a single application process for the set * Part 2 (for existing ROs) – simplified, standalone process. However, unclear how much of the 2012 structure would be needed. Outstanding action item to develop a strawman for the simplified process. * New discussion item – determining if there is demand for variant labels from existing ROs, before embarking on developing a standalone process. * Delegated IDN gTLDs – 92; Chinese and Arabic gTLDs – 61; 47 unique ROs for the 61 applicable IDN gTLDs * Proposal is to survey applicable ROs to determine interest/need, how many, timing, additional considerations. * Cyrillic is included twice, likely a typo. There are two colors without a label as well. * Existing ROs may have price sensitivity, so it might be worth asking about that (e.g., $185k, free, somewhere in between). And also could consider asking which specific variants the RO is interested in. * $185k was based on a more robust process than would likely be needed for a dedicated IDNs round. Action Item: Develop questionnaire to survey existing IDN gTLD registry operators (Chinese and Arabic only) for EPDP Team review. Propose timing for responses from ROs. * Part 3 (associated fee for applying/activating a variant label for an existing gTLD). Some have noted the revenue neutral approach, others have noted that the $185k from 2012 could possibly cover the costs. * Maybe helpful to look at the question in three pieces: For future applicants, for existing ROs, and for both future applicants and existing ROs. * For future applicants: should there be a single cost for the primary gTLD and variants? * For existing ROs – should there be a charge to activate variants? * For future and existing – what should the annual registration fee be for variants? * The goal is not to determine a precise fee, but rather talk about the principles the EPDP Team is interested in. * The standard application fee will be established by the SubPro IRT, so we do not know the specific amount, but we know what is included. * The fee should not be free, but also not as high as the full amount. For annual fees, no annual fee, but it could be aggregated for domains under management. Some support from others for this approach. * There was some SubPro discussion about fairness of an IDN gTLD and its variants paying only a single amount. * Support for additional fee being applicable for variants, stressing that it should not be the full amount. * The IDN variant is not necessarily a commercial opportunity or exploring a new market, it’s intended for end users and registrants. From a market perspective, it’s like operating a single gTLD. * If the approach is revenue neutral, this would imply a cost for variants. * Summary - For future applicants, it would be the main application fee plus some additional fee for the variants. It could be handled similarly to the 2012 processes that required extra fees in some instances (e.g., CPE, registry services eval, etc.) * From a technical perspective, variant TLDs are like any other gTLD. However, the policy assessment is that variants are special. * A next step may require that the evaluation process be analyzed to determine which steps would not apply. * In considering the ongoing fees, the concept of the primary gTLD and its variants being a single gTLD should be considered. * Suggestion again that the transactions be aggregated for principle and variants to determine number of transactions. * End users consider the domain and its variants as the same. * Noted that any agreements during this discussion is preliminary and dependent upon consultation with SO/AC/SG/Cs. B4 * This question is limited to the timing and sequence for applying for allocatable variant TLD labels, not examining the evaluation process itself. * Timing – within a gTLD application round OR on a rolling basis * Sequence – in a single package or separately, when needed * Questions to consider: * Can allocatable variants be applied for outside of the application round? * Can an applicant apply for variant labels on a rolling basis or must they all be applied for at once. * There are implications if variants are applied for versus simply being allocated. * The timing may be impacted by what level of effort is needed to allow for the activation of an IDN variant. This question may be difficult to answer without understanding the relevant processes. * Preference from some is to allow variant activation outside of an application round. * One way to allow for simplified activation of variants is to evaluate the entire allocatable set up front. * Different competing needs: market needs, promoting IDNs, preserving security and stability. These competing interests need to be taken into consideration. * Important to keep in mind that the number of allocatable variants is constrained by the RZ-LGR itself. * There are still questions to consider, like how variants are considered in string sim, objections. Reiterated that a rolling basis could be supported by pre-evaluating the entire set. B4a * N/A B5 * N/A AOB * None Steven Chan  Senior Director, Policy Development Support & GNSO Relations Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536  Email: steve.chan(a)icann.org<mailto:steve.chan@icann.org> Skype: steve.chan55 Mobile: +1.310.339.4410 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

2 1

ICANN73 Meeting Invitation | IDNs EPDP Team | Wednesday, 09 March 2022 at 14:30 AST | 18:30 UTC
by Devan Reed 09 Mar '22

09 Mar '22

Dear all, As a reminder the meeting being held during ICANN73 will take place on Wednesday, March 09 2022 at 14:30 local time (18:30 UTC). * ICANN73 wiki agenda page: https://community.icann.org/x/OQIiCw * Please be sure you are registered for ICANN73! * Zoom participation links will be published 24 hours before the ICANN73 sessions start. For more information on how to participate, visit: https://73.schedule.icann.org/attend<https://urldefense.com/v3/__https:/73.schedule.icann.org/attend__;!!PtGJab4…> Thank you! Kind regards, Devan

6 6

Daylight Saving - Keep 13:30-15:00 UTC Slot on Thursday
by Ariel Liang 09 Mar '22

09 Mar '22

Dear All, As mentioned during today’s session, Daylight Saving (DST) will start shortly after ICANN73, which may affect some members in the team. Staff suggest to keep the same UTC time (13:30-15:00 UTC) on Thursdays, as it is still the best time to accommodate EPDP Team members across different time zones. It may work a bit better for some folks (e.g., US West Coast). In absent of objection by EOB Friday 11 March, staff will schedule meetings starting from next week by keeping the same 13:30-15:00 UTC timeslot on Thursday. Best Regards, Ariel Ariel Xinyue Liang Policy Sr. Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Reminder: ICANN Zoom room requirements: Zoom Logins: First & Last Name/ Surname Only
by Nathalie Peregrine 09 Mar '22

09 Mar '22

Dear all, To ensure transparency of participation in ICANN’s multistakeholder model, please remember to sign in to Zoom sessions using your full name (e.g. First Name + Last Name/Surname). If you are in a session using the webinar format, you will need to first exit the Zoom room prior to rejoining. Please reach out to your support staff if you have any difficulties joining a Zoom session. To rename in a regular Zoom room: 1. Join the meeting. 2. Tap Participants. 3. Hover over your name on the participants list. 4. Click More. 5. Click Rename. 6. Enter the name you desire then click Rename. 7. Your name has now been changed within the meeting. To rename in a webinar Zoom room: 1. BEFORE entering the meeting, and during the login phase, update your Zoom name here: [cid:image001.png@01D83300.B8213430] 1. If you forget to do so, you can always log out of the webinar Zoom room and edit your name upon re-entering. Please contact your support staff if you run into any issues. Thank you! Kind regards, Nathalie

1 0

ICANN Zoom room requirements: Zoom Logins: First & Last Name/ Surname Only
by Nathalie Peregrine 08 Mar '22

08 Mar '22

Dear all, To ensure transparency of participation in ICANN’s multistakeholder model, please remember to sign in to Zoom sessions using your full name (e.g. First Name + Last Name/Surname). If you are in a session using the webinar format, you will need to first exit the Zoom room prior to rejoining. Please reach out to your support staff if you have any difficulties joining a Zoom session. To rename in a regular Zoom room: 1. Join the meeting. 2. Tap Participants. 3. Hover over your name on the participants list. 4. Click More. 5. Click Rename. 6. Enter the name you desire then click Rename. 7. Your name has now been changed within the meeting. To rename in a webinar Zoom room: 1. BEFORE entering the meeting, and during the login phase, update your Zoom name here: [cid:image001.png@01D83300.B8213430] 1. If you forget to do so, you can always log out of the webinar Zoom room and edit your name upon re-entering. Please contact your support staff if you run into any issues. Thank you! Kind regards, Nathalie

1 0

Proposed Agenda - IDN EPDP ICANN73 session - Wednesday 9 March 2022 at 18:30 UTC for 90 minutes
by Emily Barabas 04 Mar '22

04 Mar '22

Dear all, Please find below the preliminary proposed agenda for our ICANN73 session scheduled to take place on Wednesday 9 March 2022 at 18:30 UTC for 90 minutes. Please note that the leadership team will be meeting on Monday and the agenda may be subject to adjustment following that meeting. Kind regards, Ariel, Steve, and Emily IDN EPDP Meeting #25 Proposed Agenda 1. Welcome & Chair Updates (10 minutes) 2. Continue discussion on Charter Questions D1b and B4 & begin discussion on Charter Questions B4a and B5 (75 minutes) · Working documents<https://community.icann.org/pages/viewpage.action?pageId=176622687> 1. AOB (5 minutes)

1 0

Charter Question A7
by Tomslin Samme-Nlar 03 Mar '22

03 Mar '22

Dear everyone, I would like to make two comments on the Q.A7 discussion the team has had so far. First, I think there is value in consulting with the GP to gather more information to help us develop a better and inform viewpoint on this issue of single character TLDs. This is something NCSG will strongly encourage. Secondly, we shouldn't be too prescriptive as per the original request to the GPs, that is to have an exclusive hard list of not acceptable characters. I however, think if there are characters which are very obvious to the script experts and that might cause confusion, we could take those and use them to develop an automated tool for use by applicants before making an application for a single character TLD. This should help with predictability and also resolve some of the issues the previous tool (SWORD) had. Regards, Tomslin

1 0

IMPORTANT - Session change ICANN73: New gTLD Subsequent Procedures: Operational Design Phase
by Julie Bisland 03 Mar '22

03 Mar '22

Dear all, ⚠️ Due to scheduling conflicts the ICANN73 session New gTLD Subsequent Procedures: Operational Design Phase will take place at a different time and date. ⚠️ Previously scheduled for Wednesday 9 March 2022 at 09:00 am local time (13:00 UTC), it will now take place on Monday 7 March 2022 at 12:30 local time (16:30 UTC). To update your calendars please follow the below steps: 1. Remove the entry for New gTLD Subsequent Procedures: Operational Design Phase on Wednesday 9 March 2022 09:00 am local time. 2. If you had already selected the new gTLD Subsequent Procedures: Operational Design Phase entry in your “My Agenda” on the ICANN73 website, you will not need to re-select it. You will however need to export that session once again to your own calendar. 3. Please refer to the attached “How to Get Organised” email to refresh your memories on how to download sessions! Please reach out to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> if you have any questions. Kind regards, Nathalie

1 0