<div dir="auto">I feel this email will do us some good. Essentially, our members in ALAC, so that the general interest of the entire community is put first and not that of ALAC.<div dir="auto">Thank you. </div><div dir="auto">Pastor Peters Omoragbon </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Roberto Gaetano</strong> <span dir="auto"><<a href="mailto:roberto_gaetano@hotmail.com">roberto_gaetano@hotmail.com</a>></span><br>Date: Wed, 11 Nov 2020, 10:16<br>Subject: Re: [ALS-Mob-WP] Proposed Bylaw changes<br>To: Peters Omoragbon <<a href="mailto:petersomoragbon@gmail.com">petersomoragbon@gmail.com</a>><br>Cc: Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>>, Nadira Alaraj <<a href="mailto:nadira.araj@gmail.com">nadira.araj@gmail.com</a>>, ALS-Mob-WP <<a href="mailto:als-mob-wp@icann.org">als-mob-wp@icann.org</a>><br></div><br><br>
<div style="word-wrap:break-word;line-break:after-white-space">
Pastor Peters makes some good points, but I have a different opinion about the process.
<div><br>
</div>
<div>If I understood correctly, the ALS-Mob-WP was tasked by ALAC to produce a set of recommendations. For doing so, it has been populated with resources coming from each RALO. The WP finished its job - or, according to Pastor Peters, this phase of
the job - and is presenting the result to ALAC. I believe that we all agree on this.</div>
<div><br>
</div>
<div>Where we differ is on the follow up. I believe that ALAC can do many different things: can accept the recommendations and thank the WP for its work, can reject the recommendation and decide to move in a different direction, can evaluate the document
and ask the WP to reconvene for further work, or even other things. But in my opinion the next step is a decision by ALAC: it is ALAC that has to determine whether the work done is complete, whether all parties have been given the chance to express their opinion
(which, incidentally, does not mean that their opinion has to be accepted if it ends up in being a minority opinion), whether the recommendations are within the given mandate, or else.</div>
<div><br>
</div>
<div>So, the practical outcome could well be that the community takes more time to review the recommendation - better to be late than to be wrong in matters that affect the basic rules - but this is a decision that ALAC has to make. I believe that
after these two presentations the matter is out of the hands of the WP and in the capable hands of ALAC. If ALAC decides to task this WP - or a new one - with the job of going through another cycle of consultations, this is what will be done. But this is only
one of the many alternatives for ALAC to decide from.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Roberto</div>
<div><br>
</div>
<div>
<div><br>
<blockquote type="cite">
<div>On 11.11.2020, at 09:52, Peters Omoragbon <<a href="mailto:petersomoragbon@gmail.com" target="_blank" rel="noreferrer">petersomoragbon@gmail.com</a>> wrote:</div>
<br>
<div>
<div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
Hello Nadira. <br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
That was the point I was drawing at. <br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
Now yesterday call if I get Alan correctly is for ALAC to accept or otherwise any proposal or observations made because the work of the WP was over or completed. Which should not be. Our work would be completed after the community AND RALOs have made their
inputs and proposals for inclusion. Then we develop a cleaner document representing every interest. The motion that ALAC set up the WP and such the report is for them to consider is true but after every interest have been represented. The argument that each
RALO was represented in the WP is not absolute because, after the work, now is the time for each RALO to geberally look at the document and not take any decision taken by the WP as final.
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
It is after inputs have been collated and added that our report goes to ALAC. I made this point during our calls. I wrote it as a petition. I was ignored.
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
Secondly Sebastian made a good proposal yesterday that the community needs time to properly review the document in line with extant practice in icann. And so, these two hours call is doing deservice to that practice.
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
ALAC should not be in a hurry to adopt this document and send to the board to adopt.
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
If the board and ALAC believes in the principle of multistakeholderism from bottom up and not the other way, then, the community needs time. It is not the 2wks proposal by Maureen last night. We are not in a hurry. This document will have a far reaching implications
at the end on the future of icann and the community. <br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
It was also premature for Alan to have sent the draft to the legal team before the community input even without the knowledge of the WP.
<br>
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
Thank you. <br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt;text-align:left">
Pastor Peters Omoragbon <br>
<br>
</div>
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
<span id="m_3214931112520456483OutlookSignature">
<div dir="auto" style="direction:ltr;margin:0px;padding:0px;font-family:sans-serif;font-size:11pt">
Get <a href="https://aka.ms/ghei36" target="_blank" rel="noreferrer">Outlook for Android</a></div>
</span><br>
</div>
<hr style="display:inline-block;width:98%">
<div id="m_3214931112520456483divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt"><b>From:</b> ALS-Mob-WP <<a href="mailto:als-mob-wp-bounces@icann.org" target="_blank" rel="noreferrer">als-mob-wp-bounces@icann.org</a>> on behalf of Nadira Alaraj
<<a href="mailto:nadira.araj@gmail.com" target="_blank" rel="noreferrer">nadira.araj@gmail.com</a>><br>
<b>Sent:</b> Tuesday, November 10, 2020 11:01:35 PM<br>
<b>To:</b> Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank" rel="noreferrer">alan.greenberg@mcgill.ca</a>><br>
<b>Cc:</b> ALS-Mob-WP <<a href="mailto:als-mob-wp@icann.org" target="_blank" rel="noreferrer">als-mob-wp@icann.org</a>><br>
<b>Subject:</b> Re: [ALS-Mob-WP] Proposed Bylaw changes</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
Dear Alan,</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
Thank you for our excellent presentation and leading the discussions for the meeting. </div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
I would like to ask what would be the next step to reflect some of the comments received from the community. </div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
Jean raised a good point to be consistent in the process of the accreditation and the withdrawal of the accreditation. </div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
<br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
Would be good to have in writing the comments on the suggested WP change of the bylaws. Because I couldn't follow the discussion. I hope those who shared these points will raise them on the mailing list. </div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
<br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
Best wishes,</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
Nadira</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
<br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
<br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
<br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
<br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:small">
<br>
</div>
</div>
<br>
<div>
<div dir="ltr">On Tue, Nov 10, 2020 at 5:41 AM Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank" rel="noreferrer">alan.greenberg@mcgill.ca</a>> wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
You may recall that we were going to have the proposed Bylaw changes <br>
reviewed by the Office of the General Counsel to make sure they sis <br>
not see any conflicts or other problems.<br>
<br>
That has now been done and there have been no red flags raised.<br>
<br>
So one more step is done.<br>
<br>
Note that two Webinars on the report have been scheduled:<br>
<br>
- Tue, 10 Nov 202 at 20:00 UTC (about 16 hours from now)<br>
<br>
- Thu, 12 Nov 202 at 13:00 UTC<br>
<br>
Your participation in either or both would be welcome.<br>
<br>
Alan<br>
<br>
_______________________________________________<br>
ALS-Mob-WP mailing list<br>
<a href="mailto:ALS-Mob-WP@icann.org" target="_blank" rel="noreferrer">ALS-Mob-WP@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/als-mob-wp" rel="noreferrer noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/als-mob-wp</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 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.<br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<div style="margin:0in 0in 0pt"><br>
</div>
<p style="margin:0in 0in 0pt"><font face="Calibri"></font> </p>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
ALS-Mob-WP mailing list<br>
<a href="mailto:ALS-Mob-WP@icann.org" target="_blank" rel="noreferrer">ALS-Mob-WP@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/als-mob-wp" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/als-mob-wp</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" 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.</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>