[ALAC] Explanation of RoP Director voting alternatives

Sun Jun 26 22:01:05 UTC 2016

I would suggest that we proceed with the 
discussion, and we can extend it into the 
currently unallocated agenda item on Thursday at 9:45 if necessary.

I am working with ICANN staff to identify all of 
the changes that will be required for allowing 
the ALAC to participate in the Empowered 
Community and to take actions with regard to PTI. 
At this stage, it is unclear how extensive these 
changes will be, how detailed they may need to be 
and whether we must complete them and have them 
approved prior to ICANN implementing the new 
Bylaws in the event NTIA approves of the IANA 
Stewardship Transition Proposal and the IANA 
Functions Contract expires on 30 September 2016 
(which mean we may just have until the end of 
August to prepare these revisions).

Accordingly, I think it wise to not add other 
things to that proposed RoP change if we can possibly avoid it.

For those who have not taken the opportunity to 
prepare for this action, I am attaching to this 
message the RoP revision, the Addendum just 
circulated, and the Change Log describing each of 
the changes. Excluding updating of URLs, there 
are only 8 changes that can readily be reviewed in the time we have allocated.

Alan

At 26/06/2016 03:58 PM, Sébastien Bachollet wrote:

>Hello Alan and all,
>
>Yes the document has been out for 3 weeks.
>And yes I am sorry to inform you that I didnâ€™t have time to have an
>in-depth reading.
>I may not be the only one.
>
>Therefore I ask that only the changes that the ALT deem necessary for the
>election/selection of the At-Large Board member proceed.
>
>
>It maybe also useful to wait to include in the ROP what ALAC will need
>regarding the implementation of WS1.
>
>
>All the best
>SeB
>
>
>Skills are useful but diversity is essential.
>
>SÃ©bastien Bachollet
>+33 6 07 66 89 33
>Blog: http://sebastien.bachollet.fr/
>Mail: SÃ©bastien Bachollet <sebastien at bachollet.com>
>
>
>
>
>Le 26/06/2016 15:27, Â« Alan Greenberg Â»
><alac-bounces at atlarge-lists.icann.org on behalf of
>alan.greenberg at mcgill.ca> a Ã©crit :
>
> >Tijani, can you please say what exactly the issue
> >is. I see no reason not to proceed is it is
> >possible to address your concern in the time we have.
> >
> >All that is being proposed is clear naming of the organization we already
> >have.
> >
> >These proposed RoP changes have bee out for comment for three weeks now.
> >
> >Alan
> >
> >At 26/06/2016 04:19 AM, tijani.benjemaa at topnet.tn wrote:
> >
> >>Alan,
> >>
> >>Yes, of course, I want it to be clearly defined, but after deeper
> >>reflection. As you know, we will have to modify our RoP to comply with
> >>the bylaws change, so, lets take our time and make it more systematic.
> >>
> >>-------------------------------------------------------------------------
> >>----
> >>Tijani BEN JEMAA
> >>Executive Director
> >>Mediterranean Federation of Internet Associations (FMAI)
> >>Phone: +216 98 330 114
> >>             +216 52 385 114
> >>-------------------------------------------------------------------------
> >>----
> >>
> >>Le 26 juin 2016 Ãƒ  10:24, Alan Greenberg <alan.greenberg at mcgill.ca> a
> >>ÃƒÂ©crit :
> >>
> >>Tijani, when I distributed the revisions, I said "If there is any
> >>serious objection to these changes that cannot be readily adjusted,
> >>they will be withdrawn to not delay the changes to Section 19."
> >>
> >>I stand by that. If there is substantive concern with the changes
> >>unrelated to the Director Selection that cannot be quickly addressed,
> >>then they will be withdrawn.
> >>
> >>However, in relation to the section 3.5 that you are referring to,
> >>there are no operational changes being proposed. As Chair, I have
> >>chosen to invite certain people to the ALT meetings (they are after
> >>all generally open meetings!) and I have also in a few cases asked
> >>some people to participate in the rare in camera confidential
> >>discussions. The proposed changes ONLY add the nomenclature of
> >>"advisor" so that we have clarity when referring to the ALT exactly
> >>who is and is not included. Without the change it has often been
> >>unclear whether the Liaisons to ICANN bodies are or are not included
> >>in the definition of the ALT.
> >>
> >>The inclusion of some past Chairs is at the discretion of the current
> >>Chair, and whether they are referenced in a formal definition does not
> >>alter whether they are included in a particular meeting or not.
> >>
> >>If there is a general feeling within the ALAC that we should not
> >>clarify the definition, then it will be withdrawn.
> >>
> >>Alan
> >>
> >>At 26/06/2016 01:59 AM, tijani.benjemaa at topnet.tn wrote:
> >>
> >>Dear Alan,
> >>
> >>I read again the proposal for update of the RoP, and found that it is
> >>not adequate to make the modifications that are not necessary for the
> >>Board Director Selection at this time because 
> we didnÃƒÂ¢Ã‚Â€Ã‚Â™t have time to
> >>discuss them deeply, and because there is no urgency in making those
> >>modifications.
> >>
> >>I especially thought about the proposal to include the former ALAC
> >>Chairs in  the ALT as advisors. This will have as a consequence the
> >>number of advisors growing each time we change the ALAC Chair. And
> >>also, if we are seeking advices, why 
> donÃƒÂ¢Ã‚Â€Ã‚Â™t also include the former
> >>Board members such as Jean Jacques, Vanda and Sebastien?
> >>
> >>So, I propose to make the proposed modifications related to the
> >>selection of the Board member selected by At-Large only, leaving the
> >>remaining modifications to deeper reflection before adopting them.
> >>
> >>-------------------------------------------------------------------------
> >>----
> >>Tijani BEN JEMAA
> >>Executive Director
> >>Mediterranean Federation of Internet Associations (FMAI)
> >>Phone: +216 98 330 114
> >>            +216 52 385 114
> >>-------------------------------------------------------------------------
> >>----
> >>
> >>
> >
> >_______________________________________________
> >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+(A
> >LAC)
>
>
>Content-Type: application/xml; name="default.xml"
>Content-Disposition: attachment; filename="default.xml"
>X-Microsoft-Exchange-Diagnostics:
> 
>1;SN1PR0301MB2030;9:HC9p70UbUPq7rsbIquN/05BJ+g0HqXQ2ylpbQLpTUh22r/SWibtYsLKKXIYFnhAj9tSCwL7KEoi+/nzPRuBUsOqHdcCzfQfKtB7rR1+Usb1Aun19pBPYrOLYToul+G1byrBlyMcia/NLDWeM2ZNTvr+aX+ZWVlaMp9slcU0i5LDUvRQJhUPsv4smDkKH0JHf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ALAC RoP-Version2-Draft-2016-06-06_2.pdf
Type: application/pdf
Size: 228941 bytes
Desc: not available
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20160626/99bb760c/ALACRoP-Version2-Draft-2016-06-06_2.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ALAC RoP-Version2-Draft-2016-06-06_2-Addendum.pdf
Type: application/pdf
Size: 59317 bytes
Desc: not available
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20160626/99bb760c/ALACRoP-Version2-Draft-2016-06-06_2-Addendum.pdf>