<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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle30
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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">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 WP3 Meeting #4 – 13 July 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"><a href="https://community.icann.org/x/6ao0Aw">https://community.icann.org/x/6ao0Aw</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></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<span style="color:#1F497D">.</span><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">ACTION Items<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM - Add your contribution to SO/AC accountability google doc. WP3 edits are needed by 06:00 UTC – 14 July.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM - Provide input to staff accountability document by 06:00 UTC – 14 July.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM: Send edits and comments on diversity document by 06:00 UTC – 14 July in preparation for WP3 call.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:7.5pt;line-height:14.3pt;background:white">
<span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:blue">ACTION ITEM: Leon to consolidate documents for discussion tomorrow. </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#333333"><o:p></o:p></span></p>
<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"><b><o:p> </o:p></b></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><u>Status of documents</u>: Diversity paper circulated. SO/AC accountability paper includes changes - no changes to staff accountability paper<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><b>SO/AC accountability - </b><a href="https://community.icann.org/pages/viewpage.action?pageId=53783727"><span style="color:#0563C1">https://community.icann.org/pages/viewpage.action?pageId=53783727</span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Edits from Jan were incorporated: we have added 1) operational rules and procedures of SO/ACs; 2) new language to proposals being made from subgroup; 3) commitment from SO/ACs to perform review
of accountability mechanisms.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Most of the work will be done in WS2 in interest of time but also in consideration of mechanisms that are envisioned as part of WS1 to ensure tasks are carried out. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><u>Feedback</u>:<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- We should understand roles of SO/ACs before evaluating accountability. It would be misleading to have comparable mechanisms. We should be difficult when drawing parallels. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Review needed to build beyond that. We need to be careful about expectations we are setting as we build our model.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Any of the enhanced accountability structures are attempting to give more power and oversight collectively. There is an enhance 360 problem. We need to have a high level statement. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- We are talking about SO/AC accountability to their own community. We are implicitly giving control to rest.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- We do not have time to deal with this issue - it should be postponed to WS2. We should not push for a specific area. SO/AC accountability is not a priority. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Stress Test suggested by NTIA are under discussion (capture - periodic reviews - new Charter might not be approve (caveat) - standard of review for internal capture).<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- We have to very specific about what we are leaving for WS2 (checklist). Minimum transparency benchmarks would be desired. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- There isn't much accountability language in SO/ACs documents.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><span style="color:#4472C4">ACTION ITEM - Add your contribution to SO/AC accountability google doc. WP3 edits are needed by 06:00 UTC – 14 July.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><b>Staff accountability - </b><a href="https://community.icann.org/display/acctcrosscomm/Staff+accountability"><span style="color:#0563C1">https://community.icann.org/display/acctcrosscomm/Staff+accountability</span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">Very little volunteers and no changes made to draft that was produced. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><u>Feedback</u>:<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- There are a number of ATRT2 recomendations that we should have started working on immediately - there has been no effort. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- No time to address this.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- We have been focused on Board accountability and have not dealt with staff accountability. Complaints about executive staff. How is senior staff held accountable? Is there anything we can do
about it? <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Education and audit is critical. The transparency is an issue - it is hard to audit that. Educate members to multistakehodler model is something that we often see as should come out. It takes
time to figure out what it is to be a member in organization like ICANN. ATRT is a place where more work can be done. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- We could not discharge CEO from his responsibility and go directly to staff. Staff is indirectly responsible. CEO and/or Board are responsible. Accountability remains with CEO.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">---> Recommend we schedule programs led by CEO. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- We are looking at accountability of staff overall<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- In discussing ICANN accountability, issue of Board and CEO was discussed. Important to resolve matter. Find ways and means to contribute. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><span style="color:#4472C4">ACTION ITEM - Provide input to staff accountability document by 06:00 UTC – 14 July.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><b>Diversity - </b><a href="https://community.icann.org/display/acctcrosscomm/Diversity"><span style="color:#0563C1">https://community.icann.org/display/acctcrosscomm/Diversity</span></a><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">How would we address diversity in our mechanisms? The document includes a non-exhaustive list of criteria. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><u>Feedback</u>:<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Competency , experience and regional distribution are the three criteria we should focus on for diversity. All elements are relevant but difficult to implement. It would be inappropriate to
eliminate competent people because of gender balance.<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">---> Suggestion to have different criteria that should be taken into account. Final decision would be left to appointing bodies. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Consider this from the root: lack of diversity in overall pool That is where substantial effort need to be made. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%">- Competence can be found in all groups. It is rather finding a way of nurturing that competence, including, engaging. We need to make way for their participation. Problem statement is too long
for purpose. <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><span style="color:#4472C4">ACTION ITEM: Send edits and comments on diversity document by 06:00 UTC – 14 July in preparation for WP3 call.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:8.0pt;line-height:106%"><span style="color:#4472C4">ACTION ITEM: Leon to consolidate documents for discussion tomorrow. <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="color:#1F497D"><o:p> </o:p></span></b></p>
</div>
</body>
</html>