ICANN ICANN Email List Archives

[gnso-vi-feb10]


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

Re: [gnso-vi-feb10] RE: Proposed draft message to ICANN staff

  • To: "briancute@xxxxxxxxxxxx" <briancute@xxxxxxxxxxxx>, "'Brian Cute'" <briancute@xxxxxxxxxxxx>, "Gnso-vi-feb10@xxxxxxxxx" <Gnso-vi-feb10@xxxxxxxxx>
  • Subject: Re: [gnso-vi-feb10] RE: Proposed draft message to ICANN staff
  • From: Alan Greenberg <alan.greenberg@xxxxxxxxx>
  • Date: Wed, 12 May 2010 13:15:56 -0400

Apologies accepted. Where do we send medical bills for heart palpitations?

Alan

At 12/05/2010 01:02 PM, Brian Cute wrote:
Apologies for the reference to the ?call today? since there is none. Can we discuss this on the list?

From: Brian Cute [mailto:briancute@xxxxxxxxxxxx]
Sent: Wednesday, May 12, 2010 12:59 PM
To: 'Gnso-vi-feb10@xxxxxxxxx'
Subject: Proposed draft message to ICANN staff

Mikey and Roberto,

I took the liberty of drafting a possible message from the VIWG to the ICANN staff in relation to the deadline of May 14 for submissions to be included in DAG4. (I hope you don?t mind.) Could we discuss this item on the call today?

Regards,
Brian



Dear Kurt,

As Co-Chairs of the Vertical Integration Working Group, we write to you concerning the approaching deadline for submissions to be included in DAG4. As of today, the VIWG does not have a proposal to submit for inclusion in DAG4. The VIWG has been working hard ? with roughly 60 participants, weekly meetings and over 1500 email exchanges in a serious attempt to produce a consensus based proposal. While the VIWG does not have a specific proposal at this time, we will continue to work toward the goal of presenting a consensus based proposal to the GNSO Council (and the Board) in advance of ICANN?s Brussels meeting. The VIWG requests that Staff consider keeping a placeholder in DAG4 that notes the above expression from the VIWG pending our final report up to the GNSO Council.

Best regards,
Roberto Gaetano
Mikey O?Connor


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

Privacy Policy | Terms of Service | Cookies Policy