<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="HTML Tidy for Windows (vers 25 March 2009), see www.w3.org">
<title></title>
</head>
<body>
I read this as referring to GNSO resolutions and would have no direct impact on anything IPC chose to say. Is that correct?<br>
<br>
<br>
<br>
Sent with Good (www.good.com)<br>
<br>
<br>
-----Original Message-----<br>
<b>From: </b>Greg Shatan [<a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a>]<br>
<b>Sent: </b>Monday, October 19, 2015 02:35 AM Pacific Standard Time<br>
<b>To: </b>McGrady, Paul D.<br>
<b>Cc: </b>IPC-GNSO (ipc-gnso@icann.org)<br>
<b>Subject: </b>Re: [IPC-GNSO] [IPC Discussion List] Fwd: [council] possible motion - would need to request 10 day waiver.<br>
<br>
<div dir="ltr">
<div class="gmail_default" style="font-family:verdana,sans-serif">I certainly think so. I applaud Avri and the NCSG for taking the initiative on this effort. We can discuss today when we meet to see if there are any refinements to suggest.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Oct 19, 2015 at 10:28 AM, McGrady, Paul D. <span dir="ltr">
<<a href="mailto:PMcGrady@winston.com" target="_blank">PMcGrady@winston.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">So, if we don’t think this is a problem, should we use the opportunity to play nice with the NCSG and affirmatively through our support behind it? Brian, Heather,
what think ye?</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b>
<span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Greg Shatan [mailto:<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>]<br>
<b>Sent:</b> Monday, October 19, 2015 4:11 AM<br>
<b>To:</b> McGrady, Paul D.<br>
<b>Cc:</b> IPC-GNSO (<a href="mailto:ipc-gnso@icann.org" target="_blank">ipc-gnso@icann.org</a>)<br>
<b>Subject:</b> [IPC Discussion List] Fwd: [council] possible motion - would need to request 10 day waiver.</span></p>
<div>
<div class="h5">
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I think the potentially muzzling issue is the last part of the Resolved section (in bold), but it only relates to declaring support or opposition to outcomes, not general statements, which
is all CSG would do, so 8'm not concerned.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""> </span></p>
</div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"Arial","sans-serif""><br>
The GNSO reiterates its support for the process that is ongoing in<br>
CCWG-Accountability,<br>
<br>
its commitment to participating in continuing discussions with the goal<br>
of finding solution with broad agreement for ICANN accountabity in<br>
preparations for IANA transition, and<br>
<br>
to <b>working through the process as agreed upon in the charter before<br>
making any resolutions declaring support or opposition to possible outcomes.</b></span></p>
</blockquote>
</div>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On Mon, Oct 19, 2015 at 9:25 AM, McGrady, Paul D. <<a>PMcGrady@winston.com</a>> wrote:</p>
<p class="MsoNormal">All, please see below for last minute motion by the NCSG. A few questions:<br>
<br>
1. Does anyone read this as a muzzling of individual constituencies/SGs? I know that such was the fear but it isn't obvious to me that such is the case;<br>
2. Assuming "no" to the above question, are there any other concerns with this resolution?<br>
3. Assuming "yes" to the above question, should Heather or Brian reach out to Avri to get clarification that this isn't meant to interfere with speech from the constituencies/SG?<br>
<br>
Best,<br>
Paul<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a>owner-council@gnso.icann.org</a> [mailto:<a>owner-council@gnso.icann.org</a>] On Behalf Of Avri Doria<br>
Sent: Sunday, October 18, 2015 6:11 PM<br>
To: <<a>council@gnso.icann.org</a>><br>
Subject: [council] possible motion - would need to request 10 day waiver.<br>
<br>
<br>
To my fellow council members,<br>
<br>
I would like to offer one last motion before I end my tenure on the GNSO council.<br>
<br>
I know I have missed the motion deadline and therefore request consideration for waiver of the 10 day rule for motions, noting that this request is submitted at least 24 hours before the meeting scheduled for 21 October 2015.<br>
<br>
I also note that I am available to consider any friendly amendments that might be required for acceptance of the resolution that might come based on Stakeholder Group and Constituency consideration of this motion.<br>
<br>
--- Motion<br>
<br>
Whereas<br>
<br>
On 13 November 2014 the GNSO approved the charter for a Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountabilty);<br>
<br>
On 3 August the Public Comment on the CCWG-Accountability 2nd Draft Proposal was initiated, which ended on 12 Septemebr 2015;<br>
<br>
The CCWG-Accountabilty has analyzed the comments received in the review of the 2nd draft and is working toward updating its reference implementation taking into account the concerns expressed in those comments;<br>
<br>
and The CCWG-Accountabilty is working in a considered and collegial manner to achieve a consensus solution to ICANN Accountability;<br>
<br>
Acknowledging<br>
<br>
the superb and continuing leadership of CCWG-Accountabilty by the team which includes the GNSO appointed co-chair Thomas Rickert, to whom we are grateful for his time and consistent effort;<br>
<br>
<br>
Resolved<br>
<br>
The GNSO reiterates its support for the process that is ongoing in CCWG-Accountability,<br>
<br>
its commitment to participating in continuing discussions with the goal of finding solution with broad agreement for ICANN accountabity in preparations for IANA transition, and<br>
<br>
to working through the process as agreed upon in the charter before making any resolutions declaring support or opposition to possible outcomes.<br>
<br>
---<br>
<br>
thanks,<br>
<br>
avri<br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" target="_blank">https://www.avast.com/antivirus</a><br>
<br>
The contents of this message may be privileged and confidential. Therefore, if this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate
this message without the permission of the author.<br>
_______________________________________________<br>
IPC-GNSO mailing list<br>
<a>IPC-GNSO@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ipc-gnso" target="_blank">https://mm.icann.org/mailman/listinfo/ipc-gnso</a></p>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
<div>
<div class="h5"><br>
The contents of this message may be privileged and confidential. Therefore, if this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate
this message without the permission of the author.</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>