ICANN/GNSO GNSO Email List Archives

[council]


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

RE: [council] Comments in relation with GNSO travel funding and policy

  • To: <avri@xxxxxxx>, "GNSO Council" <council@xxxxxxxxxxxxxx>
  • Subject: RE: [council] Comments in relation with GNSO travel funding and policy
  • From: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
  • Date: Fri, 27 Mar 2009 12:10:07 -0400
  • In-reply-to: <1238169189.10941.1229.camel@bower>
  • List-id: council@xxxxxxxxxxxxxx
  • References: <bccbb21a0903171850t3174b002y9b95efa307f01f4a@mail.gmail.com> <046F43A8D79C794FA4733814869CDF07029A0A2D@dul1wnexmb01.vcorp.ad.vrsn.com> <768862D8B08B46A7923B482FDF728577@PSEVO> <1238169189.10941.1229.camel@bower>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: Acmu9PbZVq+zy/2oTrCIIcEnGlnAegAAJ+5Q
  • Thread-topic: [council] Comments in relation with GNSO travel funding and policy

Avri,

Please explain to me what you agree with.  I didn't understand Philip's
point so I obviously do not understand yours.  Please note my responses
below.

Chuck 

> -----Original Message-----
> From: owner-council@xxxxxxxxxxxxxx 
> [mailto:owner-council@xxxxxxxxxxxxxx] On Behalf Of Avri Doria
> Sent: Friday, March 27, 2009 11:53 AM
> To: 'GNSO Council'
> Subject: RE: [council] Comments in relation with GNSO travel 
> funding and policy
> 
> 
> Hi,
> 
> I would tend to agree with this.  
> 
> Constituencies are, as I understand them within the new 
> structure, the basic way participants engaged in policy 
> making are organized.  It is being a constituency that gives 
> an organized group of people with a common interest a formal 
> voice in policy making.

No disagreement here.  Constituences are by definition components of SGs
so they are included.
  
> 
> The Stakeholder groups based on the other hand are based on 
> an sector organizational principle for allowing the 
> constituencies from one of 4 sectors to manage the process 
> and provide a mechanism to allow for the formation of new 
> constituencies without having to constantly change the 
> balance of representation/votes in the council.  Since SG are 
> organized along sector lines, it is quite possible for 
> constituencies within a sector to be unaligned and in 
> disagreement with each other.

So what?  That is the case now.  We regularly have disagreement in the
Council and we regularly have disagreement within our constituencies.
That is why work toward consensus or at least rough consensus.  

> 
> As long as we are working on a model of funding where the 
> participants within a group are forced to discriminate on how 
> that money will be spent, then that basic grouping has to be 
> the constituency.  Otherwise a strong constituency within a 
> SG could refuse to allow a weaker constituency to travel thus 
> stifling their legitimate Board given voice.

SG charters should be disigned to deal with this.

> 
> Note: In saying this I repeat my minority opinion again that 
> ICANN should be providing travel on the Board level standards 
> for all council members.  But this is not the position taken 
> by the DT or council, so it remains a minority view.  In the 
> spirit of announcing how we intend to vote in advance, I will 
> probably abstain since I strongly believe this and am 
> currently the only council member, by virtue of being chair, 
> being given what I consider the proper treatment all council 
> members should be given.  I think this will be even more the 
> case when we move to the SG model as then the council reps 
> will be chosen to serve the will of the SG  and not  
> interests of their constituency.
> 
> a.
> 
> 
> On Fri, 2009-03-27 at 16:12 +0100, Philip Sheppard wrote:
> > The BC profoundly objects to the proposed change of "constituencies"
> > to "stakeholder groups" suggested by the RyC.
> >  
> > Any new constituency must be approved by the Board.
> > It is therefore legitimate.
> > It therefore deserves equitable treatment.
> >  
> > Philip
> >  
> 
> 




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