<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I agree with the proposed structure of the Report. And fully agree with caution/ warning that we should not rush for the preparation of the draft.</div><div>Elements that are carefully prepared and fully examined nay be submitted and those yet to be submitted will carefully be prepared , examined and submitted once completed. NO rush</div><div>Regards</div><div>Kavouss<br><br>Sent from my iPhone</div><div><br>On 11 Oct 2015, at 10:17, Matthew Shears <<a href="mailto:mshears@cdt.org">mshears@cdt.org</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=windows-1252" http-equiv="Content-Type">
Likewise. Excellent suggestions. Readability and clarity will be
key to militating perceptions of complexity.<br>
<br>
<div class="moz-cite-prefix">On 11/10/2015 04:08, Jordan Carter
wrote:<br>
</div>
<blockquote cite="mid:CAK2bTy_HuigSyMt=v1t6Ci9j2Ut6_9jyPaDMbxdex2dt4Zhnww@mail.gmail.com" type="cite">
<div dir="ltr">I completely agree.
<div><br>
</div>
<div>1) A readable, simple high level summary is one report and
should in my view be our core "output".</div>
<div><br>
</div>
<div>2) Then a chapter by chapter "operationalisation" report
that explains the design intent and details, more clear but
maybe about the same length as the body of our current report.</div>
<div><br>
</div>
<div>3) Then a report that is the detailed draft Bylaws
framework that sets out precisely how it would / could look in
the rules.</div>
<div><br>
</div>
<div>4) Then a process / options considered etc report.</div>
<div><br>
</div>
<div>They all have different audiences. 4) is vital for NTIA and
for policy focused people. 3) is the concrete and crystal
clear detail we haven't yet provided. 2) explains the logic.
1) presents the vision.</div>
<div><br>
</div>
<div>Jordan</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 8 October 2015 at 04:52, Greg Shatan
<span dir="ltr"><<a moz-do-not-send="true" href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_default" style="font-family:verdana,sans-serif">Given that
communication and readability is one of our major
challenges I agree strongly with Malcolm that a rushed
drafting process is not in our best interests.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">Further to that
point, I think we need to rethink how we communicate
much of what we are trying to communicate, in terms of
format, providing readable overviews as opposed to
immediately plunging into mechanics, etc., etc.</div>
<span class="HOEnZb"><font color="#888888">
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div>
</font></span></div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Oct 6, 2015 at 11:34
AM, Malcolm Hutty <span dir="ltr"><<a moz-do-not-send="true" href="mailto:malcolm@linx.net" target="_blank"></a><a class="moz-txt-link-abbreviated" href="mailto:malcolm@linx.net">malcolm@linx.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<br>
On 06/10/2015 13:58, Mathieu Weill wrote:<br>
> Dear colleagues,<br>
><br>
> The co-chairs had tasked staff to highlight
what would be a plausible<br>
> timeline scenario after our group agrees on
a proposed way forward in<br>
> Dublin.<br>
> We investigated a scenario where we would
not need a public comment, as<br>
> a well as a scenario where an extra pûblic
comment would be needed.<br>
><br>
> The attached slides present an initial
draft which we submit for<br>
> comments from the group.<br>
><br>
> In summary, in the absence of an extra PC
period, we could deliver the<br>
> final report on Nov 20 to the chartering
organisations at the earliest.<br>
> If we need an extra public comment,
delivery would be around end of<br>
> january - beginning of february 2016.<br>
<br>
</span>Seven days to redraft the report, and seven
days to review it.<br>
<br>
That means only seven days in Working Parties
really thrashing the<br>
detailed wording. Whoever has their hand on the
pen will likely need at<br>
least half that time to come up with their first
draft (perhaps more,<br>
depending on their personal schedule). So we're
really only talking<br>
about two or three days for detailed discussion of
alternative phrasing<br>
for specific clauses.<br>
<br>
Is that really enough?<br>
<br>
Maybe enough to get something on paper. But hardly
enough time to polish<br>
the language, to make it legible and accessible,
and to make sure our<br>
explanations properly consider what the
uninitiated reader might wonder.<br>
We'd also be taking big risks with unforeseen
omissions and errata (as<br>
with our previous drafts).<br>
<br>
I think it's this kind of time pressure that has
gotten us much of the<br>
criticism we've had already. I know this is not
welcome advice, but<br>
Aesop's fable of the hare and tortoise springs to
mind.<br>
<br>
Or how does Public Comment Period 4 grab you?<br>
<br>
I propose that we give an extra two weeks for WPs
to work on the text.<br>
<br>
So replace this section<br>
"3-10 November: Drafting of report language<br>
10 November: Report sections sent to CCWG for
review & CCWG call for<br>
rapporteurs to walk through edits"<br>
<br>
<br>
with<br>
<br>
"3-10 November: Drafting of report language<br>
10 November: Deadline for delivery of draft
language to WPs by rapporteurs<br>
10-24 November: Review of draft language by WPs<br>
24 November: Report sections sent to CCWG for
review & CCWG call for<br>
rapporteurs to walk through edits"<br>
<br>
with the lengths of the rest unchanged, resulting
in a close of public<br>
comments on 14th Jan.<br>
<span><font color="#888888"><br>
--<br>
Malcolm Hutty | tel: <a moz-do-not-send="true" href="tel:%2B44%2020%207645%203523" value="+442076453523" target="_blank">+44 20
7645 3523</a><br>
Head of Public Affairs | Read the LINX
Public Affairs blog<br>
London Internet Exchange | <a moz-do-not-send="true" href="http://publicaffairs.linx.net/" rel="noreferrer" target="_blank"></a><a class="moz-txt-link-freetext" href="http://publicaffairs.linx.net/">http://publicaffairs.linx.net/</a><br>
<br>
London Internet Exchange Ltd<br>
21-27 St Thomas Street, London SE1
9RY<br>
<br>
Company Registered in England No.
3137929<br>
Trinity Court, Trinity Street,
Peterborough PE1 1DA<br>
</font></span>
<div>
<div><br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a moz-do-not-send="true" href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a moz-do-not-send="true" 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>
</div>
</div>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a moz-do-not-send="true" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a moz-do-not-send="true" 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>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr" style="font-size:small">Jordan
Carter<br>
<br>
Chief Executive <br>
<b>InternetNZ</b><br>
</div>
<div dir="ltr" style="font-size:small"><br>
+64-4-495-2118 (office) | +64-21-442-649 (mob)<br>
Email: <a moz-do-not-send="true" href="mailto:jordan@internetnz.net.nz" style="color:rgb(17,85,204)" target="_blank">jordan@internetnz.net.nz</a> <br>
Skype: jordancarter<br>
</div>
<div style="font-size:small">Web: <a moz-do-not-send="true" href="http://www.internetnz.nz" target="_blank"></a><a class="moz-txt-link-abbreviated" href="http://www.internetnz.nz">www.internetnz.nz</a> </div>
<div dir="ltr" style="font-size:small"><br>
<i>A better world through a better Internet </i></div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Matthew Shears
Director - Global Internet Policy and Human Rights
Center for Democracy & Technology
<a class="moz-txt-link-abbreviated" href="mailto:mshears@cdt.org">mshears@cdt.org</a>
+ 44 771 247 2987 </pre>
<br><br>
<hr style="border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;">
<table style="border-collapse:collapse;border:none;">
<tbody><tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="https://www.avast.com/antivirus">
<img border="0" src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo">
</a>
</td>
<td>
<p style="color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;">
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/antivirus">www.avast.com</a>
</p>
</td>
</tr>
</tbody></table>
<br>
</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">Accountability-Cross-Community@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></div></blockquote></body></html>