<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 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;}
/* 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.EmailStyle17
{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 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">All:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I went through this document as quickly as I could. It’s in great shape overall. I made some minor edits to the clean version in the attached draft, with tracking
turned on. There are a couple of substantive changes I propose which I will discuss here:
<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">Para X028 currently says:<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">“All three communities determined that the global customers and partners of the IANA services and their communities of stakeholders are presently satisfied with
the performance of the IANA functions by the IANA department of ICANN. The combined proposal is not expected to impact that.”<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">This gives I think the (false) impression that the proposal just keeps everything the same and the customers didn’t want any change. However, all 3 communities
also made it clear that they want to be able to choose (or continue to choose) a different IFO should the need arise, a capability which does _<i>not</i>_ currently exist for numbers and names, but which is created by this proposal. Also if the customers wanted
no change then why did the proposal create PTI?<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">So on p. 28-9, paragraph 98 I edited the end of paragraph 98 to read:<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">98 All three communities determined that the global customers and partners of the IANA services, including the gTLD and ccTLD registries and their communities
of stakeholders; the RIRs; and the IETF are presently satisfied with the performance of the IANA functions by the IANA department of ICANN. The combined proposal is structured such that the PTI will continue to provide the IANA functions to its global customers
and partners post-transition in essentially the same manner as ICANN’s IANA department does today. In the names community, IANA customers expressed support for a clearer separation between ICANN as policy developer and IANA as implementer, and the PTI separation
accomplishes this. Also, the proposal makes it possible for each operational community to choose a different IFO should the need arise, a capability which does not currently exist for numbers and names. Thus the needs and expectations of the global customers
and partners should continue to be satisfied after the transition.<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">Also, on p. 30, para 108 implementation list I believe we need to add:<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">• Transfer of the IANA-related intellectual property and domain names to the entity.<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"><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">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Internal-cg [mailto:internal-cg-bounces@ianacg.org]
<b>On Behalf Of </b>Alissa Cooper<br>
<b>Sent:</b> Monday, October 26, 2015 1:19 PM<br>
<b>To:</b> IANA etc etc Coordination Group<br>
<b>Subject:</b> [Internal-cg] Proposal for final review<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please find attached a redlined and clean copy of the proposal reflected all changes agreed at the F2F. There are still a few spacing and footnote numbering issues to be worked out once the secretariat produces the PDF but otherwise this
is the version intended for publication with our agreed status update announcement on October 29.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If you see any errors in this version, please make them known on the mailing list by 23:59 UTC on October 28. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<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>
<p class="MsoNormal">Dropbox:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://www.dropbox.com/s/yhvx3pl8hx2oju0/IANA-transition-proposal-v8.docx?dl=0">https://www.dropbox.com/s/yhvx3pl8hx2oju0/IANA-transition-proposal-v8.docx?dl=0</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="https://www.dropbox.com/s/pj6s0igu8s8k4tq/IANA-transition-proposal-v8-clean.docx?dl=0">https://www.dropbox.com/s/pj6s0igu8s8k4tq/IANA-transition-proposal-v8-clean.docx?dl=0</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>