<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Philippe: <div class=""><br class=""></div><div class="">Thanks for this and arranging time for the discussion. </div><div class=""><br class=""></div><div class="">I think it is fine to combine the two items into the existing agenda item (especially considering the packed agenda). Both items rely on Dennis’ expertise. However, I think we should be careful to identify the issues as separate, making it clear that the Operational Track discussion will not affect the IDN EPDP Charter in any way. </div><div class=""><br class=""></div><div class="">Again, thanks for your accommodation. </div><div class=""><br class=""></div><div class="">Best regards,</div><div class=""><br class=""></div><div class="">Kurt</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 19, 2021, at 8:25 AM, <<a href="mailto:philippe.fouquart@orange.com" class="">philippe.fouquart@orange.com</a>> <<a href="mailto:philippe.fouquart@orange.com" class="">philippe.fouquart@orange.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Dear Kurt,<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">I realised we haven’t shared the response to your question with the full council, so there we go, my apologies.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">We will indeed have this discussion ‘item’ on the IDN operational track/</span><span lang="EN-GB" class=""><span class="Apple-converted-space"> </span></span><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">adoption of the IDN Implementation Guidelines v4.0, included in item 5.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">We haven’t dedicated a standalone agenda item, because of the dependencies underlined in your message. We suggest that under the item for the “Initiation of the EPDP on IDN & its Charter”, we go through the scope and charter first including timeline and then discuss the Operational track before our vote on the motion. <o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Hope that’s not too convoluted agenda-wise, this discussion is warranted and combining the two seems to make sense in substance; we’ll obviously turn to the RySG councillors to help us understand the rationale for stopping the operational track and deferring adoption of the guidelines v4 under that item, and where we move from there.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Thanks.<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Regards,<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class="">Philippe<o:p class=""></o:p></span></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><span lang="EN-GB" style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);" class=""><o:p class=""> </o:p></span></div><div class=""><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(225, 225, 225); padding: 3pt 0cm 0cm;" class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><b class=""><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class="">From:</span></b><span style="font-size: 11pt; font-family: Calibri, sans-serif;" class=""><span class="Apple-converted-space"> </span>Kurt Pritz [<a href="mailto:kurt@kjpritz.com" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">mailto:kurt@kjpritz.com</a>]<span class="Apple-converted-space"> </span><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Tuesday, May 11, 2021 12:21 AM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>FOUQUART Philippe TGI/OLN <<a href="mailto:philippe.fouquart@orange.com" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">philippe.fouquart@orange.com</a>>; Tatiana Tropina <<a href="mailto:tatiana.tropina@gmail.com" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">tatiana.tropina@gmail.com</a>>; Pam Little <<a href="mailto:pam.little@alibaba-inc.com" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">pam.little@alibaba-inc.com</a>><br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span>GNSO Council List <<a href="mailto:council@gnso.icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">council@gnso.icann.org</a>>; gnso-SECS <<a href="mailto:gnso-secs@icann.org" style="color: rgb(149, 79, 114); text-decoration: underline;" class="">gnso-secs@icann.org</a>><br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>IDN Operational Track - proposed agenda item<o:p class=""></o:p></span></div></div></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div><p class="MsoNormal" style="margin: 0cm 0cm 12pt; font-size: 12pt; font-family: "Times New Roman", serif;">Dear Council Members: <br class=""><br class="">I and my RySG Councillor colleagues are writing to propose an agenda item for the May 2021 Council meeting: <o:p class=""></o:p></p><ul type="disc" style="margin-bottom: 0cm;" class=""><li class="MsoNormal" style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;">Next Steps for IDN Operational Track<o:p class=""></o:p></li></ul><p class="MsoNormal" style="margin: 0cm 0cm 12pt; font-size: 12pt; font-family: "Times New Roman", serif;"><br class="">The purpose of this discussion is to reconsider the Council recommended approach for proceeding with the Operational Track vis-à-vis the adoption of the IDN Implementation Guidelines v4.0. The current approach calls for the formation or “reconstituting” of an IDN Guidelines Working Group to review the issues related to its implementation (raised by RySG) and assess a path forward. <br class=""><br class="">In the meantime, the Council has spun up the IDN EPDP (i.e., the Policy Track), whose charter is nearing completion. The IDN EPDP will consider some of the same issues that the IDN Implementation Guidelines version 4.0 is addressing.<br class=""><br class="">Similarly, the SubPro PDP also considered some of the same issues, and there is a likelihood that the SubPro IRT and IDN EPDP will approach these issues from a different perspective and develop what might be contradicting results.<br class=""><br class="">In both of these cases (overlap with the Guidelines Operational Track and with the SubPro IRT), some of the issues require policy considerations rather than operational implementation and are better suited for discussion in a policy development process. <br class=""><br class="">These issues are the principle and implementation of the same entity at the second level, and the harmonization of IDN tables (i.e., the creation of a consistent set of variant rules in a given registry TLD).<br class=""><br class="">Therefore, I recommend a briefing during the next meeting so that we can better understand these issues, consider our approach, and make a recommendation to the Board. Dennis Tanaka, chair of the IDN EPDP, could lead that presentation. <br class=""><br class="">As I understand it so far, a preferable approach would be to continue deferring the adoption of the IDN Implementation Guidelines 4.0 until the issues overlapping with the SubPro PDP and IDN EPDP can be fully deliberated and implemented by the corresponding Implementation Review Teams. Conditions for such a deferral might include: <o:p class=""></o:p></p><blockquote style="margin-left: 30pt; margin-right: 0cm;" class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">a. a security / stability check to ensure we are not deferring implementation of IDN Guidelines v4.0 that address stability / security issues,<br class="">b. a provision that the IDN EPDP could forward to the Council IDN Guideline-specific recommendations as they are created, rather than waiting for the final report, and<br class="">c. coordination with the SubPro IRT so that the SubPro implementation work will not be delayed in any way.<o:p class=""></o:p></div></blockquote><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><br class="">In addition to the overlapping efforts between the IDN Guidelines, the SubPro PDP, and the IDN EPDP, the ccNSO is also undertaking an IDN Policy re-write for ccTLDs. While GNSO and ccNSO policies are separable in the ICANN world, differences in outcomes can lead to confusing results for domain registrants and users. Therefore, I think we should take advantage of the timing coincidence between the GNSO and ccNSO efforts to normalize results between the two wherever possible. <br class=""><br class="">As described above, there are now several IDN-related efforts for the purpose of enhancing their availability, ease of use and security. I think we should take advantage of the timing of this EPDP to reconcile the various approaches so that there is a coherent approach to IDN policy making and ensuring a good user experience. <br class=""><br class="">Thanks for taking the time to read and consider this.<br class=""><br class="">Best regards,<o:p class=""></o:p></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">Maxim Alzoba<o:p class=""></o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">Sebastien Ducos<o:p class=""></o:p></div></div><div class=""><div style="margin: 0cm 0cm 0.0001pt; font-size: 12pt; font-family: "Times New Roman", serif;" class="">Kurt Pritz<o:p class=""></o:p></div></div></div><pre style="caret-color: rgb(0, 0, 0); font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class="">_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre></div></blockquote></div><br class=""></div></body></html>