The second decision point says: Does the community have consensus on the proposal content? Has testing shown the system is working? If so, deliver proposal to ICANN Board for delivery to NTIA. If not, develop a revised timeline. So, there is a check, but there is not time to got back to the communities to update things if there are problems found. This is the aggressive schedule.... Russ On Jul 21, 2014, at 12:36 PM, James M. Bladel wrote:
One item that was noted as ³missing² from this proposed timeline is a window to address any issues uncovered during testing that would necessitate a revision to the proposal(s), and perhaps even a re-opening of public comments on those changes.
Thanks--
J.
On 7/21/14, 11:26 , "Milton L Mueller" <mueller@syr.edu> wrote:
Very nice infographic! I have saved it in my IANA-transition folder under the filename: "timeline-optimistic." --MM
-----Original Message----- From: internal-cg-bounces@icann.org [mailto:internal-cg-bounces@icann.org] On Behalf Of Russ Housley Sent: Monday, July 21, 2014 10:20 AM To: Coordination Group Subject: Re: [Internal-cg] Timeline
I tried to accommodate all of the comments from the discussion that took place yesterday. Here is the updated document. Please review and comment.
Here is a graphic that shows the timeline. I hope this helps people see the things that are being done in parallel.
Russ
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg