On Mon, May 04, 2015 at 08:24:10AM -0700, Paul Hoffman wrote:
> IDNA2008 is a set of standards-track documents.
This is true.
> It is the only standardized way to convert between DNS names and
> representation of non-ASCII characters in the DNS.
>
This is not quite true, and anyway not convinc
On May 4, 2015, at 8:13 AM, Edward Lewis wrote:
> 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?
IDNA2008 is a set of standards-track documents. It is the only standardized wa
On May 4, 2015, at 8:11 AM, Rubens Kuhl wrote:
> I prefer changing "standard" to "current standard", since IDNA2008 use can be
> deprecated in favor of IDNA201x, like IDNA2008 replaced IDNA2003.
As one of the primary authors of IDNA2003, and a minor author of IDNA2008, I
agree. :-)
--Paul Hof
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-AS
> Em 04/05/2015, à(s) 11:58:000, Paul Hoffman escreveu:
>
> 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".
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 c
