Perhaps out of scope, but valuable: IDN Codepoint

Hi-

I am spending a bit of time with the Universal Acceptance aspect of
the new TLD launches, as well as spending a fair amount of time in my
volunteer role with the Mozilla Foundation on the IDN White-list and
the curation efforts for the Public Suffix List ( PublicSuffix.org is
the URL ).

I am noticing something that might be a worthwhile standardization in
and around having some means to identify to the registrars what are
and are not legal characters to receive registrations on for a given
TLD.  I wonder if a call that could pull down the Unicode code points
and/or any registry specific normalization, case folding, or homonym
replacement mapping  might be important to have.

Each registry seems to have strong opinions about how their solution
is the best, there are numerous cultural-linguistic elements and
sensitivities that a registry might make for having their own specific
mappings, or other things that make the character set code points
distinct to a TLD.

Mileage varies in current IDN implementations, though there are some
standardizations (ie the JET Guidelines).

The status quo in registry launches is that there is a
sunrise[1..x]->landrush->general availability cycle that happens in
the legal roman characters, followed by later launches for IDN.  What
I want to make sure of is that registries that wish to start day 1
with IDN inclusive have the ability to do so in a clean and sane
manner that is unified so that registrars can assimilate them.

Is this obtuse to our focus?

-Jothan

Jothan Frakes
+1.206-355-0230 tel
+1.206-201-6881 fax
_______________________________________________
provreg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/provreg