<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Verdana;
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
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;}
--></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">Let me reiterate an important detail that many seem to be overlooking.
<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="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The RIRs CRISP team proposed the following:
<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="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">“The Internet Number Community proposes that a new contract be established between the IANA Numbering Services Operator
and the five RIRs. The following is a proposal to replace the current NTIA IANA agreement with a new contract that more directly reflects and enforces the IANA Numbering Services Operator’s accountability to the Internet Number Community….</span></font><a name="_TOC31559"><font size="2" color="#0b0b0b" face="Arial"><span style="font-size:11.0pt;font-family:"Arial",sans-serif;color:#0B0B0B">
</span></font></a><font size="2" color="#5b9bd5" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F4E79;mso-style-textfill-fill-color:#1F4E79;mso-style-textfill-fill-alpha:100.0%"><font color="black"><span style="color:windowtext">It
is expected that the RIRs, as the contractual party of this agreement, will draft the specific language of this agreement.</span></font></span></font><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="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="MsoNormal"><font size="2" color="#1f497d" face="Calibri"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">New. Contract. Therefore it would not be difficult at all for the RIRs to develop this new contract in a way that
named PTI, rather than ICANN Inc., as the contractor. Since the proposed PTI is the same unit as the current ICANN IANA department, and they are happy with that service, I see no reason why the RIRs would have a problem with 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="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>
<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>
<div>
<p class="MsoNormal"><font size="2" face="Verdana"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">1. ICANN retains the contracts with the RIRs and IETF, with a minor amendment allowing ICANN to offer the service, but have the service fulfilled
by its wholly-controlled affiliate (or wholly-owned subsidiary) PTI.<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Verdana"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">2. ICANN enters into an "assignment and assumption" agreement whereby PTI takes over ICANN's position in the agreements.<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Verdana"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">3, ICANN and the RIRs/IETF terminate the current agreements, and PTI enters into new agreements with the RIRs and IETF.<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Verdana"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Verdana"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">The first option fits the principle of "change as little as possible (and explain any change you make".<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Verdana"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">The second option fits the principle of "make PTI as easily separable from ICANN as possible."<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="2" face="Verdana"><span style="font-size:9.5pt;font-family:"Verdana",sans-serif">The third option fits the principle of "let's make everything messy and complicated."<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Verdana"><span style="font-size:12.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></font></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><font size="3" face="Arial"><span style="font-size:12.0pt;font-family:"Arial",sans-serif"></span></font><font face="Verdana"><span style="font-family:"Verdana",sans-serif">Greg</span></font><font face="Arial"><span style="font-family:"Arial",sans-serif"></span></font><font face="Verdana"><span style="font-family:"Verdana",sans-serif"><o:p></o:p></span></font></p>
</div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><br clear="all">
<o:p></o:p></span></font></p>
<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">On Tue, Apr 7, 2015 at 7:16 PM, Avri Doria <<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>> wrote:<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-right:0in">
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Hi,<br>
<br>
One of my comment for the Sidley report is this assumption that the contracts would move to IANA.<br>
<br>
I see no reason for this to happen unless the IETF/IAB & RIRs/CRISP want them to. It seems to me that the contracts could remain with ICANN and that ICANN would use the affiliate to do the work.<br>
<br>
avri<br>
<br>
<o:p></o:p></span></font></p>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">On 07-Apr-15 15:29, Andrew Sullivan wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">Hi,<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt"><o:p> </o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">On Mon, Apr 06, 2015 at 11:04:14AM +0200, Lise Fuhr wrote:<o:p></o:p></span></font></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">Please see the attached initial discussion draft of the two models from our legal counsel.<o:p></o:p></span></font></pre>
</blockquote>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">Thanks for this. I've read it. I have some questions. Questions for<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">Sidley are listed, and then some observations for our own discussion<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">(which needn't take up Sidley's time) follow when appropriate in<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">square brackets.<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt"><o:p> </o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">In I.A, particularly in numbers 4 and 6, I can't tell whether the<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">assumption is that there are new agreements between PTI and the RIRs,<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">and PTI and IETF. I think the fact that PTI is a new legal entity<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">means that new agreements would be required. Is that correct? [The<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">reason I ask this is because there is a possible risk of things coming<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">apart if the other operational communities need to be engaged in a new<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">negotiation. If PTI just takes the existing agreements and does a<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">global search and replace for ICANN with PTI, that's nice, but it<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">doesn't solve everything. For instance, the IETF would have to<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">publish a new version of RFC 2860. It's worth remembering that every<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">grievance everyone has with an existing document comes into play once<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">the document is opened for editing.]<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt"><o:p> </o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">By way of comparison, in II.B, does using Functional Separation permit<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">ICANN to continue working under its existing MoUs? I'd assume yes,<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">because AFAIK none of the existing agreements specify the internal<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">arrangements of how ICANN delivers the service. [Notwithstanding<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">Milton's point about getting it "right", given the timeline there is a<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">significant advantage to not having to negotiate, I think, no?]<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt"><o:p> </o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">III.C talks about CSC. In the case of a full legal separation with<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">independent governance, would the CSC be needed at all? Presumably<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">the arrangements between PRI and their customers would be a<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">contractual one, and as such the management of such contractual<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">disputes ought to be via those contracts, and not through an extra<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">body. Or is the point that the way such a contractual arrangement<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">would solve such disputes ought to be along the lines of the CSC?<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt"><o:p> </o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">In III.D.2 there is a question about "ultimate accountability over<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">ICANN's stewardhip". I'm not entirely sure which cases this applies<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">to. If there is a legal separation, how is this question relevant for<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">CWG? Under the legal separation described, PTI becomes the new IANA<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">functions operator. If there's full independent governance of PTI,<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">for instance, isn't ICANN's stewardship completely gone -- it has only<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">responsibility for policy, and not for IANA operation at all, right?<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">Is that part of the point of this question?<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt"><o:p> </o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">On III.I, I'm not sure what the difference is between CSC and IRP.<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">Why are both things needed? <o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt"><o:p> </o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">Best regards,<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt"><o:p> </o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt">A<o:p></o:p></span></font></pre>
<pre><font size="2" face="Courier New"><span style="font-size:10.0pt"><o:p> </o:p></span></font></pre>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><br>
<br>
<o:p></o:p></span></font></p>
<div class="MsoNormal" align="center" style="text-align:center"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">
<hr size="2" width="99%" noshade="" style="color:#909090" align="center">
</span></font></div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td style="padding:0in 11.25pt 0in 6.0pt">
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><a href="http://www.avast.com/" target="_blank"><span style="border:solid windowtext 1.0pt;padding:0in;text-decoration:none"><img border="0" width="100" height="100" id="_x0000_i1026" src="cid:~WRD000.jpg" alt="Image removed by sender. Avast logo"></span></a><o:p></o:p></span></font></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p><font size="3" color="#3d4d5a" face="Calibri"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif;color:#3D4D5A">This email has been checked for viruses by Avast antivirus software.
<br>
<a href="http://www.avast.com/" target="_blank">www.avast.com</a> <o:p></o:p></span></font></p>
</td>
</tr>
</tbody>
</table>
<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" style="margin-bottom:12.0pt"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><br>
_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org" target="_blank">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></span></font></p>
</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>
</div>
</body>
</html>