<div dir="ltr"><div class="gmail_extra">Hi all,</div><div class="gmail_extra"><br></div><div class="gmail_extra">the deadline for submission is tomorrow, Friday. there is a unresovled comment in the document (<a href="https://docs.google.com/document/d/1L6Fj41rkku6g44FkDbvmUc12MAxv99szaRz8OSmnSbE/edit#">https://docs.google.com/document/d/1L6Fj41rkku6g44FkDbvmUc12MAxv99szaRz8OSmnSbE/edit#</a>) and I didn't see any strong objection.</div><div class="gmail_extra">with regard to Ayden question, I can add this wording:"With regard to terminology, we would like the usage of "should" instead of "encourage" and replace the current occurrences in order to urge related parties(registries and registrars) to take actions for registrants benefits for implementing IDNs", @Adyen what do you think?</div><div class="gmail_extra">if I don't hear any objection in the next 24 hours, I will submit the draft.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Rafik<br>
<br><div class="gmail_quote">2017-12-11 22:35 GMT+09:00 Dr. Tatiana Tropina <span dir="ltr"><<a href="mailto:t.tropina@mpicc.de" target="_blank">t.tropina@mpicc.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div 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><div><div class="gmail-h5">
<br>
<div class="gmail-m_-3634351293308902215moz-cite-prefix">On 10/12/17 10:00, Rafik Dammak wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="gmail-h5">
<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">icann@ferdeline.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>I don't have a strong opinion on this issue or on our
comment, however, in the <span class="gmail-TSRSpan" id="gmail-TSRSpan_20"><img class="gmail-TSRWebRatingIcon" style="width: 16px; height: 16px; border: 0px;"></span><span class="TSRSpan" id="TSRSpan_22"><img class="TSRWebRatingIcon" src="chrome-extension://cfeleongjhdjephegmmmdjgbfjiindbe/./images/webicon_green.png" style="width: 16px; height: 16px; border: 0px;"></span><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" style="background-color:rgb(184,234,184)">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="gmail-m_-3634351293308902215HOEnZb"><font color="#888888"><br>
</font></span></div>
<span class="gmail-m_-3634351293308902215HOEnZb"><font color="#888888">
<div><br>
</div>
<div>— Ayden<br>
</div>
</font></span>
<div class="gmail-m_-3634351293308902215HOEnZb">
<div class="gmail-m_-3634351293308902215h5">
<div class="gmail-m_-3634351293308902215m_6535835065789791790protonmail_signature_block">
<div class="gmail-m_-3634351293308902215m_6535835065789791790protonmail_signature_block-proton gmail-m_6535835065789791790protonmail_signature_block-empty"><br>
</div>
</div>
<div><br>
</div>
<blockquote class="gmail-m_-3634351293308902215m_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">rafik.dammak@gmail.com</a><br>
</div>
<div>To: ncsg-pc <<a href="mailto:ncsg-pc@lists.ncsg.is" target="_blank">ncsg-pc@lists.ncsg.is</a>><br>
</div>
<div><br>
</div>
<div dir="ltr">
<div>
<div class="gmail-m_-3634351293308902215m_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">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">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">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="gmail-m_-3634351293308902215m_6535835065789791790HOEnZb"><span class="gmail-m_-3634351293308902215m_6535835065789791790colour" style="color:rgb(136,136,136)">
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</span></span></div>
<span class="gmail-m_-3634351293308902215m_6535835065789791790HOEnZb"><span class="gmail-m_-3634351293308902215m_6535835065789791790colour" style="color:rgb(136,136,136)">
<div dir="ltr">-- <br>
</div>
<div class="gmail-m_-3634351293308902215m_6535835065789791790m_2516932310301042614gmail_signature">
<div dir="ltr">
<div>Regards<br>
</div>
<div>
<div>@__f_f__<br>
</div>
<div><span class="gmail-TSRSpan" id="gmail-TSRSpan_21"><img class="gmail-TSRWebRatingIcon" style="width: 16px; height: 16px; border: 0px;"></span><span class="TSRSpan" id="TSRSpan_23"><img class="TSRWebRatingIcon" src="chrome-extension://cfeleongjhdjephegmmmdjgbfjiindbe/./images/webicon_green.png" style="width: 16px; height: 16px; border: 0px;"></span><a href="https://www.linkedin.com/in/farellf" target="_blank" style="background-color:rgb(184,234,184)">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="gmail-m_-3634351293308902215mimeAttachmentHeader"></fieldset>
<br>
</div></div><pre>______________________________<wbr>_________________
NCSG-PC mailing list
<a class="gmail-m_-3634351293308902215moz-txt-link-abbreviated" href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a>
<a class="gmail-m_-3634351293308902215moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a>
</pre>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br>
<br></blockquote></div><br></div></div>