<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Subject to Avri's thoughts (as she knows the ATRT well) I would
think that using a tried and tested approach would make sense.<br>
<br>
Matthew<br>
<br>
<div class="moz-cite-prefix">On 4/12/2016 9:22 AM, Gomes, Chuck
wrote:<br>
</div>
<blockquote
cite="mid:6DCFB66DEEF3CF4D98FA55BCC43F152E4A490721@BRN1WNEXMBX01.vcorp.ad.vrsn.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-priority:99;
mso-style-link:"Body Text Char";
margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Calibri","sans-serif";}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-priority:99;
mso-style-link:"Body Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.c4a0c8ff-067a-402c-bfec-95ed9cd1c28e, li.c4a0c8ff-067a-402c-bfec-95ed9cd1c28e, div.c4a0c8ff-067a-402c-bfec-95ed9cd1c28e
{mso-style-name:c4a0c8ff-067a-402c-bfec-95ed9cd1c28e;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ARTACAPL1, li.ARTACAPL1, div.ARTACAPL1
{mso-style-name:ARTACAP_L1;
mso-style-priority:99;
margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:12.0pt;
font-family:"Arial","sans-serif";
text-transform:uppercase;
font-weight:bold;}
p.ARTACAPL2, li.ARTACAPL2, div.ARTACAPL2
{mso-style-name:ARTACAP_L2;
mso-style-priority:99;
margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Arial","sans-serif";
text-transform:uppercase;
font-weight:bold;}
span.ARTACAPL3Char
{mso-style-name:"ARTACAP_L3 Char";
mso-style-link:ARTACAP_L3;
font-family:"Arial","sans-serif";}
p.ARTACAPL3, li.ARTACAPL3, div.ARTACAPL3
{mso-style-name:ARTACAP_L3;
mso-style-priority:99;
mso-style-link:"ARTACAP_L3 Char";
margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:.75in;
text-indent:-.25in;
font-size:11.0pt;
font-family:"Arial","sans-serif";}
span.ARTACAPL4Char
{mso-style-name:"ARTACAP_L4 Char";
mso-style-link:ARTACAP_L4;
font-family:"Arial","sans-serif";}
p.ARTACAPL4, li.ARTACAPL4, div.ARTACAPL4
{mso-style-name:ARTACAP_L4;
mso-style-priority:99;
mso-style-link:"ARTACAP_L4 Char";
margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:1.25in;
text-indent:-.25in;
font-size:11.0pt;
font-family:"Arial","sans-serif";}
span.ARTACAPL5Char
{mso-style-name:"ARTACAP_L5 Char";
mso-style-link:ARTACAP_L5;
font-family:"Arial","sans-serif";}
p.ARTACAPL5, li.ARTACAPL5, div.ARTACAPL5
{mso-style-name:ARTACAP_L5;
mso-style-priority:99;
mso-style-link:"ARTACAP_L5 Char";
margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:1.25in;
font-size:11.0pt;
font-family:"Arial","sans-serif";}
span.ARTACAPL6Char
{mso-style-name:"ARTACAP_L6 Char";
mso-style-link:ARTACAP_L6;
font-family:"Arial","sans-serif";}
p.ARTACAPL6, li.ARTACAPL6, div.ARTACAPL6
{mso-style-name:ARTACAP_L6;
mso-style-priority:99;
mso-style-link:"ARTACAP_L6 Char";
margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:2.5in;
text-indent:-.5in;
font-size:11.0pt;
font-family:"Arial","sans-serif";}
p.ARTACAPL7, li.ARTACAPL7, div.ARTACAPL7
{mso-style-name:ARTACAP_L7;
mso-style-priority:99;
margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:2.5in;
text-indent:-.5in;
font-size:11.0pt;
font-family:"Arial","sans-serif";}
p.ARTACAPL8, li.ARTACAPL8, div.ARTACAPL8
{mso-style-name:ARTACAP_L8;
mso-style-priority:99;
margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:2.5in;
text-indent:-.5in;
font-size:11.0pt;
font-family:"Arial","sans-serif";}
p.ARTACAPL9, li.ARTACAPL9, div.ARTACAPL9
{mso-style-name:ARTACAP_L9;
mso-style-priority:99;
margin-top:0in;
margin-right:0in;
margin-bottom:12.0pt;
margin-left:2.5in;
text-indent:-.5in;
font-size:11.0pt;
font-family:"Arial","sans-serif";}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle37
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle38
{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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">I will defer to
Avri and Matthew on this but I do want to say that I like
the idea of doing what is done for the ATRT to the extent
that that is possible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Chuck<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a class="moz-txt-link-abbreviated" href="mailto:cwg-stewardship-bounces@icann.org">cwg-stewardship-bounces@icann.org</a>
[<a class="moz-txt-link-freetext" href="mailto:cwg-stewardship-bounces@icann.org">mailto:cwg-stewardship-bounces@icann.org</a>]
<b>On Behalf Of </b>Jonathan Robinson<br>
<b>Sent:</b> Tuesday, April 12, 2016 8:40 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:cwg-stewardship@icann.org">cwg-stewardship@icann.org</a><br>
<b>Subject:</b> [CWG-Stewardship] FW: [client com] IFRT
Reports and Permitted Redactions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-IE">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-IE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-IE">Please
can you (especially Avri & Matthew) pay attention to the
request below from Sharon.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-IE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-IE">Thank-you.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-IE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-IE">Jonathan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D" lang="EN-IE"><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"><b>From:</b> Flanagan, Sharon [<a
moz-do-not-send="true"
href="mailto:sflanagan@sidley.com"><a class="moz-txt-link-freetext" href="mailto:sflanagan@sidley.com">mailto:sflanagan@sidley.com</a></a>]
<br>
<b>Sent:</b> 12 April 2016 02:28<br>
<b>To:</b> Client Committee <<a moz-do-not-send="true"
href="mailto:cwg-client@icann.org">cwg-client@icann.org</a>><br>
<b>Subject:</b> [client com] IFRT Reports and Permitted
Redactions<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-IE"><o:p> </o:p></span></p>
<p class="MsoNormal">Dear All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The current draft ICANN bylaws (Section
18.4(a)) includes below relating to the reports that PTI will
deliver to the IFRT:
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="ARTACAPL3" style="margin-left:.5in;text-indent:0in"><span
style="font-family:"Calibri","sans-serif";background:yellow;mso-highlight:yellow">Reports
provided by PTI pursuant to the IANA Naming Function
Contract and/or IANA Naming Function SOW during the IFR
period being reviewed, any portion of which may be redacted
(i) that reflects privileged advice from legal counsel; (ii)
includes PTI or ICANN trade secrets; (iii) where disclosure
to the IFRT would otherwise constitute a breach by PTI or
ICANN of a binding contractual obligation or legal
requirement to which PTI or ICANN is subject; or (iv) if
disclosed would present a material risk of negative impact
on the security, stability or resiliency of the DNS;</span><span
style="font-family:"Calibri","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The comment noted in the CWG response
circulated on 9 April 2016 was as follows:
<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span
style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span
style="color:black;background:yellow;mso-highlight:yellow">Has
the same redaction problem we find in other reviews. This
should be treated in the same way as confidential
information is treated in ATRT, i.e. signature of NDA (ref
Confidential Disclosure to Review Teams 4.6.a.vi). May need
to refer to EC right of inspection as appeal mechanism if
NDA is not a possible solution.</span><span
style="color:black">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">For reference
Section 4.6(a)(vi) provides as follows:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="ARTACAPL4" style="margin-left:1.75in"><span
style="font-size:12.0pt">(i)</span><span
style="font-size:7.0pt;font-family:"Times New
Roman","serif"">
</span><span
style="font-family:"Calibri","sans-serif"">Confidential
Disclosure to Review Teams:
<o:p></o:p></span></p>
<p class="ARTACAPL5" style="margin-left:1.75in"><span
style="font-size:12.0pt">(A)</span><span
style="font-family:"Calibri","sans-serif"">
To facilitate transparency and openness regarding ICANN’s
deliberations and operations, the Review Teams, or a subset
thereof, shall have access to ICANN internal information and
documents pursuant to the Confidential Disclosure Framework
set forth in the Operating Standards. The Confidential
Disclosure Framework must be aligned with the following
guidelines:<o:p></o:p></span></p>
<p class="ARTACAPL6" style="margin-left:3.0in"><span
style="font-size:12.0pt">(1)</span><span
style="font-size:7.0pt;font-family:"Times New
Roman","serif"">
</span><span
style="font-family:"Calibri","sans-serif"">ICANN
must provide a justification for any refusal to reveal
requested information. ICANN’s refusal can be appealed to
the Ombudsman and/or the ICANN Board for a ruling on the
disclosure request.<o:p></o:p></span></p>
<p class="ARTACAPL6" style="margin-left:3.0in"><span
style="font-size:12.0pt">(2)</span><span
style="font-size:7.0pt;font-family:"Times New
Roman","serif"">
</span><span
style="font-family:"Calibri","sans-serif"">ICANN
may designate certain documents and information as “for
review team members only” or for a subset of the review team
members based on conflict of interest. ICANN’s designation
of documents may also be appealed to the Ombudsman and/or
the ICANN Board.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.5in;text-indent:.5in">ICANN
may require review team members to sign a non-disclosure
agreement before accessing documents.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Can CWG please clarify what process is
being requested for redactions on reports provided to PTI? Is
the suggestion that 4.6(a)(vi) above replace what is currently
in 18.4(a))? If so, we understand that the Confidential
Disclosure Framework may not be final yet. Has CWG seen
drafts and is it comfortable with this process?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please let us know so that we can mark-up
the ICANN draft bylaws accordingly. This is a point on which
the CWG proposal is silent so there isn’t guidance contained
within the proposal.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Sharon<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif"">SHARON
R. FLANAGAN</span></b><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif""><br>
</span><span
style="font-size:9.0pt;font-family:"Arial","sans-serif""><br>
<br>
<b>SIDLEY AUSTIN LLP</b><br>
555 California Street<br>
Suite 2000<br>
San Francisco, CA 94104<br>
+1 415 772 1271</span><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif""><br>
</span><span
style="font-size:9.0pt;font-family:"Arial","sans-serif""><a
moz-do-not-send="true" href="mailto:sflanagan@sidley.com"
title="Click to send email to Flanagan, Sharon"><a class="moz-txt-link-abbreviated" href="mailto:sflanagan@sidley.com">sflanagan@sidley.com</a></a></span><span
style="font-size:12.0pt;font-family:"Times New
Roman","serif""><br>
<a moz-do-not-send="true" href="http://www.sidley.com"
title="www.sidley.com"><span
style="font-size:9.0pt;font-family:"Arial","sans-serif"">www.sidley.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:10.0pt;font-family:"Arial","sans-serif""
lang="EN-IE"><img moz-do-not-send="true" id="_x0000_i1025"
src="http://www2.sidley.com/files/upload/signatures/SIDLEY_150-AUTOSIG.png"
alt="SIDLEY" border="0" height="54" width="126"></span></b><span
style="font-size:10.0pt;font-family:"Times New
Roman","serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Times New
Roman","serif""> </span><o:p></o:p></p>
<p class="c4a0c8ff-067a-402c-bfec-95ed9cd1c28e"> <o:p></o:p></p>
<p>****************************************************************************************************<br>
This e-mail is sent by a law firm and may contain information
that is privileged or confidential.<br>
If you are not the intended recipient, please delete the
e-mail and any attachments and notify us<br>
immediately.<br>
<br>
****************************************************************************************************<o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
CWG-Stewardship mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/cwg-stewardship">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Matthew Shears | Director, Global Internet Policy & Human Rights Project
Center for Democracy & Technology | cdt.org
E: <a class="moz-txt-link-abbreviated" href="mailto:mshears@cdt.org">mshears@cdt.org</a> | T: +44.771.247.2987
CDT's Annual Dinner, Tech Prom, is April 6, 2016. Don't miss out - register at cdt.org/annual-dinner.</pre>
</body>
</html>