<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div>Hi Rafik, everyone<br>
thanks much for getting the ball rolling on this. </div>
<div id="AppleMailSignature">I would be happy to help Kathy and Ayden if so desired. Folks fan get in touch off list to discuss process and timeline. March 1st in particular is around the corner. Best, Stefi<br>
Sent from my iPhone</div>
<div><br>
On Feb 23, 2017, at 02:45, Ayden Férdeline <<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>Thanks, Rafik. I would be pleased to take the lead drafting our comments on the initial report of the At-Large Review. I think we need to be careful here, people in glass houses and stones and all that... I am tempted to suggest we limit the focus of our
comments only to the inaccurate comparisons drawn between the NCUC, NCSG, and ALAC. We should also put forward our opposition to an advisory committee taking on more influence in the policy sphere, particularly with their obscene levels of staff support, as
that is a direct threat to our legitimacy and the legitimacy of the GNSO. I don't think we should comment on the rest of the report; surely At-Large is best placed to produce a response which addresses some of the methodological issues within it. And if not,
that is to their detriment.<br>
</div>
<div><br>
</div>
<div class="protonmail_signature_block ">
<div class="protonmail_signature_block-user ">
<div>- Ayden <br>
</div>
</div>
<div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br>
</div>
</div>
<div><br>
</div>
<blockquote class="protonmail_quote" type="cite">
<div>-------- Original Message --------<br>
</div>
<div>Subject: [NCSG-PC] Open Public comments<br>
</div>
<div>Local Time: 23 February 2017 12:25 AM<br>
</div>
<div>UTC Time: 23 February 2017 00:25<br>
</div>
<div>From: <a href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a><br>
</div>
<div>To: ncsg-pc <<a href="mailto:ncsg-pc@lists.ncsg.is">ncsg-pc@lists.ncsg.is</a>><br>
</div>
<div><br>
</div>
<div dir="ltr">
<div>Hi everyone,<br>
</div>
<div><br>
</div>
<div>From the Public Comments page, I picked the 3 consultations that seem relevant for us and we had some discussion about. this is kind of planning for us to cover public comments:<br>
</div>
<ol>
<li>GNSO Initial Report on the IGO-INGO Access to Curative Rights Protection Mechanisms Policy Development Process, <a href="https://www.icann.org/public-comments/igo-ingo" rel="noreferrer nofollow noopener">https://www.icann.<wbr>org/public-comments/igo-ingo</a>
, deadline <b>1 Mar 2017 </b><br>
</li><li>At-Large Review: Draft Report, <a href="https://www.icann.org/public-comments/atlarge-review-draft-report-2017-02-01-en" rel="noreferrer nofollow noopener">https://www.icann.org/public-<wbr>comments/atlarge-review-draft-<wbr>report-2017-02-01-en</a>, deadline
<b>24 Mar 2017 </b><br>
</li><li>Recommendations to Improve ICANN's Transparency, <a href="https://www.icann.org/public-comments/ccwg-acct-draft-recs-2017-02-21-en" rel="noreferrer nofollow noopener">
https://www.icann.org/public-<wbr>comments/ccwg-acct-draft-recs-<wbr>2017-02-21-en</a> , deadline
<b>10 Apr 2017 </b><br>
</li></ol>
<div>the first consultation is quite close, less than 1 week and the topic is important for us. We have an urgent need to get a volunteer to draft a quick comment. I am wondering if Kathy can jump in here. In any case, as PC we will have to act quickly if we
get a statement to review.<br>
</div>
<div><br>
</div>
<div>for at-large review, I would like to volunteer Ayden since he followed the discussion closely and read the report. @Ayden can you please start drafting and share the document with the wider NCSG list for consultation?<br>
</div>
<div><br>
</div>
<div>for the last one, related to ICANN accountability work, it will be great to have someone involved in the CCWG to take the lead here. Maybe Matthew? <br>
</div>
<div><br>
</div>
<div>while I am suggesting names among those in PC List, we can try to find other members take the lead or help.<br>
</div>
<div><br>
</div>
<div>in term of planning for future public comments, we can follow upcoming consultations here <a href="https://www.icann.org/resources/pages/upcoming-2012-02-25-en" rel="noreferrer nofollow noopener">https://www.icann.org/resources/pages/upcoming-2012-02-25-en</a>
to get an idea about what is coming (dates are of course tentative).<br>
</div>
<div><br>
</div>
<div>there is also this separate page about "operational" public comments <a href="https://www.icann.org/public-comments-operational" rel="noreferrer nofollow noopener">https://www.icann.org/public-comments-operational</a> , something to follow more closely.<br>
</div>
<div><br>
</div>
<div>Best,<br>
</div>
<div><br>
</div>
<div>Rafik<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</blockquote>
<div><br>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>NCSG-PC mailing list</span><br>
<span><a href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a></span><br>
<span><a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a></span><br>
</div>
</blockquote>
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 14">
<meta name="Originator" content="Microsoft Word 14">
<link rel="File-List" href="eui%20footer_files/filelist.xml"><link rel="themeData" href="eui%20footer_files/themedata.thmx"><link rel="colorSchemeMapping" href="eui%20footer_files/colorschememapping.xml"><style> <!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-520092929 1073786111 9 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} --> </style><style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} </style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:8.0pt;color:#595959"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;color:#595959">The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination,
distribution, forwarding, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited without the express permission of the sender. If you received this communication in
error, please contact the sender and delete the material from any computer. <o:p>
</o:p></span></p>
</div>
</body>
</html>