rfc-6452

The Unicode Code Points and Internationalized Domain Names for Applications (IDNA) - Unicode 6.0

P. Faltstrom (Editor), P. Hoffman (Editor)
date2011-11 streamIETF areaart wgappsawg statusPROPOSED STANDARD pages4 canonicalhttps://www.rfc-editor.org/rfc/rfc6452 doi10.17487/RFC6452
This memo documents IETF consensus for Internationalized Domain Names for Applications (IDNA) derived character properties related to the three code points, existing in Unicode 5.2, that changed property values when version 6.0 was released. The consensus is that no update is needed to RFC 5892 based on the changes made in Unicode 6.0. [STANDARDS-TRACK]

Extracted elements (7)

design-rationale §2

IETF consensus is that no change to RFC 5892 is needed based on the changes made in Unicode 6.0. This consensus does not imply that no changes will be made to RFC 5892 for all future updates of The Unicode Standard.

dns

interoperability-note §1

The three code point GeneralCategory changes between Unicode 5.2 and 6.0 are non-backward-compatible changes as described in Section 5.1 of RFC 5892. The derived property value differs depending on whether property definitions from Unicode 5.2 or 6.0 are used.

dns

protocol-element §1.1

U+0CF1 KANNADA SIGN JIHVAMULIYA changed GeneralCategory from So to Lo in Unicode 6.0, causing its IDNA derived property value to change from DISALLOWED to PVALID.

dns

protocol-element §1.2

U+0CF2 KANNADA SIGN UPADHMANIYA changed GeneralCategory from So to Lo in Unicode 6.0, causing its IDNA derived property value to change from DISALLOWED to PVALID.

dns

protocol-element §1.3

U+19DA NEW TAI LUE THAM DIGIT ONE changed GeneralCategory from Nd to No in Unicode 6.0, causing its IDNA derived property value to change from PVALID to DISALLOWED.

dns

registry §3

IANA updated the derived property value registry according to RFC 5892 and the property values defined in The Unicode Standard version 6.0.

registry, dns

security-consideration §4

Applying the RFC 5892 algorithm with Unicode 6.0 property definitions yields different results than with Unicode 5.2 for the three affected code points. The three code points are unlikely to occur in internationalized domain names, so the security implications of the changes are minor.

security, dns