1. Summary
This document describes the changes between Unicode 6.2.0 and Unicode
12.0.0 in the context of IDNA2008. Some additions and changes have been
made in the Unicode Standard that affect the values produced by the
algorithm IDNA2008 specifies. This document provides the necessary tables
to IANA to make the IANA database consistent with Unicode 12.0.0.
This document adds to the IDNA2008 set of standards and, as with RFC
6452 that made similar analysis and revision for Unicode 6.0, is a
standards-track document.
Barry Leiba is the document shepherd, and Murray Kucherawy is the
responsible AD.
2. Review and Consensus
This document replaces draft-faltstrom-unicode11, which was intended to
take on the specified review and analysis for Unicode version 11, but
which did not get finished before Unicode version 12 was released and
before changes to the review process were documented in RFC 8753. There
was a good level of review of draft-faltstrom-unicode11, including
substantive review through the Internationalization Directorate (there
were also GenART and SecDir reviews), and those reviews serve this,
draft-faltstrom-unicode12, well.
It's important to keep in mind that the analysis that this document does
is highly specialized and that few IETF participants have the background
knowledge and skills to do that analysis. As a result, we expect few
substantive reviews, and the consensus is necessarily achieved very
narrowly. That said, the document and the analysis it provides is
critical to the stability of the IDNA2008 standards, to ensure that the
standard continues to align with current Unicode versions.
This document is a prerequisite for the review and analysis of Unicode
version 13.
3. Intellectual Property
This document is in full compliance with BCPs 78 and 79, and the author
is not aware of any intellectual property issues or claims related to
it.
4. Other Points
This document provides, in Appendix A, a table for IANA to use to update
their IDNA character database. IANA is familiar with this process and
is well aware of what needs to be done.
There are some intentional references to obsolete RFCs, there for useful
background.