<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
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";}
span.EmailStyle18
{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"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If the DNSA is watching ICANN, and has the right to determine whether ICANN (in the DNSA’s view) has followed its processes, and can impliedly refuse to implement
changes that ICANN believes were properly arrived at (if the DNSA disagrees), I am more concerned than ever by the “single-stakeholder” (i.e., registries only) nature of the proposed DNSA.<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">Thanks for pointing out the NCUC meeting and transcript. In the meetings I attended in Singapore, I didn’t see a lot of traction for structural separation
of the IANA function of ICANN or for the creation of a new oversight body to replace the NTIA’s oversight function. But different meetings with different groups bring out different things. I see here that Larry doesn’t want to “put his thumb on the scale”
and encourages the debate. I think the NTIA is doing its best to step back and not “coach” the multistakeholder community. That is a good thing. Nothing is a priori off the table unless expressly stated in the NTIA’s press release and related documents.
Whether they will find either in scope at the end of the day, I can’t know for sure, but I’ve expressed my opinion.<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">Greg Shatan<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"><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""> Brenden Kuerbis [mailto:bnkuerbi@syr.edu]
<br>
<b>Sent:</b> Tuesday, April 01, 2014 10:49 AM<br>
<b>To:</b> Shatan, Gregory S.<br>
<b>Cc:</b> discuss@1net.org; ianatransition@icann.org<br>
<b>Subject:</b> Re: [IANAtransition] A Summary of IANA Oversight Transition Tasks and Issues<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, Mar 31, 2014 at 10:34 PM, Shatan, Gregory S. <<a href="mailto:GShatan@reedsmith.com" target="_blank">GShatan@reedsmith.com</a>> wrote:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><snip><o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p>Beyond that are the more inventive re-imaginings of IANA functions and oversight, such as removing IANA itself from ICANN and making it a stand-alone body (e.g., the "DNSA" proposal), which could make ICANN-without-IANA the overseer of this new IANA-without-ICANN,
and other ideas that the NTIA would probably find "out of scope."<o:p></o:p></p>
<p> <o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Two clarifications, just to set the record straight. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">First, "overseer" can be interpreted too broadly. The IGP proposal does not suggest a principal-agent relationship between the DNSA and ICANN. The DNSA would be contractually bound to implement changes that followed ICANN's defined policy
making process. If ICANN did not follow its defined process, then the DNSA would have a grievance. In this manner, the DNSA watches but does not direct ICANN.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Second, the NTIA has never said nor intimated that structural separation would be "out of scope". In fact, in an open discussion with the NCUC at Singapore, Asst Sec Strickling plainly stated that the benefits and costs of structural separation
is "a debate...the community should have." [1]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">---------------------------------------<br>
Brenden Kuerbis<br>
Postdoctoral Researcher, iSchool, Syracuse University <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Internet Governance Project || <a href="http://internetgovernance.org/" target="_blank">
http://internetgovernance.org</a><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">[1] <a href="http://singapore49.icann.org/en/schedule/tue-ncuc/transcript-ncuc-25mar14-en.pdf">http://singapore49.icann.org/en/schedule/tue-ncuc/transcript-ncuc-25mar14-en.pdf</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Beyond even that are the wholly unrelated, "let's change what we don't like about ICANN," "let's remake some or all of ICANN" and "let's blow up ICANN and start again" ideas. All
great fodder for IG-theorizing and even future activity, but not when we have such a significant project as that outlined above already on our hands.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">A similar exercise could be done for the transition of the Affirmation of Commitments from a US-ICANN document to a multiparty document (which might itself change significantly
or be replaced). <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Greg Shatan<o:p></o:p></p>
</div>
<p> <o:p></o:p></p>
<p align="center" style="text-align:center"><span style="font-family:"Arial","sans-serif"">* * *</span><o:p></o:p></p>
<p><span style="font-family:"Arial","sans-serif"">This E-mail, along with any attachments, is considered confidential and may well be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply
e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. Thank you for your cooperation.</span><o:p></o:p></p>
<p align="center" style="text-align:center"><span style="font-family:"Arial","sans-serif"">* * *</span><o:p></o:p></p>
<p><span style="font-family:"Arial","sans-serif"">To ensure compliance with Treasury Department regulations, we inform you that, unless otherwise indicated in writing, any U.S. Federal tax advice contained in this communication (including any attachments)
is not intended or written to be used, and cannot be used, for the purpose of (1) avoiding penalties under the Internal Revenue Code or applicable state and local provisions or (2) promoting, marketing or recommending to another party any tax-related matters
addressed herein.</span><o:p></o:p></p>
<p align="right" style="margin:0in;margin-bottom:.0001pt;text-align:right"><span style="font-size:7.5pt">Disclaimer Version RS.US.20.10.00</span><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>