On 2018-03-18 20:23, Mike Samuel wrote:
F.Y.I: Using ES6 serialization methods for JSON primitive types is
headed for standardization in the IETF.
https://www.ietf.org/mail-archive/web/jose/current/msg05716.html
<https://www.ietf.org/mail-archive/web/jose/current/msg05716.html>
<https://www.ietf.org/mail-archive/web/jose/current/msg05716.html
<https://www.ietf.org/mail-archive/web/jose/current/msg05716.html>>
This effort is backed by one of the main authors behind the
current de-facto standard for Signed and Encrypted JSON, aka JOSE.
If this is in your opinion is a bad idea, now is the right time to
shoot it down :-)
Does this main author prefer your particular JSON canonicalization
scheme to
others?
This proposal does [currently] not rely on canonicalization but on ES6
"predictive parsing and serialization".
Is this an informed opinion based on flaws in the others that make them
less suitable for
JOSE's needs that are not present in the scheme you back?
A JSON canonicalization scheme has AFAIK never been considered in the
relevant IETF groups (JOSE+JSON).
On the contrary, it has been dismissed as a daft idea.
I haven't yet submitted my [private] I-D. I'm basically here for collecting
input and finding possible collaborators.
If so, please provide links to their reasoning.
If not, how is their backing relevant?
If ES6/JSON.stringify() way of serializing JSON primitives becomes an IETF standard
with backed by Microsoft, it may have an impact on the "market".
If you can't tell us anything concrete about your backers, what they back, or
why they back it, then why bring it up?
Who they are, What they back, and Why the back it (Rationale), is in the
referred document above.
Here is a nicer HTML variant of the I-D:
https://tools.ietf.org/id/draft-erdtman-jose-cleartext-jws-00.html
Anders
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
