Iām also confused by this problem. Why not use JSON Text Sequences instead for this use case?
http://www.rfc-editor.org/rfc/rfc7464.txt ā Justin > On Mar 25, 2015, at 2:10 PM, Jim Schaad <[email protected]> wrote: > > So what happens if my JWS Payload contains a "." character in it? > >> -----Original Message----- >> From: jose [mailto:[email protected]] On Behalf Of Phillip > Hallam-Baker >> Sent: Wednesday, March 25, 2015 11:14 AM >> To: [email protected] >> Subject: [jose] Direct Compact Serialization >> >> The revised draft is now up. It is essentially a one pager. Which turns > out to be >> five with the boiler plate and IANA section. >> >> http://tools.ietf.org/html/draft-hallambaker-joseunencoded-01 >> >> 2. Serialization >> >> In the JWS Direct Serialization, no JWS Unprotected Header is used. >> In this case, the JOSE Header and the JWS Protected Header are the >> same. >> >> In the JWS Direct Serialization, a JWS is represented as the >> concatenation: >> >> UTF8(JWS Protected Header)) || '.' || (JWS Payload) || '.' || >> >> (JWS Signature) >> >> The calculation of the signature is performed over the octet sequence >> that corresponds to the concatenation: >> >> UTF8(JWS Protected Header)) || '.' || (JWS Payload) || '.' >> >> _______________________________________________ >> jose mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/jose > > _______________________________________________ > jose mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/jose
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
