>First let me clarify what I am trying to name. I want a name for the >transformation from any Unicode string to an ASCII string (and the >reverse transformation). The thing I am naming does not include the >prefix (xx--), does not include syntax restrictions like the 63-octet >limit, and does not include nameprep. The thing I am naming is the >operations performed by the pseudocode in the AMC-ACE-Z spec, and no >more. > >If people are willing to use the name ACE or ACE-1 for this, that would >be fine with me. But if you would rather use the name ACE to refer >to a larger operation, then I still want a name for the thing I just >described. > >(Up to now, ACE has been a fuzzy term. It hasn't been clear where its >boundaries were.)
I agree. ACE should stand for the UCS into ASCII A-Za-z0-9- encoding. No length restrictions, no nameprep. Though the UCS must be normalised so that it is well defined. That is, ACE should stands for: - UCS normalised into Unicode form C - then encoded into the characters A-Za-z0-9- The specific rules that could be used over DNS could be called BCE (Backward Compatible Encoding). Dan
