ICANN ICANN Email List Archives

[gnso-vi-feb10]


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

RE: [gnso-vi-feb10] Regarding the Nairobi Board Resolution

  • To: "Gnso-vi-feb10@xxxxxxxxx" <Gnso-vi-feb10@xxxxxxxxx>
  • Subject: RE: [gnso-vi-feb10] Regarding the Nairobi Board Resolution
  • From: Milton L Mueller <mueller@xxxxxxx>
  • Date: Thu, 13 May 2010 12:10:01 -0400

I strongly agree with Avri here. We had this discussion at the outset of the 
group's formation. Some of us argued then (and Kurt Pritz has since confirmed) 
that the Board was intending to "clear the table" for the GNSO to make the 
policy. Kurt's message was a very reasonable elaboration of the position that 
many of us took months ago, which is that any specific answers to the detailed 
questions about its resolution would ensnare us in a guessing game as to which 
policy the board wants, when in fact the board is telling us to make the 
policy. Which is precisely what the GNSO is supposed to be doing!!!

Why are we having this conversation? We have issues to resolve: ownership 
limits, the role of market power in affecting structural separation, the degree 
to which separation policies undermine or promote innovation and competition -- 
let's get on with it. 

--MM

> -----Original Message-----
> 
> The GNSO  initiated a PDP and the Board has cleared the table of
> preconditions and has given us a free path to do what we said we were
> going to do.  We asked for it, they gave it to us.  Now that we are
> getting down to the nitty gritty of actually making compromise, we
> decide to turn our energies toward attacking the board.  This makes no
> sense to me.
> 
> I would hate to see us waste this opportunity by now beginning to spend
> our energy on deciding what the Board may or may not have intended.  I
> admit Kurt's message could have been written better, but the point is
> the GNSO asked for the chance to define what went into the DAG and we
> are not getting it done.
> 




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

Privacy Policy | Terms of Service | Cookies Policy