Skip to main content

JSON Canonicalization Scheme (JCS)
RFC 8785

Revision differences

Document history

Date By Action
2020-09-23
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2020-09-21
(System) Received changes through RFC Editor sync (added Errata tag)
2020-06-29
(System)
Received changes through RFC Editor sync (created alias RFC 8785, changed abstract to 'Cryptographic operations like hashing and signing need the data to be …
Received changes through RFC Editor sync (created alias RFC 8785, changed abstract to 'Cryptographic operations like hashing and signing need the data to be expressed in an invariant format so that the operations are reliably repeatable. One way to address this is to create a canonical representation of the data. Canonicalization also permits data to be exchanged in its original form on the "wire" while cryptographic operations performed on the canonicalized counterpart of the data in the producer and consumer endpoints generate consistent results.

This document describes the JSON Canonicalization Scheme (JCS). This specification defines how to create a canonical representation of JSON data by building on the strict serialization methods for JSON primitives defined by ECMAScript, constraining JSON data to the Internet JSON (I-JSON) subset, and by using deterministic property sorting.', changed pages to 20, changed standardization level to Informational, changed state to RFC, added RFC published event at 2020-06-29, changed ISE state to Published RFC)
2020-06-29
(System) RFC published