Greetings,
Given the late-breaking excitement of the IAB Statement[1], I have been
chatting with a few folks (John Klensin, Andrew Sullivan, Patrik
Fältström) about text we can add to the document to explain the state of
affairs before I send it out for a second Last Call. We've worked out
the following (with a bit of editorial help from PSA):
As part of the review of Unicode 7.0 for IDNA, a question was raised
about a newly-added code point that led to a re-analysis of the
Normalization Rules used by IDNA and inherited by this document
(section 5.2.4). Some of the general issues are described in
[IAB-Statement] and pursued in more detail in
[draft-klensin-idna-5892upd-unicode70], but the result is that in
the future, this specification is likely to be updated such that the
range of characters in the LetterDigits category (Sections 4.2.1 and
9.1) may be narrowed, some characters with special properties that
are now allowed may be excluded, more Additional Mapping Rules
(Section 5.2.2) may be added, and/or alternative normalization
methods may be added. Even so, implementations that are sensitive to
the advice given in this specification (to be careful to only allow
characters whose implications they actually understand and,
especially for the LetterDigit case, characters that actually are
used to write relevant human languages) are unlikely to run into
significant problems as a consequence of these issues or potential
changes.
That is, we're aware of the issue, it's not just about Hamza, it's
documented elsewhere, and the spec might change down the road because of
it, but it's unlikely to affect an implementer who does the right thing
anyway.
Does that text work for folks? If I don't hear much in the way of
objection in the next 24 hours, I'll ask the authors to put that in and
do the Last Call.
pr
[1]
https://www.iab.org/documents/correspondence-reports-documents/2015-2/iab-statement-on-identifiers-and-unicode-7-0-0/
--
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis
