[jose] I-D: draft-rundgren-json-canonicalization-scheme-05

Anders Rundgren <anders.rundgren.net@gmail.com> Sat, 16 February 2019 19:39 UTC

References: <38131ee7-32d6-077f-cc62-7278ae6c9e17@gmail.com>
To: "jose@ietf.org" <jose@ietf.org>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <5a0d89c7-9452-badf-af07-1eae08e90516@gmail.com>
Date: Sat, 16 Feb 2019 20:39:26 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <38131ee7-32d6-077f-cc62-7278ae6c9e17@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/i1YL3bLEsPblLKxwU7GzvWFuvkY>
Subject: [jose] I-D: draft-rundgren-json-canonicalization-scheme-05
Precedence: list

https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-05

Abstract:
     Cryptographic operations like hashing and signing requires that the
     original data does not change during serialization or parsing.  By
     applying the rules defined by the JSON Canonicalization Scheme (JCS),
     data provided in JSON [RFC8259] format can be exchanged "as is",
     while still being usable by secure cryptographic operations.  JCS
     achieves this by building on the strict serialization formats for
     JSON primitives defined by ECMAScript [ES6], constraining JSON data
     to the I-JSON [RFC7493] subset, and through a platform independent
     property sorting scheme.

     The intended audiences of this document are JSON tool vendors, as
     well as designers of JSON based cryptographic solutions.

/Anders for the JCS team

[jose] I-D: draft-rundgren-json-canonicalization-… Anders Rundgren