<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=iso-8859-1"><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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:143162693;
mso-list-type:hybrid;
mso-list-template-ids:-549146918 134807567 134807577 134807579 134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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 bgcolor=white lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Milton, Mathieu & Colleagues,<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'>Some thoughts in relation to this topic:<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, having read Milton’s email below, I can’t see that I disagree with any of it and it’s unfortunate if my wording from the Frankfurt meeting does appear to do so or is taken to mean that I do.<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'>With regard to where I believe we are currently in the work of the IANA transition CWG, and recognising that this is still work in progress, I see the following critical accountability levers:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>Operational accountability. This will be driven at the first level by the IANA Customer Steering Committee and, to the extent that this Committee does not achieve satisfactory outcomes, can be escalated to the (Multistakeholder) IANA Periodic Review Team.<o:p></o:p></span></p><p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>Overall performance accountability. This will be monitored by the IANA Periodic Review Team, both periodically and on an ad-hoc basis (in response to escalation from the IANA Customer Steering Committee) and the ultimate sanction of this group is twofold:<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>a.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>The ability to terminate the contract mid-term (to the extent that such contractual provisions are written into the contract)<o:p></o:p></span></p><p class=MsoListParagraph style='margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='color:#1F497D'><span style='mso-list:Ignore'>b.<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='color:#1F497D'>The ability to contract with a new provider at the term of the contract (consistent with the contract and with processes to be determined by the IANA Periodic Review Team).<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'>Notwithstanding the above substantial accountability levers, there is the issue highlighted from the Charter of the CWG by Milton i.e. as follows:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></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><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Considering the above, I believe that the work of the IANA Stewardship CWG to date, is largely on track in relation to the following charter provision:<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'>“ … </span>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 … <span style='color:#1F497D'>”<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'>However, I believe we do need more work here:<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'>“</span>Nevertheless, the two processes are interrelated and interdependent and should appropriately coordinate their work.<span style='color:#1F497D'>”<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'>And it is this second point which now needs to be picked up as a matter of urgency and I’d welcome any guidance on this. One factor in doing so is that the Accountability CWG has only very recently had its charter approved by the chartering organisations.<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, please note the reference in the Chair’s Statement from the Frankfurt meeting to the IANA Stewardship Charter and drawing attention to the point of this email exchange as follows:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>The Cross Community Working Group (CWG) on Naming Related Functions met for a face-to-face in Frankfurt, Germany on 19 – 20 November 2014. The highly diverse CWG is one of the three groups submitting a proposal to the IANA Stewardship Transition Coordination Group (ICG) as part of the overall <a href="https://www.icann.org/stewardship">IANA Stewardship Transition</a><span class=MsoHyperlink> process</span>. <span style='color:red'>As noted in the CWG <a href="https://community.icann.org/download/attachments/48347144/CWG-DT%20Draft%20Charter%20-%2014%20August%202014%20Updated.doc?api=v2"><span style='color:red'>Charter</span></a><span class=MsoHyperlink><span style='color:red'>, </span></span>the IANA stewardship transition process is taking place alongside a parallel and related process on enhancing ICANN accountability.</span><span style='color:#1F497D'><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'>I look forward to further input, discussion and guidance in any event, and especially if my understanding outlined above is inconsistent with that of others.<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'>Thanks,<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'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Jonathan<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 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Mathieu Weill [mailto:mathieu.weill@afnic.fr] <br><b>Sent:</b> 21 November 2014 09:15<br><b>To:</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><p class=MsoNormal style='margin-bottom:12.0pt'>Dear Milton, Dear colleagues,<br><br>As one of the co-chairs of the drafting team for the accountability cross community working group, this message has obviously drawn my attention. Milton, you raise an issue about the inter-relation between the two tracks, but I must admit I have difficulties understanding both what triggered the discussion and what the actual consequences might be. This is of course because I have neither been in Frankfurt nor managed to read all the transcripts. <br><br>Could anyone be kind enough to point me to the relevant parts of the transcript ? <br><br>Best<br>Mathieu<o:p></o:p></p><div><p class=MsoNormal>Le 21/11/2014 00:15, Milton L Mueller a écrit :<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><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><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><pre>_______________________________________________<o:p></o:p></pre><pre>CWG-Stewardship mailing list<o:p></o:p></pre><pre><a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><o:p></o:p></pre><pre><a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><o:p></o:p></pre></blockquote><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><pre>-- <o:p></o:p></pre><pre>*****************************<o:p></o:p></pre><pre>Mathieu WEILL<o:p></o:p></pre><pre>AFNIC - directeur général<o:p></o:p></pre><pre>Tél: 01 39 30 83 06<o:p></o:p></pre><pre><a href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a><o:p></o:p></pre><pre>*****************************<o:p></o:p></pre><pre>ATTENTION : L'Afnic a déménagé le 31 mars 2014 !<o:p></o:p></pre><pre>Notre nouvelle adresse est :<o:p></o:p></pre><pre>Afnic - Immeuble Le Stephenson - 1, rue Stephenson - 78180 Montigny-le-Bretonneux<o:p></o:p></pre></div></body></html>