Canonicalization
02Simple and relaxed algorithms define which message formatting changes affect the signed bytes.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 3.4 ↗
RFC 6376 · § 3.4EXAMPLE
3 / 3
03
Hash canonical bytes
Both sides must obtain the same signed input.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Header and body canonicalization are selected separately.
- Header and body canonicalization are selected separately.
- Relaxed header processing normalizes specified whitespace and field-name case.
- Canonicalization is not permission for arbitrary content changes.
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