<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear Colleagues, <br>
<br>
First I would like to warmly thank Becky and her group for the quick
turnover in providing this fresh approach. This is exemplary of the
agility and responsiveness of our group. <br>
<br>
Then, I would like to highlight that this is the start of a
discussion for our whole group. We do not yet have a "response", but
we are taking onboard the feedback received. This document is
intended to facilitate CCWG input and shaping of our further
deliberations. <br>
<br>
So please join this discussion and we will also have opportunities
to further discuss in our work sessions later this week. <br>
<br>
Best<br>
Mathieu<br>
<br>
<div class="moz-cite-prefix">Le 21/06/2015 11:27, Burr, Becky a
écrit :<br>
</div>
<blockquote cite="mid:D1AC502B.36072%25becky.burr@neustar.biz"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>
<div>
<div>
<div style="color: rgb(0, 0, 0); font-family: Calibri,
sans-serif;"><span style="font-size: 15px;">Dear All -</span></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri,
sans-serif;"><span style="font-size: 15px;"><br>
</span></div>
<div><font face="Calibri,sans-serif"><span style="font-size:
15px;">Over the past couple of days a number of us
have been working to flesh out how an “empowered SO/AC
model” could provide a path towards consensus. The
deck, attached, reflects a very preliminary,
conceptual outline. This is intended to ensure a
better understanding of what is being proposed and to
encourage discussion between and among CCWG-ACCT
members. Please review it in that light and share
your thoughts to start a dialogue on the list.</span></font></div>
<div><font face="Calibri,sans-serif"><span style="font-size:
15px;"><br>
</span></font></div>
<div><font face="Calibri,sans-serif"><span style="font-size:
15px;">Speaking personally, over the course of
refining this proposal I have become more convinced
that this hybrid approach provides the foundation for
consensus that respects and addresses the very real
and fervently held concerns that have been expressed
about the various models we’ve discussed to date. </span></font></div>
<div><font face="Calibri,sans-serif"><span style="font-size:
15px;"><br>
</span></font></div>
<ul style="color: rgb(0, 0, 0); font-family: Calibri;
font-size: medium; margin-bottom: 0in; margin-top: 0in;"
type="disc">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; font-family: Calibri, sans-serif;">
The Empowered SO/AC structure is simple, easy, fast and
flexible….and it provides a powerful tool to ensure that
accountability reforms deferred to WS2 become a reality<o:p></o:p></li>
</ul>
<p class="MsoNormal" style="color: rgb(0, 0, 0);
font-family: Calibri, sans-serif; font-size: 11pt; margin:
0in 0in 0.0001pt;">
<o:p> </o:p></p>
<ul style="color: rgb(0, 0, 0); font-family: Calibri;
font-size: medium; margin-bottom: 0in; margin-top: 0in;"
type="disc">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; font-family: Calibri, sans-serif;">
If we can get community consensus around the Empowered
SO/AC structure, we’ll have no problem meeting the
timeline for the transition….it actually allows us to
confidently push off more complex and time-consuming
questions to WS2.<o:p></o:p></li>
</ul>
<p class="MsoNormal" style="color: rgb(0, 0, 0);
font-family: Calibri, sans-serif; font-size: 11pt; margin:
0in 0in 0.0001pt;">
<o:p> </o:p></p>
<ul style="color: rgb(0, 0, 0); font-family: Calibri;
font-size: medium; margin-bottom: 0in; margin-top: 0in;"
type="disc">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; font-family: Calibri, sans-serif;">
A key benefit of the Empowered SO/AC structure is its
flexibility -- it allows all of the SOs and ACs to take
the time they need to decide how to engage. Governments
get to keep their unique advisory status until such time
they decide they want to exercise any of the six
community powers.<o:p></o:p></li>
</ul>
<p class="MsoNormal" style="color: rgb(0, 0, 0);
font-family: Calibri, sans-serif; font-size: 11pt; margin:
0in 0in 0.0001pt;">
<o:p> </o:p></p>
<ul style="color: rgb(0, 0, 0); font-family: Calibri;
font-size: medium; margin-bottom: 0in; margin-top: 0in;"
type="disc">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; font-family: Calibri, sans-serif;">
Another key benefit of the Empowered SO/AC model is that
is preserves and protects the existing community
structures. It reinforces the current SOs and ACs and
relies on their built-in accountability mechanisms.<o:p></o:p></li>
</ul>
<p class="MsoNormal" style="color: rgb(0, 0, 0);
font-family: Calibri, sans-serif; font-size: 11pt; margin:
0in 0in 0.0001pt;">
<o:p> </o:p></p>
<ul style="color: rgb(0, 0, 0); font-family: Calibri;
font-size: medium; margin-bottom: 0in; margin-top: 0in;"
type="disc">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; font-family: Calibri, sans-serif;">
The Empowered SO/AC model:<o:p></o:p></li>
</ul>
<p class="MsoListParagraph" style="color: rgb(0, 0, 0);
font-family: Calibri, sans-serif; font-size: 11pt; margin:
0in 0in 0.0001pt 0.5in;">
<o:p> </o:p></p>
<ul style="color: rgb(0, 0, 0); font-family: Calibri;
font-size: medium; margin-bottom: 0in; margin-top: 0in;"
type="disc">
<ul style="margin-bottom: 0in; margin-top: 0in;"
type="circle">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; font-family: Calibri, sans-serif;">
does not require the SO/ACs to change their structures
or change their existing mechanisms and
decision-making procedures, etc.<o:p></o:p></li>
</ul>
</ul>
<p class="MsoNormal" style="color: rgb(0, 0, 0);
font-family: Calibri, sans-serif; font-size: 11pt; margin:
0in 0in 0.0001pt;">
<o:p> </o:p></p>
<ul style="color: rgb(0, 0, 0); font-family: Calibri;
font-size: medium; margin-bottom: 0in; margin-top: 0in;"
type="disc">
<ul style="margin-bottom: 0in; margin-top: 0in;"
type="circle">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; font-family: Calibri, sans-serif;">
Permits each SO and AC to decide – in its own time -
whether it is comfortable with the
voluntary/cooperative model or prefers to organize and
enforce the community powers we’ve all agreed we want.<o:p></o:p></li>
</ul>
</ul>
<p class="MsoNormal" style="color: rgb(0, 0, 0);
font-family: Calibri, sans-serif; font-size: 11pt; margin:
0in 0in 0.0001pt;">
<o:p> </o:p></p>
<ul style="color: rgb(0, 0, 0); font-family: Calibri;
font-size: medium; margin-bottom: 0in; margin-top: 0in;"
type="disc">
<ul style="margin-bottom: 0in; margin-top: 0in;"
type="circle">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; font-family: Calibri, sans-serif;">
reinforces the foundation of our existing community
structure, and would only become relevant if/when all
other accountability mechanisms are exhausted.<o:p></o:p></li>
</ul>
</ul>
<p class="MsoNormal" style="color: rgb(0, 0, 0);
font-family: Calibri, sans-serif; font-size: 11pt; margin:
0in 0in 0.0001pt;">
<o:p> </o:p></p>
<ul style="color: rgb(0, 0, 0); font-family: Calibri;
font-size: medium; margin-bottom: 0in; margin-top: 0in;"
type="disc">
<ul style="margin-bottom: 0in; margin-top: 0in;"
type="circle">
<li class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; font-family: Calibri, sans-serif;">
would change nothing about the day-to-day operations
of ICANN or the existing community structures and
processes</li>
</ul>
</ul>
<div><span style="font-size: 15px;"><br>
</span></div>
<div><span style="font-size: 15px;">A final, important note.
It appears that the same kind of mechanism could be
used in the designator model context (again, with the
limitations with respect to the budget and strat plan).
So to the extent that the designator model is still in
play, most of the concepts we’ve laid out are
applicable.</span></div>
<div><span style="font-size: 15px;"><br>
</span></div>
<div><span style="font-size: 15px;">Best,</span></div>
<div><span style="font-size: 15px;"><br>
</span></div>
<div><span style="font-size: 15px;">Becky</span></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri,
sans-serif; font-size: 14px;">
<br>
</div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri,
sans-serif; font-size: 14px;">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; "><span style="font-size: 9pt;
font-family: Arial, sans-serif;">J. Beckwith Burr<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; "><b><span style="font-size: 9pt;
font-family: Arial, sans-serif; color: rgb(6, 134,
88);">Neustar, Inc. /</span></b><span
style="font-size: 9pt; font-family: Arial, sans-serif;"> Deputy
General Counsel and Chief Privacy Officer<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; "><span style="font-size: 9pt;
font-family: Arial, sans-serif;">1775 Pennsylvania
Avenue NW, Washington, DC 20006<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;
font-size: 11pt; "><span style="font-size: 9pt;
font-family: Arial, sans-serif; color: rgb(6, 134, 88);">Office</span><span
style="font-size: 9pt; font-family: Arial, sans-serif;">:
+ 1.202.533.2932 <span style="color: rgb(6, 134, 88); "> Mobile</span>:
+1.202.352.6367 <span style="color: rgb(6, 134, 88); ">/ <a
moz-do-not-send="true"
href="mailto:becky.burr@neustar.biz" style="color:
purple; ">becky.burr@neustar.biz</a> /
<a class="moz-txt-link-abbreviated" href="http://www.neustar.biz">www.neustar.biz</a></span></span></p>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</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>