<div><font size="2" color="navy" face="Arial">
This works for me, lisa. </font></div>
<br><div><hr size="2" width="100%" align="center" tabindex="-1">
<font face="Tahoma" size="2">
<b>From</b>: <a href="mailto:idna-update-bounces@alvestrand.no">idna-update-bounces@alvestrand.no</a> <<a href="mailto:idna-update-bounces@alvestrand.no">idna-update-bounces@alvestrand.no</a>>
<br><b>To</b>: <a href="mailto:idna-update@alvestrand.no">idna-update@alvestrand.no</a> <<a href="mailto:idna-update@alvestrand.no">idna-update@alvestrand.no</a>>
<br>
<b>Sent</b>: Mon Jul 27 15:48:42 2009<br><b>Subject</b>: Mapping clarification in charter
<br></font><br></div>
<br>The IDNABIS WG participants in today's meeting had a clear consensus to go forward with the mapping document that proposes a common and interoperable mapping, but does not require it for all use cases. <br><br>When the charter was written, the phrase "elimination of character mapping in the protocol" could legitimately have been interpreted by charter readers as "no mapping standard or document". The right thing to do is to fix the charter with approval of the IETF. <br>
<br>In order to make this a minimal change, how about:<br><br>s/elimination of character mapping in the protocol/reduction of dependency on character mapping/<br><br>In context in the charter, this would read <br><br> The WG will stop work and recommend that a<br>
new charter be generated if it concludes that any of the following are<br> necessary to meet its goals:<br><br> [...]<br> (iii) A change to the basic approach taken in the design team<br> documents (Namely: independence from Unicode version and reduction of<br>
dependency on character mapping )<br><br>I believe this is a better description of what the WG is doing and plan to take this to the IESG and IETF community.<br><br>Thanks,<br>Lisa<br>