<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
Thanks Jennifer
<div><br>
</div>
<div>Look forward to discussing this with the team later today.</div>
<div><br>
</div>
<div>Donna<br id="lineBreakAtBeginningOfSignature">
<div dir="ltr">Sent from my iPhone</div>
<div dir="ltr"><br>
<blockquote type="cite">On 22 Feb 2024, at 6:10 pm, Jennifer Chung via Gnso-epdp-idn-team <gnso-epdp-idn-team@icann.org> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>@font-face { font-family: PMingLiU; }
@font-face { font-family: "Cambria Math"; }
@font-face { font-family: Calibri; }
@font-face { font-family: "@PMingLiU"; }
p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif; }
span.EmailStyle17 { font-family: Calibri, sans-serif; color: windowtext; }
.MsoChpDefault { font-family: Calibri, sans-serif; }
@page WordSection1 { size: 8.5in 11in; margin: 1in; }
div.WordSection1 { page: WordSection1; }
ol { margin-bottom: 0in; }
ul { margin-bottom: 0in; }</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In preparation for our call later, the Ry IDN small group have come up with some proposed text that can be placed either in implementation guidance (although there is no specific rec coming out of C5) or part of the response:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Although there is no specific recommendation coming out of C5, there are high level principles that should be followed during the implementation of this policy recommendation to ensure that the overall process can retain the flexibility
that can accommodate for different registry operator technical solutions and business decisions, but can still be implementable in a consistent manner.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1">ICANN is the manager for the root zone, and registry operators are the managers for second (and subsequent) level(s). As such, operational aspects in terms of the implementation of IDNs at the second level,
including harmonization mechanisms should remain in the responsibilities and scope of each respective manager.<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">The implementation of IDNs at the second level, including evolving issues such as harmonization and homoglyphs should be undertaken by respective registry operators in an operational process with ICANN org,
and must follow the IDNA2008 (including any future versions) and the IDN Implementation Guidelines (including any future versions).<o:p></o:p></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1">Security and stability of the DNS is the baseline criteria. Further details on the procedure, scope and requirements should be developed by registry operators, ICANN org and other relevant stakeholders.<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Looking forward to our discussion later on the call.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Jennifer<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<span>_______________________________________________</span><br>
<span>Gnso-epdp-idn-team mailing list</span><br>
<span>Gnso-epdp-idn-team@icann.org</span><br>
<span>https://mm.icann.org/mailman/listinfo/gnso-epdp-idn-team</span></div>
</blockquote>
</div>
</body>
</html>