To answer the question about my concerns, I was particularly worried about client implementations of mappings: the WG consensus call indicated that those who had plans to implement mappings, planned to implement TR46 rather than the WG product. <br>
<br>The WG had a lot of discussions a year ago about whether to leave mappings as a free-for-all and what I heard at that time was that a lot of people saw the value in consistent mappings across implementations -- so a user going from one browser to another, or from email to a browser, won't be surprised at where they end up. Unfortunately, we didn't arrive at a conclusion that provided that consistency, with one set of mappings proposed by the Unicode Consortium and another set proposed by this WG. I still hope for Unicode and IETF participants both to work on understanding why there are conflicting requirements and gain a realistic view of what is likely to be implemented (and over what transition period). So, work can continue thanks to individual contributions and reviews, or even through the possibility of a future WG.<br>
<br>Lisa<br><br><div class="gmail_quote">On Tue, Mar 16, 2010 at 2:40 AM, Vint Cerf <span dir="ltr"><<a href="mailto:vint@google.com">vint@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
The document will go forward from the two editors as a non-WG submission. <div><br></div><div>Although the last poll regarding the "mappings" document seemed to show that most respondents wanted to proceed with submission to the IESG, the AD felt that there were mapping issues not addressed to her satisfaction. We were unable to agree on a version of mapping that would satisfy all concerns among the AD and editors. Reference to TR46 seemed to be desired by the AD but as you see from Patrik Faltsrom's detailed review of that draft document, there is much to discuss and debate. In the end, the only way forward seemed to be to declare the WG "mappings" document to be "dead" and to allow a version of it to be submitted for publication as an independent submission.</div>
<div><br></div><font color="#888888"><div>vint</div></font><div><div></div><div class="h5"><div><br><br><div class="gmail_quote">On Tue, Mar 16, 2010 at 5:06 AM, Yoshiro YONEYA <span dir="ltr"><<a href="mailto:yoshiro.yoneya@jprs.co.jp" target="_blank">yoshiro.yoneya@jprs.co.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Dear Vint and all,<br>
<br>
I'd like to know in detail why the editors, the chair and the AD couldn't<br>
satisfied with current mappings document. If the reason was not cleared,<br>
mappings document couldn't be go forward.<br>
<br>
Even if mappings document is informational, the publication of the document<br>
as RFC is very important to keep backward compatibility and interoperability<br>
between current systems.<br>
<br>
Regards,<br>
<font color="#888888"><br>
--<br>
Yoshiro YONEYA <<a href="mailto:yoshiro.yoneya@jprs.co.jp" target="_blank">yoshiro.yoneya@jprs.co.jp</a>><br>
</font><div><div></div><div><br>
On Mon, 15 Mar 2010 19:59:32 -0400 Vint Cerf <<a href="mailto:vint@google.com" target="_blank">vint@google.com</a>> wrote:<br>
<br>
> Ladies and Gentlemen of the IDNABIS Working Group, as you see from this<br>
> notice, the last working group document that was not yet forwarded by the AD<br>
> has been declared "dead" after it proved impossible to find a version that<br>
> could be forwarded to the IESG that satisfied the preferences of the<br>
> editors, the chair of IDNABIS and the Area Director. It is expected that the<br>
> editors of the "mapping" document will offer a version of it as an<br>
> informational, non-WG contribution.<br>
><br>
> All other documents from the working group have been forwarded to the RFC<br>
> editor for final processing.<br>
><br>
> I believe this concludes the business of the IDNABIS Working Group and, as<br>
> chair, I declare that the Working Group has completed its work and can now<br>
> be retired from the active list.<br>
><br>
> I thank the editors, the Area Director, and especially the participants in<br>
> the IDNABIS working group for their time and thoughtful contributions to the<br>
> work over the past two years.<br>
><br>
> Vint Cerf<br>
><br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: The IESG <<a href="mailto:iesg-secretary@ietf.org" target="_blank">iesg-secretary@ietf.org</a>><br>
> Date: Mon, Mar 15, 2010 at 1:53 PM<br>
> Subject: ID Tracker State Update Notice: draft-ietf-idnabis-mappings<br>
> To: <a href="mailto:idnabis-chairs@tools.ietf.org" target="_blank">idnabis-chairs@tools.ietf.org</a>,<br>
> <a href="mailto:draft-ietf-idnabis-mappings@tools.ietf.org" target="_blank">draft-ietf-idnabis-mappings@tools.ietf.org</a><br>
><br>
><br>
> 'State Changes to Dead from AD is watching by Lisa Dusseault'<br>
> ID Tracker URL:<br>
> <a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18600&rfc_flag=0" target="_blank">https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=18600&rfc_flag=0</a><br>
<br>
</div></div><div><div></div><div>_______________________________________________<br>
Idna-update mailing list<br>
<a href="mailto:Idna-update@alvestrand.no" target="_blank">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></div>
</div></div><br>_______________________________________________<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>
<br></blockquote></div><br>