Dear Gihan,<br><br>The need for developper information is why I opened the <a href="http://idna2010.org">http://idna2010.org</a> wiki. To keep track of what we will have to consider among "Internet/IETF users" once IDNA2008 is released. There will most probably be a few BCPs to discuss. <br>
<br>I do not want however to open the mailing list as long as the final text has not been approved by the IESG, so we discuss something real (I do not know the architectural impact of some last minute language adjustments).<br>
<br>Portzamparc<br><br><div class="gmail_quote">2009/11/4 Gihan Dias <span dir="ltr"><<a href="mailto:gihan@uom.lk">gihan@uom.lk</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2009-11-04 ප.ව. 8:20 දින, Vint Cerf ලිව්වා:<br>
<div class="im">> there is no way to guarantee this uniformity; nor was the WG able to<br>
> define every possible case in which problems would arise. The range of<br>
> possibilities is too great given the huge number of new symbols<br>
> introduced by IDNA. This was debated extensively during the last 2<br>
> years and that is the working group consensus as I see it.<br>
><br>
</div>Vint,<br>
<br>
I understand.<br>
<br>
My point is that if the WG was unable to reach a consensus, then<br>
registrars would not be able to do so either, so what we'll have is an<br>
"anything goes" situation.<br>
<br>
At the least, we (software developers, sys admins, website owners,<br>
advertising companies, users, etc.) need to be aware of the problems.<br>
<br>
Regards,<br>
<font color="#888888"><br>
Gihan<br>
</font><div><div></div><div class="h5">_______________________________________________<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>