Early Review of draft-bray-unichars-09
review-bray-unichars-09-artart-early-alvestrand-2024-11-26-00
| Request | Review of | draft-bray-unichars-09 |
|---|---|---|
| Requested revision | 09 (document currently at 11) | |
| Type | Early Review | |
| Team | ART Area Review Team (artart) | |
| Deadline | 2025-02-14 | |
| Requested | 2024-10-04 | |
| Requested by | Orie Steele | |
| Authors | Tim Bray , Paul E. Hoffman | |
| I-D last updated | 2024-11-26 | |
| Completed reviews |
Genart Early review of -09
by Dale R. Worley
(diff)
Artart Early review of -09 by Barry Leiba (diff) Artart Early review of -09 by Harald T. Alvestrand (diff) |
|
| Comments |
This document provides general guidance regarding the use of unicode in protocols. Please consider the internationalization, interoperability and security implications of the document. Since this document is AD sponsored, please note the mailing list for discussion is: https://mailarchive.ietf.org/arch/browse/art/?q=draft-bray-unichars |
|
| Assignment | Reviewer | Harald T. Alvestrand |
| State | Completed | |
| Request | Early review on draft-bray-unichars by ART Area Review Team Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/art/jAuGW7TcpZYG-miIVu4I8wykYHc | |
| Reviewed revision | 09 (document currently at 11) | |
| Result | Ready w/issues | |
| Completed | 2024-11-26 |
review-bray-unichars-09-artart-early-alvestrand-2024-11-26-00
Summary: Ready, with one outstanding question This document is good at describing its extremely limited scope of restriction - there are a hundred ways to slice "problematic characters in Unicode", including such things as overlong combining character sequences, illegal sequences of directional controls (unpaired U+202C, for instance) and so on. 2.2 does a reasonable job of describing the limited role of this document, and to warn about what other kinds of problems may exist. One class that I'm surprised to not see mentioned is "Private-use" (https://en.wikipedia.org/wiki/Private_Use_Areas). While it may be inappropriate to limit their use by these profiles, it might be worth mentioning together with the PRECIS reference in 2.2 as a class that protocol designers can think of avoiding. (The "private" blocks are marked DISALLOWED in the PRECIS registry at https://www.iana.org/assignments/precis-tables-6.3.0/precis-tables-6.3.0.xhtml?&page=11 - but that's a few steps to follow). Apart from that, I think this document is in shape for publication.