Works for me too.<br><br><div class="gmail_quote">On Tue, Mar 25, 2008 at 8:22 PM, John C Klensin <<a href="mailto:klensin@jck.com">klensin@jck.com</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;">
That works for me. Thanks.<br>
<br>
john<br>
<br>
<br>
--On Tuesday, 25 March, 2008 20:13 -0700 Paul Hoffman<br>
<div><div></div><div class="Wj3C7c"><<a href="mailto:phoffman@imc.org">phoffman@imc.org</a>> wrote:<br>
<br>
> At 10:20 PM -0400 3/25/08, John C Klensin wrote:<br>
>> --On Tuesday, 25 March, 2008 18:24 -0700 Mark Davis<br>
>> <<a href="mailto:mark.davis@icu-project.org">mark.davis@icu-project.org</a>> wrote:<br>
>><br>
>>> That works for me. Item (iii) needs fleshing out a bit.<br>
>>><br>
>>> (iii) A change to the basic approach taken in<br>
>>> the design team documents.<br>
>>><br>
>>> It is clear when a change would violate (i) or (ii) would<br>
>>> be, but not clear what kind of change would violate (iii).<br>
>><br>
>> I more or less copied that, with some slight re-wording, from<br>
>> the last version that was posted. I would welcome narrower<br>
>> language, but am also not sure it is necessary.<br>
><br>
> Given that a few people expressed confusion on that wording,<br>
> it seems necessary. How about:<br>
><br>
> (iii) A change to the approach in the design team documents (a<br>
> protocol that is independent of Unicode versions, that removes<br>
> any character mapping in the protocol, and has improvements to<br>
> the bidi algorithm).<br>
><br>
> That does not cover all the changes between IDNA2003 and the<br>
> design team design, (see<br>
> <<a href="http://www.ietf.org/internet-drafts/draft-hoffman-idna200x-to" target="_blank">http://www.ietf.org/internet-drafts/draft-hoffman-idna200x-to</a><br>
> pics-01.txt>), but it covers the high points that could cause<br>
> a charter refresh.<br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Mark