<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 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:0in;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
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:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
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.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: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 bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Dear Mathieu (and others)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks very much for asking about the concept of Work Stream Zero (or “WS0”). I should say at the outset that the concept is very much dependent on the scope of ICANN Board authority. If we take seriously Dave Johnson’s suggestion, for example, that the Board might limit itself contractually to a narrow domain of authority then the requirement for accountability mechanisms scales back accordingly. If, however, we are obliged to proceed as we are now (with the possibility that some future Board might vote to expand ICANN authority quite a bit beyond the IANA function) then the need for external accountability measures is much greater.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>As I said in my first note to the Area 2 Working Group, the concept behind WS0 is derived from two instincts. The first is the highly practical one that the CCWG will need to prioritize its proposals to ICANN. If we ask for 50 changes in an undifferentiated mass, we are unlikely to achieve the goals we have of ensuring effective accountability. In some ways WS1 and WS2 are intended to identify that sort of priority – but there the variable is “time to implement” the change. The idea behind WS0 is that some changes (even ones that might take some time to effectuate) are absolutely vital to assure accountability going forward.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>So my answer to your question is simple. WS0 requirements are ones that are “red lines” for the community. They are ones that, in the end, we think we cannot live without and that would lead the community to recommend against the IANA Functions transition until they were adopted by the Board. So the “impact on the NTIA’s transition” is that these are sufficiently vital to community interests that failure to adopt them would prevent the transition from occurring altogether.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thus, my argument is that WS0 forms the very core of reforms that are “required to be implemented” before the transition. They are ones, without which NTIA’s transition should not proceed.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Some may think this is a null set. I do not and have separately offered my own take on what is a WS0 requirement. But whether one agrees on the content, I think the concept is a fairly explicit portion of our Charter.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Cheers<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Paul<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><span style='color:#C00000'>**NOTE: OUR NEW ADDRESS -- EFFECTIVE 12/15/14 ***<o:p></o:p></span></b></p><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='color:#1F497D'>509 C St. NE<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='color:#1F497D'>Washington, DC 20002<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='color:#1F497D'>Paul Rosenzweig<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='color:#1F497D'><a href="mailto:paul.rosenzweigesq@redbranchconsulting.com"><span style='color:#0563C1'>paul.rosenzweig@redbranchconsulting.com</span></a> <o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='color:#1F497D'>O: +1 (202) 547-0660<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='color:#1F497D'>M: +1 (202) 329-9650<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='color:#1F497D'>Skype: +1 (202) 738-1739 or paul.rosenzweig1066<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;text-align:justify;line-height:normal'><span style='color:#1F497D'><a href="http://www.redbranchconsulting.com/index.php?option=com_content&view=article&id=19&Itemid=9"><span style='color:#0563C1'>Link to my PGP Key</span></a><o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><span style='color:windowtext'>From:</span></b><span style='color:windowtext'> Mathieu Weill [mailto:mathieu.weill@afnic.fr] <br><b>Sent:</b> Monday, December 22, 2014 2:56 AM<br><b>To:</b> Steve DelBianco; accountability-cross-community@icann.org; Thomas Rickert<br><b>Cc:</b> ccwg-accountability2@icann.org<br><b>Subject:</b> Re: [CCWG-Accountability] Work Area 2: inventory of accountability mechanisms, draft 4<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dear Steve, Dear Colleagues,<br><br>Many thanks for this proposal to categorize WS1 / WS2 issues. I want to highlight that this is one of the fundamental blocks that we need to reach consensus on to proceed. <br><br>I have also noted Paul Rosenzweig idea of definition of a WS0 : <br><br><span style='font-size:12.0pt;line-height:115%'><o:p></o:p></span></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>As a result, I think that part of what we should be doing in the long run is focusing on the core/critical 3-5 items that are absolutely essential to ensuring accountability. In short, I think there is actually a sub-category of WS1 (call it <b>WS0</b> for want of a better term) that would be fundamental red-lines for the community. <o:p></o:p></p></blockquote><p class=MsoNormal>To comply with our Charter as well as anticipate reactions from some stakeholders, I think we would need to elaborate on how this related to the NTIA transition. The two key questions in our Charter are :<br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoListParagraphCxSpFirst style='margin-bottom:0in;margin-bottom:.0001pt;mso-add-space:auto;text-indent:-.25in;text-autospace:none'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt;line-height:115%'> </span><span style='mso-fareast-language:JA'>What would be the impact of NTIA’s transition of the IANA Functions Contract in ensuring ICANN’s accountability and what potential accountability concerns could this cause?</span><o:p></o:p></p><p class=MsoListParagraphCxSpLast style='margin-bottom:0in;margin-bottom:.0001pt;mso-add-space:auto;text-indent:-.25in;text-autospace:none'><span style='font-family:Symbol'>·</span><span style='font-size:7.0pt;line-height:115%'> </span><span style='mso-fareast-language:JA'>What enhancements or reforms are required to be implemented or committed to before the NTIA Stewardship Transition?</span><o:p></o:p></p></blockquote><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>I do recommend every colleague to consider this with attention. <br><br>best<br>Mathieu<br> <o:p></o:p></span></p><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Le 21/12/2014 22:10, Steve DelBianco a écrit :<o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt'>- Per requests from the chairs and from Alain Bidron, I expanded the rationale for work stream designations. These appear in the headers of the table and are shown below:<o:p></o:p></span></p></div><div><blockquote style='margin-left:30.0pt;margin-right:0in'><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt'>Proposed rationale for designating Work Streams: Work Stream 1 is designated for accountability enhancement mechanisms that must be in place [or firmly committed] before IANA transition occurs. All other consensus items could be in Work Stream 2, provided there are mechanisms in WS1 adequate to force implementation of WS2 items despite resistance from ICANN management and board. <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt'><o:p> </o:p></span></p></div></blockquote></div><blockquote style='margin-left:30.0pt;margin-right:0in'><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt'>1. Mechanisms giving the ICANN community ultimate authority over the ICANN corporation. Most of these are initially designated as WS1, since community Members need the leverage of IANA transition to obtain these Bylaws changes. <o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt'>2. Mechanisms to restrict actions of the board and management of the ICANN corporation. Most of these are initially designated as WS2, since the Members could reverse board or management decisions if Members are empowered in WS1 (above).<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt'>3. Mechanisms to prescribe actions of the ICANN corporation. Most of these are initially designated as WS2, since the Members could reverse board or management decisions if Members are empowered in WS1 (above). For example, a bottom-up consensus process to change ICANN bylaws might be rejected by ICANN board, but the Members could then reverse that decision and force the change. [I folded the Transparency items into this category]</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p></o:p></span></p></div></blockquote></blockquote><p class=MsoNormal style='margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><br><br><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: +33 1 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>Twitter : @mathieuweill<o:p></o:p></pre><pre>*****************************<o:p></o:p></pre></div></body></html>