[ALAC] Overlap between ALSes and non-At-Large parts of the ICANN community

[Jonathan Zuck]

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.

From: ALAC <alac-bounces at atlarge-lists.icann.org> on behalf of Evan Leibovitch <evan at telly.org>
Date: Sunday, April 19, 2020 at 10:01 PM
To: Alan Greenberg <alan.greenberg at mcgill.ca>
Cc: alac <alac at atlarge-lists.icann.org>
Subject: Re: [ALAC] Overlap between ALSes and non-At-Large parts of the ICANN community

Hi Alan,

I agree that disclosure is the best remedy. Just one general comment.

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.

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.

- Evan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20200420/fe47b605/attachment.html>