Strictness and canonical form
05A consuming protocol must say when to tolerate non-alphabet characters or line breaks.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 3.3 ↗
RFC 4648 · § 3.3EXAMPLE
3 / 3
03
Emit canonical text
Write the agreed alphabet, zero pad bits, and required padding.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Do not add line feeds unless a referring specification requires them.
- Do not add line feeds unless a referring specification requires them.
- Reject non-alphabet characters unless the referring specification explicitly allows another policy.
- Use canonical output to avoid several spellings for the same bytes.
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