support of metadata
jean-michel bernier de portzamparc
jmabdp at gmail.com
Mon Sep 14 20:16:52 CEST 2009
2009/9/14 John C Klensin <klensin at jck.com>
> But, again, that has nothing to do with domain identifiers or with IDNA in
> its role of making it possible to accommodate non-ASCII identifiers in the
Sorry, this only has to do with the IDNA2008 incapacity to match IDNA2003 as
far as uppercases support is concerned. IMHO this is not what the Charter
Anyway, my problem is _not_ to know what IDNA will be able to do or not. My
interest is to make sure that IDNAPLUS is able to match users' expectations,
and also to be 100% IDNA conformant. Obviously, IDNAPLUS will do things IDNA
will not do. What I try to make sure is that the difference is only :
1. to support IDNA2003 upper-cases in U-Label
2. keeping PRIVATE USE ONE and PRIVATE USE TWO PVALID as PVALID, i.e.
respecting Unicode's respect for users.
So, I do not spread an erroneous good news that could delay the IETF/LC.
One has to be carefull about this kind of quick and easy solution.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Idna-update