<div dir="ltr"><div>Dear All,</div><div>We need to be patient a little bit and monitor what CWG is doing.</div><div>We should not impose nor instruct CWG what to do. They are very busy and doing what their community agree to do.</div><div>Protocol and numbers are making panic and pushing for something which a) is not consistent with our charter and b) might produce unintended conséquences.</div><div>Please be patient</div><div>Regards</div><div>Kavouss </div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-02-26 18:29 GMT+01:00 Martin Boyle <span dir="ltr"><<a href="mailto:Martin.Boyle@nominet.org.uk" target="_blank">Martin.Boyle@nominet.org.uk</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-GB" vlink="purple" link="blue" bgcolor="white">
<div>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">I do not disagree, but it would seem to me to be useful in our role as a Coordination Group to make sure that the three different groups think a bit about the
other teams’ work – there will certainly be some need to look for areas of convergence in the different approaches and the earlier they think about differences, the more likely we will be to have the discrepancies addressed.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">Incidentally, the other direction is also important – the numbers and protocol parameters should also think about how to respond to the ideas coming from the
names community.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">If we wait until the names proposal is in, positions will be fixed and there will be little of the flexibility that Milton’s example shows.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">MB<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<div>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="color:windowtext;font-family:"Tahoma","sans-serif";font-size:10pt">From:</span></b><span lang="EN-US" style="color:windowtext;font-family:"Tahoma","sans-serif";font-size:10pt"> <a href="mailto:internal-cg-bounces@icann.org" target="_blank">internal-cg-bounces@icann.org</a>
[mailto:<a href="mailto:internal-cg-bounces@icann.org" target="_blank">internal-cg-bounces@icann.org</a>] <b>On Behalf Of </b>Milton L Mueller<br>
<b>Sent:</b> 25 February 2015 04:03<br>
<b>To:</b> joseph alhadeff; michael niebel<br>
<b>Cc:</b> IANA<span><br>
<b>Subject:</b> Re: [Internal-cg] Timeline and proposal finalization process updates<u></u><u></u></span></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><a name="14bc6f09091188e5__MailEndCompose"></a><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<div style="border-width:medium medium medium 1.5pt;border-style:none none none solid;border-color:currentColor currentColor currentColor blue;padding:0cm 0cm 0cm 4pt">
<p class="MsoNormal"><span lang="EN-US">to the extent appropriate? It is not unreasonable for us to ask that they take account of what's already been drafted, that doesn't bind them to it merely informs them of the potential benefits of drafting that could
avoid conflicts.<u></u><u></u></span></p><span>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">MM: We didn’t say this to the CRISP team even though we received the IETF proposal first. And It’s a good thing we didn’t, CRISP came up with a
slightly different take on the IPR issues and IETF was willing to adjust to accommodate it
<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p>
</span></div>
</div>
</div>
<br>_______________________________________________<br>
Internal-cg mailing list<br>
<a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/internal-cg" target="_blank">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
<br></blockquote></div><br></div>