- gnso-council-IDN-scoping - lists.icann.org

Actions & Notes: GNSO IDN Scoping Team Meeting 12 September 3:00 UTC
by Ariel Liang Sept. 23, 2019

Sept. 23, 2019

Dear All, Please find below the action items and notes captured during the IDN Scoping Team call on Thursday, 12 September at 3:00-4:00 UTC. Staff has posted to the wiki space the action items and notes. Please note that these are high-level notes and are not meant as a substitute for the recording and chat room records, which are posted on the wiki at: https://community.icann.org/x/VY7kBg Best Regards, Ariel == Action Item None Notes 1. Welcome, roll call & staff - Katrina sent a letter to the ICANN Board, requesting the Board to officially end ccNSO PDP2, so that ccNSO can launch PDP4 which focuses on outlining the difference between string similarity and IDN variant, as well as selection of IDN ccTLD strings, etc. https://ccnso.icann.org/sites/default/files/field-attached/sataki-to-chalab… - Will better understand the timeline of ccNSO PDP4 following the ccNSO Council meeting next Thursday. GNSO staff will keep coordinating with the ccNSO staff and keep the scoping team informed about the timeline. 2. Conclude identifying problems/issues related to the IDN guidelines/IDN tables (2nd level) - On sending liaison(s) to the ccPDP on IDN ccTLDs, the scoping team plans to ask the GNSO Council to call for volunteer(s) to serve as liaison(s) with the understanding that 1) the liaisons should have some expertise on the subject matter and, 2) not be limited Council members. - There may be some limitations on the number of people who will volunteer for the liaison position. - When the ccNSO PDP4 working group charter is being developed, the liaison aspect will be integrated. GNSO & ccNSO staff will also discuss the number of liaisons in the next coordination call. - For PDPs, the Council usually only assigns a single liaison. - Liaison represents one mechanism for coordination between the ccNSO and GNSO. The Scoping Team may consider holding off sending the Council the request to call for volunteer, and thinking about other mechanisms for coordination. GNSO Council does not need to rush to select liaison(s) yet. - Working conclusion of the IDN Tables/IDN Implementation Guidelines (2nd level): On the topic of ICANN IDN Implementation Guidelines the Scoping Team will propose for the GNSO to set up 2 working groups: 1) an expert group that should include policy/legal and technical/operations expertise to address outstanding issues of the implementation of the guidelines 4.0 and its implications on operations, change of backend registry and the Registry Agreement in particular as it relates to Exhibit A and Spec 6; 2) a policy working group that would look into the appropriate future processes and updates of the IDN Implementation Guidelines, including where it may be appropriate to distinguish/separate from the ccNSO, and how it fits into the broader policy context and technical/operational requirements of gTLDs. - Good to give the Council some indication on the progress and provide an update on the preliminary recommendations for the IDN Tables/IDN Implementation Guidelines. - Staff have been updating the option paper by adding the problem definition outline and will make it compatible with Edmon’s phrasing about the working conclusions. 3. Identifying problems/issues with IDN variant TLD recommendations - Presentation by Sarmad on IDN Variant TLD recommendations - Now is time to consider developing policy regarding the allocation and delegation of the variant TLD recommendations. It may be safe to say that a PDP is probably required. A PDP should probably start from the staff documents for the IDN Variant TLD recommendations. - The scope of work will help inform the selection of mechanism. Helpful questions to think of 1) is there disagreement with the conclusions? if so, which ones and why 2) is there additional research and analysis needed? 3) do you agree with the recommendations, but think there are details or precision missing? in other words, are there gaps in the recommendations? - For example, if additional research and analysis are not needed, then an Issue Report can be skipped and can request the Council to launch an EPDP, and the staff paper could serve as the Issue Report. - What would be the outcome of the GNSO PDP? Even if people agree with all the IDN variant TLD management recommendations, we will still need an official process to validate the recommendations. We could potentially rely on some inflight PDPs (RPM, SubPro) to validate those recommendations. - Maybe some part of the recommendations can be deliberated by SubPro, but some other parts cannot work, as it is forward looking. GNSO Council can also change the scope of SubPro PDP, if necessary.  - One of the problems with the recommendation is about the multiple applicant for variant TLDs. 4. AOB

2 1

Agenda: IDN Scoping Team Call on 29 August 8-9 UTC
by Ariel Liang Sept. 12, 2019

Sept. 12, 2019

Dear All, Please see below the proposed agenda for this week’s meeting: 1. Welcome, roll call, and staff note on meeting rotation 2. Update about ccNSO efforts 3. Identify problems/issues related to the IDN guidelines/IDN tables (2nd level) 4. Time permitting, start identifying problems/issues with IDN variant TLD recommendations 5. AOB Background document: IDN TLD Variants Implementation - GNSO Options Paper: https://docs.google.com/document/d/1o_9bfnkKufrSxiJGxpNcOcfTK2VLWp5XYQvwe5q… Thank you, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 804 2761 Skype: ariel.liang.icann www.icann.org

3 3

Post call | IDN Scoping Team call | Thursday, 12 September 2019 at 03:00 UTC
by Andrea Glandon Sept. 12, 2019

Sept. 12, 2019

Dear all, All recordings for the IDN Scoping Team call held on Thursday, 12 September 2019 at 03:00 UTC can be found on the agenda wiki page<https://community.icann.org/x/VY7kBg> (attendance included) and the GNSO Master calendar <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> . 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) For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-council-idn-scoping/> and the main wiki page<https://community.icann.org/x/b4HkBg>. Thank you. Kind regards, Andrea

1 0

Actions & Notes: GNSO IDN Scoping Team Meeting 29 August 8:00 UTC
by Ariel Liang Aug. 29, 2019

Aug. 29, 2019

Dear All, Please find below the action items and notes captured during the IDN Scoping Team call on Thursday, 29 August at 8:00-9:00 UTC. Staff has posted to the wiki space the action items and notes. Please note that these are high-level notes and are not meant as a substitute for the recording and chat room records, which are posted on the wiki at: https://community.icann.org/x/RY7kBg Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) == Action Items None Notes 1. Welcome, roll call, and staff note on meeting rotation - Remaining four meetings before ICANN66 will alternate between the 03:00-04:00 UTC and 08:00-09:00 UTC time slots 2. Update about ccNSO efforts - ccNSO Council Chair plans to send a letter to the ICANN Board next week, requesting to end the ccNSO PDP 2 on the selection of IDN ccTLD strings and inclusion of IDN ccTLDs in the ccNSO. After the Board approves this request and officially ends ccNSO PDP 2, the ccNSO is able to launch its PDP 4, which deals with issues including outlining the differences between the similarity review and IDN variant TLD recommendations. - The earliest time that the ccNSO is able to launch PDP 4 is during its next Council meeting in September (19 September), if the Board approves its request before that date. The ccNSO aims to launch PDP 4 no later than ICANN66. After the launch of the PDP 4, the ccNSO will form a drafting team to develop charter for its PDP 4 working group. - Staff are coordinating with ccNSO colleagues to monitor the ccNSO effort, and will advise the GNSO Council on the appropriate timing to send out the call for volunteer message, soliciting GNSO liaison to follow the ccNSO PDP 4. 3. Identify problems/issues related to the IDN guidelines/IDN tables (2nd level) - There are issues with how the Guidelines get updated, as well as operational and implementation issues with the Guidelines. - Regarding the “same entity” requirements in the IDN Guidelines, there is no prescription on how it can be achieved. The framework is to have the registry objective ID glued to IDN domain names, which is problematic. - There is inconsistency between the Registry Agreement and the IDN Guidelines. For example, the guidelines to activate variants in the second level according to the recommendation no.12 of the IDN Guidelines v4 are not consistent with the relevant provisions in Exhibit A of the Registry Agreement. There are provisions pertaining to variant in various parts of the Registry Agreement. How do we reconcile those languages between the two documents? - In summary, there are three issues related to the IDN Guidelines: 1) change process of the IDN Guidelines (consensus policy related), 2) technical requirements, 3) compliance/legal issues. - Issue no.3 has been discussed to death during the RA amendment process. ICANN did not change Exhibit A of RA but added Specs 6. The intent is to have the IDN Guidelines rule items that are IDN based. The specific issues were brought by the Chinese community. The main question is whether the CDNC policy can be implemented. - Not sure how IDN tables intersects with IDN Guidelines. - RySG raised the issue that a previously approved IDN table for existing TLDs may not be compliant with the standards and technical advice ICANN has received. RySG received a letter from Goran about the process of ICANN org updating its IDN reference tables with the standards and the latest technical advice. The standards have not change since 2008. There is issue with the technical advice (regarding registry service testing processes) that ICANN org gets and incorporates in the tables. This technical advice was not disseminated in advance, so the registries did not know what to expect. - If the goal is to address security and stability concerns, shouldn’t we update all the IDN tables, not just for the new ones? Usability of the IDN at the 2nd level should be the main focus. - All current tables are approved IDN tables, and no table has caused the security and stability problems. Registries are forced to adopt the new tables while the old tables are safe and secure. GDD explains that everything is the same, but when you go through the RST, the previously approved IDN tables get bounced back with additional requirements. - Need clear requirements for Specs 6 – there are amendments to Specs 6 that refer to another separate work document (e.g., Specification 7 that lays out the requirements for the RPMs which reside in a different document). Need to find a way to reconcile these work documents and not to repeat each other. Pre 2012 Registries do not have to implement the RPM requirements. - IDN Guidelines are created for everyone, but ccTLDs are not bound to IDN Guidelines. It is creating inconsistency and duplication of language. IDN Guidelines v4 has done a little bit too much, therefore causing the overreach problems perceived by Registries. It causes issues for the gTLD due to the enforcement and compliance mechanism. IDNs are already hard to adopt, so forcing compliance won’t help the push for IDNs. May need the creation of a high-level document to ensure the practice of ccTLDs and gTLDs are consistent. Guidelines can be split for gTLD and ccTLD portions. The gTLD portion can focus on creating more consistency that we are seeking. ccTLDs and gTLDs all have the freedom at 2nd level to do as they find best.   - Regarding the technical and compliance disconnect in the IDN Guidelines, those issues can be lumped together to get clarification from ICANN org. Regarding the change process of the IDN Guidelines, the entire process has to be reviewed. A working group may need to be created. - Work in two streams. One stream is to look at the entire change process of the IDN Guidelines. Another stream is to review the backend registry service testing process and the IDN reference tables. There seems to be urgency in clarifying the second work stream items with ICANN. The second stream seems like an effort in the registry side rather than the whole GNSO. It can be a group in the RySG to work it out with ICANN? RST is an internal process of ICANN and up to ICANN how to deal with issues related to it. - If there are perceived errors regarding how ICANN is implementing the IDN tables and technical requirements in the IDN Guidelines (e.g., widespread feeling that Exhibit A and Specs 6 are somewhat inconsistent and registries don’t know which rules follow), maybe the scoping team can recommend that RySG continues the discussions with ICANN? The GNSO side can focus on the overall change process, i.e., the creation/update of the IDN Guidelines. - The technical and compliance/legal issues are not just registry issues; they also impact the registrars. The less confusing and the simpler the implementation, the better for the clients of registrars. The “same entity” requirement is extremely relevant to registrars. - The fundamental question is how we safely use the rules designed for the Root Zone to apply at the second and third level. - A PDP WG can look at the change process of the IDN Guidelines. To give legitimacy/credibility to the IDN Guidelines is a broader structural question. The GNSO needs to think it through going forward. - An expert group can review the technical and compliance issues in the IDN Guidelines, which have urgency and need more immediate fixing. The idea of an expert group may work, as IDN is a niche topic. We also should build in opportunity for community input, so the public can review and comment on the outcome of the expert group. We need to ensure that representatives of Ry and Rr to be there (not just individuals) for an expert group to prevent issues we see now with IDN Guidelines v4. 4. Time permitting, start identifying problems/issues with IDN variant TLD recommendations 5. AOB

1 0

Post call / IDN Scoping Team call / Thursday, 29 August 2019 at 08:00 UTC
by Nathalie Peregrine Aug. 29, 2019

Aug. 29, 2019

Dear all, All recordings for the IDN Scoping Team call held on Thursday, 29 August 2019 at 08:00 UTC can be found on the agenda wiki page <https://community.icann.org/display/IDNST/2019-08-29+IDN+Scoping+Team+Call> (attendance included) and the GNSO Master calendar <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> . 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) For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-council-idn-scoping/> and the main wiki page<https://community.icann.org/x/b4HkBg>. Thank you. Kind regards, Nathalie

1 0

REMINDER: UPDATE DOODLES-Please complete-IDN Scoping Team Call Rotation
by Ariel Liang Aug. 21, 2019

Aug. 21, 2019

Dear IDN Scoping Team members, If you have not yet done so, please fill out the two doodle polls to help identify our bi-weekly meeting times. APAC Friendly Doodle: https://doodle.com/poll/eectniavxh96s9xu NA/EU Friendly Doodle: https://doodle.com/poll/w36ic955ep6fgwvh Thank you! Ariel From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of Andrea Glandon <andrea.glandon(a)icann.org> Date: Monday, August 19, 2019 at 10:31 To: "gnso-council-idn-scoping(a)icann.org" <gnso-council-idn-scoping(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [gnso-secs] REMINDER- UPDATE DOODLES-Please complete-IDN Scoping Team Call Rotation Dear all, Please use the updated links to Doodle polls to find an APAC friendly time and an EU/NA friendly time for bi-weekly IDN Scoping team meetings to be held on Thursdays. APAC Friendly Doodle: https://doodle.com/poll/eectniavxh96s9xu [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_eectni…> NA/EU Friendly Doodle: https://doodle.com/poll/w36ic955ep6fgwvh [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_w36ic9…> Thank you! Kind Regards, Andrea Glandon From: gnso-council-IDN-scoping <gnso-council-idn-scoping-bounces(a)icann.org> on behalf of Andrea Glandon via gnso-council-IDN-scoping <gnso-council-idn-scoping(a)icann.org> Reply-To: Andrea Glandon <andrea.glandon(a)icann.org> Date: Thursday, August 15, 2019 at 13:48 To: "gnso-council-idn-scoping(a)icann.org" <gnso-council-idn-scoping(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [GNSO-Council-IDN-Scoping] DOODLES-Please complete-IDN Scoping Team Call Rotation Dear all, The IDN Scoping team will be meeting bi-weekly on Thursdays and we would like to find 2 rotating times. Please complete each Doodle, this will be to find an APAC friendly time and a NA/EU friendly time. Once the time is chosen, we will rotate the times bi-weekly. At this time the next call will take place on Thursday, 29 August and we will use the EU/NA friendly time since the last call was an APAC friendly time. APAC Friendly Doodle: https://doodle.com/poll/eectniavxh96s9xu [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_eectni…> NA/EU Friendly Doodle: https://doodle.com/poll/w36ic955ep6fgwvh [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_w36ic9…> Thank you! Andrea Glandon GNSO SO/AC Support Internet Corporation for Assigned Names and Numbers (ICANN) Email: andrea.glandon(a)icann.org<mailto:andrea.glandon@icann.org> Skype ID: acglandon76 Find out more about the GNSO by visiting: https://learn.icann.org/ [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 [twitter.com]<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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global Calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 0

REMINDER- UPDATE DOODLES-Please complete-IDN Scoping Team Call Rotation
by Andrea Glandon Aug. 19, 2019

Aug. 19, 2019

Dear all, Please use the updated links to Doodle polls to find an APAC friendly time and an EU/NA friendly time for bi-weekly IDN Scoping team meetings to be held on Thursdays. APAC Friendly Doodle: https://doodle.com/poll/eectniavxh96s9xu [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_eectni…> NA/EU Friendly Doodle: https://doodle.com/poll/w36ic955ep6fgwvh [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_w36ic9…> Thank you! Kind Regards, Andrea Glandon From: gnso-council-IDN-scoping <gnso-council-idn-scoping-bounces(a)icann.org> on behalf of Andrea Glandon via gnso-council-IDN-scoping <gnso-council-idn-scoping(a)icann.org> Reply-To: Andrea Glandon <andrea.glandon(a)icann.org> Date: Thursday, August 15, 2019 at 13:48 To: "gnso-council-idn-scoping(a)icann.org" <gnso-council-idn-scoping(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [GNSO-Council-IDN-Scoping] DOODLES-Please complete-IDN Scoping Team Call Rotation Dear all, The IDN Scoping team will be meeting bi-weekly on Thursdays and we would like to find 2 rotating times. Please complete each Doodle, this will be to find an APAC friendly time and a NA/EU friendly time. Once the time is chosen, we will rotate the times bi-weekly. At this time the next call will take place on Thursday, 29 August and we will use the EU/NA friendly time since the last call was an APAC friendly time. APAC Friendly Doodle: https://doodle.com/poll/eectniavxh96s9xu [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_eectni…> NA/EU Friendly Doodle: https://doodle.com/poll/w36ic955ep6fgwvh [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_w36ic9…> Thank you! Andrea Glandon GNSO SO/AC Support Internet Corporation for Assigned Names and Numbers (ICANN) Email: andrea.glandon(a)icann.org<mailto:andrea.glandon@icann.org> Skype ID: acglandon76 Find out more about the GNSO by visiting: https://learn.icann.org/ [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 [twitter.com]<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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global Calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 0

UPDATE DOODLES-Please complete-IDN Scoping Team Call Rotation
by Andrea Glandon Aug. 16, 2019

Aug. 16, 2019

Dear all, Please use the updated links to Doodle polls to find an APAC friendly time and an EU/NA friendly time for bi-weekly IDN Scoping team meetings to be held on Thursdays. APAC Friendly Doodle: https://doodle.com/poll/eectniavxh96s9xu [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_eectni…> NA/EU Friendly Doodle: https://doodle.com/poll/w36ic955ep6fgwvh Thank you! Kind Regards, Andrea Glandon From: gnso-council-IDN-scoping <gnso-council-idn-scoping-bounces(a)icann.org> on behalf of Andrea Glandon via gnso-council-IDN-scoping <gnso-council-idn-scoping(a)icann.org> Reply-To: Andrea Glandon <andrea.glandon(a)icann.org> Date: Thursday, August 15, 2019 at 13:48 To: "gnso-council-idn-scoping(a)icann.org" <gnso-council-idn-scoping(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [GNSO-Council-IDN-Scoping] DOODLES-Please complete-IDN Scoping Team Call Rotation Dear all, The IDN Scoping team will be meeting bi-weekly on Thursdays and we would like to find 2 rotating times. Please complete each Doodle, this will be to find an APAC friendly time and a NA/EU friendly time. Once the time is chosen, we will rotate the times bi-weekly. At this time the next call will take place on Thursday, 29 August and we will use the EU/NA friendly time since the last call was an APAC friendly time. APAC Friendly Doodle: https://doodle.com/poll/eectniavxh96s9xu [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_eectni…> NA/EU Friendly Doodle: https://doodle.com/poll/w36ic955ep6fgwvh [doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_w36ic9…> Thank you! Andrea Glandon GNSO SO/AC Support Internet Corporation for Assigned Names and Numbers (ICANN) Email: andrea.glandon(a)icann.org<mailto:andrea.glandon@icann.org> Skype ID: acglandon76 Find out more about the GNSO by visiting: https://learn.icann.org/ [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 [twitter.com]<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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global Calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 0

DOODLES-Please complete-IDN Scoping Team Call Rotation
by Andrea Glandon Aug. 16, 2019

Aug. 16, 2019

Dear all, The IDN Scoping team will be meeting bi-weekly on Thursdays and we would like to find 2 rotating times. Please complete each Doodle, this will be to find an APAC friendly time and a NA/EU friendly time. Once the time is chosen, we will rotate the times bi-weekly. At this time the next call will take place on Thursday, 29 August and we will use the EU/NA friendly time since the last call was an APAC friendly time. APAC Friendly Doodle: https://doodle.com/poll/eectniavxh96s9xu NA/EU Friendly Doodle: https://doodle.com/poll/w36ic955ep6fgwvh Thank you! Andrea Glandon GNSO SO/AC Support Internet Corporation for Assigned Names and Numbers (ICANN) Email: andrea.glandon(a)icann.org<mailto:andrea.glandon@icann.org> Skype ID: acglandon76 Find out more about the GNSO by visiting: https://learn.icann.org/ Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO [twitter.com]<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 [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global Calendar [features.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__features.icann.org_cal…>

1 1

Actions & Notes: GNSO IDN Scoping Team Meeting 15 August 3:00 UTC
by Ariel Liang Aug. 15, 2019

Aug. 15, 2019

Dear All, Please find below the action items and notes captured during the IDN Scoping Team call on Thursday, 15 August at 3:00-4:00 UTC. Staff has posted to the wiki space the action items and notes. Please note that these are high-level notes and are not meant as a substitute for the recording and chat room records, which are posted on the wiki at: https://community.icann.org/x/-4XkBg Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) == ACTION ITEMS - Staff to rephrase the sentence in the Option Paper: “Coordinate with the ccNSO to seek to ensure a consistent set of policies and procedures governing gTLD and to the extent possible, ccTLDs”. - The Scoping Team recommends the GNSO Council to send two or three liaison(s) to follow/monitor the ccNSO PDP 4, once it is starting. Council to make a call for volunteer for the liaison position, encouraging people with subject matter expertise to apply. - Staff to check with GNSO-Secs Team about time zone rotation and help the Scoping Team identify appropriate time slots to organize biweekly meetings. NOTES 1. Roll Call & Brief Welcome 2. Background & 3. Scope of Work - Issue with the IDN Tables is how the LGRs are applied in the second level and enforced on registry operators. Need more transparency about the process. - RST is forcing Registry operators using LGRs in situation where ICANN approved IDN tables are already in IANA. - Need people who are subject manner experts to staff the PDP for IDNs, if it happens. - To have a liaison with the ccNSO would be helpful, but the GNSO cannot sync everything with the ccNSO. GNSO doesn’t have to expect full synchronization with the ccNSO (due to nonconformity of certain areas, like emojis). - Is the scoping team looking for a Councilor or a member in the scoping team to be a ccNSO PDP 4 liaison? - Rubens plans to propose another mechanism option for the consideration of the Scoping Team on the mailing list. - Variant recommendations will impact RPMs. - The Scoping Team should state rationale related to the mechanism the it is recommending to the Council. - If recommend EPDP just to shorten the process, it may be fine. But caution not to overburden the volunteers. - Don’t understand why EPDP is an option. May not be a big appetite from the GNSO Council to launch more PDPs / EPDPs right now. - An EPDP is just a PDP without issue report. This issue is pretty well understood so an EPDP suits the work. - Separate the Variant TLD/ccNSO coordination issues from the IDN Implementation Guidelines / IDN Tables. The first two concern with the top level domain names, and the second two concern with the second level. - IDN Implementation Guidelines and IDN Tables also tie with the coordination with the ccNSO. So coordination with ccNSO apply to all three areas. - While it is unlikely ccNSO will ever adopt binding policies, some kind of seal might work. We could create a "Domain Industry IDN Usual Practices" and a ccTLD could say they commit to follow those practices. - ccNSO policies for IDNs might be binding only to non IDN ccTLDs , IDN ccTLDs are not part of ccNSO yet - The Scoping Team should review the Specification 6 of the RA; the IDN guidelines have evolved in an inconsistent way . - ACTION ITEM: Staff to rephrase the sentence in the Option Paper: “Coordinate with the ccNSO to seek to ensure a consistent set of policies and procedures governing gTLD and to the extent possible, ccTLDs”. - ACTION ITEM: The Scoping Team recommends the GNSO Council to send two or three liaison(s) to follow/monitor the ccNSO PDP 4, once it is starting. Council to make a call for volunteer for the liaison position, encouraging people with subject matter expertise to apply. 4. Working Method - No discussion 5. Next Steps - The Scoping Team aims to propose a mechanism to the Council by ICANN66. - Try meet biweekly, doodle for a new time, consider regional rotation (consult with GNSO-Secs team to find appropriate time slots). - ACTION ITEM: Staff to check with GNSO-Secs Team about time zone rotation and help the Scoping Team identify appropriate time slots to organize biweekly meetings.

1 0