IDNA Update for Unicode 7.0 and Later Versions
draft-klensin-idna-5892upd-unicode70-05
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | John Klensin , Patrik Fältström | ||
| Last updated | 2018-04-19 (latest revision 2017-10-08) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-klensin-idna-5892upd-unicode70-05.txt
Abstract
The current version of the IDNA specifications anticipated that each new version of Unicode would be reviewed to verify that no changes had been introduced that required adjustments to the set of rules and, in particular, whether new exceptions or backward compatibility adjustments were needed. The review for Unicode 7.0.0 first identified a potentially problematic new code point and then a much more general and difficult issue with Unicode normalization. This specification discusses those issues and proposes updates to IDNA and, potentially, the way the IETF handles comparison of identifiers more generally, especially when there is no associated language or language identification. It also applies an editorial clarification to RFC 5892 that was the subject of an earlier erratum and updates RFC 5894 to point to the issues involved.
Authors
John Klensin
(john-ietf@jck.com)
Patrik Fältström
(paf@netnod.se)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)