On 2017-02-13 06:26, Martin Thomson wrote:
<snip>
In the examples below, JWS objects are shown in the JSON or flattened
JSON serialization, with the protected header and payload expressed
as base64url(content) instead of the actual base64-encoded value, so
that the content is readable. Some fields are omitted for brevity,
marked with "...".
I didn't really understand this without an example to use for
reference. Given that the first actual use of this form is 15 (!)
pages further down the document, maybe you could move this there.
JWS is great for what is was originally designed for. ES6 normalization
nullifies the need for dressing JSON data in Base64Url.
Anders
https://cyberphone.github.io/doc/security/jsonsignatures.html
_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme
