October 2021 - Gnso-epdp-idn-team

ICANN72 GNSO Policy Briefing Available for Download
by Terri Agnew Oct. 6, 2021

Oct. 6, 2021

Dear All, On behalf of the GNSO Team, please find the GNSO Policy Briefing for ICANN72 is now available for download at https://go.icann.org/outlook72 Thank you. With kind regards, Terri --- Terri Agnew Policy Operations Specialist (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: terri.agnew.icann 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…>

1 0

RZ-LGR and DNS stability review
by Tan Tanaka, Dennis Oct. 6, 2021

Oct. 6, 2021

Hello —during today’s meeting some of you referred to the DNS stability review process as the function to determine whether an applied-for string if deemed fit for the root zone. I also observed that we might want to focus on the very limited function of the RZ-LGR, and to deal with contention sets and other evaluation procedures later on. To that end, I looked at the old applicant guide book and searched for the DNS stability: string requirements (2.2.1.3.2). Basically, string requirements is broken down into three parts: Part I (technical requirements for all labels, Part II (requirements for IDNs), and Part III (policy requirements for gTLDs). The RZ-LGR, I believe, is meant to “replace” or “automate” Parts I and II of the string requirements review process (a copy of the text is down below for your reference). In addition to those functions, also helps with the calculation of variant labels, so that the applicants don’t have to come up with IDN variant rules of their own. The difference between the prior AGB and the RZ-LGR (if adopted), are 1. that the latter starts with a smaller universe of “valid” letters. Before RZ-LGR, virtually all protocol valid code points were available to be used in a TLD string (with exception of course of hyphen and digits). The RZ-LGR starts with a smaller repertoire than IDNA2008 (i.e. Maximal Starting Repertoire) which is further limited by each script generation panel. The result of each generation panel’s work is merged into the RZ-LGR. So, one applicant might challenge the RZ-LGR’s results because it did not accept one letter, or a combination or some script rule. This should be okay to challenge, but the process by which the applicant finds resolution would be through the established LGR procedure (i.e. make the case for inclusion of a new letter or rule) to maintain the stability of the RZ-LGR. 2. the RZ-LGR is designed to calculate the variant labels. The prior DNS stability review process did not do that; applicants were asked to provide these self-identified variant labels. I hope this helps the discussion. Best, Dennis Part I -- Technical Requirements for all Labels (Strings) – The technical requirements for top-level domain labels follow. 1. 1.1 The ASCII label (i.e., the label as transmitted on the wire) must be valid as specified in technical standards Domain Names: Implementation and Specification (RFC 1035), and Clarifications to the DNS Specification (RFC 2181) and any updates thereto. This includes the following: 1.1.1 The label must have no more than 63 characters. 1.1.2 Upper and lower case characters are treated as identical. 1. 1.2 The ASCII label must be a valid host name, as specified in the technical standards DOD Internet Host Table Specification (RFC 952), Requirements for Internet Hosts — Application and Support (RFC 1123), and Application Techniques for Checking and Transformation of Names (RFC 3696), Internationalized Domain Names in Applications (IDNA)(RFCs 5890-5894), and any updates thereto. This includes the following: 1.2.1 The ASCII label must consist entirely of letters (alphabetic characters a-z), or 1.2.2 The label must be a valid IDNA A-label (further restricted as described in Part II below). Part II -- Requirements for Internationalized Domain Names – These requirements apply only to prospective top-level domains that contain non-ASCII characters. Applicants for these internationalized top-level domain labels are expected to be familiar with the Internet Engineering Task Force (IETF) IDNA standards, Unicode standards, and the terminology associated with Internationalized Domain Names. 1. 2.1 The label must be an A-label as defined in IDNA, converted from (and convertible to) a U-label that is consistent with the definition in IDNA, and further restricted by the following, non-exhaustive, list of limitations: 2.1.1 Must be a valid A-label according to IDNA. 2.1.2 The derived property value of all codepoints used in the U-label, as defined by IDNA, must be PVALID or CONTEXT (accompanied 2.1.3 The general category of all codepoints, as defined by IDNA, must be one of (Ll, Lo, Lm, Mn, Mc). 2.1.4 The U-label must be fully compliant with Normalization Form C, as described in Unicode Standard Annex #15: Unicode Normalization Forms. See also examples in http://unicode.org/faq/normalization.html. 2.1.5 The U-label must consist entirely of characters with the same directional property, or fulfill the requirements of the Bidi rule per RFC 5893. 1. 2.2 The label must meet the relevant criteria of the ICANN Guidelines for the Implementation of Internationalised Domain Names. See http://www.icann.org/en/topics/idn/implementation-guidelines.htm. This includes the following, non- exhaustive, list of limitations: 2.2.1 All code points in a single label must be taken from the same script as determined by the Unicode Standard Annex #24: Unicode Script Property (See http://www.unicode.org/reports/tr24/) 2.2.2 Exceptions to 2.2.1 are permissible for languages with established orthographies and conventions that require the commingled use of multiple scripts. However, even with this exception, visually confusable characters from different scripts will not be allowed to co-exist in a single set of permissible code points unless a corresponding policy and character table are clearly defined.

4 5

Reminder & Duration Change: Meeting Invitation | IDNs EPDP Team | Thursday, 07 October 2021 at 13:00 UTC
by Nathalie Peregrine Oct. 6, 2021

Oct. 6, 2021

Dear all, The IDNs EPDP Team meeting is scheduled on Thursday, 07 October 2021 at 13:00 UTC for 90 minutes. Please click the link below to join the webinar: https://icann.zoom.us/j/94276275950?pwd=dG5hanFzMlpsYmh0NnFjTEQwOUV1dz09 [icann.zoom.us]<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 [icann.zoom.us]<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 [gnso.icann.org]<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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the Wiki agenda page: https://community.icann.org/x/rABmCg * Check your time zone: https://tinyurl.com/tsne6sb7 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/tsne6sb7__;!!PtGJab4!v9hDwP8…> 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

1 0

IDNs EPDP Team meeting
by ICANN Policy Calendar Oct. 6, 2021

Oct. 6, 2021

Meeting: IDNs EPDP Team meeting Date/time: Every Thursday at 13:00 UTC for 1 hour, beginning Thursday, 02 September 2021 through 21 October 2021 (exception 7th Oct: 90 mins) 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 [gnso.icann.org]<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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Visit the 02 Sept) Wiki agenda page (see left side for future dates): https://community.icann.org/x/lwBmCg * Check your time zone: https://tinyurl.com/4ex5bsh5 ONLY for Members and Participants * Please join via the above Main Zoom Webinar link and staff will promote you to panelist. * Please select Panelists and Attendees, or 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

Proposed Agenda - IDN EPDP Meeting #9 - 7 October 2021 for 90 minutes
by Emily Barabas Oct. 6, 2021

Oct. 6, 2021

Dear all, Please find below the proposed agenda for our meeting on 7 October 2021 at 13:00 UTC. As there have been no objections raised on list, this call will be extended to 90 minutes to make time for Sarmad to deliver his full presentation. Kind regards, Steve, Marika, and Emily IDN EPDP Meeting #9 Proposed Agenda 1. Roll Call & SOI Updates 2. Welcome & Chair Updates 3. ICANN org presentation on RZ-LGR 4. AOB * Next call: 14 October at 13:00 UTC

1 0

Extending the 7 October 2021 Meeting to 90 Minutes
by Steve Chan Oct. 4, 2021

Oct. 4, 2021

Dear EPDP Team, EPDP Team leadership has coordinated with ICANN org’s IDN Program team to help plan an informational session on the RZ-LGR. After some discussion, we have come to the conclusion that the typical 60 minutes is inadequate to get through all of the presentation materials. As leadership believes it is preferable to hold the informational session during a single meeting, they are proposing that the upcoming meeting on 7 October be extended to 90 minutes to better accommodate the agenda. Noting that all EPDP Team meeting are of course recorded, in the event you are not able to join for the full 90 minutes, please respond to this email if you object to this one-time meeting time extension. Best, Steve Steven Chan  Senior Director, GNSO Support 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