<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 12 (filtered medium)">
<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";}
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;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.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:419914330;
        mso-list-template-ids:-1165749946;}
@list l0:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l1
        {mso-list-id:814226229;
        mso-list-template-ids:-618518872;}
@list l1:level1
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:.5in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
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=Section1>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Just recognized that my response to this thread did not address Wolf-Ulrich's
point regarding 'implementation' ..<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I'm not sure whether Wolf-Ulrich is referring to the same
session, but I recall that this was also raised as a question by Larry to the
co-chairs of the CWG at a GAC session, I believe on Sun. ..<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I agree with Milton this needs further scrutiny, as we need to
have a common understanding on what we mean by implementation here and how does
this align with NTIA's expectation ..<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</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>&nbsp;</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>WUKnoben<br>
<b>Sent:</b> Friday, February 13, 2015 4:52 AM<br>
<b>To:</b> WUKnoben; internal-cg@icann.org<br>
<b>Subject:</b> Re: [Internal-cg] ICANN52<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<div>

<div>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>In
my assessment to Larry Stricklings remarks I was erroneously referring to the
“names and protocols” proposals (see attached). I meant the “<u>numbers</u> and
protocols” proposals.<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Calibri","sans-serif";
color:black'>This is owed to a long week of discussions around the matter.<br>
<br>
Best regards<br>
<br>
Wolf-Ulrich<o:p></o:p></span></p>

</div>

<div>

<div>

<div>

<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:black'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<div>

<p class=MsoNormal style='background:whitesmoke'><b><span style='font-size:
10.0pt;font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> <a
href="mailto:wolf-ulrich.knoben@t-online.de"
title="wolf-ulrich.knoben@t-online.de">WUKnoben</a> <o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='background:whitesmoke'><b><span style='font-size:
10.0pt;font-family:"Tahoma","sans-serif";color:black'>Sent:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> Friday,
February 13, 2015 12:10 AM<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='background:whitesmoke'><b><span style='font-size:
10.0pt;font-family:"Tahoma","sans-serif";color:black'>To:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> <a
href="mailto:internal-cg@icann.org" title="internal-cg@icann.org">internal-cg@icann.org</a>
<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal style='background:whitesmoke'><b><span style='font-size:
10.0pt;font-family:"Tahoma","sans-serif";color:black'>Subject:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> ICANN52<o:p></o:p></span></p>

</div>

</div>

</div>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

</div>

</div>

<div>

<div>

<div>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>Dear
colleagues,<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>my
take from the ICANN52 meeting in Singapore re the IANA Stewardship Transition
and the future ICG related work:<o:p></o:p></span></p>

</div>

<div>

<ul type=disc>
 <li class=MsoNormal style='color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
     auto;mso-list:l0 level1 lfo1'><span style='font-family:"Calibri","sans-serif"'>see
     <strong><span style='font-family:"Calibri","sans-serif"'>statement from
     Steve Crocker</span></strong>, ICANN Board Chair:<o:p></o:p></span></li>
</ul>

</div>

<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:black'>&lt;&lt;<o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><em><span
style='color:black'>We have received several questions requesting clarification
as to how ICANN will handle receipt of the proposal from the ICG and the Work
Stream 1 proposal from the CCWG.&nbsp; We hope the following will be helpful.</span></em><span
style='color:black'><o:p></o:p></span></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><em><span
style='color:black'>NTIA is expecting coordinated proposals from both
groups.&nbsp; They cannot act on just one.&nbsp; Further, they expect the ICG
proposal will take into account the accountability mechanisms proposed by the
CCWG.&nbsp; We are heartened by the close coordination between the groups,
including liaisons from the ICG to the CCWG. ICANN is expecting to receive both
proposals at roughly the same time.&nbsp; When ICANN receives these proposals,
we will forward them promptly and without modification to NTIA. As we have
previously stated, if we do submit the proposals with an accompanying
communication of comments, they will be on points we had already shared with
the community during the development of the proposals.</span></em><span
style='color:black'><o:p></o:p></span></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><em><span
style='color:black'>We therefore encourage the groups to continue coordinating
closely to ensure ICANN receives the proposals together and is able to provide
them to NTIA in a coordinated manner.</span></em><span style='color:black'><o:p></o:p></span></p>

<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><em><span
style='color:black'>With respect to improvements in our accountability, we are
definitely open to improvements</span></em><span style='color:black'>.<o:p></o:p></span></p>

</blockquote>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>&nbsp;<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>&nbsp;&nbsp;&nbsp;
He’s referring to the Names Community Proposal as an output from the
CWG-stewardship and the CCWG-accountability.<o:p></o:p></span></p>

</div>

<div>

<p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:black'>&nbsp;&nbsp;&nbsp;
Consequently the ICG would have to accomodate the overall timeline accordingly.<o:p></o:p></span></p>

</div>

<div>

<ul type=disc>
 <li class=MsoNormal style='color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:
     auto;mso-list:l1 level1 lfo2'><strong><span style='font-family:"Calibri","sans-serif"'>Larry
     Strickling, NTIA</span></strong><span style='font-family:"Calibri","sans-serif"'>
     Assistant Secretary, in a session on Sunday, 09 Feb., pointed out that
     NTIA is expecting a common proposal from the three communities (protocols,
     numbers, names). The proposal as a whole should be ready for
     implementation.<o:p></o:p></span></li>
</ul>

</div>

<div>

<p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Calibri","sans-serif";
color:black'>&nbsp;&nbsp;&nbsp; From this point of view I wonder whether the
names and protocol proposals delivered in the present version reach this level
of readiness. I’d like to suggest beginning a related ICG discussion about.
this item and the potential consequences.<br>
<br>
Best regards<br>
<br>
Wolf-Ulrich<o:p></o:p></span></p>

</div>

</div>

</div>

</div>

</div>

</div>

</div>

</body>

</html>