<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">+1 for 40 days. Let's not fool around.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 12, 2015 at 11:45 AM, 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">No, they don't, in fact.<br>
<br>
It's intentional.<br>
<span class="HOEnZb"><font color="#888888"><br>
el<br>
--<br>
Sent from Dr Lisse's iPad mini<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> On 12 Nov 2015, at 18:18, Nigel Roberts <<a href="mailto:nigel@channelisles.net">nigel@channelisles.net</a>> wrote:<br>
><br>
> Indeed. Agree 100%.<br>
><br>
> As one Government type put it to me in Dublin, off the record ...<br>
><br>
> "they SERIOUSLY expect that any substantive work is done in the public sector over the Christmas period????"<br>
><br>
><br>
><br>
><br>
>> On 11/12/2015 04:07 PM, Malcolm Hutty wrote:<br>
>> I agree with Phil's reasoning as to why any extension is required.<br>
>><br>
>> However, given that the public comment period would span the holiday<br>
>> season, I would suggest that public comment not close until Friday 8th<br>
>> January.<br>
>><br>
>> This will materially relieve any criticism that we have made it<br>
>> unreasonably difficult for comments to be assembled by choosing dates<br>
>> that co-incide with the holiday season, without causing any significant<br>
>> additional delay.<br>
>><br>
>> Malcolm.<br>
>><br>
>>> On 12/11/2015 15:32, Phil Corwin wrote:<br>
>>> On one hand I am relieved to see this as I was planning to post an email<br>
>>> today urging the Co-Chairs to either postpone issuance of the Executive<br>
>>> Summary until there was actually a completed final Proposal to<br>
>>> summarize, or to relabel it so that it would be clear that it was not a<br>
>>> document reflecting final resolutions of key issues on which formal<br>
>>> comments could be based. You have taken the second course and chosen to<br>
>>> label it as “Formal Update on our progress in and after the Dublin meeting”.<br>
>>><br>
>>><br>
>>><br>
>>> On the other hand, this decision now makes clear that the length of the<br>
>>> public comment period is inadequate. In the CCWG’s October 22^nd<br>
>>> Statement<br>
>>> <<a href="https://www.icann.org/news/blog/cross-community-working-group-on-enhancing-icann-accountability-icann54-co-chairs-statement" rel="noreferrer" target="_blank">https://www.icann.org/news/blog/cross-community-working-group-on-enhancing-icann-accountability-icann54-co-chairs-statement</a>><br>
>>> this appears:<br>
>>><br>
>>> The current timeline proposes posting a high-level overview of<br>
>>> recommendations and a summary of changes from the 2nd Draft Proposal for<br>
>>> a 35-day public comment on 15 November 2015. Alongside the 35-day public<br>
>>> comment, the CCWG-Accountability will submit these resources to the<br>
>>> Chartering Organizations for initial feedback. The CCWG-Accountability<br>
>>> plans to issue a full detailed report, including annexes and in-depth<br>
>>> documentation, mid-way into the public comment period for roughly 20<br>
>>> days of consultation.<br>
>>><br>
>>><br>
>>><br>
>>> A Formal Update cannot legitimately be the basis of either public<br>
>>> comment or informed feedback from the Chartering organizations. Thus it<br>
>>> is clear that there is really only a 21-day public comment period under<br>
>>> the current timetable, starting with the November 30 release of the 3^rd<br>
>>> draft Proposal, if the current target of December 21 is adhered to. This<br>
>>> is inadequate for a matter of this importance and complexity, and<br>
>>> considering the major differences between the Member and Designator models..<br>
>>><br>
>>><br>
>>><br>
>>> *Therefore I again urge the CCWG to extend the public comment period<br>
>>> deadline to at least December 30 to permit a 30-day comment period,<br>
>>> which should be the minimum requirement in this case.*<br>
>>><br>
>>> * *<br>
>>><br>
>>> Lastly, I do not think that the issuance of a Formal Update obviates the<br>
>>> need for an Executive Summary to accompany the 3^rd draft proposal. Such<br>
>>> a Summary could be extremely useful in assisting the community in<br>
>>> understanding the document, particularly by explaining how the key<br>
>>> remaining issues were resolved.<br>
>>><br>
>>><br>
>>><br>
>>> Thank you for consideration of my views.<br>
>>><br>
>>><br>
>>><br>
>>> *Philip S. Corwin, Founding Principal*<br>
>>><br>
>>> *Virtualaw LLC*<br>
>>><br>
>>> *1155 F Street, NW*<br>
>>><br>
>>> *Suite 1050*<br>
>>><br>
>>> *Washington, DC 20004*<br>
>>><br>
>>> *202-559-8597/Direct*<br>
>>><br>
>>> *202-559-8750/Fax*<br>
>>><br>
>>> *202-255-6172/cell***<br>
>>><br>
>>> * *<br>
>>><br>
>>> *Twitter: @VlawDC*<br>
>>><br>
>>><br>
>>><br>
>>> */"Luck is the residue of design" -- Branch Rickey/*<br>
>>><br>
>>><br>
>>><br>
>>> *From:*<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><br>
>>> [mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>] *On Behalf Of<br>
>>> *Mathieu Weill<br>
>>> *Sent:* Thursday, November 12, 2015 8:22 AM<br>
>>> *To:* <a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a><br>
>>> *Subject:* [CCWG-ACCT] Status of summary document<br>
>>><br>
>>><br>
>>><br>
>>> Dear Colleagues,<br>
>>><br>
>>><br>
>>><br>
>>> The activity on the list has been very intense lately. As co-chairs we<br>
>>> would like to warmly thank all commenters on the recent documents. The<br>
>>> feedbacks were extremely helpful, whether on substance or format, and<br>
>>> our support team is working hard to take your feedback in account for<br>
>>> the updated version.<br>
>>><br>
>>><br>
>>><br>
>>> You will remember that a lot of concerns were raised that what the CCWG<br>
>>> is working on is difficult to understand for those who are not following<br>
>>> the groups intense work. In response to that, we have discussed and<br>
>>> agreed we would publish a document explaining in plain language what we<br>
>>> are doing. We have factored this into the agreed plan.<br>
>>><br>
>>><br>
>>><br>
>>> At the time, we had expected to having reached consensus on all<br>
>>> remaining questions. As this is not the case today, we suggest flagging<br>
>>> this accordingly and move forward with the publication of the document,<br>
>>> which we would call a *Formal Update on our progress in and after the<br>
>>> Dublin meeting*, rather than an executive summary.<br>
>>><br>
>>><br>
>>><br>
>>> Many of you have correctly stated that the document we shared with you<br>
>>> is not an executive summary due to its length. It is rather a short<br>
>>> version of our report without offering information on the rationale for<br>
>>> decisions and the genesis of our recommendation. This level of detail<br>
>>> will be found in our report. We have, however, added a 2 page abstract<br>
>>> in addition to incorporating a plethora of your suggestions to make this<br>
>>> document accurate, more accessible and shorter.<br>
>>><br>
>>><br>
>>><br>
>>> To be clear:<br>
>>><br>
>>><br>
>>><br>
>>> The document that we are planning to issue on Nov 15 is designed to<br>
>>> update the community on the progress we have made during and after ICANN<br>
>>> 54. Its goal is to raise awareness of where we are, what our proposals<br>
>>> are, so that outreach can start and consideration of our final report<br>
>>> (announced for Nov 30th) can take place in a shorter time frame.<br>
>>><br>
>>><br>
>>><br>
>>> While the content of the document would reflect the positions of our<br>
>>> group, closing outstanding issues is not a requirement before issuing<br>
>>> this formal update. Outstanding issues will be flagged as such. What is<br>
>>> needed is a high level summary, as well as some level of detail<br>
>>> regarding the topics we made progress on in Dublin : decision making,<br>
>>> sole designator model, budget, individual director removal, and human<br>
>>> rights.<br>
>>><br>
>>><br>
>>><br>
>>> Our public comment period will then focus on soliciting feedback on<br>
>>> these changes in order to avoid the duplication of efforts for<br>
>>> commenters on areas of our report that already enjoyed broad support.<br>
>>><br>
>>><br>
>>><br>
>>> With the full report, we will offer the opportunity to publish minority<br>
>>> statements.<br>
>>><br>
>>><br>
>>><br>
>>> We do hope that you find these clarifications and suggestions helpful.<br>
>>> We will circulate the next version of the Update within the next 12<br>
>>> hours, and the discussion of the document will be on the agenda of our<br>
>>> call on Friday 13 November, at 6.00 UTC.<br>
>>><br>
>>><br>
>>><br>
>>> Many thanks again to all of you for your continued commitment.<br>
>>><br>
>>><br>
>>><br>
>>> Thomas, Leon and Mathieu<br>
>>><br>
>>> Co-chairs<br>
>>><br>
>>> ------------------------------------------------------------------------<br>
>>><br>
>>> No virus found in this message.<br>
>>> Checked by AVG - <a href="http://www.avg.com" rel="noreferrer" target="_blank">www.avg.com</a> <<a href="http://www.avg.com" rel="noreferrer" target="_blank">http://www.avg.com</a>><br>
>>> Version: 2015.0.6140 / Virus Database: 4450/10889 - Release Date: 10/25/15<br>
>>> Internal Virus Database is out of date.<br>
>>><br>
>>><br>
>>><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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><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" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</div></div></blockquote></div><br></div>