<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">For the record, when the AoC was presented to the ICANN board September 2009 we raised an immediate objection to the original text of the Whois review. We got pushback that the entire text had been negotiated and it would put at risk the adoption of the Affirmation of Commitments. We have been wrestling with this “detail” for six years. There is no reason to perpetuate inappropriate text. As I had said early in the process, I think in reference to the IANA contract, it is a misperception/misunderstanding to assume that the existing text is some sort of gold standard. There is LOT of experience with the relationship between the text in both the IANA contract and the AoC document and what’s needed in practice.<div><br></div><div>We’re not trying to reduce our commitments or make major changes, but there is no reason to perpetuate non-sensical provisions and ignore the accumulated experience.</div><div><br></div><div>Steve</div><div><br><div><br></div><div><br><div><div>On Jul 17, 2015, at 10:40 AM, Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; 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;" type="cite">
<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;" type="cite">
<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;" type="cite">
<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="MAC_OUTLOOK_SIGNATURE">
<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>
<span><2015-07-17 DRAFT FOR 2nd REPORT - AoC Reviews into Bylaws - V4.docx></span>_______________________________________________<br>WP1 mailing list<br><a href="mailto:WP1@icann.org">WP1@icann.org</a><br>https://mm.icann.org/mailman/listinfo/wp1<br></blockquote></div><br></div></div></body></html>