Rob Austein's tagged name components proposal will also make this possible, in that you can have 2 PTR records, one in ASCII and one in "charset+"; a non-i18n resolver will get only one of these returned.This is what the UTF5 encoding provides, an ability for those who still insist on using ASCII to read multilingual double byte characters. Unfortunately, UTF5 transformation may not lead to a meaningful or even semi-meaningful ASCII host name but at least, you can key in the character string in ASCII.
-- Harald Tveit Alvestrand, EDB Maxware, Norway Harald.Alvestrand@xxxxxxxxxxxxxx