273	Proposed Update UTS #39, Unicode Security Mechanisms	Closing Date: 2014.07.28
Status:	Closed
Originator:	UTC
Informal Discussion:	Unicode Mail List (Join)
Formal Feedback:	Contact Form
Resolution:	The UTS will be updated with final content and published.

Description of Issue:

This UTS is being updated to correspond with Unicode 7.0. Text has been added about the use of NFC, and on the use of Catalan in identifiers. A note has been added on the collection of confusable data outside of Status=allowed, such as for non-NFKC characters.

The most important data files for review are:

• http://unicode.org/Public/security/7.0.0/confusablesSummary.txt The number of identified confusables increased from 6,156 items to 6,673, about an 8% gain. The most important characters to review are those that are confusable with high-use scripts. We ask reviewers to pay particular attention to characters confusable with characters from high-use scripts.
• http://unicode.org/Public/security/7.0.0/xidmodifications.txt There are very few new allowed characters from 7.0; most are marked as restricted. We ask reviewers to confirm that none of the restricted characters are in high-frequency modern use.

These files can be downloaded and diffed against the corresponding files in http://unicode.org/Public/security/6.3.0

The data was updated on 2014-07-14 due to some changes resulting from a reported issue with idempotence of skeleton values, and some associated changes discovered in the course of fixing that. (The problems involved use of Script Extensions data, and use of certain Version 6.3 property data during the previous generation).

It appears that the issue with idempotence can be addressed for all of the mappings, with some extensive changes.​ The issue will be documented in the text. The data was updated 2014-07-24 to make these changes.

Draft updated 2014-07-24. Data updated 2014-07-24.

How to Provide Feedback: For information about how to discuss this Public Review Issue and how to supply formal feedback, please see the feedback and discussion instructions. The accumulated feedback received so far on this issue is shown below, or you can look at a full page view. Feedback is reviewed by the relevant committee according to their meeting schedule.