Marshall Eubanks wrote: > .internal What's that supposed to be good for ? At the moment the 2606bis draft proposes to create a IANA registry of new reserved TLDs, populated with TLDs surviving IETF review. > maybe translations of .test Covered, a copy of the 11 IDN test TLDs created by ICANN some months ago, complete with A-labels and U-labels, see http://tools.ietf.org/html/draft-ellermann-idnabis-test-tlds-06#section-4 > .example Not yet covered, as there's no evidence that ICANN wants to reserve their initially 11 "example" translations as TLDs. With IETF consensus behind it adding them now, or later in a separate memo, is no issue. > .invalid .localhost Bad idea, IMO, these names are not reserved for tests or examples, but technical reasons, and no subject for I18N. > other languages / character sets. ITYM languages / scripts, not character sets. That is a wide field, as there are dozens of scripts and hundreds of languages. If all you want are the *existing* example translations corresponding to the 11 IDN test TLDs it's possible. Otherwise we better wait until the IDN ccTLDs are on their way in about a year. >From my POV I'd like to have one I18N example, and don't care which of the 11 existing strings are reserved, just take them all is an idea. But let's not make up things. > whether there is a better mail list for this discussion It's as "general" as it can get, and I guess the IDNAbis folks won't be thrilled if they are hit by side effects of their effort... ;-) Frank _______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf