<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;"><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><span style="font-size: x-large;">CCWG,</span></div><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><font size="5"><br></font></div><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><font size="5">We appreciate the continued work that the CCWG is doing to consider the public comments received on its second draft report. Following the Los Angeles F2F we have heard suggestions that a Designator model relying on California statutes may be a replacement for the Sole Member model that was in the second draft report.<o:p></o:p></font></div><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><o:p><font size="5"> </font></o:p></div><div style="margin: 0in 0in 0.0001pt;"><font size="5">To be clear, the concerns that the Board raised on the Sole Member model still apply to a Designator model. The Designator model still introduces a new legal structure with powers that are intrinsically beyond the structure we have been using. We understand that many believe it is possible to constrain these powers in order to provide established protections, accountability and thresholds: This is unproven territory and will require more detail and time to understand and test the impact on our bedrock multistakeholder balance. </font></div></div></div></div><font size="5"><br></font><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="margin: 0in 0in 0.0001pt;"><font size="5">Further, it is unclear that this would represent the full multistakeholder community because we do not know yet which SO/ACs will join now or later. Moreover, the same community accountability issues present in the Sole Member are present in the Designator model.</font></div></div></div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><font size="5"><o:p></o:p></font></div><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><o:p><font size="5"> </font></o:p></div><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><font size="5">Steve del Bianco’s constructive suggestion over the weekend that the Board could commit to a future governance structure review triggered by key factors seems like a good path forward. This can be enshrined in a new fundamental bylaw that would require the holding of a future governance structure review if SOs and ACs agree to kick off that review.</font></div><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><o:p><font size="5"> </font></o:p></div><div style="margin: 0in 0in 0.0001pt; font-family: Cambria;"><font size="5">We are all in complete agreement on the objective of enforcement of the five community powers, with new/stronger mechanisms for board removal if/when necessary. Let’s focus on finalizing the details on these consensus elements to enable implementation and a successful transition. </font></div><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><font size="5"><br></font></div><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><font size="5">Steve Crocker</font></div><div style="font-family: Cambria; margin: 0in 0in 0.0001pt;"><font size="5">for the ICANN Board of Directors</font></div></div></div></div><br></div></div><br></body></html>