<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Rafik,</p>
<p>Friday looks like a good solution - will go through the comment
tonight. Thank you.</p>
<p>Farz and I are working on the jurisdiction and ombudsman reports
comments, so a note to all to stay tuned - we will share them this
week probably.</p>
<p>Cheers,</p>
<p>Tanya <br>
</p>
<br>
<div class="moz-cite-prefix">On 10/12/17 10:00, Rafik Dammak wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAH5sTh=W6=nKwBLScaGePS+VbRZUz5UuWQTYg1S-+J-eTqjoAw@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">
<div class="gmail_extra">Hi Ayden,</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Thanks for the question, it seems that
when it comes to a matter related to technical aspects (they
are using IETF terminology), "must" is often used while
"encourage" (6 occurrences )is more for informational matter
and urging registries to cooperate for example. knowing how
much IDNs are facing as problems to be implemented and not
necessarily seen as a good business opportunity for many
registrars except for some non-latin scripts, I would think
the guidelines should be implementable and less onerous in
order to provide registrants more choice.<br>
we can put a note anyway saying that we think that we prefer
the term "shall" or "should" at least which is probably
stronger "encourage".</div>
<div class="gmail_extra">btw the staff is keen to give us an
extension and asking when we can submit. I would suggest to
them that we can submit by this Friday.</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Best,</div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Rafik</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2017-12-10 6:40 GMT+09:00 Ayden
Férdeline <span dir="ltr"><<a
href="mailto:icann@ferdeline.com" target="_blank"
moz-do-not-send="true">icann@ferdeline.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>I don't have a strong opinion on this issue or on our
comment, however, in the <a
href="https://www.icann.org/en/system/files/files/draft-idn-guidelines-03mar17-en.pdf"
title="https://www.icann.org/en/system/files/files/draft-idn-guidelines-03mar17-en.pdf"
rel="nofollow" target="_blank" moz-do-not-send="true">source
document</a>, the word "encourage" is used frequently.
i.e. "Encourage registrars to notify registrants of
non-conforming registered domain names".<br>
</div>
<div><br>
</div>
<div>Do we think this terminology is appropriate? I prefer
words like "must" - they give registrants more clarity
over what they can expect from registrars - but I could
be persuaded otherwise.<span class="HOEnZb"><font
color="#888888"><br>
</font></span></div>
<span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<div>— Ayden<br>
</div>
</font></span>
<div class="HOEnZb">
<div class="h5">
<div
class="m_6535835065789791790protonmail_signature_block">
<div
class="m_6535835065789791790protonmail_signature_block-proton
m_6535835065789791790protonmail_signature_block-empty"><br>
</div>
</div>
<div><br>
</div>
<blockquote
class="m_6535835065789791790protonmail_quote"
type="cite">
<div>-------- Original Message --------<br>
</div>
<div>Subject: [NCSG-PC] Fwd: [NCSG-Discuss] Second
Public Comment on IDN Guidelines<br>
</div>
<div>Local Time: 9 December 2017 5:37 AM<br>
</div>
<div>UTC Time: 9 December 2017 05:37<br>
</div>
<div>From: <a href="mailto:rafik.dammak@gmail.com"
target="_blank" moz-do-not-send="true">rafik.dammak@gmail.com</a><br>
</div>
<div>To: ncsg-pc <<a
href="mailto:ncsg-pc@lists.ncsg.is"
target="_blank" moz-do-not-send="true">ncsg-pc@lists.ncsg.is</a>><br>
</div>
<div><br>
</div>
<div dir="ltr">
<div>
<div data-smartmail="gmail_signature"
class="m_6535835065789791790gmail_signature">
<div>hi all,<br>
</div>
<div><br>
</div>
<div>the deadline for submission is 10th
December, I will try to ask for few days
extension. I would like to ask you review
the draft for endorsement or not.<br>
</div>
<div>after that, we can focus on several
public comments which deadline is around 5th
January.<br>
</div>
<div><br>
</div>
<div>Best,<br>
</div>
</div>
</div>
<div><br>
</div>
<div>Rafik<br>
</div>
<div class="gmail_quote">
<div>---------- Forwarded message ----------<br>
</div>
<div>From: <b class="gmail_sendername">Farell
Folly</b> <span dir="ltr"><<a
href="mailto:farellfolly@gmail.com"
target="_blank" moz-do-not-send="true">farellfolly@gmail.com</a>></span><br>
</div>
<div>Date: 2017-12-05 0:38 GMT+09:00<br>
</div>
<div>Subject: [NCSG-Discuss] Second Public
Comment on IDN Guidelines<br>
</div>
<div>To: <a
href="mailto:NCSG-DISCUSS@listserv.syr.edu"
target="_blank" moz-do-not-send="true">NCSG-DISCUSS@listserv.syr.edu</a><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div dir="ltr">
<div>Dear All,<br>
</div>
<div><br>
</div>
<div>In October 2017, ICANN called for a
second public comment on the version 4.0 of
IDN Guidelines. Actually, following the
first round of comments most of the concerns
addressed by the community were taken into
account. Nevertheless, two questions remain
open and some people here may think it is
useful to discuss them. Please check what
we <a
href="https://docs.google.com/document/d/1L6Fj41rkku6g44FkDbvmUc12MAxv99szaRz8OSmnSbE/edit#"
target="_blank" moz-do-not-send="true">drafted</a>
so far and make your suggestions, if any.
Otherwise, we won't have a significant
comment on this report and just endorse it.<br>
</div>
<span class="m_6535835065789791790HOEnZb"><span
class="m_6535835065789791790colour"
style="color:#888888">
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</span></span></div>
<span class="m_6535835065789791790HOEnZb"><span
class="m_6535835065789791790colour"
style="color:#888888">
<div dir="ltr">-- <br>
</div>
<div data-smartmail="gmail_signature"
class="m_6535835065789791790m_2516932310301042614gmail_signature">
<div dir="ltr">
<div>Regards<br>
</div>
<div>
<div>@__f_f__<br>
</div>
<div><a
href="https://www.linkedin.com/in/farellf"
target="_blank"
moz-do-not-send="true">https://www.linkedin.com/in/fa<wbr>rellf</a>
<br>
</div>
</div>
</div>
</div>
</span></span></div>
</div>
</blockquote>
<div><br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
NCSG-PC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
</pre>
</blockquote>
<br>
</body>
</html>