<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:"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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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;
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas",serif;
color:black;}
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 WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Each OC has its own procedures for ensuring continuity and stability in their proposals.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">E.g., the IETF requires ICANN to commit to those parts of the legacy IANA contract that require cooperation with the new operator and continuity; the RIR proposal
has similar arrangements. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The biggest transition compatibility problem that the different OCs and ICG identified was the trademarks and domains. If these are moved to an independent (non-IFO)
trust, that problem should be resolved. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">What we want to avoid is any statement or implication that any one OC has to get the approval of the other OCs to change their IANA functions operator. That won’t
fly politically, as we have learned several times.<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">--MM<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 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><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"> Matthew Shears [mailto:mshears@cdt.org]
<br>
<b>Sent:</b> Friday, September 4, 2015 5:02 AM<br>
<b>To:</b> Mueller, Milton L; NCSG-DISCUSS@LISTSERV.SYR.EDU<br>
<b>Subject:</b> Re: [NCSG-Discuss] [Consultation] Important NCSG draft comment on ICG IANA stewardship proposal<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Milton, thanks for the comments, etc.<br>
<br>
I don't have any misconception on this matter. I am just raising a concern I see when it comes to moving to another IFO and how such a change would occur and whether there is a need to coordinate such a change to mitigate any issues related to continuity and
stability - that's all. If we believe that this is not the case nor necessary then fine we can delete.<br>
<br>
<u>Others should review/edit the comments and see if they can be supported as an NCSG input - we don't much time - THANKS!</u><br>
<br>
Matthew<o:p></o:p></p>
<div>
<p class="MsoNormal">On 9/3/2015 9:14 PM, Mueller, Milton L wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>I went over it. Made some additions, fleshed out a few things. <o:p></o:p></pre>
<pre>But we do have a serious disagreement. Whoever wrote the initial draft is laboring under the misconception that any change in IANA function operators must be coordinated across all three operational communities. This is just not true. The plan (and at least 2 of the 3 OCs involved) assumes that each OC has the ability to select a new IANA functions operator independently for its own part of the functions. None of the numbers and protocols people have expressed any concern about the compatibility implications of doing that. It seems to be only names people who are worried about that.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>I would object to all of that language but before deleting it wanted to flag this issue on the list for discussion. <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>-----Original Message-----<o:p></o:p></pre>
<pre>From: NCSG-Discuss [<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU</a>] On Behalf<o:p></o:p></pre>
<pre>Of Matthew Shears<o:p></o:p></pre>
<pre>Sent: Thursday, September 3, 2015 10:11 AM<o:p></o:p></pre>
<pre>To: <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><o:p></o:p></pre>
<pre>Subject: Re: [NCSG-Discuss] [Consultation] Important NCSG draft comment<o:p></o:p></pre>
<pre>on ICG IANA stewardship proposal<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks Rafik - this is very "drafty" so please consider it a strawman.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Matthew<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>On 9/3/2015 2:47 PM, Rafik Dammak wrote:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Hi everyone,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Thanks to Matt, we got a NCSG draft comment for the ICG proposal and<o:p></o:p></pre>
<pre>we should submit this asap (the deadline for submission is 8th Sept).<o:p></o:p></pre>
<pre>the document is here<o:p></o:p></pre>
<pre><a href="https://docs.google.com/document/d/14wO_tu">https://docs.google.com/document/d/14wO_tu</a>-<o:p></o:p></pre>
</blockquote>
<pre>liqEqzlMSm_NnGD4_BME7f7Fhg_<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Z7d1lwYBc/edit please review it and share your comments. the document<o:p></o:p></pre>
<pre>is in suggestion mode to make the review and input more easier.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>For reminder, Milton is our representative in the ICG.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Best Regards,<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Rafik<o:p></o:p></pre>
</blockquote>
<pre><o:p> </o:p></pre>
<pre>--<o:p></o:p></pre>
<pre>Matthew Shears<o:p></o:p></pre>
<pre>Global Internet Policy and Human Rights<o:p></o:p></pre>
<pre>Center for Democracy & Technology (CDT)<o:p></o:p></pre>
<pre>+ 44 (0)771 247 2987<o:p></o:p></pre>
</blockquote>
</blockquote>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Matthew Shears<o:p></o:p></pre>
<pre>Global Internet Policy and Human Rights<o:p></o:p></pre>
<pre>Center for Democracy & Technology (CDT)<o:p></o:p></pre>
<pre>+ 44 (0)771 247 2987<o:p></o:p></pre>
</div>
</div>
</body>
</html>