Re: [At-Large] Rules of procedure, draft 2
I would double-check with General Counsel.
While the one you point out is a general rule, there is still the
possibility of changing the Liaison during the year.
As a matter of fact, John Klensin (IETF Liaison) stepped down in June 2005,
and was replaced immediately, while Sharil (GAC Liaison) stepped down in
March 2007, while his successor had been appointed already since Sao Paulo
and there has been a three months overlap.
The only case where strict rules are enforced is the TLG Liaison, but this
is because there is a rotation among ETSI, ITU and W3C, and they serve one
year each.
Regards,
Roberto
> -----Original Message-----
> From: alac-bounces@xxxxxxxxxxxxxxxxxxxxxxx
> [mailto:alac-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
> Jacqueline A. Morris
> Sent: 17 April 2007 16:27
> To: jam@xxxxxxxxxxxxxxxxxxxx; shahshah@xxxxxxxx; 'Vittorio
> Bertola'; 'Adam Peake'; alac@xxxxxxxxx
> Subject: Re: [At-Large] Rules of procedure, draft 2
>
> Oops
> I just read the bylaws again. They are clear that "the
> non-voting liaisons shall serve terms that begin at the
> conclusion of each annual meeting. At least one month before
> the commencement of each annual meeting, each body entitled
> to appoint a non-voting liaison shall give the Secretary of
> ICANN written notice of its appointment."
> So that we HAVE to have the Board liason chosen at least 1
> month before the annual meeting. What we can possibly do is
> have the ALAC elections at the meeting BEFORE the annual
> meeting? But then it's the outgoing ALAC that will choose the
> new positions, and the new members will nto have a chance to
> participate.
> Unless we separate the Board liason position from the rest?
> Jacqueline
>
> -----Original Message-----
> From: Jacqueline A. Morris [mailto:jam@xxxxxxxxxxxxxxxxxxxx]
> Sent: Tuesday, April 17, 2007 10:06 AM
> To: shahshah@xxxxxxxx; 'Vittorio Bertola'; 'Adam Peake';
> alac@xxxxxxxxx
> Subject: Re: [At-Large] Rules of procedure, draft 2
>
> This makes sense to me as well. It puts a bit of work onto
> the 2 Board liaisons to interact, and doesn't let the new
> Liaison have the first Board meeting f2f, but rather via
> telecom, but we aren't going to choose a Board liason who
> doesn't know the Board members, so that isn't too much of a burden.
> Jacqueline
>
> -----Original Message-----
> From: Siavash Shahshahani [mailto:shahshah@xxxxxxxx]
> Sent: Sunday, April 15, 2007 12:25 PM
> To: Vittorio Bertola; Adam Peake; alac@xxxxxxxxx
> Subject: Re: [At-Large] Rules of procedure, draft 2
>
> Sorry, rather late, but I miss the point of this debate. If
> ALAC's liaison to the Board is selected at AGM (or any other
> time for that matter), the old liaison can do the job for the
> following six weeks required(suggested) by the by laws while
> the new one gets ready on the sidelines.
> Siavash
>
> > On 2007-04-11 16:47:14 +0200, Vittorio Bertola wrote:
> >
> >>> I'd respectfully suggest that you stop wagging the dog with this.
> >
> >> "Wagging the dog" implies that there is a bigger, hidden issue
> >> behind, so... what do you mean?
> >
> > The idea that the rest of the ICANN community should adopt its
> > schedule to ALAC's whim. Having the appointments somewhat
> in synch is
> > beneficial for all.
> >
> > (Resending with non-work address.)
> >
> > _______________________________________________
> > ALAC mailing list
> > ALAC@xxxxxxxxxxxxxxxxxxxxxxx
> >
> http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-l
> ists.icann.org
> >
> > www.alac.icann.org
> > www.icannalac.org
> >
>
>
> -------------------------------------------------
> IPM/IRNIC
> P.O.Box 19395-5564, Shahid Bahonar Sq.
> Tehran 19548, Iran
> Phone: (+98 21) 22 82 80 80; 22 82 80 81, ext 113
> Cell: (+98 912)104 2501
> Fax: (+98 21) 22 29 57 00
> Email: shahshah@xxxxxxxx, shahshah@xxxxxx
> -----------------------------------------------
>
> _______________________________________________
> ALAC mailing list
> ALAC@xxxxxxxxxxxxxxxxxxxxxxx
> http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-l
> ists.icann.org
>
> www.alac.icann.org
> www.icannalac.org
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 269.4.0/762 - Release
> Date: 4/15/2007
> 4:22 PM
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 269.4.0/762 - Release
> Date: 4/15/2007
> 4:22 PM
>
>
>
> _______________________________________________
> ALAC mailing list
> ALAC@xxxxxxxxxxxxxxxxxxxxxxx
> http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-l
> ists.icann.org
>
> www.alac.icann.org
> www.icannalac.org
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 269.4.0/762 - Release
> Date: 4/15/2007
> 4:22 PM
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 269.4.0/762 - Release
> Date: 4/15/2007
> 4:22 PM
>
>
>
> _______________________________________________
> ALAC mailing list
> ALAC@xxxxxxxxxxxxxxxxxxxxxxx
> http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-l
> ists.icann.org
>
> www.alac.icann.org
> www.icannalac.org
_______________________________________________
ALAC mailing list
ALAC@xxxxxxxxxxxxxxxxxxxxxxx
http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org
www.alac.icann.org
www.icannalac.org