<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:999038520;
mso-list-type:hybrid;
mso-list-template-ids:1196359460 67698713 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I agree with the intent of Jean-Jacques’ proposed modification and with Arasteh’s modification of it. The language
however is a bit redundant at the end, and we need to work more directly from the clear, step by step language that Alissa has already put into the document. So how about this:
<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
<p class="MsoListParagraphCxSpFirst" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><font size="3" face="Arial"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><span style="mso-list:Ignore">a.<font size="1" face="Times New Roman"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><![endif]><font face="Arial"><span style="font-family:"Arial",sans-serif">The ICG will post the final proposal on its public web site.<o:p></o:p></span></font></p>
<p class="MsoListParagraphCxSpMiddle"><font size="3" face="Arial"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></font></p>
<p class="MsoListParagraphCxSpMiddle" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><font size="3" face="Arial"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><span style="mso-list:Ignore">b.<font size="1" face="Times New Roman"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><![endif]><font face="Arial"><span style="font-family:"Arial",sans-serif">The ICG will transmit the final proposal to the ICANN Board.
<o:p></o:p></span></font></p>
<p class="MsoListParagraphCxSpMiddle"><font size="3" face="Arial"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></font></p>
<p class="MsoListParagraphCxSpMiddle" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><font size="3" face="Arial"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><span style="mso-list:Ignore">c.<font size="1" face="Times New Roman"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><![endif]><font face="Helvetica"><span style="font-family:"Helvetica",sans-serif">The ICANN Board will send the final proposal to NTIA without making any changes within 14 days of receiving the proposal from the ICG. Any accompanying
letter will be posted publicly.</span></font><font face="Arial"><span style="font-family:"Arial",sans-serif"><o:p></o:p></span></font></p>
<p class="MsoListParagraphCxSpMiddle"><font size="3" face="Arial"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></font></p>
<p class="MsoListParagraphCxSpLast" style="text-indent:-.25in;mso-list:l0 level1 lfo1">
<![if !supportLists]><font size="3" face="Helvetica"><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif"><span style="mso-list:Ignore">d.<font size="1" face="Times New Roman"><span style="font:7.0pt "Times New Roman"">
</span></font></span></span></font><![endif]><font face="Helvetica"><span style="font-family:"Helvetica",sans-serif">If the ICANN Board has an issue with the proposal, the ICG understands that the ICANN Board will have already shared that with the ICG in a
timely manner, through the available opportunities of dialogue and public comment.<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="3" face="Arial"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">--MM<o:p></o:p></span></font></p>
<p class="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></font></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;font-weight:bold">From:</span></font></b><font size="2" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> internal-cg-bounces@icann.org
[mailto:internal-cg-bounces@icann.org] <b><span style="font-weight:bold">On Behalf Of
</span></b>Kavouss Arasteh<br>
<b><span style="font-weight:bold">Sent:</span></b> Tuesday, December 9, 2014 8:58 AM<br>
<b><span style="font-weight:bold">To:</span></b> Subrenat, Jean-Jacques<br>
<b><span style="font-weight:bold">Cc:</span></b> ICG<br>
<b><span style="font-weight:bold">Subject:</span></b> Re: [Internal-cg] Please review: proposal finalization process<o:p></o:p></span></font></p>
</div>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><o:p> </o:p></span></font></p>
<div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Dear Alisa<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">I agree with Jean Jacques but suggesting to replace the word "expects "to "understands "due to the fact that our views is more than an expectation<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Regards<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Kavouss
<o:p></o:p></span></font></p>
</div>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><o:p> </o:p></span></font></p>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">2014-12-09 12:21 GMT+01:00 Subrenat, Jean-Jacques <<a href="mailto:jjs@dyalog.net" target="_blank">jjs@dyalog.net</a>>:<o:p></o:p></span></font></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Alissa,<br>
<br>
with reference to 4e, the ICG has no authority to say what the ICANN Board should or should not do. We can only express a wish or a firm expectation. Therefore, 4d and 4e should be collapsed into one, and reformulated as follows:<br>
<br>
"The ICG expects the ICANN Board to send the final proposal to the NTIA within 14 days of receipt, without making any changes to the proposal. If the ICANN Board were to have an issue with the proposal, the ICG expects the ICANN Board would have already shared
that with the ICG in a timely manner, through the available opportunities of dialogue and public comment. In the latter case, the ICG expects the ICANN Board would not modify the proposal, but would send it with a letter of transmission to be made public."<br>
<br>
Jean-Jacques.<br>
<br>
<br>
<br>
<br>
<br>
<br>
----- Mail original -----<br>
De: "Kavouss Arasteh" <<a href="mailto:kavouss.arasteh@gmail.com">kavouss.arasteh@gmail.com</a>><br>
À: "Narelle Clark" <<a href="mailto:narelle.clark@accan.org.au">narelle.clark@accan.org.au</a>><br>
Cc: "ICG" <<a href="mailto:internal-cg@icann.org">internal-cg@icann.org</a>><br>
Envoyé: Mardi 9 Décembre 2014 10:51:33<br>
Objet: Re: [Internal-cg] Please review: proposal finalization process<o:p></o:p></span></font></p>
<div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><br>
<br>
<br>
<br>
Alissa,<br>
I saw a document with several track changes accompanied by you explanatory Note .<br>
Then I asked myself the followings\<br>
What are these changes ?<br>
Who made them?<br>
why they were made?<br>
WHAT WAS THE REASONS TO MAKE SUCH CHANGES?<br>
if I misunderstood the issue, pls correct me<br>
Regards<br>
Kavouss<br>
<br>
<br>
2014-12-09 3:05 GMT+01:00 Narelle Clark < <a href="mailto:narelle.clark@accan.org.au">
narelle.clark@accan.org.au</a> > :<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
I seem to have missed the part where we agreed that the ICANN board needed to send a letter of endorsement or otherwise. Surely as a body independent of the ICG they can do whatever they see fit (and ought to).<br>
<br>
<br>
<br>
Why does it need to be referred to here?<br>
<br>
<br>
<br>
I can see a point in including a piece where we go through a review process with the ICANN board on the basis that it is, ultimately, the contracted party here.<br>
<br>
<br>
<br>
Regards<br>
<br>
<br>
<br>
Narelle<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
From: <a href="mailto:internal-cg-bounces@icann.org">internal-cg-bounces@icann.org</a> [mailto:
<a href="mailto:internal-cg-bounces@icann.org">internal-cg-bounces@icann.org</a> ] On Behalf Of Alissa Cooper<br>
Sent: Tuesday, 9 December 2014 2:45 AM<br>
To: ICG<br>
Subject: [Internal-cg] Please review: proposal finalization process<br>
Importance: High<br>
<br>
<br>
<br>
All,<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Please take a look at the proposal finalization process document and the thread below. We really need to wrap this up, hopefully on this week’s call or shortly thereafter.<br>
<br>
<br>
<br>
<br>
<br>
Thanks,<br>
<br>
<br>
Alissa<br>
<br>
<br>
<br>
<br>
<br>
Begin forwarded message:<br>
<br>
<br>
<br>
<br>
<br>
<br>
From: Alissa Cooper < <a href="mailto:alissa@cooperw.in">alissa@cooperw.in</a> ><br>
<br>
<br>
Subject: Re: [Internal-cg] Proposal finalization process v3<br>
<br>
<br>
Date: December 1, 2014 at 3:37:31 PM PST<br>
<br>
<br>
To: Paul Wilson < <a href="mailto:pwilson@apnic.net">pwilson@apnic.net</a> ><br>
<br>
<br>
Cc: ICG < <a href="mailto:internal-cg@icann.org">internal-cg@icann.org</a> ><br>
<br>
<br>
<br>
<br>
<br>
<br>
Hi Paul,<br>
<br>
<br>
<br>
<br>
<br>
I reviewed your proposed edits to v3 and my comments are below. I’ve also uploaded and attached an edited version that reflects my comments and includes the finalization process steps provided by Kuo. <
<a href="https://www.dropbox.com/home/CoordinationGroup/Proposal%20finalization%20process" target="_blank">
https://www.dropbox.com/home/CoordinationGroup/Proposal%20finalization%20process</a> ><br>
<br>
<br>
<br>
<br>
<br>
On Nov 9, 2014, at 4:58 PM, Paul Wilson < <a href="mailto:pwilson@apnic.net">pwilson@apnic.net</a> > wrote:<br>
<br>
<br>
<br>
<br>
<br>
Hi all,<br>
<br>
I’ve proposed a bunch of edits to this document, attached, and also in dropbox here:<br>
<br>
<a href="https://www.dropbox.com/s/wvemyk00s5l86w9/proposal-finalization-process-v3-pw.docx?dl=0" target="_blank">https://www.dropbox.com/s/wvemyk00s5l86w9/proposal-finalization-process-v3-pw.docx?dl=0</a><br>
<br>
<br>
Some of these changes reflect my understanding of the timeline, as shown in the Excel file here:<br>
<br>
<a href="https://www.dropbox.com/s/07zp3xlgx2uvwcs/TimelineDiscussion-v7.docx?dl=0" target="_blank">https://www.dropbox.com/s/07zp3xlgx2uvwcs/TimelineDiscussion-v7.docx?dl=0</a><br>
<br>
In particular this timeline show the release of a draft proposal in March, and a final proposal in June; so I’ve added these extra steps to the process.<br>
<br>
<br>
<br>
<br>
<br>
Agreed, good to have these other milestones in there.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Also, please note I’ve proposed a few substantial additional steps in this process:<br>
<br>
- A public call for comments on the community proposal development processes (deadline 31 Jan 2015); this will allow us to formally gather remaining concerns, or statements of support for the processes which produced community proposals.<br>
<br>
<br>
<br>
<br>
<br>
I have concerns about asking the communities to duplicate efforts here. RFP Section VI already asks the communities to document their processes, level of consensus achieved, and areas of contention or disagreement. We also made it explicit in the RFP that if
people felt that they could not provide comments within those processes, they could send them to the ICG forum <
<a href="http://forum.icann.org/lists/icg-forum/" target="_blank">http://forum.icann.org/lists/icg-forum/</a> > and we’ve been passing those on to the communities.<br>
<br>
<br>
<br>
<br>
<br>
The target deadline for RFP responses is 15 January, so I don’t think we want to ask people to separately document similar information in a parallel process that we run ourselves at the same time when we’re expecting the communities to be focusing on finishing
their RFP responses. I also do not think it’s appropriate for us to try to circumvent the community processes — if the process comments we receive after receiving the proposals themselves and the statements made in the proposals are inconsistent, it’s not
clear what we would do with that information.<br>
<br>
<br>
<br>
<br>
<br>
My edits in the attached reflect this view — I’ve re-combined into a single step 1 the ICG’s initial reviews of both process and substance.<br>
<br>
<br>
<br>
<br>
<br>
<br>
- A specific provision for ICG consultation with communities and other stakeholders during assessment of the first draft proposal.<br>
<br>
- Incorporating the ICANN meetings in February and June 2015 into the process as opportunities for (in Feb) communities to present their proposals to the ICANN audience, and then (in June) ICG to present the final transition proposal.<br>
<br>
- Presentation of the final proposal to the ICANN board, during a meeting with them; rather than mere “transmission” to them.<br>
<br>
<br>
<br>
<br>
<br>
I would prefer if we not be overly prescriptive about any of the above items, nor about the exact structure or format of any text we might draft to accompany the transition proposal. We have already declared in the timeline our intention to consult with everyone,
so I don’t think we need to say it again. Obviously we will be talking to people at various ICANN meetings, but there will surely be other venues where the proposal gets discussed (as it should be), so I’d rather not single out any particular meetings in this
document. And I’m not sure why we would need to specifically meet the ICANN Board in order to send them the final proposal, particularly in light the statement of finalization steps that we now have from Kuo.<br>
<br>
<br>
<br>
<br>
<br>
Looking forward to feedback from you and others.<br>
<br>
<br>
<br>
<br>
<br>
Thanks,<br>
<br>
<br>
Alissa<br>
<br>
<br>
<br>
_______________________________________________<br>
Internal-cg mailing list<br>
<a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/internal-cg" target="_blank">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
<br>
<br>
<br>
_______________________________________________<br>
Internal-cg mailing list<br>
<a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/internal-cg" target="_blank">https://mm.icann.org/mailman/listinfo/internal-cg</a><o:p></o:p></span></font></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><o:p> </o:p></span></font></p>
</div>
</div>
</div>
</body>
</html>