Since the ES6 Number type is 64-bit IEEE, there's no need to worry about number canonicalization either if you base the signature system on ES6 which seems like a pretty safe bet.
http://www.ecma-international.org/ecma-262/6.0/index.html#sec-tostring-applied-to-the-number-type That is, AFAICT, clear-text in-object JSON signatures are already compatible with ES6 (and I must drop my "number preservation" stuff...). Folks working with constrained devices will probably settle for CBOR. On 2015-10-25 10:08, Anders Rundgren wrote:
http://www.ecma-international.org/ecma-262/6.0/index.html#sec-ordinary-object-internal-methods-and-internal-slots-ownpropertykeys I can't say I'm able "deciphering" the ES6 specification but it seems that the largest base of JSON parsers (the browsers), now are compliant with in-object JSON clear-text signature schemes of the kind I have proposed (pushing maybe...), albeit with some (IMO for practical purposes insignificant) limitations: - Integer property names doesn't work. - Numeric values would have to be normalized. Java, Python, and C# already manages this as well. Yay! Anders
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
