<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;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
Today the BC agreed to share these points about the draft new bylaws, regarding the SSR and WHOIS Affirmation Reviews. </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;">
These 2 reviews are <u>already</u> late per the Affirmation requirements, and would also be “late" when we add the review requirement to the Bylaws. The BC is not troubled by a new Bylaw that also requires ICANN to begin the next SSR and WHOIS review as soon
as possible. </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 style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div><br>
</div>
<div>Draft Bylaws Section 4.6 (c) (v), regarding timing of the Security, Stability, and Resiliency (SSR) review required under the Affirmation of Commitments, which is now to be brought into ICANN bylaws.</div>
<div><br>
</div>
<div>Text from new Bylaws: "The SSR Review shall be conducted no less frequently than every five years, measured from the date the previous SSR Review Team was convened."</div>
<div><br>
</div>
<div><b>BC Comment</b>: The previous SSR review was convened in 2010, so a 5-year interval would require the next review by Oct-2015. Some CCWG members are concerned that the above text creates a new problem since the SSR review would be at least 1 year late
at the time the Bylaws are approved. Those concerned are suggesting revisions to the draft Bylaws to avoid a situation where ICANN is immediately failing to honor its new Bylaws. </div>
<div><br>
</div>
<div>The SSR review is already later than is required under the Affirmation of Commitments, so ICANN is already failing to meet that obligation. We are not troubled by a new Bylaw that also requires ICANN to begin the next SSR review as soon as possible. </div>
<div><br>
</div>
</div>
<div><font face="Calibri,sans-serif">We prefer that ICANN follow through on the Board-approved 2016 start date for SSR-2 review. We expect SSR-2 to assess ICANN’s implementation of SSR-1, including the extent to which ICANN is prepared to meet future challenges
and threats to the security, stability, and resiliency of the Internet DNS, consistent with ICANN's limited technical mission.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
—</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div>
<div><font face="Calibri,sans-serif">Draft Bylaws Section 4.6 (e) (v), regarding timing of the Whois/Directory Service review required under the Affirmation of Commitments, which is now to be brought into ICANN bylaws.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Text from new Bylaws: "</font><span style="font-family: Calibri, sans-serif;">The Directory Service Review shall be conducted no less frequently than every five years, measured from the date the previous Directory Service
Review Team was convened.</span><font face="Calibri,sans-serif">”</font></div>
<div><span style="font-family: Calibri, sans-serif;"><br>
</span></div>
<div><font face="Calibri,sans-serif"><b>BC Comment</b>: The previous Whois review was convened in Oct-2010, so a 5-year interval would require the next review by Oct-2015. Some CCWG members are concerned that the above text creates a new problem since the
Whois/Directory Service review would be at least 1 year late at the time the Bylaws are approved. Those concerned are suggesting revisions to the draft Bylaws to avoid a situation where ICANN is immediately failing to honor its new Bylaws. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">The Whois review is already later than is required under the Affirmation of Commitments, so ICANN is already failing to meet that obligation. We are not troubled by a new Bylaw that also requires ICANN to begin the next
Whois/Directory Service review as soon as possible. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">We prefer that ICANN follow through on the Board-approved 2016 start date for Whois-2 review. We expect Whois-2 to assess ICANN’s implementation of Whois-1 and current Whois policy. We recognize that there are policy efforts
underway to develop a next generation registration directory service. As repeatedly reinforced by ICANN’s Board, however, the effort to replace Whois complements, and runs in parallel with, ICANN’s obligation to fully enforce existing consensus policy and
contractual conditions relating to Whois. </font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</body>
</html>