ICANN/DNSO
DNSO Mailling lists archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [council] Draft rules for non NCmembers


Paul
I had exactly the same thought, a minimum of two from two different
Constituencies shouldn't prove to onerous and would add credibility to the
group.
Tony
> -----Original Message-----
> From:	Paul M. Kane [SMTP:Paul.Kane@reacto.com]
> Sent:	Tuesday, July 03, 2001 10:39 AM
> To:	Philip Sheppard
> Cc:	NC (list)
> Subject:	Re: [council] Draft rules for non NCmembers
> 
> Just another thought...
> Might I suggest f) be clarified to ensure a min of two NC members. One
> of whom will be the Chair.
> I think it makes for better communication to the NC.  
> 
> I am assuming the TF will have a mailing list that will be archived so 
> those wishing to review dialogue may do so.
> 
> best
> 
> Paul
> 
> > Philip Sheppard wrote:
> > 
> > Thank you Erica for first comments on the draft rules for non NC
> > member participation. I have incorporated these comments below.
> > Comments please by Thursday 5 July.
> > Philip
> > 
> > [start draft ]
> > 
> > 3. NC committees and task forces
> > 
> > From time  to time the NC may form  sub-groups. These are typically of
> > three types.  Each type may form  small further sub-groups from within
> > their membership. 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.
> > 
> > Interim  committee ?   a preparatory  group of  around 3-5  NC members
> > charged with turning an  idea into a proposed action plan. The interim
> > committee  is  dissolved following  NC  adoption of  the action  plan.
> > 
> > Committee  ? a  small  group of  around 3-5  NC  members of  which has
> > typically been delegated a limited authority from the NC.
> > 
> > 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. A
> > task force 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
> > 
> > b)  the  nominee has  the  support  of the  three  NC  members of  the
> > constituency
> > 
> > c)   the  nominee   is   a  member   of  the   nominees?  constituency
> > 
> > d)  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
> > 
> > e)   no  two   nominees  are   members  of  the   same  ICANN-relevant
> > organisation, the first nominee taking priority
> > 
> > f) there is at least one NC member of the task force
> > 
> > g) the chair of the task force is an NC member.
> > 
> > Note:  An ICANN-relevant organisation  is defined  as one that  any NC
> > member considers to be ICANN-relevant.
> > 
> > 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].
> > 
> > [end draft]


<<< Chronological Index >>>    <<< Thread Index >>>