[jose] Jws Json Unencoded option and JSON payloads

[Sergey Beryozkin <[e-mail]>]

Hi

I've been experimenting recently with JWS JSON and
https://tools.ietf.org/html/rfc7797

I did some tests awhile back with the plain text payload, all was good, 
but now I've tried passing an encoded JSON, example, {"a":"b"} which 
resulted in

{
   "payload": "{"a":"b"}"
   ...
}

which caused a parse error on the receiving side. I found

https://tools.ietf.org/html/rfc7797#section-8

referring to the fact it is the responsibility of the application to 
deal with it.

My question is, why, when "b64":false is set, it is not possible to have

{
"payload": {"a":"b"}
...
}

for payloads which are in JSON format as opposed to having a restriction 
the JWS JSON payload should always be a JSON string ?

Thanks, Sergey