Vint, <br>you will permit me to kindly but firmly protest. For two reasons:<br><br>1. Three of us were banned and my father quitted because they only alluded to the need of interoperability with the users contributed ML-DNS exploration. Here you quote a pure political project which has far less technical interest than Project.FRA and Multilinc. These two projects have defined R&D objectives and want to be the two operationnal experiences required by the IETF in its standardization track.<br>
<br>2. this ICANN document is VERY embarassing and I think we should clarify through the IETF/ICANN and IETF/ISO liaisons. This memo transfers the ICANN interest in the internet to the political sector: until now (Tymnet 1978 agreement, RFC 920, RFC 1531, ICP-1) the reference for the international network was the ISO 3166 standard, accompanied by the ISO 639 and ISO 10646 series in this WG area and the ISO 639-6 mainteneer participate to this WG. <br>
<br>The ICANN's call upon the UN competence, without even a reference to the WSIS ad-hoc structure is an important change to the understanding of the Internet and to the UN consensus. The Users, politically through the Civil Society and technically through the IUCG, will most probably question this as they we have no liaison and no say in there. As long as the UN is concerned the Internet adminance (administrative and technical governance) belongs to the scope of its enhanced cooperation decided by the WSIS and ICANN prevented so far. In this enhanced cooperation regalian, civil, private, international and normative interests are authoritatively present. <br>
<br>The Internet standardisation process MUST stay centralised within the IETF. This is what IESG implied in responding to JFC's appeal and why the IUCG was established as non-WG IETF mailing list and not as an UN/WSIS enhanced cooperation. I think we MUST professionnally finish the WG/LC and document set review process, in adressing each and every point this WG has listed and we compiled in <a href="http://www.ietf.org/internet-drafts/draft-iucg-wgidnabislc-00.txt">http://www.ietf.org/internet-drafts/draft-iucg-wgidnabislc-01.txt</a>. Then we should be able to go as quickly/seemlessly as possible through the IETF/LC (could ICANN proceeed if the IDNA document set is disputed at the IETF?), once the script metadata support issue - typified by the French majuscules - is resolved, most probably in cooperation with Unicode or through an ISO NWIP.<br>
<br>I think that the Project.FRA team will do its best to document the interplus "better internet usage architecture" within the same time windows (but we need the whole <a href="http://www.ietf.org/internet-drafts/draft-iucg-wgidnabislc-00.txt">http://www.ietf.org/internet-drafts/draft-iucg-wgidnabislc-01.txt</a> to be addressed first). We were the first to ask this WG to consider the 9/9/30 date including for the very reasons you give now. We were rebuked by several.<br>
<br>I wish also to say that I am surprised after so many linguistics issues have been debated by engineers in this WG, we might accept that politics and lawyers come and decide that the "few" linguistics aspects of IDNA only relate to ISO 3166 issues (that ICANN should already addressed for a long [and I understand have been positively answered] through its - I hope active - participation within the ISO 3166/MA. <br>
<br>IMHO, but I may be wrong, the internet technology should not be the result of a competition between merchants and users? <br><br>Marie-France Berny<br><br><br><div class="gmail_quote">2009/9/10 Vint Cerf <span dir="ltr"><<a href="mailto:vint@google.com">vint@google.com</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;"><div style="word-wrap: break-word;">ICANN is moving ahead. I would like to submit final I-D's to IESG in the next few days if possible.<div>
<br></div><div>Editors:</div><div><br></div><div>what is the status of each of your documents in terms of absorbing inputs from last call?</div><div><br></div><div>What issues do you need me, as chair, to provide guidance for, if any?</div>
<div><br></div><div>thanks</div><div><br></div><div>vint</div><div><br></div><div><br><div><br><div>Begin forwarded message:</div><br><blockquote type="cite"><div><div style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; color: rgb(0, 0, 0);" color="#000000" face="Helvetica" size="3"><b>From: </b></font><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">ICANN News Alert <<a href="mailto:communications@icann.org" target="_blank">communications@icann.org</a>></font></div>
<div style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; color: rgb(0, 0, 0);" color="#000000" face="Helvetica" size="3"><b>Date: </b></font><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">September 9, 2009 7:35:58 PM EDT</font></div>
<div style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; color: rgb(0, 0, 0);" color="#000000" face="Helvetica" size="3"><b>To: </b></font><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3"><a href="mailto:vint@google.com" target="_blank">vint@google.com</a></font></div>
<div style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal; color: rgb(0, 0, 0);" color="#000000" face="Helvetica" size="3"><b>Subject: </b></font><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3"><b>ICANN News Alert -- Status Update: IDN ccTLD Fast Track Process Implementation</b></font></div>
<div style="margin: 0px; min-height: 14px;"><br></div> </div> <div style="background-color: rgb(255, 255, 255); font-family: arial; font-size: small;"> <div style="border: 1px solid rgb(204, 204, 204); padding: 10px; width: 758px; margin-left: auto; margin-right: auto;">
<div style="width: 738px; margin-left: auto; margin-right: auto;"> <a href="http://www.icann.org/" target="_blank"><img src="" style="border: 0px none ; width: 94px; height: 94px; float: left; margin-top: 0px; margin-right: 10px;" alt="ICANN"></a> <h2>
News Alert</h2><p style="margin: 0px 0px 10px; font-family: arial; font-size: small;"><a href="http://www.icann.org/en/announcements/announcement-2-09sep09-en.htm" target="_blank">http://www.icann.org/en/announcements/announcement-2-09sep09-en.htm</a></p>
<hr style="margin: 20px 0px 0px;"> <h2 style="clear: left; margin-bottom: 0px;">Status Update: IDN ccTLD Fast Track Process Implementation</h2><p style="margin: 15px 0px 0px;">9 September 2009</p><p> <b> </b> ICANN is pleased to provide the following status report on the progress of implementation of the IDN ccTLD Fast Track Process. Overall, the implementation is tracking to the project plan and it is planned to be submitted to the Board during the ICANN meeting in Korea, Seoul, 26-30 October 2009. Discussion of the implementation plan will continue during the Korea meeting and the plan can be amended if a change is indicated. Anticipating positive Board consideration, the process can be launch within a very small timeframe after the Seoul meeting (in the fourth quarter of 2009). </p>
<p> The proposed Final Implementation Plan will be posted online for public review at the end of September 2009, and a new status update of the overall implementation will be provided prior to the Korea meeting. </p><p><b> Implementation Update: </b></p>
<ul> <li><p> DNS Stability Panel: Interisle has been contracted to form the DNS Stability Panel that conducts the technical string requirement evaluations for requested IDN ccTLDs. This includes a verification that the delegations of new TLD strings will not result in user confusion with any existing strings in the DNS. Interisle is currently in the process of forming the DNS Stability Panel for Fast Track Process String Evaluation and providing on-boarding material to panel members. </p>
</li> <li><p> Online Request System: the online system through which IDN ccTLD requests will be submitted is in the final stages of development and testing. The next three weeks will be used: (i) finalize the online content (ii) perform a legal review (iii) undertake a live test. As part of the live test ICANN has consulted with representatives of five countries and invited them to participate in testing of the system. Testing includes: submitting a test request in the system, processing / qualification by staff, providing feedback on the test to participants. These tests will run from the end of September through 9 October after which a new status report of overall Fast Track implementation will be released. </p>
</li> <li><p> Online IDN area: the IDN area online will be revised with an FAQ, factsheets, and a manual reference for use of the online request system. The new and improved site will be released prior to the Fast Track Process launch time. </p>
</li> <li><p> Linguistic Processes: there are a few aspects of the Fast Track Process that are related to linguists or require the advice or statements from experts in writing systems. An important piece of this relates to the requested string(s) as a meaningful representation of a country or territory name. UNGEGN has agreed to support Fast Track participants as needed with referrals to such expertise. The referrals will be provided through an ICANN point of contact and the method for requesting such expertise will be described in the proposed Final Implementation Plan. ICANN plans to support to those requiring linguistic assistance. </p>
</li> <li><p> Outstanding issues: several topics that has been discussed in public comment on implementation proposals of the Fast Track Process since the initial draft implementation plan was released on 23 October 2008. These include: (i) the form of relationship between an IDN ccTLD manager and ICANN, (ii) cost considerations regarding contribution to processing and TLD support costs, (iii) management of variant TLDs. Solutions to these issues have been discussed, and it is believed that current opinions or positions of each community segment is well understood. </p>
</li> </ul><p> For questions, please contact Tina Dam, at ICANN, at: <a href="mailto:tina.dam@icann.org" target="_blank">tina.dam@icann.org</a>. </p> <hr><p style="text-align: center;"><b><a href="http://www.icann.org/magazine/" target="_blank">Sign up for ICANN's Monthly Magazine</a></b></p>
</div> </div> <br><br><table border="0" cellpadding="1" cellspacing="0" width="100%"> <tbody><tr> <td bgcolor="#333333"><table bgcolor="#ffffff" border="0" cellpadding="6" cellspacing="0" width="100%"> <tbody><tr>
<td bgcolor="#ffffff" width="100%"><font face="Verdana, Arial, Helvetica, sans-serif" size="1">This message was sent from ICANN News Alert to <a href="mailto:vint@google.com" target="_blank">vint@google.com</a>. It was sent from: ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601. You can modify/update your subscription via the link below.</font></td>
<td bgcolor="#ffffff" width="2%"><div style="margin: 0px; padding: 4px 10px; font-family: Arial,Helvetica,sans-serif; text-align: center; font-size: 10px;"><a href="http://www.icontact.com/a.pl/144186" style="color: rgb(153, 153, 153); text-decoration: none;" target="_blank">Email Marketing by</a><br>
<a href="http://www.icontact.com/a.pl/144186" target="_blank"><img src="" alt="iContact - Try It Free!" border="0" height="38" width="117"></a></div></td> </tr> </tbody></table></td> </tr> </tbody></table><br> <table border="0" cellpadding="4" cellspacing="0">
<tbody><tr> <td bgcolor="#ffffff"> <font face="Verdana, Arial, Helvetica, sans-serif" size="1"> <img src="" border="0" height="14" width="14"> <a href="http://app.icontact.com/icp/mmail-mprofile.pl?r=9828131&l=6333&s=9CK0&m=260133&c=165637" style="text-decoration: none;" target="_blank"> Manage your subscription </a> </font> </td>
</tr> </tbody></table> <img src="" height="1" width="1"> </div> </blockquote></div><br></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>