<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="margin: 0px; font-size: 12px; min-height: 14px; "><br></div><div style="margin: 0px; font-size: 14px; ">Dear Co-Chairs, Dear Colleagues:</div><div style="margin: 0px; min-height: 14px; "><br></div><div style="margin: 0px; font-size: 14px; ">Further to today's SOAC Accountability SG conference call, I have re-read the draft report and have the following comments and suggestions:</div><div style="margin: 0px; font-size: 14px; min-height: 14px; "><br></div><div style="margin: 0px; font-size: 14px; ">1.<span class="Apple-tab-span" style="white-space:pre"> </span>The report is comprehensive, balanced and thorough. I can support the report as it stands without amendment should that be the WG's decision.</div><div style="margin: 0px; font-size: 14px; min-height: 14px; "><br></div><div style="margin: 0px; font-size: 14px; ">2.<span class="Apple-tab-span" style="white-space:pre"> </span>Regarding the question of open or closed conference calls, which was discussed on our call today, I would recommend that on pages 6 and 18, it should be made clear that closed meetings would be exceptional and justified <u>on a case by case basis</u>. Not as a general rule.</div><div style="margin: 0px; font-size: 14px; min-height: 14px; "><br></div><div style="margin: 0px; font-size: 14px; ">3.<span class="Apple-tab-span" style="white-space:pre"> </span>From that point of view, the sub-paragraph 4. at the bottom of page 23 could be redrafted slightly to refer to meetings that are <u>'exceptionally' closed… </u></div><div style="margin: 0px; font-size: 14px; "><span class="Apple-tab-span" style="white-space:pre"> </span>Such amendment would also respond to the point raised by RySG.</div><div style="margin: 0px; font-size: 14px; min-height: 14px; "><br></div><div style="margin: 0px; font-size: 14px; ">More generally, closed meetings within ICANN among commercially oriented stakeholders could give rise to allegations of collusion and should be discouraged. </div><div style="margin: 0px; font-size: 14px; ">It is important that ICANN, which is charged with promoting conditions of fair competition not be perceived as acquiescing in collusion among commercial stakeholders. </div><div style="margin: 0px; font-size: 14px; min-height: 14px; "><br></div><div style="margin: 0px; font-size: 14px; ">I trust that this is helpful</div><div style="margin: 0px; font-size: 14px; min-height: 14px; "><br></div><div style="margin: 0px; font-size: 14px; ">Regards</div><div style="margin: 0px; font-size: 14px; min-height: 14px; "><br></div><div style="margin: 0px; font-size: 14px; ">Christopher</div><div style="margin: 0px; font-size: 14px; "><br></div><div><div>On 27 Jul 2017, at 05:47, Cheryl Langdon-Orr <<a href="mailto:langdonorr@gmail.com">langdonorr@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_default"><font face="trebuchet ms, sans-serif"><br clear="all"></font></div><div class="gmail_default"><div class="gmail_default"><b><font face="trebuchet ms, sans-serif">Please join the Work Stream 2 - SO/AC <span class="gmail-m_3150598658363082981gmail-il">Accountability</span> Subgroup Meeting #26 on Thursday, 27 July @ 13:00 UTC.</font></b></div><div class="gmail_default"><font face="trebuchet ms, sans-serif"><br>CALL DETAILS: Link to Adobe Connect: <a href="https://participate.icann.org/mssi-projects" target="_blank">https://participate.<wbr>icann.org/mssi-projects </a></font></div><div class="gmail_default"><font face="trebuchet ms, sans-serif"><br></font></div><div class="gmail_default"><font face="trebuchet ms, sans-serif">Mobile: <a href="tel://1-712-770-4218*,,2731447">tel://1-712-770-4218*,,2731447</a><wbr>485# </font></div><div class="gmail_default"><font face="trebuchet ms, sans-serif">Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). </font></div><div class="gmail_default"><font face="trebuchet ms, sans-serif"><br></font></div><div class="gmail_default"><font face="trebuchet ms, sans-serif">After joining the call, as a courtesy to others and the presenters, please MUTE your phone. </font></div><div class="gmail_default"><font face="trebuchet ms, sans-serif">This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. </font></div><div class="gmail_default"><font face="trebuchet ms, sans-serif"><br></font></div><font face="trebuchet ms, sans-serif"><br></font><div class="gmail_default"><font face="trebuchet ms, sans-serif"><br></font></div><div class="gmail_default"><b><font face="trebuchet ms, sans-serif">Agenda </font></b></div><div class="gmail_default"><b><font face="trebuchet ms, sans-serif"><br></font></b></div><div class="gmail_default"><div><font face="trebuchet ms, sans-serif">0. Call Admin and Roll Call / Apologies (2min-<div class="gmail_default" style="display:inline"> </div><div class="gmail_default" style="display:inline"></div> CLO<div class="gmail_default" style="display:inline"></div> ) Apologies </font></div><div><font face="trebuchet ms, sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif">1. Welcome - Opening Remarks - Our aim and purpose for today's call (3-5 min- <div class="gmail_default" style="display:inline"></div>SDB, CLO)</font></div><div><font face="trebuchet ms, sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif">2. Review (brief) of last meeting records here and any Action Items (5-10 min- SDB, CLO) </font></div><div><font face="trebuchet ms, sans-serif"><font>Refer here to </font><span style=""> </span><span style="">revised report that reflects consensus of our subgroup on our 13-Jul call. This was first circulated this on 17-Jul, and </span><span style="">doc, pdf, and a redline, </span><span style="">sent again to our list earlier today. </span><span style=""> A Google Doc version is available </span><a href="https://docs.google.com/document/d/1ACU9BXxqBh0XPYGAZf3Lv2v7WMoyAvb5LN_MRc6jGJU/edit?usp=sharing" target="_blank">here</a><span style="">.</span></font></div><div><font face="trebuchet ms, sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif">3. Primary Agenda Item - Discussion <div class="gmail_default" style="display:inline"></div>(25<div class="gmail_default" style="display:inline"> -35</div> min SDB, FB, CLO)</font></div><div><ul><li><font face="trebuchet ms, sans-serif">Review Public Comment documentation, <span class="gmail-m_3150598658363082981gmail-il">and </span>consideration of any amendments to our recommendations, today we will start with the Good Practices section and call for consensus planning for edits to our documentation as reviewed.</font></li></ul><ul><li><font face="trebuchet ms, sans-serif">Start development of options for our FINAL Recommendation text edits or changes and then publish a report on results of the public consultation. To be inline with current timeline and milestone dates for WS2 project *completion* by end June 2018. <display new timeline slide BT> <br></font></li></ul></div><div><font face="trebuchet ms, sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif"><div class="gmail_default" style="display:inline">4</div>. Next Steps. (5 min- CLO, SB)</font></div><div><ul><ul><li style="margin-left:15px"><font face="trebuchet ms, sans-serif">- CCWG will also need to determine if any changes to our report are significant or not.<br>- If significant changes are recommended, CCWG-<span class="gmail-m_3150598658363082981gmail-il">Accountability</span> <span class="gmail-m_3150598658363082981gmail-il">WS2 </span>may require a second public consultation.<br>- If changes are not significant, CCWG-<span class="gmail-m_3150598658363082981gmail-il">Accountability</span> <span class="gmail-m_3150598658363082981gmail-il">WS2</span> can forward final recommendations to Chartering Organizations for approval, and then to the ICANN Board for consideration and adoption. Noting the timeline and Key milestone dates.<br><br></font></li></ul></ul></div><div><font face="trebuchet ms, sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif">5. AOB / Meeting Schedule (5 min- CLO)</font></div><div><font face="trebuchet ms, sans-serif">August Dates:</font></div><div><font face="trebuchet ms, sans-serif">Thursday 3rd @1900 UTC</font></div><div><font face="trebuchet ms, sans-serif">Thursday 10th @ 0500 UTC</font></div><div><font face="trebuchet ms, sans-serif">Thursday 17th @ 1300 UTC</font></div><div><font face="trebuchet ms, sans-serif">Thursday 24th @ 1900 UTC</font></div><div><font face="trebuchet ms, sans-serif">Thursday 31st @ 0500 UTC</font></div><div><font face="trebuchet ms, sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif"><br></font></div></div></div><div><div class="gmail-m_3150598658363082981gmail-m_-1714504013484703070gmail_signature"><div dir="ltr"><font face="trebuchet ms, sans-serif"><br><a href="http://about.me/cheryl.LangdonOrr" style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;color:rgb(58,169,233);text-decoration:none;line-height:18.2px" target="_blank"><table border="0" cellpadding="0" cellspacing="0" style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;vertical-align:baseline"><tbody style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;vertical-align:baseline"><tr style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;vertical-align:baseline"><td align="left" valign="top" style="padding:0px;border:0px;outline:0px;vertical-align:top;line-height:1"><div style="margin:0px;padding:0px;border:0px;outline:0px;vertical-align:baseline;line-height:1"><font color="#674ea7"><i>Cheryl Langdon-O</i><i>rr ... </i><span style="font-style:inherit">(CLO)</span></font></div><div style="font-style:inherit;margin:3px 0px 0px;padding:0px;border:0px;outline:0px;font-weight:inherit;vertical-align:baseline;color:rgb(43,130,173)"><br></div><div style="font-style:inherit;margin:3px 0px 0px;padding:0px;border:0px;outline:0px;font-weight:inherit;vertical-align:baseline;color:rgb(43,130,173)">about.me/cheryl.LangdonOrr</div></td></tr><tr style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;vertical-align:baseline"><td align="left" valign="top" style="padding:8px 0px 0px;border:0px;outline:0px;font-style:inherit;vertical-align:top;line-height:1"><div style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;vertical-align:baseline;text-align:right;background-color:rgb(197,208,224);height:4px"><img src="http://d13pix9kaak6wt.cloudfront.net/signature/colorbar.png" alt="Cheryl Langdon-Orr on about.me" width="88" height="4" style="margin: 0px; padding: 0px; border: 0px; outline: 0px; font-weight: inherit; font-style: inherit; vertical-align: baseline; float: right; display: block;"></div></td></tr><tr style="margin:0px;padding:0px;border:0px;outline:0px;font-weight:inherit;font-style:inherit;vertical-align:baseline"><td style="padding:0px;border:0px;outline:0px;font-style:inherit;vertical-align:baseline;height:20px"> </td></tr></tbody></table></a></font><div><font face="trebuchet ms, sans-serif"> </font></div></div></div></div>
</div>
_______________________________________________<br>Ws2-so_ac mailing list<br><a href="mailto:Ws2-so_ac@icann.org">Ws2-so_ac@icann.org</a><br>https://mm.icann.org/mailman/listinfo/ws2-so_ac<br></blockquote></div><br></body></html>