<br><br><div class="gmail_quote">On Thu, Mar 27, 2008 at 11:30 AM, Paul Hoffman <<a href="mailto:phoffman@imc.org">phoffman@imc.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">At 1:53 PM -0400 3/27/08, Vint Cerf wrote:<br>
>it seems to me that what is more important than whether there are<br>
>disagreements among the design team is what the specifications they<br>
>have produced actually say.<br>
<br>
</div>If the disagreements among the design team are not important, than<br>
the following part of the proposed charter (when a re-charter would<br>
be needed) does not make sense:<br>
<div class="Ih2E3d"> (iii) A change to the basic approach taken in the design<br>
team documents (Namely: a protocol that is independent of Unicode<br>
versions, that removes any character mapping in the<br>
protocol, and that has improvements to the bidi algorithm).<br>
</div>Assume that the WG says "let's change this part of the original<br>
documents". One team member says "that's a change to the basic<br>
approach; recharter" and a different team member says "that's not a<br>
basic change; continue". This section of the charter falls over.</blockquote><div><br>I don't understand your point. What we have done in the Namely clause is to spell out what is included. So to take the example cited earlier, "improvements to bidi" are in the charter -- it says nothing about being limited to a single label. Someone who argued that the charter didn't allow looking at multiple labels wouldn't have a leg to stand on.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Either there is agreement among the design team about everything that<br>
is "the basic approach", or the above paragraph is a recipe for<br>
procedural morass.<br>
<div class="Ih2E3d"><br>
>The basic action in the WG at the outset is to obtain broader review<br>
>of the text of these documents to determine whether it is agreed<br>
>that these specifications represent an improvement in framework and<br>
>formulation for IDNs than the earlier effort. what I would have<br>
>thought is of more interest is the text of the documents and less<br>
>the text of the now much-massaged charter?<br>
<br>
</div>It sounds like you haven't been active in many IETF WGs for the past<br>
few years. The IESG, and many process wonks, consider the charter to<br>
be worthy of spending huge amounts of time agonizing over. Having a<br>
charter that has a "recharter if" clause that is fragile is a good<br>
way to delay finishing the work we want to do.<br>
<div><div></div><div class="Wj3C7c">_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no">Idna-update@alvestrand.no</a><br>
<a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Mark