[iucg] wrt IDNA2008 migration (was: IDN processing-related security considerations for draft-ietf-websec-strict-transport-sec)

Patrick Suger psuger at gmail.com
Tue Oct 4 19:54:00 CEST 2011

as a group we do not understand because we did not understand what the
problem was and what we really agreed upon. No surprise, this is typically a
"third window" problem. This also is true for Jean-Michel and most of the
"JEDIs" I am afraid.
There is no bottom-up, nor top-down correct approach: this was the actual
IDNA2008 consensus. This is complexity. There is an iterative synergy
approach. The work carried by ICANN WG/VIP might be impressive: yet how
could the IETF methodology address it and make a better internet out of
their variants?
I agree with you guys that the Intersem could be the correct approach but
through internal self-catalysis. However, who is ready to think that way?

2011/10/4 J-F C. Morfin <jfc at morfin.org>

>  At 05:59 04/10/2011, Mark Davis ☕ wrote:
> There are other alternatives. The obvious one is, well, maintaining
> backwards compatibility. In this case, it would provide that:
>    - Every valid 2003 IDN remains valid under 2008
>    - Additional valid IDNs are allowed under 2008: with either post
>    Unicode 3.2 characters or those unmapped by 2003.
> This is exactly what IDNA2003 did not permit and IDNA2003 does permit.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.alvestrand.no/pipermail/idna-update/attachments/20111004/e63b6ff7/attachment.html>

More information about the Idna-update mailing list