[council] NC task forces composition
I fear there may be some misunderstanding on the NC decision
to allow non NC participation in certain of its sub-groups. The resolution we passed (see below) states in 3.1c
c) Task Force – a group equally
representative of each NC constituency (typically one from each) and typically
charged with forming a recommendation to the NC or
implementing an agreed NC action plan.
The reference to non-members (3.3) is a variation of this
simply saying that instead of an NC member it may be a non NC person under
certain conditions.
This does not to my mind therefore mean that for typical task
forces a constituency will make more than ONE nomination. The constituency
chooses to nominate a NC members or an non NC member. (This was my
intent in drafting and I would seek to re-discuss if another inference is
given.)
The alternative is problematic. Allowing a constituency to
make multiple nominations means that task forces may be unbalanced between
constituencies and that a single constituency can determine the size and
workability of a task force.
To my reading all task forces we have are typical except for
UDRP where (we had a clause 3.5 variation) and voted on a specific
composition.
(Based on this I would ask the gTLD constituency to
re-consider its nominations for the dot org and UDRP task forces.)
Philip
3. NC committees and task forces 3.1 Types From time to time the NC may form sub-groups. These are typically of three types. Each type may form and be responsible for further sub-groups from within their membership. The composition of these groups shall follow the spirit of the ICANN Bylaws with regard to geographic diversitya) Interim committee – a preparatory group of around 3-5 NC members from different constituencies charged with turning an idea into a proposed action plan or writing terms of reference. The interim committee is dissolved following NC adoption of its output and/or the setting up of a new group to act upon that output. b) Committee – a small group of around 3-5 from different constituencies which has typically been delegated a limited authority from the NC. c) Task Force – a group equally representative of each NC constituency (typically one from each) and typically charged with forming a recommendation to the NC or implementing an agreed NC action plan. 3.2 Chair The chair of an interim committee, committee or task force is appointed by the NC. In the case of a task force the NC typically chooses to ratify the election of a chair by the task force itself. The chair must be an NC member. 3.3 Composition of committees and task forces Both type-b committees and type-c task forces may comprise NC members and/or nominees from outside of the NC provided that: a) the nominee is nominated by a member of the NC and be a member of the nominees’ constituency or, where there is GA involvement, be nominated by the chair of the GA and be a member of the GA b) a constituency nominee has the support of the three NC members of the constituency c) the nominee is not also a member of the same ICANN-relevant organisation as an NC member on the task force, the NC member taking priority at any time d) no two nominees are members of the same ICANN-relevant organisation, the first nominee taking priority e) there are at least two NC members of the task force from different constituencies f) regardless of the number of members of the group no constituency nor the general assembly may have more than one vote g) where authority has been delegated by the NC, a simple majority must be NC members, those NC members hold the delegated authority and only those NC members can vote. Note: An ICANN-relevant organisation is defined as one that any NC member considers to be ICANN-relevant. 3.4 Working group In addition to the above groups the NC will from time to time form a DNSO working group (WG) with a membership open to all DNSO participants. The WG objective is to formulate positions on policies, facilitate the development of consensus support for policies and to produce a report to the NC highlighting these positions and level of support. See the separate Procedures for Working Groups for full detail [in preparation]. 3.5 Variations Specific variations to the above guidelines may exist within the DNSO rules of procedures, such specific variations taking precedence. Any other variation requires the approval of the NC.
|