<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
Update to reflect discussions in WP1 yesterday, regarding the non-disclosure provision.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div>
<div>CCWG is proposing giving AoC Review Teams access to ICANN internal documents, which includes some information that is proprietary or sensitive. This creates two disclosure concerns:</div>
<div><br>
</div>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div>First, what to do if ICANN redacts or withholds any information sought by a review team?</div>
<div>
<div id=""></div>
</div>
</blockquote>
</div>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><br>
</div>
<div>Second, of information that is shared with the review team, how to determine which information the Review Team must <u>not</u> disclose — in its report or otherwise?</div>
<div><br>
</div>
</blockquote>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
A subset of WP1 members (Alan Greenberg, Greg Shatan, James Gannon, Jordan Carter, and me) drafted new text, shown below and on page 3 of the attached doc.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><font face="Calibri,sans-serif">Confidential Disclosure to Review Teams:</font></div>
<div><font face="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. If ICANN refuses to reveal documents
or information requested by the review team, ICANN must provide a justification to the review team. If the review team is not satisfied with ICANN’s justification, it can appeal to the Ombudsman and/or the ICANN Board for a ruling on the disclosure request.
</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">For documents and information that ICANN does disclose to the review team, ICANN may designate certain documents and information as not for disclosure by the review team, either in its report or otherwise. If the review
team is not satisfied with ICANN’s designation of non-disclosable documents or information, it can appeal to the Ombudsman and/or the ICANN Board for a ruling on the non-disclosure designation. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">A confidential disclosure framework shall be published by ICANN. The confidential disclosure framework shall describe the process by which documents and information is classified, including a description of the levels of
classification that documents or information may be subject to, and the classes of persons who may access such documents and information</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">The confidential disclosure framework shall describe the process by which a review team may request access to documents and information that are designated as classified or restricted access</font><span style="font-family: Calibri, sans-serif;">.</span><span class="Apple-tab-span" style="font-family: Calibri, sans-serif; white-space: pre;">
</span><span style="font-family: Calibri, sans-serif;">The confidential disclosure framework must provide a mechanism to escalate and/or appeal the refusal to release documents and information to duly recognized review teams. </span></div>
</blockquote>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Steve DelBianco<br>
<span style="font-weight:bold">Date: </span>Monday, July 20, 2015 at 2:01 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:wp1@icann.org">wp1@icann.org</a>"<br>
<span style="font-weight:bold">Cc: </span>Jordan Carter, Avri Doria<br>
<span style="font-weight:bold">Subject: </span>Bringing AoC Reviews into ICANN Bylaws, v5 reflecting Paris Saturday discussion<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>Updated to reflect Saturday in Paris, where we said that commitments stated within the new gTLD and WHOIS reviews would stay in that section of the Bylaws, instead of moving them to the Core Values. </div>
<div><br>
</div>
<div>I have noted 1 area with yellow highlighting for follow-up:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>In the chapeau on page 3 we note the need to define confidentiality and non-disclosure rules when the review team accesses documents that ICANN management says are confidential, sensitive, or proprietary.</div>
<div><br>
</div>
</blockquote>
<div>—Steve</div>
<div><br>
</div>
<div>
<div id=""></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Steve DelBianco<br>
<span style="font-weight:bold">Date: </span>Friday, July 17, 2015 at 7:40 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>"<br>
<span style="font-weight:bold">Cc: </span>Jordan Carter, Avri Doria, "<a href="mailto:wp1@icann.org">wp1@icann.org</a>"<br>
<span style="font-weight:bold">Subject: </span>Bringing AoC Reviews into ICANN Bylaws, v4 reflecting Paris discussion<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>Today (17-Jul) we reviewed and revised the proposal to bring AoC Reviews into the ICANN Bylaws.</div>
<div><br>
</div>
<div>By my notes, here are the changes we agreed today:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>Preference for option 2 on team composition, so removed 3-May proposal and Option 1.</div>
<div><br>
</div>
<div>Allow ATRT to <u>amend</u> these reviews, too. </div>
<div><br>
</div>
<div>Add 1 ICANN board member to each review team under option 2. Note that our 3-May draft had a board member on each team.</div>
<div><br>
</div>
<div>Bruce Tonkin suggested requiring review teams to <u>Prioritize</u> their recommendations. We heard several objections to making that a requirement, so I added it as a suggestion: "The review team should attempt to assign priorities to its recommendations."</div>
</blockquote>
<div><br>
</div>
<div>Remaining challenges:</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><br>
</div>
<div>How to give review team access to ICANN Internal documents, while preventing disclosure/publication of information that is sensitive, confidential, or proprietary? Do we impose sanctions for unauthorized disclosure? HELP NEEDED HERE.</div>
</blockquote>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>Steve Crocker recommended changing the AoC commitments for WHOIS/Directory Services. We heard some agreement with that idea, but strong cautions about attempting to drop WHOIS commitments as part of the transition. Instead, amendments to the WHOIS/Directory
Services review could be recommended by the first post-transition ATRT.</div>
<div><br>
</div>
<div><br>
</div>
</blockquote>
<div>
<div>
<div id="">
<div>—</div>
<div>
<div>Steve DelBianco</div>
<div>Executive Director</div>
<div>NetChoice</div>
<div><a href="http://www.netchoice.org/">http://www.NetChoice.org</a> and <a href="http://blog.netchoice.org/">http://blog.netchoice.org</a></div>
<div>+1.703.615.6206</div>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</span></div>
</div>
</span>
</body>
</html>