<div dir="ltr"><div><br></div>Main comment is on the reconsideration request (RfR) process. It appears greatly expanded. It is now involving the Board and Ombudsman for all RfRs, and scope for what is an acceptable RfR is much broader. A 120 decision is also much longer than most RfRs are taking. <div><br></div><div>The Ombudsman is currently one human with little budget. There is simply no way his/her office could handle 60+ RfR per year. One could expect regular RfR challenges of ICANN policy decisions, plus regular challenges of ICANN new gTLD or any TLD decisions as a result. Keep in mind ICANN envisions a rolling new gTLD programme, with continued applications over time. One could reasonably expect upwards of 100 RfR per year under this proposed model. </div><div><br></div><div>Moreover, it is unclear how it interacts with a standard Ombudsman complaint process, the DIDP, or the CEP/IRP. This is because at no point is the 'end to end' appeals / accountability process described. </div><div><br></div><div>This report - or the final version - should include a clear road map with case examples of complaints going through the process with a worst case scenario explored and considered by this group before being finalised. <br></div><div><br></div><div>In other words, this looks like a good description of the parts of the animal, but gives me little clue what the animal looks like. </div><div><br></div><div>Hopefully that's the next stage of the work. </div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div>Jacob Malthouse<br></div><div>Co-founder & Director, Big Room Inc. </div><div>778-960-6527</div><div><a href="http://www.bigroom.ca/" target="_blank">www.bigroom.ca</a> </div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On 20 April 2015 at 09:38, Dr Eberhard W Lisse <span dir="ltr"><<a href="mailto:el@lisse.na" target="_blank">el@lisse.na</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Dear Co-Chairs,</div><div><br></div><div>Thogh Mr Arasteh is technically incorrect as the Charter is unequivocally clear, that it must be done, I find myself in agreement otherwise.</div><span class=""><div><br>el<br>-- <span></span><div><span style="font-size:13pt">Sent from </span><span style="font-size:13pt">Dr Lisse's iPhone 6</span></div><div><br></div></div></span><div><div class="h5"><div><br>On Apr 20, 2015, at 15:34, Kavouss Arasteh <<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div>Thomas</div><div>It is a pity that there is no opportunity that minority from formal members of CCWG , s views could not be reflected in the report which could give the wrong impression that the output represent consensus.</div><div>In ICG we have the opportunity to include minority views after several chair,s attempt ti resolve that </div><div>Having said that it is necessary to indicate in the output dic.'that it does not represent the consensus</div><div>Kavouss </div><div><br>Sent from my iPhone</div><div><br>On 20 Apr 2015, at 15:54, Thomas Rickert <<a href="mailto:rickert@anwaelte.de" target="_blank">rickert@anwaelte.de</a>> wrote:<br><br></div><blockquote type="cite"><div><div>Dear Eberhard,</div><div>it is not foreseen in our charter to have minority views for other scenarios than the consensus recommendations. I suggest you use the public comment period to voice your concerns or indicate your preference where our report is providing options as I am sure many of the colleagues in the CCWG and their respective groups will do.</div><div><br></div><div>Thomas<br><br><div><span style="font-size:13pt">---</span></div><div><a href="http://rickert.net" target="_blank">rickert.net</a></div><div><br></div></div><div><br>Am 20.04.2015 um 15:42 schrieb Dr Eberhard W Lisse <<a href="mailto:el@lisse.na" target="_blank">el@lisse.na</a>>:<br><br></div><blockquote type="cite"><div><div>Dear Co-Chairs</div><div><br></div><div>indeed we do not have Consensus on the interim findings, so I intend to provide a minority viewpoint on the interim findings for public comment.</div><div><br></div><div>el <br>-- <span></span><div><span style="font-size:13pt">Sent from </span><span style="font-size:13pt">Dr Lisse's iPhone 6</span></div><div><br></div></div><div><br>On Apr 20, 2015, at 14:35, Thomas Rickert <<a href="mailto:rickert@anwaelte.de" target="_blank">rickert@anwaelte.de</a>> wrote:<br><br></div><blockquote type="cite"><div><div>Dear Eberhard,</div><div>please note that our group has not reached a consensus yet. As mentioned on numerous occasions during our calls, we plan to present our interim findings to the community and invite the community to comment. </div><div><br></div><div>The group will be alerted if and when we are asking for support with or objections to a set of recommendations that could form the consensus of the group. You will also be able to chime in when such final report is prepared for publication. </div><div><br></div><div>Thanks,</div><div>Thomas</div><div><br><div><span style="font-size:13pt">---</span></div><div><a href="http://rickert.net" target="_blank">rickert.net</a></div><div><br></div></div><div><br>Am 18.04.2015 um 12:28 schrieb Dr Eberhard W Lisse <<a href="mailto:el@lisse.na" target="_blank">el@lisse.na</a>>:<br><br></div><blockquote type="cite"><div><div>Dear Co-Chairs,</div><div><br></div><div>please advise how I will be able to attach my dissenting minority report (objecting against process and (lack of) substance) so it can be publicly commented on.</div><div><br></div><div>greetings, el<br><br>-- <div>Sent from Dr Lisse's iPad mini</div></div><div><br>On Apr 18, 2015, at 10:10, Thomas Rickert <<a href="mailto:thomas@rickert.net" target="_blank">thomas@rickert.net</a>> wrote:<br><br></div><blockquote type="cite"><div><div style="margin:0px">All, </div><div style="margin:0px">please find attached the draft report with the input we got from the sub-teams. They can also be found at<span style="font-family:Calibri,sans-serif;font-size:14px"> </span><a href="https://community.icann.org/display/acctcrosscomm/Draft+Report" style="font-family:Calibri,sans-serif;font-size:14px" target="_blank">https://community.icann.org/display/acctcrosscomm/Draft+Report</a>. This is the frozen version of the document until our intensive two work days. Please note that you know most of the information already. We suggest you focus on the recommendations of WP1 and WP2, since the introductory part is primarily narrative and giving context. The stress test have been discussed quite extensively already. We are working on summaries or tables to make it easier for you to digest the information, but we wanted to get the frozen draft report out to you as soon as possible. </div><div style="margin:0px">Such additional materials will be worked on in collaboration with the rapporteurs to ensure that we provide information in a more handy while not misrepresenting interim work results.</div><div style="margin:0px"><br></div><div style="margin:0px">Let us also use this opportunity to thank all of you, our fabulous rapporteurs and staff for their outstanding work and commitment.</div><div style="margin:0px"><br></div><div style="margin:0px">Kindest regards,</div><div style="margin:0px">León, Mathieu and Thomas</div><div style="margin:0px"><br></div><div style="margin:0px"><br></div><div style="margin:0px"></div></div></blockquote><blockquote type="cite"><div><Appendices - 17 April.pdf></div></blockquote><blockquote type="cite"><div><div style="margin:0px"></div></div></blockquote><blockquote type="cite"><div><CCWG-Report Draft v1.1.pdf></div></blockquote><blockquote type="cite"><div><div style="margin:0px"></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Accountability-Cross-Community mailing list</span><br><span><a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></div></blockquote></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Accountability-Cross-Community mailing list</span><br><span><a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></div></blockquote></div></blockquote></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Accountability-Cross-Community mailing list</span><br><span><a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></div></blockquote></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Accountability-Cross-Community mailing list</span><br><span><a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></div></blockquote></div></blockquote></div></div></div><br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>