<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear Colleagues,<br>
<br>
During our 30th December call, we had extensive discussions
regarding what our group would consider work stream 1 or swork
stream 2. We concluded with an action item as such : <br>
<blockquote type="cite"><span
style="font-size:10.0pt;line-height:106%;font-family:Symbol"><span
style="mso-list:Ignore"><span style="font:7.0pt "Times
New Roman""> </span></span></span><b><span
style="font-size:10.0pt;line-height:106%;font-family:"Calibri",sans-serif">ACTION:</span></b><span
style="font-size:10.0pt;line-height:106%;font-family:"Calibri",sans-serif"> Recap of definitions of WS1/WS2 for mailing list and discussion next week.</span></blockquote>
As Co-chairs, we have attempted to summarize the various inputs
expressed on the list as well as during the calls on the matter.
Below is a recap, including a proposal for discussion, inspired by
the WA2 proposal, and which, in our opinion, would be a good
candidate to move forward. <br>
<br>
This is for you review at this stage before we discuss it tomorrow
during the weekly call. Comments or alternate will be welcome during
the call or later on this thread. <br>
<br>
I'd like to once again thank Steve del Bianco and the WA2 team for
their essential contribution to this key piece of our work. <br>
<br>
Mathieu<br>
<br>
------------------------<br>
Main inputs, comments and positions expressed so far regarding
WS1/WS2: <br>
<blockquote type="cite">Problem statement from our Charter : <br
class="">
<blockquote type="cite" class="">
<div class="">
<pre style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: inherit;" class=""><font class="" color="#010101" face="Calibri"><span style="font-size: 11pt;" class="">The concerns raised during these discussions around the transition process indicate that the existing
ICANN accountability mechanisms do not yet meet stakeholder expectations. Recent statements
made by various stakeholders suggest that current accountability mechanisms need to be reviewed
and, if need be, improved, amended, replaced, or supplemented with new mechanisms (see for
instance ATRT recommendations). Considering that the NTIA has stressed that it is expecting
community consensus regarding the transition, a failure to meet stakeholder expectations with
regards to accountability may create a situation where NTIA does not accept the IANA transition
proposal as meeting its conditions. Thus reviewing ICANN’s accountability mechanisms was
considered to be crucial for the transition process.</span></font></pre>
</div>
</blockquote>
Work stream scopes from our Charter :<br class="">
<blockquote type="cite" class="">
<div class="">
<div style="font-family: Calibri, sans-serif; font-size: 16px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<div style="margin: 4.75mm 0mm 0mm; text-indent: 0mm;"
class="" align="left"><font class="" color="#010101"
face="Calibri"><span style="font-size: 11pt;" class="">In
the discussions around the accountability process, the
CCWG-Accountability will proceed with two Work
Streams:</span></font></div>
<ul style="margin-top: 0mm; margin-bottom: 0mm;" class="">
<li style="margin-left: 5pt; margin-right: 0pt;
padding-left: 0pt; font-family: Symbol; font-size: 11pt;
color: rgb(1, 1, 1);" class=""> <font class=""
color="#010101" face="Calibri"><span style="font-size:
11pt; font-weight: bold;" class=""><b class="">Work
Stream 1</b></span><span class=""> </span><span
style="font-size: 11pt;" class="">: focused on
mechanisms enhancing ICANN accountability that must
be in place or committed to within the time frame of
the IANA Stewardship Transition;</span></font> </li>
<li style="margin-left: 5pt; margin-right: 0pt;
padding-left: 0pt; font-family: Symbol; font-size: 11pt;
color: rgb(1, 1, 1);" class=""> <font class=""
color="#010101" face="Calibri"><span style="font-size:
11pt; font-weight: bold;" class=""><b class="">Work
Stream 2</b></span><span class=""> </span><span
style="font-size: 11pt;" class="">: focused on
addressing accountability topics for which a
timeline for developing solutions and full
implementation may extend beyond the IANA
Stewardship Transition.</span></font> </li>
</ul>
<div class="" align="left"><font class="" color="#010101"
face="Calibri"><span style="font-size: 11pt;" class=""><br
class="">
</span></font></div>
<div class="" align="left"><font class="" color="#010101"
face="Calibri"><span style="font-size: 11pt;" class="">The
CCWG-Accountability will allocate issues to Work
Stream 1 and Work Stream 2. Some issues may span both
Work Streams.</span></font></div>
<div class="" align="left"><font class="" color="#010101"
face="Calibri"><span style="font-size: 11pt;" class=""><br
class="">
</span></font></div>
<div class="" align="left"><font class="" color="#010101"
face="Calibri"><span style="font-size: 11pt;" class="">Suggested
questions to be considered as part of Work Stream 1
include, but are not limited to: </span></font></div>
<ul style="margin-top: 0mm; margin-bottom: 0mm;" class="">
<li style="margin-left: 5pt; margin-right: 0pt;
padding-left: 0pt; font-family: Symbol; font-size: 11pt;
color: rgb(1, 1, 1);" class=""> <font class=""
color="#010101" face="Calibri">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?</font>
</li>
<li style="margin-left: 5pt; margin-right: 0pt;
padding-left: 0pt; font-family: Symbol; font-size: 11pt;
color: rgb(1, 1, 1);" class=""> <font class=""
color="#010101" face="Calibri">What enhancements or
reforms are required to be implemented or committed to
before the NTIA Stewardship Transition?</font>
<ul style="margin-top: 0mm; margin-bottom: 0mm;"
class="">
<li style="margin-left: 10pt; margin-right: 0pt;
padding-left: 0pt; font-family: 'Courier New';
font-size: 11pt;" class=""> <font class=""
color="#010101" face="Calibri">How will these
enhancements or reforms be stress-tested?</font> </li>
</ul>
</li>
<li style="margin-left: 5pt; margin-right: 0pt;
padding-left: 0pt; font-family: Symbol; font-size: 11pt;
color: rgb(1, 1, 1);" class=""> <font class=""
color="#010101" face="Calibri">What enhancements or
reforms must be committed to before the NTIA
Stewardship Transition, but could be implemented
after.</font>
<ul style="margin-top: 0mm; margin-bottom: 0mm;"
class="">
<li style="margin-left: 10pt; margin-right: 0pt;
padding-left: 0pt; font-family: 'Courier New';
font-size: 11pt;" class=""> <font class=""
color="#010101" face="Calibri">If the
implementation of enhancements or reforms are to
be deferred, how can the community be assured they
will be implemented?</font> </li>
<li style="margin-left: 10pt; margin-right: 0pt;
padding-left: 0pt; font-family: 'Courier New';
font-size: 11pt;" class=""> <font class=""
color="#010101" face="Calibri">How will these
enhancements or reforms be stress-tested?</font> </li>
</ul>
</li>
</ul>
</div>
<br class="">
</div>
</blockquote>
Work Area 2 proposed definition of WS1/2 :<br class="">
<blockquote type="cite" class="">
<div class="">
<div style="font-family: Calibri, sans-serif; font-size: 16px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<font class="" face="Calibri,sans-serif">WS 1 is designated
for accountability mechanisms that must be in place of
rimly committed to before IANA transition occurs. </font></div>
<div style="font-family: Calibri, sans-serif; font-size: 16px;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
<font class="" face="Calibri,sans-serif">All other consensus
items could be in WS2, provided<span class=""> </span><b
class="">there are mechanisms in WS1 adequate for force
implementation of WS2 items despite resistance from
Icann management and Board.</b> </font></div>
</div>
</blockquote>
Paul Rosenzweig tentative defintiion of WS0 :<br class="">
<blockquote type="cite" class="">
<div class="">
<blockquote style="font-family: Arial; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-align:
-webkit-auto; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; font-size: inherit;"
class=""> 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<span class=""> </span><b
class="">WS0</b><span class=""> </span>for want of a
better term) that would be fundamental red-lines for the
community. </blockquote>
<br class="">
</div>
</blockquote>
Alan Greenberg's concern : <br class="">
<blockquote type="cite" class="">
<div class="">
<pre style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: inherit;" class=""><font class="" face="Arial">Needs to demontrate why items in WS1 or WS2 are needed as a consequence of the NTIA transition. </font></pre>
</div>
</blockquote>
<br class="">
Comment from Becky Burr :<br class="">
<div style="font-family: Arial; font-style: normal; font-variant:
normal; font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: 2; text-align: -webkit-auto;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;
font-size: inherit;" class=""> <span style="font-family: Arial;
white-space: normal;" class="">Understands the community to
say there were certain basic accountability mechanisms that
would enable them to feel comfortable with the IANA
transition, these may not be directly related to the
transition itself. What we need from WS1 is the community
feels comfortable that tools are in place to continue the work
to create real and meaningful accountability. </span></div>
</blockquote>
-----------------------------------<br>
Proposal submitted for comments (to be presented and initially
discussed during tomorrow's call): <br>
<blockquote type="cite"><font class="" face="Calibri,sans-serif">WS1
mechanisms are those that, when in place or committed to, would
provide the community with confidence that any accountability
mechanism that would further enhance Icann's accountability
would be implemented if it had consensus support from the
community, even if it were to encounter Icann management
resistance or if it were against the interest of Icann as a
corporate entity. </font></blockquote>
<br>
<pre class="moz-signature" cols="72">--
*****************************
Mathieu WEILL
AFNIC - directeur général
Tél: +33 1 39 30 83 06
<a class="moz-txt-link-abbreviated" href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a>
Twitter : @mathieuweill
*****************************
</pre>
</body>
</html>