<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=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<![if !supportAnnotations]>
<style id="dynCom" type="text/css"><!-- --></style>
<script language="JavaScript"><!--
function msoCommentShow(anchor_id, com_id)
{
if(msoBrowserCheck())
{
c = document.all(com_id);
a = document.all(anchor_id);
if (null != c && null == c.length && null != a && null == a.length)
{
var cw = c.offsetWidth;
var ch = c.offsetHeight;
var aw = a.offsetWidth;
var ah = a.offsetHeight;
var x = a.offsetLeft;
var y = a.offsetTop;
var el = a;
while (el.tagName != "BODY")
{
el = el.offsetParent;
x = x + el.offsetLeft;
y = y + el.offsetTop;
}
var bw = document.body.clientWidth;
var bh = document.body.clientHeight;
var bsl = document.body.scrollLeft;
var bst = document.body.scrollTop;
if (x + cw + ah / 2 > bw + bsl && x + aw - ah / 2 - cw >= bsl )
{ c.style.left = x + aw - ah / 2 - cw; }
else
{ c.style.left = x + ah / 2; }
if (y + ch + ah / 2 > bh + bst && y + ah / 2 - ch >= bst )
{ c.style.top = y + ah / 2 - ch; }
else
{ c.style.top = y + ah / 2; }
c.style.visibility = "visible";
} } }
function msoCommentHide(com_id)
{
if(msoBrowserCheck())
{
c = document.all(com_id);
if (null != c && null == c.length)
{
c.style.visibility = "hidden";
c.style.left = -1000;
c.style.top = -1000;
} }
}
function msoBrowserCheck()
{
ms = navigator.appVersion.indexOf("MSIE");
vers = navigator.appVersion.substring(ms + 5, ms + 6);
ie4 = (ms > 0) && (parseInt(vers) >= 4);
return ie4;
}
if (msoBrowserCheck())
{
document.styleSheets.dynCom.addRule(".msocomanchor","background: infobackground");
document.styleSheets.dynCom.addRule(".msocomoff","display: none");
document.styleSheets.dynCom.addRule(".msocomtxt","visibility: hidden");
document.styleSheets.dynCom.addRule(".msocomtxt","position: absolute");
document.styleSheets.dynCom.addRule(".msocomtxt","top: -1000");
document.styleSheets.dynCom.addRule(".msocomtxt","left: -1000");
document.styleSheets.dynCom.addRule(".msocomtxt","width: 33%");
document.styleSheets.dynCom.addRule(".msocomtxt","background: infobackground");
document.styleSheets.dynCom.addRule(".msocomtxt","color: infotext");
document.styleSheets.dynCom.addRule(".msocomtxt","border-top: 1pt solid threedlightshadow");
document.styleSheets.dynCom.addRule(".msocomtxt","border-right: 2pt solid threedshadow");
document.styleSheets.dynCom.addRule(".msocomtxt","border-bottom: 2pt solid threedshadow");
document.styleSheets.dynCom.addRule(".msocomtxt","border-left: 1pt solid threedlightshadow");
document.styleSheets.dynCom.addRule(".msocomtxt","padding: 3pt 3pt 3pt 3pt");
document.styleSheets.dynCom.addRule(".msocomtxt","z-index: 100");
}
// --></script>
<![endif]>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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";}
p.MsoCommentText, li.MsoCommentText, div.MsoCommentText
{mso-style-priority:99;
mso-style-link:"Comment Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Calibri","sans-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;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.CommentTextChar
{mso-style-name:"Comment Text Char";
mso-style-priority:99;
mso-style-link:"Comment Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:266038687;
mso-list-type:hybrid;
mso-list-template-ids:-174168144 -2068402394 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:Arial;}
@list l1
{mso-list-id:1231842322;
mso-list-type:hybrid;
mso-list-template-ids:-469440484 1756633714 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:Arial;}
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 style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Many thanks Alissa and everyone else for the comments ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I almost agree to all and have included my own inline below ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Apologies for the late sending ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Looking forward to further discuss on the call ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Kind Regards<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>--Manal <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
internal-cg-bounces@icann.org [mailto:internal-cg-bounces@icann.org] <b>On
Behalf Of </b>Alissa Cooper<br>
<b>Sent:</b> Wednesday, December 10, 2014 1:20 AM<br>
<b>To:</b> ICG<br>
<b>Subject:</b> [Internal-cg] Proposal finalization process v4<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have consolidated the comments and edits from Milton,
Adiel, Joe, and Russ in the attached v4 <<a
href="https://www.dropbox.com/home/CoordinationGroup/Proposal%20finalization%20process">https://www.dropbox.com/home/CoordinationGroup/Proposal%20finalization%20process</a>>.
I accepted changes on all the text where no one had commented for easier
reading. I also inserted a few comments/edits of my own the proposed changes,
which I repeat below.<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Step 1a, bullet 3: Milton suggested using "Whether the
proposal obtained consensus” instead of “How the proposal obtained
consensus.” <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I am fine with “whether.” I would also be fine
with “Whether and how.” In the RFP, we ask the communities to
explain “the steps that were taken to develop the proposal and to determine
consensus.” I would consider a list of those steps to be the
“how.”<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[MI]: I'm fine with either .. Although I think the point is that
we want to ensure 'Whether' the proposal obtained consensus (the steps of which
will describe 'How' of course as you rightly mentioned) yet we do not have agreed
detailed criteria to evaluate the 'How' steps .. so maybe we should not be focusing
on the steps and be more concerned with the result .. <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal>Step 1b: Adiel suggested adding a bullet about
timeliness. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I do not think this is actionable and so should not be
included. If we get a proposal after the target deadline, I do not believe we
are in a position to do anything other than start conducting the assessment in
step 1. Of course, if we get a proposal many weeks/months after the target
deadline, it will create some chaos for all of the steps afterward, but I
don’t really see a lot of value in specifying how we will handle every
possible case of that sort that could arise depending on the exact timing and
sequence of the arrival of the component proposals.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[MI]: Agree with your reasons for not adding this ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal>Step 2: Adiel questioned whether the statement that the
ICG’s role “is not to draft a single transition proposal” is
accurate.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I believe it is accurate, in the sense that we are not
“drafting” or writing anything of our own. I added the words
“of its own” to the end of that phrase to try to make this more
clear.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[MI]: Agree with you but also see Adiel's point .. The draft is
misleading until you finish reading whole sentence, which is fine for me .. But
I can suggest the following alternative:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>"According to the ICG Charter, its role is to assemble a
single transition proposal from component proposals, not to draft its own."
<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal>Step 2: Adiel questioned the use of the word
“unifying.”<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I agree that “unifying” and
“uniform” are confusing. I believe our task is one of assembly. Our
goal is to end up with one document, but not to massage the text of the
component proposals to achieve “unity.” I have replaced the word
“unified” in this section with the word “single” to
make this clear. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[MI]: Agree with you and Adiel ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal>Step 2a: Joe inserted “possibly conflicting” as
a qualifier for “overlaps”<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I don’t understand what a conflicting overlap is, and
I think the proposals need to have a coherent story about all overlaps. So I
disagree with this addition.<span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[MI]: I noted the rest of the discussion on this in later emails
.. So basically you and Joe are saying the same thing, whether, in case of
overlaps, the different proposals are suggesting the same or conflicting things
.. Yet I would suggest saying here "any conflicting overlaps" rather
than "all possibly conflicting overlaps" .. The reason is that the
latter gives the feeling that we already expect overlaps and we already expect
that those overlaps are suggesting conflicting proposals .. Is this the case? Or
have I misunderstood it?<o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Step 2b: Joe asked whether we need to cross-reference the
ICANN accountability work.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I think this is already covered by the fact that we are
already asking "Do the proposals together include appropriate and properly
supported independent accountability mechanisms for running the IANA
function?”<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[MI]: In fact, I have a question on the second part stating: "Are
there any gaps in overall accountability under the single proposal?" .. How
are we going to handle such gaps? Will we go back to the relevant operational
community only and they coordinate with CCWG-Accountability if necessary or we
will coordinate directly with both?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal>Step 2c: There has been list discussion between Joe and Russ
about testing.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>I suggested some text as a middle ground approach. In the
RFP we do ask the communities to describe any testing they do. I’m not
quite sure how the test results could conflict with each other or otherwise be
problematic in combination, but I’m happy to check for that when
we’re assembling the single proposal.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[MI]: I'm fine with the new text you proposed for Step 2c ..<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[MI]: Step 3: I have a problem understanding the highlighted part
of this sentence: "The ICG will coordinate with the operational
communities <b>to have public comments addressed within their components</b>
before assembling an interim final proposal."<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Is this meant to say: <o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>"The ICG will
coordinate with the operational communities <b>to have public comments on their
components addressed</b> before assembling an interim final proposal."? OR<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>"The ICG will
coordinate with the operational communities to have public comments addressed within
their <b>communities</b> before assembling an interim final proposal."<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal>Step 5: I have made the latest changes suggested on the list
by Milton, which I think address everyone’s concerns.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>[MI]: Agree with Milton's proposed text, but I have 2 remarks:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I'm more inclined to
concatenate the first 2 bullets (5.a & 5.b) into one that reads "The
ICG will post the final proposal on its public web site and transmit it to the
ICANN Board." .. The rationale is that I feel those are simultaneous steps
whereas as the bullets stands now they give the feeling that those are 2
sequential steps that may have a period of time in between ..<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><span
style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span dir=LTR></span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I'm also inclined to
precede bullet 5.c with "As conveyed/communicated by the ICANN Board,"
.. so the whole sentence would read " As conveyed/communicated by the
ICANN Board, the 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 " .. The rationale here is, rather than
speaking on behalf of the Board or say that we are expecting, that we accurately
describe the situation .. This is what was conveyed to us from the Board .. Not
sure though, language wise, whether it's better/more accurate to say convey, communicate
or something else ..<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Alissa<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<div style='mso-element:comment-list'><![if !supportAnnotations]>
<hr class=msocomoff align=left size=1 width="33%">
<![endif]></div>
</body>
</html>