<div dir="ltr">Hi all<div>As far as I understood from our meeting with Rob at the intersessional, these comments aren't binding. So I would second Farzaneh in going step by step and see how we can answer this.</div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-02-18 14:34 GMT-05:00 farzaneh badii <span dir="ltr"><<a href="mailto:farzaneh.badii@gmail.com" target="_blank">farzaneh.badii@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">The process is ICANN staff review and make suggestions. We dont even have to consider these suggestions. But it's better to understand them and give a reason why we do not accept some of the comments. As to the nature of suggestions, there is not much of a mandate . They just provide comments including editorial and substative. I suggest doing this:we see which editorial suggestions we can accept, we point out to the comments that we cannot accept and we give our reasons why. Then we have a meeting with staff and tell them. Then send to Board. Remember that this will go to board. It makes it much easier when we provide reason why we don't accept the staff suggestions. <div dir="auto"><br></div><div dir="auto">There is an alternative which is a bit extreme. We can just adopt the bylaws. Board will look at them though and might tell us not to adopt before changing it. But I don't feel extreme today. </div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 18 Feb 2017 13:19, "Tatiana Tropina" <<a href="mailto:tatiana.tropina@gmail.com" target="_blank">tatiana.tropina@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Farzaneh and all.<div>I don't think we should agree to get the meeting where the comments are "explained" to us. While am in general very cooperative, I think accepting the offer to "explain" why someone would unilaterally rewrite our mission and the membership rules is already too much. We have to send it back with the note that the staff was supposed to do copy-editing of the text for the purpose of consistency, not rewriting the provisions that constituency came up with.</div><div>Farzy and I are involved in the AC/SO accountability WS2 and I was working on membership data capture there. Yes!!! - other constituencies (BC, IPC) <b>do</b> <b>have</b> membership, eligibility criteria and process of becoming a member. Another argument why we shall not accept the document and just send it back with a polite note that ICANN consultant overstepped the mandate with regard to what can be edited. </div><div>Warm regards</div><div>Tanya </div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 18 February 2017 at 04:37, farzaneh badii <span dir="ltr"><<a href="mailto:farzaneh.badii@gmail.com" target="_blank">farzaneh.badii@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">EC, </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Please find attached ICANN staff comments on NCUC bylaws. I will arrange a meeting with Rob and staff but before doing that we need to go through the comments. We can do that within two weeks and then have a meeting with him and staff to explain the comments to us. Then we will discuss with Rob and staff and then discuss with our members, finalize and ask Rob to send it to Board.</div><span class="m_-8019546143439599552m_911315402518393756HOEnZb"><font color="#888888"><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div><div class="m_-8019546143439599552m_911315402518393756m_9119696556438840596gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font face="verdana, sans-serif">Farzaneh </font></div></div></div></div>
</font></span></div>
<br>______________________________<wbr>_________________<br>
NCUC-EC mailing list<br>
<a href="mailto:NCUC-EC@lists.ncuc.org" target="_blank">NCUC-EC@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" rel="noreferrer" target="_blank">http://lists.ncuc.org/cgi-bin/<wbr>mailman/listinfo/ncuc-ec</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div>
</div></div><br>______________________________<wbr>_________________<br>
NCUC-EC mailing list<br>
<a href="mailto:NCUC-EC@lists.ncuc.org">NCUC-EC@lists.ncuc.org</a><br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" rel="noreferrer" target="_blank">http://lists.ncuc.org/cgi-bin/<wbr>mailman/listinfo/ncuc-ec</a><br>
<br></blockquote></div><br></div>