[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[atlarge-discuss] First Thoughts on ALAC
- To: apisan@servidor.unam.mx
- Subject: [atlarge-discuss] First Thoughts on ALAC
- From: DannyYounger@cs.com
- Date: Fri, 19 Jul 2002 23:37:39 EDT
- CC: denisemichel@sbcglobal.net, atlarge-discuss@lists.fitug.de
- Delivered-To: mailing list atlarge-discuss@lists.fitug.de
- List-Help: <mailto:atlarge-discuss-help@lists.fitug.de>
- List-Post: <mailto:atlarge-discuss@lists.fitug.de>
- List-Subscribe: <mailto:atlarge-discuss-subscribe@lists.fitug.de>
- List-Unsubscribe: <mailto:atlarge-discuss-unsubscribe@lists.fitug.de>
- Mailing-List: contact atlarge-discuss-help@lists.fitug.de; run by ezmlm
The current "Blueprint" calls for a 15-member board with 5 "Liaisons" who may
participate in Board discussions and deliberations like Directors but don't
cast votes. These liaisons are drawn from the "Advisory Committees": TAC,
RSSAC, SAC, GAC and the IETF/IAB.
Under the Blueprint, the ALAC will not have Liaison status. This issue
should be reviewed.
The Charter for the ALAC will probably wind up being pretty much the same as
described for the TAC -- I have eliminated the word "technical" from the
description of the TAC in the Blueprint, and substituted ALAC for TAC in the
text... this results in:
The ALAC should be available to provide *** advice and guidance to the Board
and to other organizations within ICANN. It should serve both as a resource
that can be called upon to pursue specific questions and as an active
watchdog ensuring that *** issues that might otherwise be overlooked are
brought to the attention of decision makers. It also serves as a meeting
point for different parts of the *** community to come together to discuss
global *** policy issues within the scope of ICANN's mission.
Please note that ALL current advisory committees have an "appointed"
membership, and that it would be naive to think that the ALAC will be an
exception to this rule (even the governments appoint members to the GAC).
This leads to the question, how many members should there be on the ALAC, and
most importantly how should it be structured?
The ICANN Bylaws (Article VII, Section 3(b)) provide a good framework and may
be amended as follows:
There shall be an At-Large Advisory Committee. The initial chairman of the
At-Large Advisory Committee shall be appointed by the Board and shall hold
that position until the election of his or her successor; subsequent chairs
shall be elected by the members of the At-large Advisory Committee pursuant
to procedures adopted by such members. Membership of the At-Large Advisory
Committee shall be open to all At-Large Organizations. Membership shall also
be open to Individuals on the invitation of the At-Large Advisory Committee
through its Chair, or on invitation of the ICANN Board. Member organizations
of the At-Large Advisory Committee shall appoint one accredited
representative to the Committee. The accredited representative of a member
must hold a formal official position within the member organization. The term
"official" includes a holder of an elected office, or a person who is
employed by such organization, and whose primary function with such
organization is to develop or influence policies. The At-Large Advisory
Committee should consider and provide advice on the activities of the
Corporation as they relate to concerns of users. The Board will notify the
chairman of the At-Large Advisory Committee of any proposal for which it
seeks comments and will consider any response to that notification prior to
taking action.
This stuff is not rocket science, as good operative models already exist.
Add a little bit more transparency and everyone should be reasonably
happy.... comments?
Spcifically, the ERC has asked for our ideas on how to structure an At-Large
Advisory Committee
the Security Committee. The members of the Committee are:
Alain Aina (Consultant)
Jaap Akkerhuis (SIDN)
Doug Barton (Yahoo!)
Steve Bellovin (ATT)
Rob Blokzijl (RIPE)
David Conrad (Nominum)
Steve Crocker (Consultant), Chair
Daniel Karrenberg (RIPE-NCC)
Mark Kosters (VeriSign)
Allison Mankin (ISI)
Ram Mohan (Afilias)
Russ Mundy (Network Associates Laboratories)
Jun Murai (Keio University)
Frederico Neves (registro.br)
Ray Plzak (ARIN)
Doron Shikmoni (ForeScout, ISOC-IL)
Ken Silva (VeriSign)
Bruce Tonkin (Melbourne IT)
Paul Vixie (ISC)
Rick Wesson (Alice's Registry)
The Board shall be composed of 15 voting Directors. Additionally there shall
be 5 non-voting Liaisons as specified below who may participate in Board
discussions and deliberations like Directors but shall not cast votes (and as
such, do not count towards quorum counts of the Board)
The 15 voting Directors shall be selected as follows:
8 Directors selected by the Nominating Committee (NomCom)
2 Directors selected from each of the three Supporting Organizations
The President of ICANN
The 5 non-voting Liaisons shall be selected as follows:
1 by the TAC
1 by the IAB/IETF4
1 by the RSSAC
1 by the SAC
1 by the GAC
---------------------------------------------------------------------
To unsubscribe, e-mail: atlarge-discuss-unsubscribe@lists.fitug.de
For additional commands, e-mail: atlarge-discuss-help@lists.fitug.de