<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The notes, recordings and transcripts for the CCWG ACCT meeting with ICANN Board / ICANN 53 – 21 June will be available here:
<o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="https://community.icann.org/pages/viewpage.action?pageId=53781357">https://community.icann.org/pages/viewpage.action?pageId=53781357</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">A copy of the notes and action items may be found below.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">Kim<o:p></o:p></p>
<div style="border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:14.0pt">Notes<o:p></o:p></span></b></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Introduction</span></b><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:black">Objective is to improve accountability. There is inaccurate perception that tension. ICANN Board is fully committed to enhancing ICANN accountability. There is more cooperation in this process than might be perceived. We are trying to understand how mechanisms will work, what consequences will be. Whatever perceived weaknesses, we are a much stronger organization now. </span><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">We are impressed by effort that goes into this (phones, calls, physical meetings).</span><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-family:"Arial",sans-serif;color:black">CCWG Update</span></b><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:black">Thank you for opportunity to discuss where we are. We had a session in Singapore. We note a lot of Board participation in this process. Level of specifity from questions show. Happy the Board can follow up with questions. Other parts of community does not know what concerns were. Many comments were supportive of our approach. Enhancements to review and redress are considered to be right way to go. We have spent a lot of time analyzing comments to determine action needed. All comments have been discussed individually and in-detail. </span><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Support observed for four building blocks, review redress, and powers. Major themes were identified by community: diversity (operationalize diversity), openesss (proposal easy to understand - no barriers for </span><span style="font-size:11.5pt;font-family:"Arial",sans-serif;color:black">understanding</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">).
Level of complexity was challenged. Question of community mechanism is a question we entirely visited. No determination has yet been made on legal tool that would be used to enact powers. Reference Model: 5 votes for all groups except for SSAC RSSAC (2 votes). This has caused a lot of confusion: why this layer of additional entities? Who controls these entities? Who watches the watchers? There were multiple opportunities of options on how we could forward and we discussed this as a group through "salespitches". Common grounds were observed. We revisited list of requirements for accountability architecture to see whether this still stands after comment period. We determined there were options we could rule out. This reference model is now off table. We have entered discussion into new phase and are merging options. We are currently looking at leaving SO/ACs as they are - they would not register additional entities but they would express views when it comes to give opinion. Should they wish more formalized format, they can pass resolution to exercise community powers. That would be sufficient legal personality to have powers and authority. We would have staggered approach to firm up community powers. We are moving closer to consensus. It is important to understand how flexible we are in our thinking. </span><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">Feedback</span></b><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">- Appreciate openness and intention to keep it simple. We would like to make sure proposals remain as simple as possible while achieving what you are looking for. Detailed set of questions was given to identify questions that might arise in political processes once proposal gets submitted. Intent is to ensure there are clear answers to these questions. We recognize that questions will take time to consider. There is no expectation that all of them should be answered in a great deal of specificity. We would like to work in a collaborative manner with you. Objective is to focus on substance. There are parts that can be enhanced as we go forward. </span><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">- Impressed with willingness to look at different models. Concerned about external review. Is external judiciary review
a necessary part ? Is it a "show-stopper" if not in proposal? </span><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black">--> We have had assistance from Counsel on this subject to correction. Do we need mechanism of ultimate enforceability? The community is split on this. </span><span style="font-family:"Arial",sans-serif;color:black">If you come up with options that gives enforceability what are your options.
There are adaptive means of challenging disputes through that. Government don't have ability to enter into arbitration. That is not a done deal. But the scary process of spending in California Court should be taken off table.</span><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:black">- What would the impact of this new structure be on ICANN? What about if structure of ICANN change? </span><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">--> How could we do that without going into Bylaws?</span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">- It is based on current constituency - you need to think about future. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">--> This is an important aspect. It is something we need to consider. Key question will be how to safeguard when strong reform happens: should it be something the Board can do on its own? Or is it something the community can have a veto on. It is a discussion we will have in our group. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">--> Every single proposal on table involves revising current Bylaws. There is no proposal that doesn't involve that. Cannot imagine circumstance where Bylaws would not be amended to implement recommentation.</span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">--> CCWG participant expresses appreciation to CoChairs, staff. Congratulates Chair on reflection something does not work. For two areas of empowered community, independent review mechanisms, with 2/3 models we have - how can these powers be exercised? Without UAs, what are
the modalities to make it possible? Mechanisms of independent review (selection, diversity) - it should be clarified whether ICANN selects or pre-selects. There should be changes to transfer Board power to community. If some or few of SO/ACs decided not to be part of mechanism, what is the status of SO/AC with respect to collective decision?</span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">--> Questions were initially perceived as hostility. They will help us move forward. Appreciate helpful nature of comments. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt">- Restructuring is an issue for the future. Recommendation is to move foward step by step. Simplicity question was already raised. Have a good contribution for WS1 to enable transition. At end of WS2 could move to WS3 which could include restructuring. This will be a task for tomorrow </span><span style="font-size:11.5pt;font-family:"Arial",sans-serif">–</span><span style="font-size:12.0pt"> ICANN
2020. If you want to do everything at once, you will fail. </span><span style="font-size:12.0pt;font-family:"Arial",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">--> There is no intention to restructure SO/ACs. It is not what we were tasked to do. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">-->The problems are not that challenging if we end up giving SO/ACs equal say in governance. If we invent a brand new construct, we will need to think carefully of where they fit. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">---> We are looking at community input into Bylaws, strategic decisions, Board recall - three categories that are simple. If we have big picture right, we get everything right. Bylaws are natural home for organization - its changes is not a huge undertaking. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt">- Thanks for hard work. Specific comment regarding proposal to reject budget - Concerns. I have not seen mechanisms on how this would work. There are three unintended consequences: 1) budget paralysis whereby members of community vote against each other to facilitate
personal interest; 2) Threat to financial stability of ICANN - proposal gives rights without </span><span style="font-size:11.5pt">responsibilities</span><span style="font-size:12.0pt">; 3) Unfairness - final budget decisions will be made by community who do not act in interest of all global stakeholders. Food for thought.</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">--> Budget operating plan are critical parts. We have to juggle requirements of CWG. All concerns that are being raised are important ones and we have already tackled part of them: thresholds, new issues to delay budget. More work needed. There will need
to be adjustments. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">---> Board is from community. It should be spelled out more often. The Board is still last resort. The community needs the Board since it will change the Bylaws. We need to work together as closely as possible. This organization needs to be as flexible as possible. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">- Triumph of multistakeholder model. If transition does not happen, we can always talk about this effort as example that it works. What we have built at ICANN is very delicate. As you enter transition, last thing we need is to destabilize delicate balance. It is designed to be a model that includes Bylaws but also people. What you do is critical: you are strenghtening what we have but please do it with care. Will the model be perfect at conclusion? No - this is a continous improvement. We should avoid creating special interest powers and some are trying. Let's not reanchor ICANN in a US jurisdictional by mistake. We are trying to globalize ICANN. Your work is important and we will support you for it. We will need to be responsible for what we are buidling. This is a model for generations. This model should survive scrutiny of time. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">- How do we want to reply to public comments? </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">--> We are using same PCRT as is used for PDPs. We have populated answers and summaries have been produced. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="color:black">Next Steps & resources</span></b><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Urgent task to start amending Bylaws to bring them in alignment with CCWG-Acct work. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:12.0pt">--> Welcomes suggestion to have more regular calls and dialogues. Encourages Board members to participate directly. Outstanding contributions from Bruce, Erika, Chris, Wolfgang bringing value in flagging concerns and experience. We need to fully </span><span style="font-size:11.5pt">understand</span><span style="font-size:12.0pt"> what underlying concerns are. We need dialogue as much as possible with as many of you. </span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">--> Drafting of Bylaws needs to be tackled as soon as possible. Some of proposals are very mature. Let's put them in next phase as early as possible in cooperation with ICG. We need to assess
consequences of overall Bylaws when we change one single article. Our groups cannot have perfect expertise in all Bylaws. We will welcome technical assistance on Bylaws drafting. Useful to community to know that this is being kicked off. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="color:black">Conclusions</span></b><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">--> We appreciate comments received and will incorporate them in next iteration of document. We look forward to working with staff</span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">- Technical assistance will be made available as soon as possible. Details will be announced. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">- We want to facilitate process. Our intention has already been in direction of what it takes to implement. There is concern that have procedure. We don't want to shortcircuit. We are equally focused on this
at Board level. </span><span style="font-size:10.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">Nature of substance: we are willing to have extreme failure instances. There is interesting interplay. We have time pressure. Useful to move this forward as rapidly as possible.
We anticipate this is not the last and final iteration process. There will a requirement to continue process – it is evolving. Impact is enormous. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:#1F497D"><o:p> </o:p></span></b></p>
</div>
</body>
</html>