For those interested in the post IDNA2008 work on an IDNA2010 BCP.<br><a href="http://idna2010.org">http://idna2010.org</a> (an IUCG direct access)<br><br>Portzamparc<br>Moderator <a href="mailto:workon@idna2010.org">workon@idna2010.org</a><br>
<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">Dear all,<br>
<br>
Further to the IESG announcement of their approval of the IDNA2008 documents, I intend to appeal that decision. I will most probably be supported by others in so doing. This appeal will be a special appeal and will be carefully documented. The intent here is not to oppose the documents, which are in fact excellent and represent a major and positive step ahead for the Internet, but rather to oppose their publication without further work being carried out beforehand. To use IDNA2008, which is the Internet protocol for supporting IDNs, without the proper IDNA2010 work firstly being completed regarding its support on the user side, may create undesired confusion, high security risks and, therefore, an inappropriate and undesirable image of IDNA.<br>
<br>
This is particularly the case of the ICANN Fast Track project (limited to a discriminated set of IDNccTLDs) and of the rather similar ATLARGE My Track project (open to every IDNg/ccTLD project). As one of the initiators of the My Track project, I will do my best to delay it until things have been clarified. None of the multiple contact attempts with the ICANN BoD Members, IDNs related staff, and key persons in their IDN area has resulted in response. By their silence they are endangering the stability of the Internet. They must be officially warned by the IAB, elucidated by the IESG, and assisted by documents from the IETF and IUCG.<br>
<br>
Here is my projected calendar:<br>
<br>
1. to document the problem from the document that I sent to the IESG as the Chair of Project.FRA. It explained explaining what actions the ICANN's political precipitation obliges on us.<br>
2. to document how this kind of major problem (a complete change in the understanding of the Internet and domain name system architectures is involved) could be addressed.<br>
3. to appeal the decision before March 7, and to propose the most limited number of necessary changes in order to make it understood that this publication is excellent but that it MUST be considered as premature to use it.<br>
<br>
I do not want this appeal to be considered as community dissent. Therefore, I will not discuss it on the <a href="mailto:workon@idna2010.org" target="_blank">workon@idna2010.org</a> mailing list. I will be attentive, however, as to what may be discussed on this list, which is destined to work on an IDNA2010 BCP as to the different ways to implement and deploy IDNA2008 as a user, an ISP, a zone manager, etc.).<br>
<br>
I hereby note that prior to the publishing of this intent of appeal, I have fully respected the appeal procedure: I let the WG/IDNABIS members know (I am banned from that WG) and I dialoged with, or reported to, the WG/IDNABIS Chair, the Application Area AD in charge, and the IETF Chair. This appeal is personal and does not involve any of my other IETF related duties and obligations.<br>
<br>
Best regards<br>
JFC Morfin<br>
Internet User.<br>
<br>
_______________________________________________<br></div></div>
iucg mailing list<br>
<a href="mailto:iucg@ietf.org" target="_blank">iucg@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/iucg" target="_blank">https://www.ietf.org/mailman/listinfo/iucg</a><br>
</blockquote></div><br>