RFC 8785 on JSON Canonicalization Scheme (JCS)
rfc-editor@rfc-editor.org Mon, 29 June 2020 17:08 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DDFE3A081D for <ietf-announce@ietfa.amsl.com>; Mon, 29 Jun 2020 10:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pX6Jij7kf2AV for <ietf-announce@ietfa.amsl.com>; Mon, 29 Jun 2020 10:08:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 496CF3A081C for <ietf-announce@ietf.org>; Mon, 29 Jun 2020 10:08:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 72142F40737; Mon, 29 Jun 2020 10:08:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8785 on JSON Canonicalization Scheme (JCS)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200629170819.72142F40737@rfc-editor.org>
Date: Mon, 29 Jun 2020 10:08:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/T60l8KmmvpTom--50mnjcSj4FZk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2020 17:08:39 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8785
Title: JSON Canonicalization Scheme (JCS)
Author: A. Rundgren,
B. Jordan,
S. Erdtman
Status: Informational
Stream: Independent
Date: June 2020
Mailbox: anders.rundgren.net@gmail.com,
bret.jordan@broadcom.com,
erdtman@spotify.com
Pages: 20
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-rundgren-json-canonicalization-scheme-17.txt
URL: https://www.rfc-editor.org/info/rfc8785
DOI: 10.17487/RFC8785
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.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC