ICANN ICANN Email List Archives

[gnso-restruc-dt]


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

RE: [gnso-restruc-dt] Q4; In Section 3.1: Question of constituency role

  • To: "avri@xxxxxxx" <avri@xxxxxxx>, "Gnso-restruc-dt@xxxxxxxxx" <Gnso-restruc-dt@xxxxxxxxx>
  • Subject: RE: [gnso-restruc-dt] Q4; In Section 3.1: Question of constituency role
  • From: Milton L Mueller <mueller@xxxxxxx>
  • Date: Thu, 7 May 2009 12:32:59 -0400



> -----Original Message-----
> policy staff does have the ability to bring up issues and ask questions
> if they believe it will help us take all the issues into consideration.
 
> Another reason for considering the question worthwhile might be that
[snip]

All very well and good, Avri, but I provided a pretty comprehensive answer to 
the question in my initial message. About as long as your response above I 
reproduce it below in case you did not read it. ;-)

> >  y answer, which is similar to the one provided on the
> >  call by someone whose name I do not know, is VOICE. In the NCSG
> >  charter, for example, Constituencies get a seat on the policy
> >  committee, and their statements on a policy issue must be included in
> >  any submissions of SG statements on that issue. They also can propose
> >  that WGs be formed and the Council reps must follow those
> >  recommendations once a certain threshold is reached.
> >
> > I note that the Board Governance Committee was interested in new
> >  constituencies ONLY insofar as they expanded representation,
> >  participation and the diversity of voices. It was not interested in
> >  new constituencies as an end in themselves (although some staff
> >  members seem to have erroneously interpreted it that). Detaching
> >  constituencies from Council seats actually makes it much easier to
> >  form new constituencies, and thus to get more diversity of voices.
> >




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

Privacy Policy | Terms of Service | Cookies Policy