<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">
<meta name="Title" content="">
<p class="MsoNormal"><span
style="font-size:11.0pt;mso-bidi-font-size:10.0pt;
font-family:Calibri;mso-ascii-theme-font:major-latin;mso-hansi-theme-font:major-latin;
mso-ansi-language:EN-GB">Dear colleagues, <br>
<br>
</span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;mso-bidi-font-size:10.0pt;
font-family:Calibri;mso-ascii-theme-font:major-latin;mso-hansi-theme-font:major-latin;
mso-ansi-language:EN-GB">As mentioned by the GAC chair during
our meeting in
Paris, the GAC </span><span
style="font-size:11.0pt;font-family:
Calibri;mso-ascii-theme-font:major-latin;mso-hansi-theme-font:major-latin"
lang="EN-US">consensus
advice contained in the 2013 Beijing communique was a result
of a long process
that originated before the new gTLD application round was
open. The Beijing
consensus advice was the result of a long and lengthy process
of providing
rationale to the board, ICANN community, including applicants,
on future GAC
related responses to new gTLD applications. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Calibri;
mso-ascii-theme-font:major-latin;mso-hansi-theme-font:major-latin"
lang="EN-US">The processes
provided several avenues for applicants to engage with the GAC
and individual
governments regarding any concerns raised by individual
governments and GAC as
a whole. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Calibri;
mso-ascii-theme-font:major-latin;mso-hansi-theme-font:major-latin"
lang="EN-US">Best regards<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:Calibri;
mso-ascii-theme-font:major-latin;mso-hansi-theme-font:major-latin"
lang="EN-US">Alice<o:p></o:p></span></p>
<meta name="Keywords" content="">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 2008">
<meta name="Originator" content="Microsoft Word 2008">
<link rel="File-List"
href="file://localhost/Users/alicemunyua/Library/Caches/TemporaryItems/msoclip/0/clip_filelist.xml">
<!--[if gte mso 9]><xml>
<o:DocumentProperties>
<o:Template>Normal.dotm</o:Template>
<o:Revision>0</o:Revision>
<o:TotalTime>0</o:TotalTime>
<o:Pages>1</o:Pages>
<o:Words>92</o:Words>
<o:Characters>517</o:Characters>
<o:Company>Home</o:Company>
<o:Lines>9</o:Lines>
<o:Paragraphs>2</o:Paragraphs>
<o:CharactersWithSpaces>646</o:CharactersWithSpaces>
<o:Version>12.0</o:Version>
</o:DocumentProperties>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>0</w:Zoom>
<w:TrackMoves>false</w:TrackMoves>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:DrawingGridHorizontalSpacing>18 pt</w:DrawingGridHorizontalSpacing>
<w:DrawingGridVerticalSpacing>18 pt</w:DrawingGridVerticalSpacing>
<w:DisplayHorizontalDrawingGridEvery>0</w:DisplayHorizontalDrawingGridEvery>
<w:DisplayVerticalDrawingGridEvery>0</w:DisplayVerticalDrawingGridEvery>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:DontGrowAutofit/>
<w:DontAutofitConstrainedTables/>
<w:DontVertAlignInTxbx/>
</w:Compatibility>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="276">
</w:LatentStyles>
</xml><![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 0 0 0 1 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin-top:0cm;
margin-right:0cm;
margin-bottom:10.0pt;
margin-left:0cm;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Cambria;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-ansi-language:EN-US;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;
mso-header-margin:36.0pt;
mso-footer-margin:36.0pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-ansi-language:EN-US;}
</style>
<![endif]--><!--StartFragment--><!--EndFragment--><br>
<br>
On 22/07/2015 19:06, Robin Gross wrote:<br>
</div>
<blockquote
cite="mid:D4CC77F4-A8A5-4F74-A4D3-EACB76535D77@ipjustice.org"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=windows-1252">
Indeed requiring explanations for all key decisions is critical to
ICANN's general accountability. In the recent .africa case, the
IRP panel declared GAC should have provided a rationale for its
objection and that the board had a duty of diligence to examine
that reason. These are fundamental concepts in good governance
and absolutely appropriate for enhancing ICANN's accountability to
the public it serves.
<div><br>
</div>
<div>Robin<br>
<div><br>
</div>
<div><br>
<div>
<div>On Jul 22, 2015, at 8:48 AM, Burr, Becky wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div>
<div>
<div>
<div>Actually, I don’t think that it is too much to
ask the GAC to provide a reason for its Advice.
It need not disclose truly private information –
but without a basic explanation, how can ICANN
enter into a reasonable discussion to arrive at a
mutually agreeable solution? And how can members
of the community understand whether or not there
is a way to address the GAC concerns. </div>
<div><br>
</div>
<div><br>
</div>
<div>
<p class="MsoNormal"><span>J. Beckwith Burr</span></p>
<p class="MsoNormal"><b><span>Neustar, Inc. /</span></b><span> Deputy
General Counsel and Chief Privacy Officer</span></p>
<p class="MsoNormal"><span>1775 Pennsylvania
Avenue NW, Washington, DC 20006</span></p>
<p class="MsoNormal"><span>Office</span><span>: +
1.202.533.2932 <span> Mobile</span>:
+1.202.352.6367 <span>/ <a
moz-do-not-send="true"
href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a> /
<a moz-do-not-send="true"
href="http://www.neustar.biz">www.neustar.biz</a></span></span></p>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<span>From: </span>Paul Rosenzweig <<a
moz-do-not-send="true"
href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@redbranchconsulting.com</a>><br>
<span>Date: </span>Wednesday, July 22, 2015 at 7:42
AM<br>
<span>To: </span>"<a moz-do-not-send="true"
href="mailto:Mathieu.Weill@afnic.fr">Mathieu.Weill@afnic.fr</a>"
<<a moz-do-not-send="true"
href="mailto:Mathieu.Weill@afnic.fr">Mathieu.Weill@afnic.fr</a>>,
Becky Burr <<a moz-do-not-send="true"
href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a>>,
'Robin Gross' <<a moz-do-not-send="true"
href="mailto:robin@ipjustice.org">robin@ipjustice.org</a>><br>
<span>Cc: </span>"<a moz-do-not-send="true"
href="mailto:wp2@icann.org">wp2@icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:wp2@icann.org">wp2@icann.org</a>><br>
<span>Subject: </span>RE: [WP2] slightly revised
mission, commitments, core values for discussion
later today<br>
</div>
<div><br>
</div>
<div>
<meta name="Generator" content="Microsoft Word 15
(filtered medium)">
<div lang="EN-US">
<div class="WordSection1">
<div class="MsoNormal"><span>FWIW, I have been
reflecting on the “with explanation”
requirement in the second of these items
below and I think I am increasingly somewhat
sympathetic to those who oppose this
requirement – especially in the GAC (for
whom I generally have no great sympathy
</span><span>J</span><span>). Reflecting on
public policy requirements I can at least
imagine some plausible scenarios where a
government (or many governments) might wish
to avoid having to say publicly what they
know to be true privately. These can range
from diplomatic reasons of creative
ambiguity to perhaps even the possession of
confidential information about an issue that
is sufficient to raise concern, but not
disclosable. At least in situations where
the recommendation is by a large consensus,
we might be comfortable with the idea that
the internal discipline of the advisory
committee is sufficient.</span></div>
<div class="MsoNormal"><span> </span></div>
<div class="MsoNormal"><span>As I said, I am not
all the way there on this yet, given my
general skepticism of unexplained
decisionmaking, but even some colleagues in
whom I repose some trust have suggested that
explaining everything may be a bit of
overkill. Thoughts?</span></div>
<div class="MsoNormal"><span> </span></div>
<div class="MsoNormal"><span>Paul</span></div>
<div class="MsoNormal"><span> </span></div>
<div>
<div class="MsoNormal"><span>Paul Rosenzweig</span></div>
<div class="MsoNormal"><span><a
moz-do-not-send="true"
href="mailto:paul.rosenzweigesq@redbranchconsulting.com"><span>paul.rosenzweig@redbranchconsulting.com</span></a></span></div>
<div class="MsoNormal"><span>O: +1 (202)
547-0660</span></div>
<div class="MsoNormal"><span>M: +1 (202)
329-9650</span></div>
<div class="MsoNormal"><span>VOIP: +1 (202)
738-1739</span></div>
<div class="MsoNormal"><span>Skype:
paul.rosenzweig1066</span></div>
<p class="MsoNormal"><span><a
moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.redbranchconsulting.com_index.php-3Foption-3Dcom-5Fcontent-26view-3Darticle-26id-3D19-26Itemid-3D9&d=AwMFAw&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=QdR2C2NsA_zaHrigHjxzxPajAX1O54bDXJBzkeJEvrQ&s=PP63erk7JrvpRWCjYpYnUvudFkCytuKycAdCjfyNNyU&e="><span>Link
to my PGP Key</span></a></span></p>
<div class="MsoNormal"><span> </span></div>
</div>
<div class="MsoNormal"><span> </span></div>
<div>
<div>
<div class="MsoNormal"><b><span>From:</span></b><span>
Mathieu Weill [<a moz-do-not-send="true"
href="mailto:mathieu.weill@afnic.fr">mailto:mathieu.weill@afnic.fr</a>]
<br>
<b>Sent:</b> Wednesday, July 22, 2015
6:43 AM<br>
<b>To:</b> Burr, Becky; Robin Gross<br>
<b>Cc:</b> <a moz-do-not-send="true"
href="mailto:wp2@icann.org">wp2@icann.org</a><br>
<b>Subject:</b> Re: [WP2] slightly
revised mission, commitments, core
values for discussion later today</span></div>
</div>
</div>
<div class="MsoNormal"> </div>
<div class="MsoNormal">Dear WP2 colleagues,<br>
<br>
I want to thank all of you for trying very
hard to find agreement on all these topics. I
appreciate how everyone is keeping an open
mind.
<br>
<br>
I may have missed this in the discussions but
what is the rationale for inserting the words
"within their respective jurisdictions" in
Core Value 7 (ex-11). I remember we had some
pushback on this in Paris.
<br>
<br>
<br>
</div>
<blockquote type="cite">
<div class="MsoNormal"><span>While remaining
rooted in the [private sector], including
business stakeholders, civil society, the
technical community, and academia,
recognizing that governments and public
authorities are responsible for public
policy <u>within their respective
jurisdictions</u> and duly taking into
account the public policy advice of
governments and public authorities </span></div>
</blockquote>
<div class="MsoNormal"><br>
The proposed addition in Article XI of the
sentence below is also attracting some
pushback.
<br>
<br>
</div>
<blockquote type="cite">
<div class="MsoNormal">or where the Advisory
Committee has not explained the specific
reason(s) for its advice.</div>
</blockquote>
<p class="MsoNormal">My personal view is that it
may not be most appropriate to have this
criteria in the same sentence and at the same
level as "not exceeding the Mission".
<br>
<br>
I also wonder whether we could find ATRT
agreed language on the provision of rationales
in support of advice. It seemed to me that
these reviews had contributed to significant
improvements in that regard and the use of
"agreed language" often helps when time is
short. <br>
<br>
Best,</p>
<div>
<div class="MsoNormal">Le 21/07/2015 20:43,
Burr, Becky a écrit :</div>
</div>
<blockquote type="cite">
<div>
<div>
<div>
<div class="MsoNormal">Whoops, apologies
– will fix that in the discussion</div>
</div>
<div>
<div class="MsoNormal"> </div>
</div>
<div>
<div class="MsoNormal"><span>J. Beckwith
Burr</span><span></span></div>
<div class="MsoNormal"><b><span>Neustar,
Inc. /</span></b><span> Deputy
General Counsel and Chief Privacy
Officer</span><span></span></div>
<div class="MsoNormal"><span>1775
Pennsylvania Avenue NW, Washington,
DC 20006</span><span></span></div>
<div class="MsoNormal"><span>Office</span><span>:
+ 1.202.533.2932 </span><span> Mobile</span><span>:
+1.202.352.6367 </span><span>/ <a
moz-do-not-send="true"
href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a> /
<a moz-do-not-send="true"
href="http://www.neustar.biz/">www.neustar.biz</a></span><span></span></div>
</div>
</div>
</div>
<div>
<div class="MsoNormal"> </div>
</div>
<div>
<div class="MsoNormal"><b><span>From:
</span></b><span>Robin Gross <<a
moz-do-not-send="true"
href="mailto:robin@ipjustice.org">robin@ipjustice.org</a>><br>
<b>Date: </b>Tuesday, July 21, 2015 at
2:36 PM<br>
<b>To: </b>Becky Burr <<a
moz-do-not-send="true"
href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a>><br>
<b>Cc: </b>"<a moz-do-not-send="true"
href="mailto:wp2@icann.org">wp2@icann.org</a>"
<<a moz-do-not-send="true"
href="mailto:wp2@icann.org">wp2@icann.org</a>><br>
<b>Subject: </b>Re: [WP2] slightly
revised mission, commitments, core
values for discussion later today</span></div>
</div>
<div>
<div class="MsoNormal"> </div>
</div>
<div>
<div>
<div class="MsoNormal">Looks good - except
it is missing the critical word of
"not". So it should read:
</div>
<div>
<div class="MsoNormal"> </div>
</div>
<div>
<div class="MsoNormal"><i><span>[...] </span></i><i><span>ICANN
shall have no authority to act or
refrain from acting in response to
<s><span>input</span></s><span>
advice</span> from an Advisory
Committee where such advice would
require ICANN to exceed its
Mission or violate these Bylaws
<span>or where the Advisory
Committee has not explained the
specific reason(s) for its
advice.</span></span></i> </div>
</div>
<div>
<div class="MsoNormal"> </div>
</div>
<div>
<div class="MsoNormal">Thank you,</div>
</div>
<div>
<div class="MsoNormal">Robin</div>
</div>
<div>
<div class="MsoNormal"> </div>
<div>
<div>
<div class="MsoNormal">On Jul 21,
2015, at 11:30 AM, Burr, Becky
wrote:</div>
</div>
<div class="MsoNormal"><br>
<br>
</div>
<blockquote type="cite">
<div>
<div>
<div>
<div>
<div class="MsoNormal"><span> </span></div>
</div>
<div>
<div>
<div class="MsoNormal"><span>J.
Beckwith Burr</span><span></span></div>
</div>
<div>
<div class="MsoNormal"><b><span>Neustar,
Inc. /</span></b><span> Deputy
General Counsel and
Chief Privacy Officer</span><span></span></div>
</div>
<div>
<div class="MsoNormal"><span>1775
Pennsylvania Avenue
NW, Washington, DC
20006</span><span></span></div>
</div>
<div>
<div class="MsoNormal"><span>Office:
+
1.202.533.2932 Mobile:
+1.202.352.6367 </span><span>/ <a
moz-do-not-send="true" href="mailto:becky.burr@neustar.biz">becky.burr@neustar.biz</a> /
<a
moz-do-not-send="true"
href="http://www.neustar.biz/">www.neustar.biz</a></span><span></span></div>
</div>
</div>
</div>
</div>
</div>
<div class="MsoNormal"><7-21
Mission and Core Values
V2.docx>_______________________________________________<br>
WP2 mailing list<br>
<a moz-do-not-send="true"
href="mailto:WP2@icann.org">WP2@icann.org</a><br>
<a moz-do-not-send="true"
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_wp2&d=AwMFAw&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=QdR2C2NsA_zaHrigHjxzxPajAX1O54bDXJBzkeJEvrQ&s=cikIxfFi2RCxlG6v79P01rRdz5RE-Vk-az7lyopa0FQ&e=">https://mm.icann.org/mailman/listinfo/wp2</a></div>
</blockquote>
</div>
<div class="MsoNormal"> </div>
</div>
</div>
</div>
<div class="MsoNormal"><br>
<br>
<br>
</div>
<pre>_______________________________________________</pre>
<pre>WP2 mailing list</pre>
<pre><a moz-do-not-send="true" href="mailto:WP2@icann.org">WP2@icann.org</a></pre>
<pre><a moz-do-not-send="true" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_wp2&d=AwMFAw&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=QdR2C2NsA_zaHrigHjxzxPajAX1O54bDXJBzkeJEvrQ&s=cikIxfFi2RCxlG6v79P01rRdz5RE-Vk-az7lyopa0FQ&e=">https://mm.icann.org/mailman/listinfo/wp2</a></pre>
</blockquote>
<div class="MsoNormal"><br>
<br>
</div>
<pre>-- </pre>
<pre>*****************************</pre>
<pre>Mathieu WEILL</pre>
<pre>AFNIC - directeur général</pre>
<pre>Tél: +33 1 39 30 83 06</pre>
<pre><a moz-do-not-send="true" href="mailto:mathieu.weill@afnic.fr">mathieu.weill@afnic.fr</a></pre>
<pre>Twitter : @mathieuweill</pre>
<pre>*****************************</pre>
</div>
</div>
</div>
</span>
</div>
</blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
WP2 mailing list
<a class="moz-txt-link-abbreviated" href="mailto:WP2@icann.org">WP2@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/wp2">https://mm.icann.org/mailman/listinfo/wp2</a>
</pre>
</blockquote>
<br>
</body>
</html>