<div dir="ltr">hi all,<div><br></div><div>all fair questions and concerns, I don't think we elaborated too much in our draft anyway. I didn't submit and so we can drop this as we already passed the deadline. While I see that we should respond every time, we chose to not do so in previous occurrences.</div><div><br></div><div>my personal conclusion for the last related IDN comments is that we need more capacity on that area and having more members following closely and getting involved on the teams. I know that some are participating with their individual capacity in several LGR teams (they are by script) and we can build on that.</div><div>I discussed with Farznaeh and thinking we should:</div><div>- reach to ICANN staff for some introductory webinars for our members to build more awareness on IDN on the technical side, policy-related matters.</div><div>- identify experts within NCSG membership who can help through webinar too. <br>an approach that can be applied to other areas.</div><div><br>Best,</div><div><br></div><div>Rafik</div><div><br></div><div><div class="gmail_quote"><div dir="ltr">Le mar. 18 sept. 2018 à 18:42, Farell FOLLY <<a href="mailto:farell@benin2point0.org">farell@benin2point0.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space">Hi Farzaneh,<div><br></div><div>I was part of the drafters' team and I must confess that I did not put too much effort on the work since I was also concerned with other Public Comments that required an effective attention from me, too.</div><div><br></div><div>Not only the question asked and the IDN issues as a whole require a high technical knowledge and experience with the subject, but also there was a lot of documents to read and a strong background to have before writing something. I went through all the docs but I could not answer most of the questions with enough confidence within the time slot proposed. If you still can, don’t hesitate, go ahead and edit the draft. However; there is no issue/problem not answering all the questions…. We can write “no answer” or “NIHIL”. </div><div><br></div><div>As far as not submitting a comment here (in state or not), I must refer to Rafik, the policy Chair whose vision is rather to always comment/acknowledge on/a calls.</div><div><br></div><div>Regarding the questions and in my opinion, 1 is yes, 2a is yes, 2.b is possible (but needs further discussions within NCSG) 3 is mostly yes but with some nuances to clarify. For 5, I am unable to answer by now (further reading and IDN knowledge to gain). Regarding the 6th, what you are describing seems to be a valid additional risk, and there may be many others to add but with strong rationale (to describe and to simulate their impacts)</div><div><br></div><div><br></div><div>That’s it!<br><div>
<div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="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;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="word-wrap:break-word;line-break:after-white-space"><br class="m_-5190476675869645435Apple-interchange-newline">@__f_f__<br><br>Best Regards<br><div style="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">____________________________________</div><div style="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"><br></div><div style="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">(Ekue) Farell FOLLY</div><div style="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">NCUC Rep. to the NCSG Policy Committee</div><div style="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"><a href="http://linkedin.com/in/farellf" target="_blank">linkedin.com/in/farellf</a> <br></div><div style="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"><br></div><div style="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"><br></div><br class="m_-5190476675869645435Apple-interchange-newline"></div></div><br class="m_-5190476675869645435Apple-interchange-newline" style="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"><br class="m_-5190476675869645435Apple-interchange-newline" style="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"></div></div></div></div>
</div>
<div><br><blockquote type="cite"><div>On 18 Sep 2018, at 05:52, farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" target="_blank">farzaneh.badii@gmail.com</a>> wrote:</div><br class="m_-5190476675869645435Apple-interchange-newline"><div><div dir="ltr"><div style="font-family:verdana,sans-serif">Hi All</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">I know we are all overburdened with a lot of work and I thank whoever drafted this document. But I think this comment needs further improvement. We are not really addressing the issues that the report is asking for.</div><div style="font-family:verdana,sans-serif">I pasted the questions. I am sorry I am of no help, I really don't have the time to read carefully but here are my observations: </div><div style="font-family:verdana,sans-serif">1. I think something pertinent to question 3 and 4 (and I might be wrong) is that if they want to again delegate the name of the countries in IDN to the cctld managers, these managers should not be allowed to use UDRP service providers such as WIPO. (I don't know how far they go, do they delegate similar names of countries and territories -overreach alert- or exact names? I could not figure out)</div><div style="font-family:verdana,sans-serif">Why am I against that? Because even in non IDN ccTLDs we see trademark overreach. Amazon has claimed so many domain names that have had similarities to Amazon in ccTLDs that Amazon did not even have any business at!!! Rest assured that this is going to happen to IDNs as well. Note that processes such as WIPO are most of the time only in English.</div><div style="font-family:verdana,sans-serif">If we are defenders of diversity I think this is where we should act! </div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Anyhow. I might be wrong. As I said it was a cursory review and general knowledge.If we cannot elaborate on the questions below, then I think we should not submit the comment in its current state.</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif">Questions that were asked:</div><div style="font-family:verdana,sans-serif"><br></div><div style="font-family:verdana,sans-serif"><ol style="box-sizing:border-box;margin:0px 0px 1.25rem;padding:0px 0px 0px 30px;color:rgb(51,51,51);font-family:helvetica,arial,sans-serif;font-size:16px"><li style="box-sizing:border-box;line-height:1.4rem;margin:0px 0px 15px 20px"><em style="box-sizing:border-box">The rationale for the RZ-<abbr title="Label Generation Rules" style="box-sizing:border-box;font-weight:inherit;unicode-bidi:bidi-override;direction:ltr;border-bottom:1px dotted rgb(153,153,153);text-decoration-line:none;text-decoration-style:initial">LGR</abbr> requires strictly adhering to the IDN variant label sets defined by the community through the RZ-<abbr title="Label Generation Rules" style="box-sizing:border-box;font-weight:inherit;unicode-bidi:bidi-override;direction:ltr;border-bottom:1px dotted rgb(153,153,153);text-decoration-line:none;text-decoration-style:initial">LGR</abbr>. Is this a reasonable pre-requisite for implementing IDN Variant TLDs?</em></li><li style="box-sizing:border-box;line-height:1.4rem;margin:0px 0px 15px 20px"><em style="box-sizing:border-box">Do the proposed recommendations appropriately address the management and implementation of the IDN Variant TLDs?</em><ol class="m_-5190476675869645435gmail-lower-alpha" style="box-sizing:border-box;margin:0px 0px 1.25rem;padding:0px 0px 0px 30px;list-style-type:lower-alpha"><li style="box-sizing:border-box;line-height:1.4rem;margin:0px 0px 15px 20px"><em style="box-sizing:border-box">Do any suggested recommendations need to be changed? Why?</em></li><li style="box-sizing:border-box;line-height:1.4rem;margin:0px 0px 15px 20px"><em style="box-sizing:border-box">Are any additional recommendations needed?</em></li></ol></li><li style="box-sizing:border-box;line-height:1.4rem;margin:0px 0px 15px 20px"><em style="box-sizing:border-box">Does the analysis suitably cover the impact of the recommendations on existing procedures for IDN ccTLDs and IDN gTLDs? Is there alternate analysis for certain cases? Are there any additional impacts on the procedures not identified?</em></li><li style="box-sizing:border-box;line-height:1.4rem;margin:0px 0px 15px 20px"><em style="box-sizing:border-box">Which (if any) of the recommendations require policy consideration by <abbr title="Generic Names Supporting Organization" style="box-sizing:border-box;font-weight:inherit;unicode-bidi:bidi-override;direction:ltr;border-bottom:1px dotted rgb(153,153,153);text-decoration-line:none;text-decoration-style:initial">GNSO</abbr> and <abbr title="Country Code Names Supporting Organization" style="box-sizing:border-box;font-weight:inherit;unicode-bidi:bidi-override;direction:ltr;border-bottom:1px dotted rgb(153,153,153);text-decoration-line:none;text-decoration-style:initial">ccNSO</abbr>, whereas the remaining would only have an impact on procedures?</em></li><li style="box-sizing:border-box;line-height:1.4rem;margin:0px 0px 15px 20px"><em style="box-sizing:border-box">To prevent the permutation issue which can be introduced by using variant labels, as identified by <abbr title="Security and Stability Advisory Committee" style="box-sizing:border-box;font-weight:inherit;unicode-bidi:bidi-override;direction:ltr;border-bottom:1px dotted rgb(153,153,153);text-decoration-line:none;text-decoration-style:initial">SSAC</abbr>, how may the allocated IDN Variant <abbr title="Top Level Domain" style="box-sizing:border-box;font-weight:inherit;unicode-bidi:bidi-override;direction:ltr;border-bottom:1px dotted rgb(153,153,153);text-decoration-line:none;text-decoration-style:initial">TLD</abbr> labels be limited? Are the mechanisms suggested in Appendix C appropriate? What other factors may also be relevant?</em></li><li style="box-sizing:border-box;line-height:1.4rem;margin:0px 0px 15px 20px"><em style="box-sizing:border-box">Are the risks and their mitigation measures sufficiently comprehensive? Are there any additional risks? Should there be different or additional mitigation measures?</em></li></ol></div><div><div dir="ltr" class="m_-5190476675869645435gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Sep 17, 2018 at 8:08 PM Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">hi all,<div><br></div><div>the deadline passed but it is possible to submit. please chime in</div><div>the draft comment is quite short.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik<br><br><div class="gmail_quote"><div dir="ltr">Le lun. 17 sept. 2018 à 22:06, Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">hi all,<div><br></div><div>please review the draft statement, the deadline for submission is today.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik</div><div><br><div class="gmail_quote"><div dir="ltr">Le sam. 15 sept. 2018 à 16:44, Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" target="_blank">rafik.dammak@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>please review the draft comment <a href="https://docs.google.com/document/d/19IIt4o1kSwN2o0aJJ09IL1Qh49GVdlps2QLdhmpA0BI/edit" target="_blank">https://docs.google.com/document/d/19IIt4o1kSwN2o0aJJ09IL1Qh49GVdlps2QLdhmpA0BI/edit</a>. the deadline for submission is the 17th September.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik<br><br><br><div class="gmail_quote"><div dir="ltr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Farell FOLLY</strong> <span dir="ltr"><<a href="mailto:farell@benin2point0.org" target="_blank">farell@benin2point0.org</a>></span><br><br></div><br><br><div style="word-wrap:break-word;line-break:after-white-space"><div>Dear All,</div><div><br></div><div>This is another public comment on the IDN for review. It is a brief comment but all new suggestions are welcome. The deadline is to the 17th of September.</div><div><br></div><a href="https://docs.google.com/document/d/19IIt4o1kSwN2o0aJJ09IL1Qh49GVdlps2QLdhmpA0BI/edit" target="_blank">https://docs.google.com/document/d/19IIt4o1kSwN2o0aJJ09IL1Qh49GVdlps2QLdhmpA0BI/edit</a><br><div>
<div dir="auto" style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="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;word-wrap:break-word;line-break:after-white-space"><div dir="auto" style="word-wrap:break-word;line-break:after-white-space"><br class="m_-5190476675869645435m_-1271707571789352458m_7089830092193148125m_4680673000357330933m_-1602939769246788619Apple-interchange-newline">@__f_f__<br><br>Best Regards<br><div style="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">____________________________________</div><div style="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"><br></div><div style="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">(Ekue) Farell FOLLY</div><div style="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">NCUC Rep. to the NCSG Policy Committee</div><div style="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"><a href="http://linkedin.com/in/farellf" target="_blank">linkedin.com/in/farellf</a> <br></div><div style="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"><br></div><div style="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"><br></div><br class="m_-5190476675869645435m_-1271707571789352458m_7089830092193148125m_4680673000357330933m_-1602939769246788619Apple-interchange-newline"></div></div><br class="m_-5190476675869645435m_-1271707571789352458m_7089830092193148125m_4680673000357330933m_-1602939769246788619Apple-interchange-newline" style="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"><br class="m_-5190476675869645435m_-1271707571789352458m_7089830092193148125m_4680673000357330933m_-1602939769246788619Apple-interchange-newline" style="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"></div></div></div></div>
</div>
<br></div></div></div></div>
</blockquote></div></div></div>
</blockquote></div></div></div>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">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/listinfo/ncsg-pc</a><br>
</blockquote></div>
_______________________________________________<br>NCSG-PC mailing list<br><a href="mailto:NCSG-PC@lists.ncsg.is" target="_blank">NCSG-PC@lists.ncsg.is</a><br><a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br></div></blockquote></div><br></div></div></blockquote></div></div></div>