<div dir="auto">Thanks for the clarification Maureen <div dir="auto"><br><div dir="auto">As Dave mentioned, it was a discussion that came up during AFRALO monthly meeting and we invited Alan towards the end of the call(thanks to Alan for joining on short notice) who provided some clarifications which is in sync with what you've stated as well.<br><br><span style="font-family:sans-serif">It's good to know that there will be an opportunity in future to consider the text that finally becomes part of the proposed bylaw changes.</span></div><div dir="auto"><font face="sans-serif"><br></font></div><div dir="auto"><font face="sans-serif">Regards<br></font><div data-smartmail="gmail_signature" dir="auto">Sent from my mobile<br>Kindly excuse brevity and typos</div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 3 Dec 2020, 18:54 Maureen Hilyard, <<a href="mailto:maureen.hilyard@gmail.com">maureen.hilyard@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">HI Dave<div><br></div><div>Just if I may add a comment here with regards to this paragraph.</div><div><br></div><div>As I have indicated before, the removal of the actual bylaw discussions is something that was agreed upon because we did not want to hold the report back from being presented as a report endorsed by the ALAC for any further work required (in this case by Legal).</div><div><br></div><div>However, to remove this particular paragraph would mean that we are dismissing any reference to all the discussions the WP had about any possible changes that might be required in the Bylaws. When these are requested for further higher level discussions by ICANN Legal, because they have been alluded to here, then Alan will be able to resurrect them again.</div><div><br></div><div>But I really think that this reference to proposed Bylaw Changes should remain, to remind the WP of the other discussions that took place and how they will be dealt with in the future - not something that we decide on at this stage.</div><div><br></div><div>But thank you for bringing your RALO's concerns to the wider community.</div><div><br></div><div>Regards</div><div>Maureen</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Dec 3, 2020 at 7:34 AM Dave Kissoondoyal <<a href="mailto:dave@igf-mu.org" target="_blank" rel="noreferrer">dave@igf-mu.org</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>
<p><font face="Calibri">Dear Alan,</font></p>
<p><font face="Calibri">I want to thank you and all the members of
the ALS Mobilization Working Party team for the number of hours
devoted to come with a comprehensive report. I want to thank you
also to listen to the voice of the community and bring the
appropriate changes to the report.<br>
</font></p>
<p><font face="Calibri">I have already voted for the approval of the
report and I have voted with a YES. However following the
discussions we had in the AFRALO monthly meeting and after
careful consideration of the points raised by members, I would
humbly ask the following paragraph be removed from the ALS
Mobilization Working Party Final Report :</font></p>
<font face="Calibri"> </font>
<p><font face="Calibri"><b>Proposed Bylaw Changes <br>
</b><font color="#002E7A">In the course of carrying out its
work, the WP identified a number of places where the Bylaws
should be modified either to align them with the current
embodiment of At-Large or to address changes in these
recommendations. <br>
The proposed changes are still under discussion with the
Office of the General Counsel and will be proposed to the ALAC
at a later time. None of the recommendations in this report
depend on the Bylaw change proposals.</font></font></p>
<p><font face="Calibri">As there is agreement that the bylaw changes
are excluded from the report, it makes sense to remove the above
paragraph from same.</font></p>
<p><font face="Calibri">Let us tackle the changes of the bylaws as
already defined by <span style="color:rgb(77,81,86);font-family:arial,sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:left;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><font face="Calibri">Section 25 of the</font><span><em><font face="Calibri"> </font></em><font face="Calibri">bylaws.</font><em><br>
</em></span></span></font></p>
<p><font face="Calibri">Thanks and kind regards</font></p>
<p><font face="Calibri">Dave Kissoondoyal</font></p>
<p><font face="Calibri"><br>
</font></p>
<div>On 03/12/2020 06:46, Alan Greenberg
wrote:<br>
</div>
<blockquote type="cite">
Thanks for the comment Tijani,<br>
<br>
To be clear, the proposed Bylaw changes that were in the earlier
version
were issues discovered while the ALS-Mob-WP performed their duties
of
reviewing all of the documents. However, none of the issues
discovered
(an error in the intro paragraph of the ALAC section of the
Bylaws, the
confusing use of "certify" and "accredit" and the
problem of the Bylaw still referring to individual members as an
option)
were actually related to the recommendation that the WP was making
related to ALSes.<br>
<br>
So nothing is harmed by delaying discussion of that section. And
it is
important to approve the ALS-related recommendation so that we can
report
to the Board that it is done (a report is required no later than
the end
of December) and of course start the work of implementation.<br>
<br>
Referring to the Office of the General Counsel is simply a
mechanism to
ensure that there will not be any surprises down the road. There
has been
abundant time for people to comment on the proposals, and short of
your
comment that was based on an incorrect report version being
posted, there
have been NO negative comments on the intent of what was being
proposed.
Lastly, I note that it is typical in ICANN to have the legal team
do the
actual drafting of Bylaws so clearly they see them before the
group
concerned. Ultimately, the request to the Board to amend the
Bylaws will
have to come from the ALAC and that will ensure full support.<br>
<br>
Alan<br>
<br>
<br>
At 2020-12-02 06:06 AM, Tijani BEN JEMAA wrote:<br>
<blockquote type="cite"><font color="#002E7A">Good
morning,</font><br>
<font color="#002E7A"><br>
I see that the ALAC is asked to ratify the ALS Mobilization WP
final
report that contains the following:<br>
</font><b>Proposed Bylaw Changes <br>
</b><font color="#002E7A">In the course of carrying out its
work, the WP
identified a number of places where the Bylaws should be
modified either
to align them with the current embodiment of At-Large or to
address
changes in these recommendations. <br>
The proposed changes are still under discussion with the
Office of the
General Counsel and will be proposed to the ALAC at a later
time. None of
the recommendations in this report depend on the Bylaw change
proposals.<br>
<br>
Perhaps it’s more appropriate to wait and have the the whole
report
(with the proposed bylaw changes) submitted to the ALAC for
ratification.<br>
</font><br>
<font color="#002E7A">As I said before, in my opinion, the
office of the
general counsel shouldn’t be consulted about changes that
the ALAC
didn’t already approve.<br>
<br>
My 2 cents.<br>
<br>
</font><br>
<blockquote type="cite">Le 2 déc. 2020 Ã
00:58,
ICANN At-Large Staff
<<a href="mailto:noreply-116500@bigpulse.com" target="_blank" rel="noreferrer">
noreply-116500@bigpulse.com</a>> a écrit :<br>
<br>
Dear All, <br>
<br>
The ALAC has been asked the following question:<br>
<br>
Do you support the ratification of the ALS Mobilization
Working Party
Final Report (v 28 November 2020)? Please view the report
<a href="https://community.icann.org/download/attachments/120821482/ALS-Mob-WP-Report-Final-Revised-Clean.pdf" target="_blank" rel="noreferrer">
here</a>.<br>
<br>
Please note that the ALAC ratification vote will <u>close on</u>
<u>Friday, 04 December 23:59 UTC</u>.<br>
<br>
Kind Regards,<br>
<br>
ICANN Policy Staff in support of the At-Large Community<br>
Website:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge.icann.org_&d=DwMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=HedNXfBayuWxdPer7COiCJBd39KxvJQIgCaiDYF2Tm8&m=c45nfg-BhYDRy-UcbtBoRVo6esDVHm47FnrsaYKHqtI&s=uurR7PGdO1th90fafDVxz94_ZUjZVU6s9HMAuC4mTfc&e=" target="_blank" rel="noreferrer">
atlarge.icann.org</a> <br>
Facebook:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_icannatlarge&d=DwMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=HedNXfBayuWxdPer7COiCJBd39KxvJQIgCaiDYF2Tm8&m=c45nfg-BhYDRy-UcbtBoRVo6esDVHm47FnrsaYKHqtI&s=P5Em8y3Lku13nXudSAePkzgYSTAVnF4Ojv_R9Do8gDQ&e=" target="_blank" rel="noreferrer">
facebook.com/icannatlarge</a><br>
Twitter:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANNAtLarge&d=DwMDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=HedNXfBayuWxdPer7COiCJBd39KxvJQIgCaiDYF2Tm8&m=c45nfg-BhYDRy-UcbtBoRVo6esDVHm47FnrsaYKHqtI&s=1cykVgdsql92ysT5A6AIisXzOOPxNd5zRpXhv7K_tsw&e=" target="_blank" rel="noreferrer">
@ICANNAtLarge</a><br>
_______________________________________________<br>
ALAC-Announce mailing list<br>
<a href="mailto:ALAC-Announce@atlarge-lists.icann.org" target="_blank" rel="noreferrer">
ALAC-Announce@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac-announce" target="_blank" rel="noreferrer">
https://atlarge-lists.icann.org/mailman/listinfo/alac-announce</a><br>
<br>
At-Large Official Site:
<a href="http://www.atlarge.icann.org/" target="_blank" rel="noreferrer">http://www.atlarge.icann.org</a>
<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" target="_blank" rel="noreferrer">
https://www.icann.org/privacy/policy</a>) and the website
Terms of
Service
(<a href="https://www.icann.org/privacy/tos" target="_blank" rel="noreferrer">
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>
<br>
Tijani BEN JEMAA<br>
<br>
<br>
<br>
_______________________________________________<br>
At-Large mailing list<br>
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank" rel="noreferrer">At-Large@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" target="_blank" rel="noreferrer">
https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br>
<br>
At-Large Official Site:
<a href="http://atlarge.icann.org/" target="_blank" rel="noreferrer">
http://atlarge.icann.org</a><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" target="_blank" rel="noreferrer">
https://www.icann.org/privacy/policy</a>) and the website
Terms of
Service
(<a href="https://www.icann.org/privacy/tos" target="_blank" rel="noreferrer">
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>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
At-Large mailing list
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank" rel="noreferrer">At-Large@atlarge-lists.icann.org</a>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" target="_blank" rel="noreferrer">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a>
At-Large Official Site: <a href="http://atlarge.icann.org" target="_blank" rel="noreferrer">http://atlarge.icann.org</a>
_______________________________________________
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" target="_blank" rel="noreferrer">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank" rel="noreferrer">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.</pre>
</blockquote>
</div>
_______________________________________________<br>
At-Large mailing list<br>
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank" rel="noreferrer">At-Large@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" rel="noreferrer noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br>
<br>
At-Large Official Site: <a href="http://atlarge.icann.org" rel="noreferrer noreferrer" target="_blank">http://atlarge.icann.org</a><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 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 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>
At-Large mailing list<br>
<a href="mailto:At-Large@atlarge-lists.icann.org" target="_blank" rel="noreferrer">At-Large@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/at-large" rel="noreferrer noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/at-large</a><br>
<br>
At-Large Official Site: <a href="http://atlarge.icann.org" rel="noreferrer noreferrer" target="_blank">http://atlarge.icann.org</a><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 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 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>