<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 13px; font-family: Calibri, sans-serif;"><div>Milton,</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div 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"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div class="WordSection1"><div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><div><p class="MsoNormal"><span style="font-size: 10pt; font-family: Calibri, sans-serif; color: black;">As I mentioned at the microphone, my understanding of Larry's speech at the State of the Net was that the issue of whether or not there is separability isn't all
that germane to the question of acceptability of proposal, what matters in this context is whether or not the accountability requirements imposed by NTIA can be met with the resulting structures. That is, if you posit a world in which the RIRs can separate
themselves from ICANN, how can the RIRs/NRO guarantee the subsequent management of Internet Numbers resources are accountable to the global stakeholder community and are not subject to capture, not susceptible to double-dealing/corruption/influence-peddling,
etc.? <o:p></o:p></span></p></div><div><p class="MsoNormal"><span style="font-size: 10pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">MM: And as Mr. Woodcock replied to you, the numbers community (and I would say the names community too) knows what it needs and is capable of exercising the most
basic, fundamental form of accountability -- the ability to change providers.</span></p></div></div></div></div></div></blockquote></span><div><br></div><div>I've no doubt all the communities are well aware of their needs, but I believe Larry was suggesting accountability in the other direction. As Vint Cerf pointed out at the microphone during the ARIN meeting, there are more folks involved here than just those communities. My interpretation of what Larry said at the State of the Net, is that if a model that allows for separation is chosen, how will the communities (e.g., the naming community, the IETF, and the NRO) demonstrate accountability at least as strong as what ICANN provides _to the global stakeholder community_ if that separation occurs? </div><div><br></div><div>Regards,</div><div>-drc</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div 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"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div class="WordSection1"><div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"><div><p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> <o:p></o:p></span></p></div></div></div></div></div></blockquote></span><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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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></body></html>