I'm going to ask this as a question, not a comment, directed to those who know something about IDN.
Isn't IDNA2008 a "convention" on top of the representation? And, this
isn't about display, it's about, well, encapsulation, maybe? And isn't
IDN tied to Unicode?
I ask for a few reasons - "non-ASCII" might include raw binary or bit
encodings other than Unicode.
The punycode algorithm maps Unicode (code points) to DNS-label compatible
strings. (No-case, etc.)
IDNA 2008 is a treatment of labels generated by the punycode algorithm to
achieve a number of other goals.
(I guarantee you I am missing something in the above, like Normalization
Forms and such.)
When I use "IDN" I think of a representation of a Unicode string in a DNS
label according to a bunch of conventions. Perhaps IDN is taking on a
wider meaning. I don't know.
On 5/4/15, 10:58, "Paul Hoffman" <paul.hoff...@vpnc.org> wrote:
>Greetings. As I was removing the definition of ccTLDs based on the recent
>discussion, I realized that there was no stand-alone definition of IDNs.
>Proposal:
>
>IDN --- The common abbreviation for "internationalized domain name". IDNs
>are the standard
>mechanism for displaying names with non-ASCII characters in applications.
>The standard,
>normally called "IDNA2008", is defined in {{RFC5890}}, {{RFC5891}},
>{{RFC5892}},
>{{RFC5893}}, and {{RFC5894}}.
>
>--Paul Hoffman
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
