Re: [gnso-ppsc-pdp] Proposed Timeline and Path Forward

[Alan Greenberg <alan.greenberg@xxxxxxxxx>]

Dates still ok for me.

I have not looked at the timeline in any detail yet, but it strikes 
me that the last three items are way to close together (assuming we 
get any substantive comments, which I would hope we would).
15 April        Closing of Public Comment Period
22 April        Meeting of the PDP-WT - Review and discussion of 
public comments received
30 April        Revise Final Report, if appropriate, and submit to PPSC

It seems too optimistic to summarize and have us all review the 
comments in one week, and then come to closure of what we do with 
them in one meeting. I guess it is fine to plan for this, but 
probably not achievable.
Alan


At 21/11/2009 10:00 PM, Neuman, Jeff wrote:
> All,
>
> On the last call, we discussed putting out a timeline and path 
> forward to complete our work.  Please find a timeline ICANN staff 
> helped put together.  It is quite ambitious and does rely on a face 
> to face meeting as discussed in January.  The tentative dates for 
> that meeting (assuming it gets approved by ICANN) will be January 
> 18th and 19th.  We recognize that the 18th is a holiday for some in 
> the US (Martin Luther King Day) so we wanted to make sure that those 
> who indicated it was ok in the Doodle poll can still make that day.
> Please let us know.
>
> Thanks!
>
> Jeffrey J. Neuman
> Neustar, Inc. / Vice President, Law & Policy
> 46000 Center Oak Plaza Sterling, VA 20166
> Office: +1.571.434.5772  Mobile: +1.202.549.5079  Fax: 
> +1.703.738.7965 / 
> <mailto:jeff.neuman@xxxxxxxxxxx>jeff.neuman@xxxxxxxxxxx  / 
> www.neustar.biz
> The information contained in this e-mail message is intended only 
> for the use of the recipient(s) named above and may contain 
> confidential and/or privileged information. If you are not the 
> intended recipient you have received this e-mail message in error 
> and any review, dissemination, distribution, or copying of this 
> message is strictly prohibited. If you have received this 
> communication in error, please notify us immediately and delete the 
> original message.