Tim,
The chance of the JOSE working group moving the vast world of
deployed JSON infrastructure round to 0.00. Thus putting a MUST
reject in here would essentially say you can't use well-debugged
production software, and would be a really bad idea.
So, JSON is not easily changed, but adopting I-JSON will easier. OK,
I'll take your word on that.
On the other hand, if JOSE specified that producers' messages MUST
conform to I-JSON, and a couple other WGs climbed on that bandwagon,
and the word started to get around, I wouldn't be surprised if a few
of the popular JSON implementations added an I-JSON mode. That would
be a good thing and lessen the attack surface of all JSON-based
protocols (which these days, is a whole lot of them).
I am comfortable with mandating I-JSON if you believe that will be a
more effective way to
encourage change.
Steve
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
