RFC 8785: JSON Canonicalization Scheme (JCS)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8785
- Published
- June 2020
- Authors
- A. Rundgren; B. Jordan; S. Erdtman
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8998ShangMi (SM) Cipher Suites for TLS 1.3Current
March 2021
- RFC 8133The Security Evaluated Standardized Password-Authenticated Key Exchange (SESPAKE) ProtocolCurrent
March 2017
- RFC 8812CBOR Object Signing and Encryption (COSE) and JSON Object Signing and Encryption (JOSE) Registrations for Web Authentication (WebAuthn) AlgorithmsCurrent
August 2020
- RFC 8746Concise Binary Object Representation (CBOR) Tags for Typed ArraysCurrent
February 2020
- RFC 8742Concise Binary Object Representation (CBOR) SequencesCurrent
February 2020
- RFC 8727JSON Binding of the Incident Object Description Exchange FormatCurrent
August 2020
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
- RFC 8935Push-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?