Good point about the "no typing in uppercase" unless we consider other mappings (e.g. deletions).
> In all cases, the process that encodes the hostname is responsible for > applying nameprep, not the process that makes the query. Hmmm. Is that true? And can it be enforced? It is interesting that you consider that when one types a URL in an editor, the editor is the one "encoding" the host name. But paste the same string in the browser, and is the browser then re-"encoding" it? Most likely. I think that at the end of the day, while we agree that adding more code points to Unicode will break some applications that use a Nameprep released before the code points were assigned, it is also true that it is likely that IDN will become an OS-based service and that it will be upgraded soon enough. I can definitely imaging Microsoft shipping updates to a Nameprep/Stringprep/IDN library as part as language support (e.g. you get the support for the new language/script, you get the rest with it). But it is still possible to generate perfectly legal Nameprepped data from an older standard that cannot be matched agains the same data Nameprepped from a more recent revision. YA
