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

[Justine Chew]

I believe the recommendations of the WP as Alan has posited are correct.

With respect to " 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. ", 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.

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.

Justine
------


On Mon, 20 Apr 2020 at 14:40, Jonathan Zuck <JZuck at innovatorsnetwork.org>
wrote:

> 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
>
>
> _______________________________________________
> ALAC mailing list
> ALAC at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/alac
>
> At-Large Online: http://www.atlarge.icann.org
> ALAC Working Wiki:
> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
> _______________________________________________
> 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 (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20200420/3e31437e/attachment.html>