Good questions. My take below.<br><br clear="all">Mark<br>
<br><br><div class="gmail_quote">On Tue, Feb 24, 2009 at 22:13, Patrik Fältström <span dir="ltr"><<a href="mailto:patrik@frobbit.se">patrik@frobbit.se</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 25 feb 2009, at 00.26, Mark Davis wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
1. That is, unless a local mapping is added.<br>
2. That means, effectively, that every reasonable implementation will<div class="Ih2E3d"><br>
need to add a local mapping so as to not have disgruntled users.<br></div>
3. But there is no standard mapping anymore as part of the protocol.<br>
4. That means that different implementations can use different mappings.<br>
5. Given no guidance, we know that they will.<br>
6. That means we will end up with a very significant interoperability and<br>
security problem.<br>
</blockquote>
<br>
This I agree with of course, but after separating the domain name from the mapping from the application specific implementation suggestions, the next questions arrive:<br>
<br>
1. Does IDNA2008 documents have to be blocked until the rest of the "full picture" is ready as documents?</blockquote><div> </div><div>Because of the major interoperability issues in the transition from IDNA2003 to the draft IDNA2008, we have to have all of our ducks in a row before release, so "yes".<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
2. Does the IDNA2008 documents include "enough" text about this? if not, what should be added where?</blockquote><div><br>No. By allowing allowing arbitrary local mappings, it leaves interoperability in a muddle. It's not a matter of just changing explanatory text.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
3. How much of the mapping can and should be the same regardless of the application(s)?</blockquote><div><br>All. If everyone doesn't map the same way, we are going to have a horrible mess.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
4. Why has not work continued on the pre-i-d that Mark worked on, should that work continue?</blockquote><div><br>The indications that we have gotten all along is that that the authors of IDNA2008 were not interested in that. We have continued that effort in the Unicode Consortium, so as to at least ameliorate the situation by having a specification that people can apply uniformly. It would, of course, be better if it were part of IDNA2008.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
5. What pieces (ranging from all to none) of the UTC work in this area should be adopted by IETF?</blockquote><div><br>I believe that all should be. That would meet the main goals of IDNA2008, but also provide the necessary interoperability with IDNA2003. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
6. What mappings (and similar) do applications already do today?</blockquote><div><br>Today, I have not heard of any significant implementation of IDNA that doesn't apply the mappings defined by IDNA2003, except for two variations that are widely implemented:<br>
<ul><li>Updating the normalization mappings to the latest version of Unicode (which, as you know, do not have any significant effect).</li><li>Applying the mapping to the entire domain name (only affects domain names with some very unusual characters, like <code>
<a href="http://unicode.org/cldr/utility/character.jsp?a=2488">
U+2488</a></code> ( ⒈ ) DIGIT ONE FULL STOP).</li></ul>These are documented in <a href="http://www.unicode.org/reports/tr46">http://www.unicode.org/reports/tr46</a><br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Etc...<br><font color="#888888">
<br>
Patrik<br>
<br>
</font></blockquote></div><br>