Hello Edmon, I think the idea of not overlapping with other current PDPs is a good one. The PDP will allow to have in the initial report in addition to the current document set potential list of the items, which might be changed or with which IDN policy (I think if it is PDP -> in the end we hope to have a policy). As I mentioned before, we have not dived into operational and legal part (of what might be caused by 'the same entity' idea for the existing domains and for domains, where different rightful owners have TM rights, for example for variants of the same word). I believe we need to review more in deep overlaps of SSAC060 and IDN Guidelines and to add it to the documents not just as a bit of text mentioning the relevance , but to investigate to what degree and what should we do in the team about it. Also I believe that there are more than two stakeholder groups (it is not just Registrars and Registries), who are going to be most affected by the 'same entity' owner for variants idea, but the TM owners and Registrants, so it would be reasonable to request input from the SGs. Sincerely Yours, Maxim Alzoba Special projects manager, International Relations Department, FAITID Current UTC offset: +3.00 (.Moscow)
On 11 Dec 2019, at 02:19, Edmon via gnso-council-IDN-scoping <gnso-council-idn-scoping@icann.org> wrote:
Thanks Steve.
It seems clear at this point we should recommend for the matters to proceed in a separate PDP and not added to existing PDPs.
One of the important decisions the group needs to make though, is whether to recommend to the GNSO Council: A) A regular PDP, for which an Issues Report needs to be developed B) An EPDP, for which the only difference from a PDP is a further Issues Report is not required
Given the volume of background information already produced for the topic, as well as the rough draft which staff has drawn up, which includes the issues (1) as well as the listing of the background documents (2): 1. https://docs.google.com/document/d/13tO5IP64EAnFebdefRahK3vuhIBzUEdl1oeGFBnQ... <https://docs.google.com/document/d/13tO5IP64EAnFebdefRahK3vuhIBzUEdl1oeGFBnQ...> 2. https://docs.google.com/document/d/1vhbIIpua9_3s_0G-LMNQ3hdWo8SkIxObUSpfJPk-... <https://docs.google.com/document/d/1vhbIIpua9_3s_0G-LMNQ3hdWo8SkIxObUSpfJPk-...>
It appears that an EPDP is the appropriate approach because there is ample background information on the subject and there does not seem to be any clear gaps requiring an Issues report.
I understand that Maxim has raised concerns about EPDP, but that seems to stem from the emotional aftermath of how the EPDP in response to GDPR was created more than the actual requirement (i.e. of the Issues Report). If there are any other concerns or objections to proceeding with EPDP please raise them.
If we do move forward to recommend an EPDP approach, the chartering team can determine the structure and membership of the EPDP working group and complete the IDN Variant Issues Scoping (1. Above) which would form essentially an issues report for the working group consideration.
Please take a look and we hope to come to conclusion on the matter so we can make the recommendation to the council before its meeting in January.
Edmon
From: gnso-council-IDN-scoping [mailto:gnso-council-idn-scoping-bounces@icann.org <mailto:gnso-council-idn-scoping-bounces@icann.org>] On Behalf Of Steve Chan via gnso-council-IDN-scoping Sent: Saturday, December 7, 2019 4:02 AM To: gnso-council-idn-scoping@icann.org <mailto:gnso-council-idn-scoping@icann.org> Subject: [GNSO-Council-IDN-Scoping] Actions & Notes: GNSO IDN Scoping Team Meeting on 5 December at 3:00 UTC
Dear Team,
With apologies for the late delivery, please find below the action items and notes captured during the IDN Scoping Team call on Thursday, 5 December at 3: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/z5czBw <https://community.icann.org/x/z5czBw>
Best, Steve
== Action Item - Staff to add SAC060 and SAC052 to the list of documents - Edmon to determine if he feels like he can make an assessment as to which Option the scoping team supports to recommend to the GNSO Council. If he is able, he will provide his assessment to the email list for input.
NOTES Welcome and roll call
- Edmon may need to leave meeting early - Update on coordination with the SubPro PDP – SubPro leadership does not believe that the IDN work must take place in SubPro. If an IDN variants PDP is launched, it can further the related work done in SubPro and build upon it. - Edmon has review the SubPro draft recs and they indeed seem like they can be built upon rather than needing to be overturned. - SubPro may want to consider the technical utilization paper for the RZ-LGR, currently under Board consideration, but they should be aware that it’s a fluid situation of they indeed review the document now. - GNSO policies can be replaced by policy development taking place at a later date, so a new PDP on IDN variants could in theory develop recommendations that go against the SubPro recommendations on IDN variants.
Review of new Issue Scoping Document here: https://docs.google.com/document/d/13tO5IP64EAnFebdefRahK3vuhIBzUEdl1oeGFBnQ... <https://docs.google.com/document/d/13tO5IP64EAnFebdefRahK3vuhIBzUEdl1oeGFBnQ...>
- Purpose of this document is to explore whether or not there is sufficient background documentation and analysis to serve as a proxy for an Issue Report, which could make an EPDP make some sense - There is also the existing work on IDN variants taking place in SubPro - Document is structured similarly to the substantive part of an Issue Report and make sure that all of the required elements are present. - First part is about identifying the problems that need to be solved, which in this case come from the Board resolution (e.g., RZ-LGR must be the only source and that policies should be developed to manage IDN variant TLDs for current and future gTLDs). - Also notes that coordination with ccNSO is needed and GNSO concerns about the process by which the IDN Guidelines are updated from version to version. - Second section identifies the list of relevant documentation. There is also, by reference, a comprehensive list of documents related to IDN variants.
ACTION – Add SAC060 and SAC052 to the list of documents
- The list is not intended to limit what a PDP may consider, in the event something relevant arises later. - Third part of the document is about the issues and questions a PDP should consider and address. Firstly, broken down into the two challenges. Lists out the recommendations from the staff report. - Also lists out questions from the staff report where there may be policy implications. This list is captured verbatim from the staff paper. - The Council did not specifically request a charter from the IDN Scoping team - There was not a specific time frame dictated by the Council, but there is an expectation that the scoping team will provide its recommendations prior to the end of the year. Concerns expressed from Maxim about the time constraint.
After discussing agenda item 2, revisiting the options paper:https://docs.google.com/document/d/1o_9bfnkKufrSxiJGxpNcOcfTK2VLWp5XYQvwe5qx... <https://docs.google.com/document/d/1o_9bfnkKufrSxiJGxpNcOcfTK2VLWp5XYQvwe5qx...>
- In light of the previous discussion about what could be in an issue report, based on existing materials and analysis, what option makes the most sense? - Option A is to leverage existing PDPs (i.e., SubPro and RPMs), Option B is to separate new gTLDs versus existing gTLDs, Option C is a PDP or EPDP, Option D is an expert working group. - Maxim indicates that there is not support from the entire group to for an EPDP, suggestion that he should indicate why he oppose, what he prefers, and why. Also indicates that GNSO should not feel obligated to follow pace of ccNSO.
ACTION – Edmon to determine if he feels like he can make an assessment as to which Option the scoping team supports to recommend to the GNSO Council. If he is able, he will provide his assessment to the email list for input.
- Maxim notes that some believe that the set of documents is not holistic and that further analysis is needed.
Possible next steps
- None, discussed above
AOB
- None
Steven Chan > Policy Director, GNSO Support
Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 >
Email: steve.chan@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=DwMG...> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGNS...> 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_group-2Dactivities_calendar&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DRa2dXAvSFpCIgmkXhFzL7ar9Qfqa0AIgn-H4xR2EBk&m=jLNFXvpu9gNdUeHi-G6sjWNCF9w4_AwhzzUDFZy2elE&s=-L6chFfv0OperrXHHpTF722WnH3FZIutn4cS16IvpOg&e=>_______________________________________________ gnso-council-IDN-scoping mailing list gnso-council-IDN-scoping@icann.org <mailto:gnso-council-IDN-scoping@icann.org> https://mm.icann.org/mailman/listinfo/gnso-council-idn-scoping <https://mm.icann.org/mailman/listinfo/gnso-council-idn-scoping>
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <https://www.icann.org/privacy/tos>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.