<div dir="ltr"><div>Dear Mathiew</div><div>Dear All,</div><div>Thank you very much for the draft.</div><div>I have noted reference to DOC.I understand that we are preparing REVISED BALAWS DEALING WITH transition AND POST ttransition</div><div>MAY YOU KINDLY ADVISE WHAT role DOC will BE EXPECTED TO PLAY AFTER TRANSION </div><div>please READ WHAT IS INCLUDED IN THE Draft </div><div> </div><div><font color="#000000" face="Times New Roman" size="3">
</font><p style="margin:0in 0in 0pt"><em><b><span style="font-family:"Calibri","sans-serif";font-size:14pt"><font color="#000000">Quote</font></span></b></em></p><p style="margin:0in 0in 0pt"><em><b><span style="font-family:"Calibri","sans-serif";font-size:14pt"><font color="#000000">4.</font></span></b><span style="font-family:"Calibri","sans-serif";font-size:11pt"><font color="#000000">
<strong>DOC</strong> affirms its commitment to a multi-stakeholder, private sector led,
bottom-up policy development model for DNS technical coordination that acts for
the benefit of global Internet users. A private coordinating process, the
outcomes of which reflect the public interest, is best able to flexibly meet
the changing needs of the Internet and of Internet users.</font></span></em></p><font color="#000000" face="Times New Roman" size="3"><em>
</em></font><p style="margin:0in 0in 0pt"><span style="font-family:"Calibri","sans-serif";font-size:11pt"><font color="#000000"><em> </em></font></span></p><font color="#000000" face="Times New Roman" size="3"><em>
</em></font><p style="margin:0in 0in 0pt 0.5in"><span style="font-family:"Calibri","sans-serif";font-size:11pt"><font color="#000000"><em>The above are <strong>DOC</strong> commitments.</em></font></span></p><font color="#000000" face="Times New Roman" size="3"><em>
</em></font><p style="margin:0in 0in 0pt"><span style="font-family:"Calibri","sans-serif";font-size:11pt"><font color="#000000"><em> </em></font></span></p><font color="#000000" face="Times New Roman" size="3"><em>
</em></font><p style="margin:0in 0in 0pt"><span style="font-family:"Calibri","sans-serif";font-size:11pt"><font color="#000000"><em>ICANN and <strong>DOC</strong> recognize that there is a group of participants
that engage in ICANN's processes to a greater extent than Internet users
generally. To ensure that its decisions are in the public interest, and not
just the interests of a particular set of stakeholders, ICANN commits to
perform and publish analyses of the positive and negative effects of its
decisions on the public, including any financial impact on the public, and the
positive or negative impact (if any) on the systemic security, stability and
resiliency of the DNS.</em></font></span></p><font color="#000000" face="Times New Roman" size="3">
</font></div><div><strong>Unquote </strong></div><div><strong>Regards</strong></div><div><strong>Kavouss </strong></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-03-17 11:51 GMT+01:00 Matthew Shears <span dir="ltr"><<a href="mailto:mshears@cdt.org" target="_blank">mshears@cdt.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi all<br>
<br>
Attached a revised version (incorporating feedback from Steve and
Robin) of the paper on additional items that could be inserted in
the bylaws, etc., from the Affirmation of commitments. <br>
<br>
Thoughts/comments very welcome.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthew</font></span><div><div class="h5"><br>
<br>
<div>On 3/8/2015 9:03 PM, Robin Gross wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">Thanks very much for this discussion paper, Matthew.
A few comments / suggestions redlined in the attached draft.
<div><br>
</div>
<div>Thanks again,</div>
<div>Robin</div>
<br>
<fieldset></fieldset>
<br>
</div></div><div><br>
<div><br>
</div>
<div><br>
<div><span>
<div>On Mar 8, 2015, at 1:05 PM, Matthew Shears wrote:</div>
<br>
</span><blockquote type="cite"><div><div class="h5">
<div text="#000000" bgcolor="#FFFFFF"> <br>
Dear all - attached please find an overview of other
elements of the AoC that need to be further discussed
within the WP as well as some suggestions that could be
brought into the bylaws.<br>
<br>
Looking forward to your thoughts/comments.<br>
<br>
Matthew<br>
<br>
<div>On 3/4/2015 5:38 PM, Steve
DelBianco wrote:<br>
</div>
<blockquote type="cite">
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
<div>
<div>Regarding Kavouss’ point about the ATRT
assessing the 'effectiveness of the GAC’. </div>
<div>A deeper read of ICANN bylaws tells me that
‘effectiveness’ is part of what the structural
reviews are about. So while these structural
reviews don’t actually assess the effectiveness
of the GNSO, CCNSO, etc., they do make
recommendations about how to improve the
effectiveness. (see bylaws below)</div>
</div>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px"> <br>
</div>
<div>
<blockquote style="margin:0px 0px 0px 40px;padding:0px;border:currentColor">
<div><font face="Calibri,sans-serif">Section 4.
PERIODIC REVIEW OF ICANN STRUCTURE AND
OPERATIONS</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">1. The Board
shall cause a periodic review of the
performance and operation of each Supporting
Organization, each Supporting Organization
Council, each Advisory Committee (other than
the Governmental Advisory Committee), and the
Nominating Committee by an entity or entities
independent of the organization under review.
The goal of the review, to be undertaken
pursuant to such criteria and standards as the
Board shall direct, shall be to determine (i)
whether that organization has a continuing
purpose in the ICANN structure, and (ii) i<span style="background-color:rgb(255,255,0)">f
so, whether any change in structure or
operations is desirable to improve its
effectiveness.</span></font></div>
</blockquote>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px"> <br>
</div>
<span style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in;text-align:left;color:black;font-family:Calibri;font-size:12pt"> <span style="font-weight:bold">From: </span>Steve
DelBianco<br>
<span style="font-weight:bold">Date: </span>Wednesday,
March 4, 2015 at 5:27 PM<br>
<span style="font-weight:bold">To: </span>Jordan
Carter, "<a href="mailto:wp1@icann.org" target="_blank">wp1@icann.org</a>"<br>
<span style="font-weight:bold">Cc: </span>Matthew
Shears, Fiona Asonga, ACCT-Staff<br>
<span style="font-weight:bold">Subject: </span>WP1:
Draft 5, with all Affirmation Reviews implemented
as Bylaws changes<br>
</div>
<div><br>
</div>
<div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
<div>
<div>
<div>Draft v5 (attached) reflects the
discussion/suggestions from our call on
4-Mar-2015.</div>
<div><br>
</div>
</div>
</div>
<span>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in;text-align:left;color:black;font-family:Calibri;font-size:12pt"> <span style="font-weight:bold">From: </span>Steve
DelBianco<br>
<span style="font-weight:bold">Date: </span>Monday,
March 2, 2015 at 3:56 PM<br>
<span style="font-weight:bold">To: </span>Jordan
Carter, "<a href="mailto:wp1@icann.org" target="_blank">wp1@icann.org</a>"<br>
<span style="font-weight:bold">Cc: </span>Matthew
Shears, Fiona Asonga, ACCT-Staff<br>
<span style="font-weight:bold">Subject: </span>WP1:
Draft 4, with all Affirmation Reviews
implemented as Bylaws changes<br>
</div>
<div><br>
</div>
<div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
<div>
<div>
<div>here’s an updated doc for
Matthew, Fiona, and me, where we are
importing the <i>Affirmation of
Commitments</i> Reviews into the
ICANN Bylaws. The last 2 pages of
this doc show proposed bylaws
language for all 4 reviews.</div>
</div>
</div>
<div><br>
</div>
<span>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
<div>
<div>Matthew Shears also has draft
language regarding other
commitments from AoC that should
be considered for import into
ICANN bylaws.</div>
<div> </div>
<div>
<div>
<div>Best,</div>
<div>
<div>Steve </div>
</div>
<div><br>
</div>
</div>
</div>
</div>
<div><br>
</div>
</div>
</span></div>
</div>
</span></div>
</div>
</span> </blockquote>
<br>
</div>
</div></div><span><span><Proposals for incorporating additional elements
of the AoC v1.docx></span>_______________________________________________<br>
WP1 mailing list<br>
<a href="mailto:WP1@icann.org" target="_blank">WP1@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/wp1" target="_blank">https://mm.icann.org/mailman/listinfo/wp1</a><br>
</span></blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
WP1 mailing list<br>
<a href="mailto:WP1@icann.org">WP1@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/wp1" target="_blank">https://mm.icann.org/mailman/listinfo/wp1</a><br>
<br></blockquote></div><br></div>