<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Thank you Tatiana. I will send more soon. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div><div dir="ltr" class="gmail_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" class="gmail_attr">On Wed, Feb 13, 2019 at 3:19 AM Tatiana Tropina <<a href="mailto:tatiana.tropina@gmail.com">tatiana.tropina@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto">Hi, </div></div><div dir="auto">As those points align with my position, I can certainly make them before voting yes — either tomorrow or on the GNSO call. I guess there will be time for expressing opinions. If this would be a consensus position of the NCSG, one of us can make a statement, as we did with Red Cross. I guess we have enough time to prepare a consensus statement before the GNSO vote, if necessary. </div><div dir="auto">Cheers </div><div dir="auto">Tanya </div><div><br><div class="gmail_quote"><div dir="ltr">On Wed 13. Feb 2019 at 09:12, farzaneh badii <<a href="mailto:farzaneh.badii@gmail.com" target="_blank">farzaneh.badii@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div dir="auto">Yes I will send my thoughts but it is not a<span class="gmail_default" style="font-family:verdana,sans-serif"> n NCSG </span> <span class="gmail_default" style="font-family:verdana,sans-serif"> consensus position. so just take them as a personal opinion for now</span></div></div><div dir="auto"><span class="gmail_default" style="font-family:verdana,sans-serif"><br></span></div><div><span class="gmail_default" style="font-family:verdana,sans-serif">It seems like the motion is to approve the whole report and then move forward. So the easiest and most logical is to vote for the approval of the report. I am not well versed in GNSO operating procedures, so I don't really know if this is feasible but I would like to know if one of our council members as well as saying yes to the approval could make some of the following points:</span></div><div dir="auto"><span class="gmail_default" style="font-family:verdana,sans-serif"><br></span></div><div><span class="gmail_default" style="font-family:verdana,sans-serif">1. The EPDP despite an unrealistic timeline achieved its goal and delivered the final report(of phase 1). We are pleased with the outcome of the group and our councilors have voted yes to the approval of this report, but we would like to record our concerns with some aspects of the report. Grateful, nice multistakeholder participation, thanks you,you are all heros. </span></div><div><span class="gmail_default" style="font-family:verdana,sans-serif"><br></span></div><div><span class="gmail_default" style="font-family:verdana,sans-serif">2. The registrants data elements that are a part of the data elements matrix have expanded and include "</span><span style="color:black;font-family:Calibri,sans-serif;font-size:12pt">Additional data elements as identified by Registry Operator in its registration policy<span class="gmail_default" style="font-family:verdana,sans-serif"> ".Which can be sensitive, personal information of domain name registrants. We have raised this concern and emphasized that there is no reason to add or even mention the additional data elements to the data matrix and no need to base some of the purposes (such as purpose 7) based on this data</span></span><span style="font-family:verdana,sans-serif;color:black;font-size:12pt">. The response that we received was that this provision<span class="gmail_default" style="font-family:verdana,sans-serif"> and the related purposes</span> will not lead to the expansion of registration data elements. This is not a satisfactory response. we would like to register our concern and warn the ICANN community and domain name registrants that registration data elements might be expanded and include even more sensitive data, due to this addition, that can be disclosed to third parties. </span></div><div><span style="color:black;font-family:Calibri,sans-serif;font-size:12pt"><span class="gmail_default" style="font-family:verdana,sans-serif"><br></span></span></div><div><span style="color:black;font-family:Calibri,sans-serif;font-size:12pt"><span class="gmail_default" style="font-family:verdana,sans-serif">3. Data protection should be provided for all domain name registrants globally regardless of their location. Discriminatory treatment of domain name registrants globally is not justified, especially as we are moving towards disclosing domain name registrants data to third parties "globally".</span></span></div><div><span style="color:black;font-family:Calibri,sans-serif;font-size:12pt"><span class="gmail_default" style="font-family:verdana,sans-serif"><br></span></span></div><div><div class="gmail_default" style="font-family:verdana,sans-serif">--- </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">This is for now. I will send some more thoughts later.</div><br></div><div><span style="color:black;font-family:Calibri,sans-serif;font-size:12pt"><span class="gmail_default" style="font-family:verdana,sans-serif"><br></span></span></div><div><span style="color:black;font-family:Calibri,sans-serif;font-size:12pt"><span class="gmail_default" style="font-family:verdana,sans-serif"><br></span></span></div><div><span style="color:black;font-family:Calibri,sans-serif;font-size:12pt"><span class="gmail_default" style="font-family:verdana,sans-serif"><br></span></span></div></div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Feb 12, 2019 at 5:19 PM Elsa S <<a href="mailto:elsa.saade@gmail.com" target="_blank">elsa.saade@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto">I know that everyone in the team is extremely swamped, but for the sake of best representation, would the NCSG EPDP team perhaps be able to send us their thoughts prior to the Thursday meeting?</div></div><div dir="auto"><br></div><div dir="auto">I’ve personally been following the mailing list and developments, however, my position should also take into account the thoughts of the EPDP team members IMHO.</div><div dir="auto"><br></div><div dir="auto">Thanks again Rafik,</div><div dir="auto"><br></div><div dir="auto">Elsa</div><div dir="auto">—</div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Feb 12, 2019 at 4: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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div>Hi,<div dir="auto"><br></div>Yes there is council meeting in 14th Feb but the vote will be in meeting of 21st Feb which is more important. Scheduling the NCSG call was a timing issue and Friday is least worse option.</div><div dir="auto"><br></div><div dir="auto">I think the agendas of the 2 council meetings indicates the topics and material. For EPDP, it is the final report. For IGO-INGO, the material are the same like for the previous calls.</div><div dir="auto"><br></div><div dir="auto">Best,</div><div dir="auto"><br></div><div dir="auto">Rafik </div></div><div dir="auto"><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote" dir="auto"><div dir="ltr">On Wed, Feb 13, 2019, 06:01 Elsa S <<a href="mailto:elsa.saade@gmail.com" target="_blank">elsa.saade@gmail.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto">Hi Rafik,</div></div><div dir="auto"><br></div><div dir="auto">Thanks for organizing this! I look forward to the calls. Just a question though, isn’t the placeholder council EPDP meeting this Thursday 14th?</div><div dir="auto"><br></div><div dir="auto">And if there’s certain material that we need to keep an eye out for more than others, it would be great to highlight them so that our conversation would be more constructive and efficient.</div><div dir="auto"><br></div><div dir="auto">E.</div><div dir="auto">—</div><div><br><div class="gmail_quote"><div dir="ltr">On Mon, Feb 11, 2019 at 9:13 PM Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" rel="noreferrer" target="_blank">rafik.dammak@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi all,</div><div dir="ltr"><br></div><div>with regard to calls, I suggest:</div><div>1- A call on Friday this week as update on EPDP and getting sense of NCSG positions on the recommendations (we might need to vote recommendation by recommendation based on level of consensus )<br>2- A call next week Monday for NCSG Policy call as usual. The council agenda for next week call is mainly about EPDP</div><div>so I expect we will cover mainly EPDP during the 2 calls.</div><div><br></div><div>the 2 calls will be 90min each to no put more burden.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik</div></div><div dir="ltr"><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le jeu. 7 févr. 2019 à 23:49, Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com" rel="noreferrer" target="_blank">rafik.dammak@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello,<div><br></div><div>as we are having 2 GNSO Council meetings and the delivery of final report for EPDP to decide on, I would like to propose:</div><div><ul><li>1 call for EPDP update only next week, not necessarily before the extraordinary meeting (we are not voting there ). that will helps us for any position on consensus designation, voting at council level and giving any relevant update.<br></li><li>1 call for the usual NCSG Policy call. I will suggest some dates/times as I will be traveling in the week of 18th Feb.</li></ul></div><div>Another approach is just to have 1 call instead, maybe longer (2h30 with allocating more time for EPDP update e.g.60 or 90min) next week.</div><div><br></div><div>Best,</div><div><br></div><div>Rafik</div></div>
</blockquote></div></div>
_______________________________________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is" rel="noreferrer" target="_blank">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail-m_1818772888166455281m_8200213494635633951gmail-m_-5191273043398708930gmail-m_1122424580152080551gmail-m_-2011027838392794560m_-7998915746055125033m_-8564673428341647189m_-8476295107166076897gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">--<br><br>Elsa Saade<br>Consultant</div></div><div>Gulf Centre for Human Rights</div><div>Twitter: @Elsa_Saade</div></div></div></div></div>
</blockquote></div></div></div>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail-m_1818772888166455281m_8200213494635633951gmail-m_-5191273043398708930gmail-m_1122424580152080551gmail-m_-2011027838392794560m_-7998915746055125033gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">--<br><br>Elsa Saade<br>Consultant</div></div><div>Gulf Centre for Human Rights</div><div>Twitter: @Elsa_Saade</div></div></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></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></div>
</blockquote></div>