<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;" class="">Thank you very much for this information Rinalia.<div class=""><br class=""></div><div class="">I believe it would be of great benefit for Jamie to have a look and understand the work Garth has been doing on this matter.</div><div class=""><br class=""></div><div class="">Maybe we should try to find a time to speak to Jamie on this?</div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div class="">Best regards,</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">León</div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">El 11/04/2017, a las 13:35, Rinalia Abdul Rahim <<a href="mailto:rinalia.abdulrahim@gmail.com" class="">rinalia.abdulrahim@gmail.com</a>> escribió:</div><br class="Apple-interchange-newline"><div class="">Dear ALAC and Regional Leaders,<div class=""><br class=""></div><div class="">FYI below. At-Large views would be extremely valuable for continuous improvement of ICANN compliance.</div><div class=""><br class=""></div><div class="">Best regards,</div><div class=""><br class=""></div><div class="">Rinalia<br class=""><div class=""><br class=""></div><div class=""><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri">Jamie Hedlund's bog that was just posted on improving contractual compliance:<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri"> <a href="https://www.icann.org/news/blog/improving-contractual-compliance" class="gmail_msg" target="_blank">https://www.icann.org/news/blog/improving-contractual-compliance</a><u class="gmail_msg"></u><u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><b class="gmail_msg"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri">Improving Contractual Compliance<u class="gmail_msg"></u><u class="gmail_msg"></u></span></b></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><b class="gmail_msg"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></b></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri">About ten days ago, members of the Registry Stakeholder Group (RySG) and the Intellectual Property Constituency (IPC) submitted a document entitled, “<a href="https://www.icann.org/en/system/files/correspondence/rysg-ipc-to-compliance-28mar17-en.pdf" class="gmail_msg" target="_blank">Joint Recommendations for ICANN Compliance</a>.” A few months into my new role leading Contractual Compliance and Consumer Safeguards, I appreciated the constructive input from these two constituencies.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri">At a <a href="https://community.icann.org/pages/viewpage.action?pageId=63144494&preview=/63144494/64069639/transcript_ncphlunch_140217.pdf" class="gmail_msg" target="_blank">session</a> at the <a href="https://community.icann.org/pages/viewpage.action?pageId=63144494" class="gmail_msg" target="_blank">Non-Contracted Parties House Intercessional 2017</a> in Reykjavik, in sessions at the ICANN58 Community Forum with <a href="https://schd.ws/hosted_files/icann58copenhagen2017/9f/I58CPH_Sun12Mar2017-ALAC%20and%20Regional%20Leaders%20Working%20Session%20Part%208-en.pdf" class="gmail_msg" target="_blank">the At-Large Community</a>, <a href="https://schd.ws/hosted_files/icann58copenhagen2017/03/Transcript%20RySG_Part%20I_14%20March%202017_Transcript%5B1%5D.pdf" class="gmail_msg" target="_blank">the Registry Stakeholder Group</a>, <a href="https://schd.ws/hosted_files/icann58copenhagen2017/2c/Transcript%20RrSG%20meeting%20I%2014%20March%20.pdf" class="gmail_msg" target="_blank">the Registrar Stakeholder Group</a>, <a href="https://schedule.icann.org/event/9nnX/ssac-private-meeting-c" class="gmail_msg" target="_blank">the Security and Stability Advisory Committee</a>, <a href="https://schd.ws/hosted_files/icann58copenhagen2017/6c/Transcript%20BC%2014%20March%20Copenhagen%5B1%5D.pdf" class="gmail_msg" target="_blank">the Business Constituency</a>, <a href="https://schd.ws/hosted_files/icann58copenhagen2017/90/2017_03March_14%20IPC%20Open%20Meeting%20Transcription.pdf" class="gmail_msg" target="_blank">the Intellectual Property Committee</a>, and <a href="https://participate.icann.org/p3rrfzfm4p9/?launcher=false&fcsContent=true&pbMode=normal" class="gmail_msg" target="_blank">the Governmental Advisory Committee</a> in Copenhagen, and during formal and informal calls with community members, there were lively discussions regarding the need for improvements in Contractual Compliance.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri">To help us succeed in making desired changes, I asked for examples of where we could do better, as well as specific and concrete recommendations that we could implement. I was specifically asking for more than general statements such as “ICANN isn’t transparent” or “ICANN is bad at compliance”. The RySG-IPC Joint submission, which I understand was underway before these recent discussions, includes recommendations that are clear and specific and can be assessed for feasibility, cost and effort. And that’s just what we in Contractual Compliance will do.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri">There is another effort underway that also recommends improvements to Contractual Compliance. In the “<a href="https://www.icann.org/public-comments/cct-rt-draft-report-2017-03-07-en" class="gmail_msg" target="_blank">Competition, Consumer Trust and Consumer Choice Review Team Draft Report of Recommendations for New gTLDs</a>,” the Review Team seeks input on recommendations related to Contractual Compliance. In particular, Recommendation 23 urges ICANN to “Include more detailed information on the subject matter of complaints in ICANN publicly available compliance reports.” The draft recommendations are now out for public comment. This is an excellent opportunity for community members to provide input just as RySG and IPC representatives have done. (Full disclosure – I am a member of the CCT-RT).<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri">If you have examples of where Contractual Compliance could improve, especially on its commitment to transparency, and specific and concrete recommendations on how to improve ICANN’s Contractual Compliance function, please consider submitting them to the CCT-RT Public Comment forum. Alternatively, please submit them by email to me at <a href="mailto:jamie.hedlund@icann.org" class="gmail_msg" target="_blank">jamie.hedlund at icann.org</a>. Once the public comment period on the CCT-RT’s closes, we will review all of the input we receive and provide a report on changes that we will undertake as well as a rationale for not undertaking others. Please send us your good ideas!<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p><p class="MsoNormal gmail_msg" style="color:rgb(49,49,49);word-spacing:1px"><span class="gmail_msg" style="font-size:11pt;font-family:Calibri"><u class="gmail_msg"></u> END</span></p></div></div>
_______________________________________________<br class="">ALAC mailing list<br class=""><a href="mailto:ALAC@atlarge-lists.icann.org" class="">ALAC@atlarge-lists.icann.org</a><br class="">https://atlarge-lists.icann.org/mailman/listinfo/alac<br class=""><br class="">At-Large Online: http://www.atlarge.icann.org<br class="">ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</div></blockquote></div><br class=""></div></body></html>