Proposed document structure and content for IDNA

Frank Ellermann hmdmhdfmhdjmzdtjmzdtzktdkztdjz at
Fri Jul 11 00:16:24 CEST 2008

JFC Morfin wrote:

> one thing: to use "ISO 10646" than "Unicode".

The "tables" and "BiDi" need Unicode properties
defined in TUS.  AFAIK (I never looked into it)
the other memo doesn't specify these properties.

I've no problem with the document structure, and
long drafts with more than 92 pages can be hard
to read.  If the bulk of the "tables" would go
in a IANA registry later, not in the published
RFC (same idea as in 4645bis, or before in the
4645 drafts), joining three I-Ds can make sense.

But I'd still like an overview in the style of
the "rationale" defining some basic terms such
as A-label and U-label, and/or a memo about the
<toplabel> issue with hardcore ABNF.  Limited to
what implementors need to know when they intend
to support A-labels incl. A-<toplabel>s in their
code as some opaque gibberish that should work.  


More information about the Idna-update mailing list