[gnso-ppsc] Deliverables and Timing for Completion of PDP work

["Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx>]

There has been a lot of discussion at the Council level about the timing for 
completion of the PDP-WT work as well as the timing and completion of the work 
of the PPSC and I wanted to throw out my assumptions and best guess at a 
timeline moving forward.  I have already shared these dates with the Council.  
However, some in the community have stated that I was not pushing the group to 
act more quickly.  So, with that in mind, I want to send this to the list and 
if you believe that any of the steps below can be eliminated or shortened, 
please provide me with such feedback along with an alternate schedule in which 
you believe work can get done.  Please keep in mind all of the outstanding 
issues listed at https://st.icann.org/icann-ppsc/index.cgi?pdp_team (in the doc 
dated November 25th) as well as the fact that we need to complete the draft 
final report which includes draft Bylaw and PDP Guideline language.

1.  Completion of the draft final report:   February 1, 2010.  Remember that we 
have the holidays, a number of outstanding issues and we have yet to get any 
comments from the group on the draft that has been previously circulated.   I 
am also basing this assumption on having five (5) more conference call between 
now and then, with perhaps one of those being an extended call  (Dec 23rd, 
January 6, Jan 13, Jan 20th and Jan 27th).  Does anyone believe we can complete 
all of work any sooner than that?

2.  Public Comment period:  Feb 1 - March 25th (53 days).  I realize that this 
may sound like a long time, but (a) I am building in some buffer in case we do 
not publish by Feb 1 and (b) we want to be able to get comments at a public 
ICANN meeting (which ends on the 18th).  I have built in the extra week because 
of the rule we propose in our draft final report of allowing for at least a 
week after an ICANN meeting.  Remember that a whole host of other documents 
will likely be posted by mid February to prepare for the San Francisco meeting. 
 Also, remember that there will be a lot of new material and even with more 
than 90 days of comment prior for the initial report, some groups like the NCSG 
and others did not provide feedback for several months after the deadline.  
Given the considerations outlined above, are there any suggestions in making 
that time quicker?

3.  Preparation of the final report:  March 25th - April 30th.  This is where 
we will take the input from the public comment period and incorporate into our 
final report (as necessary).  Personally I believe this time period would be 
too short, but I am willing to work on it if you all are.

4.  Consideration by the PPSC of final Report:  May 1 - June 27th.  This may 
seem like a long time to some, but remember, this is where the PPSC needs to 
review the report, send questions back to the PDP-WT, if any, and submit the 
report to Council.  I am assuming June 27th is the Council meeting.

Please note that the above is a VERY aggressive time frame and assumes that we 
will have full participation on the call as well as on the mailing lists.

Again, if anyone has any issues with the above time frame, please speak up now. 
 And if you do, please provide an alternate proposal on action items and time 
frames.

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 / 
jeff.neuman@xxxxxxxxxxx<mailto:jeff.neuman@xxxxxxxxxxx>  / 
www.neustar.biz<http://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.