<div dir="ltr">+1 from me as well.<br><div><br></div><div>Regards,</div><div>Gaurav</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 24, 2019 at 4:48 PM James Gannon <<a href="mailto:james@cyberinvasion.net">james@cyberinvasion.net</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 lang="EN-US">
<div class="gmail-m_9051162702821266421WordSection1">
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">This has my support thanks Byron.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">-James<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><u></u> <u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">ICANN-CSC <<a href="mailto:icann-csc-bounces@icann.org" target="_blank">icann-csc-bounces@icann.org</a>> on behalf of Byron Holland <<a href="mailto:byron.holland@cira.ca" target="_blank">byron.holland@cira.ca</a>><br>
<b>Date: </b>Tuesday, 24 September 2019 at 16:46<br>
<b>To: </b>"<a href="mailto:ICANN-CSC@icann.org" target="_blank">ICANN-CSC@icann.org</a>" <<a href="mailto:ICANN-CSC@icann.org" target="_blank">ICANN-CSC@icann.org</a>><br>
<b>Subject: </b>[ICANN-CSC] CSC Quorate Rule Amendment<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Calibri,sans-serif">Dear colleagues,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Calibri,sans-serif">As you will recall, I committed to drafting some suggested text for our internal procedure to capture our discussion with respect to the need to ensure the basic business of
the CSC could continue in the event one or more seats of the four (4) members are vacant.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Calibri,sans-serif">After looking at the procedures again: I suggest that we amend section 5.2 ( the quorum) rule to:</span><u></u><u></u></p>
<p class="gmail-m_9051162702821266421MsoBodyText" style="margin-right:0cm;margin-left:36pt;margin-bottom:0.0001pt">
<span style="font-size:10pt;font-family:Arial,sans-serif;color:black">A CSC meeting shall be quorate if the 4 (four) Members are present at the meeting.<span class="gmail-m_9051162702821266421apple-converted-space"> </span><b><u>In the exceptional circumstance where there are one
or more vacancies in the Members, the CSC meeting shall be quorate if all appointed Members are present.
</u></b>The notes will state if the meeting was quorate, or, if only quorate for a part of the meeting, state which items of business were discussed when quorate. This internal rule will be reviewed in conjunction with the first review of the CSC charter.</span><u></u><u></u></p>
<p class="MsoNormal" style="text-align:start;word-spacing:0px">
<span style="font-size:14pt;font-family:Calibri,sans-serif">In addition, and to capture the limitation in the power to take decisions, I also suggest to amend section 6.1 ( decision-making at meetings) and 6.2 decision-making by email by adding the following
line:</span><u></u><u></u></p>
<p class="MsoNormal"><b><u><span lang="EN-GB" style="font-family:"Calibri Light",sans-serif;color:black">In the exceptional circumstance where there are one or more vacancies in the Members, the decision-making of the CSC shall be limited to and not go beyond
the approval of the CSC’s monthly report.</span></u></b><b><span lang="EN-GB" style="font-family:"Calibri Light",sans-serif">
</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Calibri,sans-serif">For your reference I have include a redline version of the Internal procedure.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Calibri,sans-serif">If there are no objections by the other members by 28 September 23.59 UTC, I will consider the proposed changes adopted,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Calibri,sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Calibri,sans-serif">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:14pt;font-family:Calibri,sans-serif">Byron</span><u></u><u></u></p>
</div>
</div>
_______________________________________________<br>
ICANN-CSC mailing list<br>
<a href="mailto:ICANN-CSC@icann.org" target="_blank">ICANN-CSC@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/icann-csc" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/icann-csc</a><br>
<br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" target="_blank">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Regards,<br>Gaurav Vedi</div>