<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>Thanks. I accepted nearly all your edits.</div>
<div><br>
</div>
<div>One that I didn’t accept was on page 1:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>You said that AoC now requires ICANN to implement review team recommendations. </div>
<div>Not true. AoC requires only that "The Board will take action …”</div>
<div><br>
</div>
</blockquote>
<div>On p.2 You suggest we cite legal advice that we cannot require implementation. If you can find that advice, then let’s include that citation. But we stopped short of requiring implementation mainly because some recommendations might be justifiably rejected. </div>
<div><br>
</div>
<div>Can you dig-up anything useful for the non-disclosure bit on page 3?</div>
<div><br>
</div>
<div>Please accept the other edits in there and re-circ to WP1 before next call.</div>
<div><br>
</div>
<div>Thanks! </div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></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>Grace Abuhamad<br>
<span style="font-weight:bold">Date: </span>Tuesday, July 21, 2015 at 4:51 PM<br>
<span style="font-weight:bold">To: </span>Steve DelBianco, "<a href="mailto:wp1@icann.org">wp1@icann.org</a>"<br>
<span style="font-weight:bold">Cc: </span>Avri Doria<br>
<span style="font-weight:bold">Subject: </span>Re: [WP1] 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: 14px; font-family: Calibri, sans-serif;">
<div>Hi all, </div>
<div>Here are some suggested edits from Bernie and me. </div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; 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><<a href="mailto:wp1-bounces@icann.org">wp1-bounces@icann.org</a>> on behalf of Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>><br>
<span style="font-weight:bold">Date: </span>Monday, July 20, 2015 at 11:01 PM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:wp1@icann.org">wp1@icann.org</a>" <<a href="mailto:wp1@icann.org">wp1@icann.org</a>><br>
<span style="font-weight:bold">Cc: </span>Avri Doria <<a href="mailto:avri@acm.org">avri@acm.org</a>><br>
<span style="font-weight:bold">Subject: </span>[WP1] 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><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></div>
</div>
</span>
</body>
</html>