Public Review Issue #172: Proposed Update Unicode IDNA Compatibility Processing

The Unicode Technical Committee has posted a new issue for public review and comment. Details are on the following web page:

http://www.unicode.org/review/

Review period for the new item closes on September 9, 2010.

Please see the page for links to discussion and relevant documents. Briefly, the new issue is:

#172 Proposed Update UTS #46, Unicode IDNA Compatibility Processing

http://www.unicode.org/reports/tr46/proposed.html

There is a proposed update with the following features: alignment with Unicode 6.0, the addition of conformance test files, and support of the IDNA2003 option UseSTD3ASCIIRules=false.

Feedback is requested both on both the draft text http://www.unicode.org/reports/tr46/proposed.html and draft data files http://unicode.org/Public/idna/6.0.0/

If you have comments for official UTC consideration, please post them by submitting your comments through our feedback & reporting page:

http://www.unicode.org/reporting.html

If you wish to discuss issues on the Unicode mail list, then please use the following link to subscribe (if necessary). Please be aware that discussion comments on the Unicode mail list are not automatically recorded as input to the UTC. You must use the reporting link above to generate comments for UTC consideration.

http://www.unicode.org/consortium/distlist.html

Public Review Issue #176: Properties of Two Khmer Characters

The Unicode Technical Committee has posted a new issue for public review and comment. Details are on the following web page:http://www.unicode.org/review/.

Review periods for the new items close on October 25, 2010.
Please see the page for links to discussion and relevant documents. Briefly, the new issue is:

PRI #176: Properties of Two Khmer Characters

The UTC is considering potential changes to the General_Category property values and default collation weighting of two Khmer characters, U+17B4 KHMER VOWEL INHERENT AQ and U+17B5 KHMER VOWEL INHERENT AA. The UTC is seeking feedback on this topic. In particular, the UTC would be interested in learning of any current implementations which might be adversely affected by any of the proposed modifications to the General_Category and/or default collation weighting of these two characters. Please see the background document http://www.unicode.org/review/pr-176.html for details on the proposal.

If you have comments for official UTC consideration, please post them by submitting your comments through our feedback & reporting page: http://www.unicode.org/reporting.html.

If you wish to discuss issues on the Unicode mail list, then please use the following link to subscribe (if necessary). Please be aware that discussion comments on the Unicode mail list are not automatically recorded as input to the UTC. You must use the reporting link above to generate comments for UTC consideration. http://www.unicode.org/consortium/distlist.html.


----
All of the Unicode Consortium lists are strictly opt-in lists for members or interested users of our standards. We make every effort to remove users who do not wish to receive e-mail from us. To see why you are getting this mail and how to remove yourself from our lists if you want, please see http://www.unicode.org/consortium/distlist.html#announcements.

Public Review Issue #175: CLDR 1.9 Collation Changes

The Unicode CLDR committee is making Unicode locale-sensitive collation a major focus for the next release, CLDR 1.9. There are specific changes for a large number of languages, plus a change in the default ordering of punctuation vs symbols for all languages.

Please see the background document for more information: http://www.unicode.org/review/pr-175.html

If you have any feedback on any of the actions, please file a ticket with CLDR as described in the background document.

Review period for this issue closes on October 1, 2010.

If you wish to discuss issues on the CLDR Users mail list, then please use the following link to subscribe (if necessary). Please be aware that discussion comments on the mail list are not automatically recorded as input to the committee. You must use the submission mechanism described in the background document to generate comments for consideration. http://www.unicode.org/consortium/distlist.html


----
All of the Unicode Consortium lists are strictly opt-in lists for members or interested users of our standards. We make every effort to remove users who do not wish to receive e-mail from us. To see why you are getting this mail and how to remove yourself from our lists if you want, please see http://www.unicode.org/consortium/distlist.html#announcements

Unicode Security and Domain Names

The Unicode Consortium has released three important specifications related to Internationalized Domain Names (IDNs) and Security.

UTS #46: Unicode IDNA Compatibility Processing
http://www.unicode.org/reports/tr46/

UTR# 36: Unicode Security Considerations
http://www.unicode.org/reports/tr36/

UTR# 39: Unicode Security Mechanisms
http://www.unicode.org/reports/tr39/

UTS #46: Unicode IDNA Compatibility Processing

Client software, such as browsers and emailers, faces a difficult transition from the version of international domain names approved in 2003 (IDNA2003), to the revision approved in 2010 (IDNA2008). The specification in this document provides a mechanism that minimizes the impact of this transition for client software, allowing client software to access domains that are valid under either system. The specification provides two main features: One is a comprehensive mapping to support current user expectations for casing and other variants of domain names.
Such a mapping is allowed by IDNA2008. The second is a compatibility mechanism that supports the existing domain names that were allowed under IDNA2003. This second feature is intended to improve client behavior during the transitional period.

UTR# 36: Unicode Security Considerations

Because Unicode contains such a large number of characters and incorporates the varied writing systems of the world, incorrect usage can expose programs or systems to possible security attacks. This is especially important as more and more products are internationalized.

This document describes some of the security considerations that programmers, system analysts, standards developers, and users should take into account, and provides specific recommendations to reduce the risk of problems.

UTR# 39: Unicode Security Mechanisms

Because Unicode contains such a large number of characters and incorporates the varied writing systems of the world, incorrect usage can expose programs or systems to possible security attacks. This document specifies mechanisms that can be used to detect possible security problems.

New PRI: Proposed Draft UTR #49 Unicode Character Categories

The Unicode Technical Committee has posted a new issue for public review and comment. Details are on the following web page: http://www.unicode.org/review/ Review periods for the new items close on October 25, 2010. Please see the page for links to discussion and relevant documents.

Briefly, the new issue is:
PRI #174 Proposed Draft UTR #49, "Unicode Character Categories"
http://www.unicode.org/reports/tr49/tr49-1.html
This proposed draft UTR presents an approach to the categorization of Unicode characters, and documents a data file that implementers can use for defining Unicode character categories.

If you have comments for official UTC consideration, please post them by submitting your comments through our feedback & reporting page: http://www.unicode.org/reporting.html If you wish to discuss issues on the Unicode mail list, then please use the following link to subscribe (if necessary). Please be aware that discussion comments on the Unicode mail list are not automatically recorded as input to the UTC. You must use the reporting link above to generate comments for UTC consideration. http://www.unicode.org/consortium/distlist.html