<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi All<div>Yes Alan paraphrased our discussion well. I think the idea of disclosure he was mentioning was in the form of an soi but this working group does not have that ability. But many of us were thinking it would be like it is in the GNSO where the subject of disclosure is talked about on each meeting as the first item. Ex. Does anyone have any changes to their soi. </div><div><br></div><div>We did nit deal at all with individual members as that is the subject of s different working group that Maureen will lead</div><div><br></div><div>Judith<br><div><br><div id="AppleMailSignature" dir="ltr">Sent from my iPhone<div><a href="mailto:Judith@jhellerstein.com">Judith@jhellerstein.com</a></div><div>Skype ID:Judithhellerstein </div></div><div dir="ltr"><br>On Apr 20, 2020, at 3:00 AM, Justine Chew <<a href="mailto:justine.chew.icann@gmail.com">justine.chew.icann@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div dir="ltr">I believe the recommendations of the WP as Alan has posited are correct.<br><br>With respect to "
<span style="color:rgb(0,0,255)">There is no prohibition on an ALS Representative holding roles in other parts of ICANN (non-At-Large), but those roles comparable to those listed below must be formally declared.</span> ", I was hoping that Alan could remind us if there were any WP indications as to (i) how (eg. existing At-Large SOI) and (ii) to whom (i.e. both within At-Large and outside of the At-Large), such a mechanism for formal declaration might be implemented. <br><br>I agree with Jonathan that the question of reciprocity raised by Evan is out of scope for the ALS Mobilization WP, but even if it were to be taken up elsewhere, we could only reasonably stipulate that those affected must declare (howsoever) those roles to the At-Large community. We cannot stipulate requirements with respect to any other parts of ICANN. <br><br>Justine<br><span style="font-family:arial,helvetica,sans-serif">------</span><br><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 20 Apr 2020 at 14:40, Jonathan Zuck <<a href="mailto:JZuck@innovatorsnetwork.org">JZuck@innovatorsnetwork.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 lang="EN-US">
<div class="gmail-m_-4618446657739831147WordSection1">
<p class="MsoNormal">Agree with this but, as Alan said, it’s out of the scope of his WG. I think it’s something to put on the agenda of the newly reconstituted FBSC and would most likely have consensus.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">ALAC <<a href="mailto:alac-bounces@atlarge-lists.icann.org" target="_blank">alac-bounces@atlarge-lists.icann.org</a>> on behalf of Evan Leibovitch <<a href="mailto:evan@telly.org" target="_blank">evan@telly.org</a>><br>
<b>Date: </b>Sunday, April 19, 2020 at 10:01 PM<br>
<b>To: </b>Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>><br>
<b>Cc: </b>alac <<a href="mailto:alac@atlarge-lists.icann.org" target="_blank">alac@atlarge-lists.icann.org</a>><br>
<b>Subject: </b>Re: [ALAC] Overlap between ALSes and non-At-Large parts of the ICANN community<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">Hi Alan,<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">I agree that disclosure is the best remedy. Just one general comment.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">Are the rules reciprocal? We have had instances in which members of other constituencies have tried (sometimes ... energetically) to influence At-Large positions and in some cases
disrupt what might otherwise be consensus. While often being candid and open about the cross-participation, I have on numerous times heard the "I may work for a contracted but I'm an end-user too!" refrain upon confrontation. I would hesitate to put many limitations,
or disclosures, on At-Large participants contributing elsewhere in ICANN if there is no reciprocity.
<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">To this end I would suggest that anyone participating in a substantive discussion in either a RALO or an At-Large WG (who is not a verifiable individual RALO participant or member
of an ALS) should be obligated to file and maintain an accurate SOI, I had to have one on file anytime I did anything touching the GNSO, so it's not like we'd be creating an imbalance, And anyone without conflicts could do the SOI very quickly.<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)"><u></u> <u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Tahoma,sans-serif;color:rgb(11,83,148)">- Evan<u></u><u></u></span></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</div>
_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</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" 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></div>
</div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>ALAC mailing list</span><br><span><a href="mailto:ALAC@atlarge-lists.icann.org">ALAC@atlarge-lists.icann.org</a></span><br><span><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac">https://atlarge-lists.icann.org/mailman/listinfo/alac</a></span><br><span></span><br><span>At-Large Online: <a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a></span><br><span>ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></span><br><span>_______________________________________________</span><br><span>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">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos">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.</span></div></blockquote></div></div></body></html>