Charles H. Lindsey writes: > Moreover, since these drafts are so written that they are intended to be > updated each time a new Unicode Version appears, it would be useful to > have actual experience of doing that exercise on a draft, rather than on a > published RFC.
This is interesting -- has the Unicode consortium promised to always update the CK normalization tables in a forward compatible way? Since IDNs will be used to identify hosts for security critical purposes, a change in the normalization could in theory be exploited to spoof identities in, e.g., TLS.
