[Internal-cg] Strawman proposal finalization process

Manal Ismail manal at tra.gov.eg
Tue Sep 23 06:37:57 UTC 2014

Many thanks Alissa ..
Very useful ..
I'm attaching (also in dropbox) some initial comments ..

Kind Regards

-----Original Message-----
From: internal-cg-bounces at icann.org [mailto:internal-cg-bounces at icann.org] On Behalf Of Alissa Cooper
Sent: Tuesday, September 23, 2014 12:35 AM
Subject: [Internal-cg] Strawman proposal finalization process

As discussed in the thread about ICANN 51 side meetings, it seems like it would be helpful for us to develop a shared understanding of how we will assemble and finalize a unified transition proposal after we start receiving individual proposals from the operational communities and broader input from all stakeholders. My guess is that we will not come to a firm conclusion about all details of this process prior to ICANN 51, which is fine. But we certainly need to come to some conclusions about it within the next few months, so that we are prepared when we start receiving proposals from the operational communities and input from all stakeholders.

I’ve put together a strawman proposal for a process to use to assemble and finalize a unified transition proposal (attached and in dropbox). It is heavily influenced by our charter. You will see that there are many open questions — I’m just throwing this out as a starting point to get discussion going. Please comment.

I don’t think we need to document every little detail and possible corner case for how things might go once we start receiving proposals and input, but I do think we should have a rough plan that we can articulate to establish expectations about how we will proceed.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: proposal-finalization-process-v0-mi.docx
Type: application/octet-stream
Size: 36404 bytes
Desc: proposal-finalization-process-v0-mi.docx
URL: <http://mm.icann.org/pipermail/internal-cg/attachments/20140923/74aa4f8a/proposal-finalization-process-v0-mi.docx>

More information about the Internal-cg mailing list