<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 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:11.0pt;
font-family:"Calibri","sans-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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
span.emailstyle17
{mso-style-name:emailstyle17;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Let me elaborate a little more now that I am on my laptop and not just my phone.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">First of all, because I was also not in Frankfurt nor able to participate much remotely and have not yet had time to review the results of the F2F in detail, my initial thoughts need to be taken in that context.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">But to the extent that the recommendations that came out of the F2F meeting do not reflect a strong requirement that the IANA Transition should not happen before broader independent ICANN Accountability mechanisms
are assured, then I believe that they ignore one of the clear requirements that that the community in near unanimity stated in public comments and dialog. And I also think that the IANA Stewardship Transition CWG Charter allowed for connection of the two
separate work efforts in that way.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">That said, I will try to catch up in the next few days. And I believe that we have plenty of time now to correct this if in fact it is not reflected sufficiently in the F2F results.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Finally, regardless of the above, I want to thank and compliment all of those who worked very long and hard in the F2F meeting. You had a huge task in an extremely short timeframe and I am confident that you
produced draft recommendations that the community can now review, comment and improve.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<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""> cwg-stewardship-bounces@icann.org [mailto:cwg-stewardship-bounces@icann.org]
<b>On Behalf Of </b>Gomes, Chuck<br>
<b>Sent:</b> Thursday, November 20, 2014 9:41 PM<br>
<b>To:</b> Milton L Mueller; 'jonathan.robinson@ipracon.com'<br>
<b>Cc:</b> cwg-stewardship@icann.org<br>
<b>Subject:</b> Re: [CWG-Stewardship] scope and accountability<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif"">I have the same concern as Milton.<span style="color:#1F497D"><o:p></o:p></span></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:#575757">Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><br>
<br>
-------- Original message --------<br>
From: Milton L Mueller <<a href="mailto:mueller@syr.edu">mueller@syr.edu</a>> <br>
Date:11/20/2014 6:17 PM (GMT-05:00) <br>
To: "'jonathan.robinson@ipracon.com'" <<a href="mailto:jonathan.robinson@ipracon.com">jonathan.robinson@ipracon.com</a>>
<br>
Cc: <a href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a> <br>
Subject: [CWG-Stewardship] scope and accountability <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal">Jonathan<o:p></o:p></p>
<p class="MsoNormal">I’ve been reading the transcripts of the Frankfurt meeting. Sorry I couldn’t be there to correct what I saw as an oversight or error in the discussion. Although others committed the same error, it was most concisely expressed in a quote
from you, so that’s why I am picking on you ;-) You said: <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">“Then there's the broader ICANN accountability issue, which I think is beyond the remit of this committee and into the next working group, except to the extent it deals with accountability for IANA functions.”
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">This implies that IANA accountability and ICANN accountability are two completely separate things. The problem is that they are interrelated. This interdependency is explicitly recognized in the ICG’s charter:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">“The IANA stewardship transition process is taking place alongside a parallel and related process on enhancing ICANN accountability. While maintaining the accountability of Internet identifier governance is central to both processes, this
group’s scope is focused on the arrangements required for the continuance of IANA functions in an accountable and widely accepted manner after the expiry of the NTIA-ICANN contract. Nevertheless, the two processes are interrelated and interdependent and should
appropriately coordinate their work.”<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Of course the IANA transition process cannot fix all the accountability issues in ICANN’s policy making process, nor do we want it to. But “interrelated and interdependent” means that how we handle accountability in the IANA transition
will have direct impact on the enhanced accountability process for the rest of ICANN. As a simple example, if the IANA transition merely hands over control of IANA to ICANN with no oversight or separability whatsoever, then the enhanced accountability CWG
will have a _<i>lot</i>_ more urgent work to do, especially in track 1. On the other hand, if the IANA transition process allows the community to take IANA away from a misbehaving ICANN, or otherwise leverages the control of IANA to ensure that ICANN complies
with certain good governance requirements, then the IANA transition has implications for ICANN accountability, not just IANA accountability.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The clear intent of the ICG charter is to recognize that both ICANN and IANA accountability are related. The creation of two tracks in the ICANN accountability CWG - one that must be completed before the IANA transition is effectuated and
the other involving reforms that can wait until after the transition - is another explicit recognition of the interdependency of the IANA and ICANN accountability. The simple fact is that the IANA transition process _<i>must</i>_ take into account the broader
implications of its proposed changes for the overall accountability of ICANN.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I hope the CWG Frankfurt meeting’s failure to recognize the interdependency this did not prevent it from making progress in other areas.
<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Milton L Mueller<o:p></o:p></p>
<p class="MsoNormal">Laura J. and L. Douglas Meredith Professor<o:p></o:p></p>
<p class="MsoNormal">Syracuse University School of Information Studies<o:p></o:p></p>
<p class="MsoNormal"><a href="http://faculty.ischool.syr.edu/mueller/">http://faculty.ischool.syr.edu/mueller/</a><o:p></o:p></p>
<p class="MsoNormal">Internet Governance Project<o:p></o:p></p>
<p class="MsoNormal"><a href="http://internetgovernance.org/">http://internetgovernance.org</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>