Text comparison and security
05Valid Unicode text does not automatically have one spelling or safe display behavior.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 10 ↗
RFC 3629 · § 10EXAMPLE
3 / 3
03
Keep identities explicit
Visual similarity alone does not establish equal identifiers or trusted names.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Different Unicode sequences can appear equivalent to a person.
- Different Unicode sequences can appear equivalent to a person.
- Normalization and comparison rules belong to the consuming protocol.
- Decoding must reject invalid input before security-sensitive comparisons.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy