On Wed, Dec 19, 2012 at 3:26 AM, Mike Jones <[email protected]> wrote: > QUESTION TO WORKING GROUP: I'm curious whether people would like to see us > enable avoiding double base64encoding of JWS payloads when they are already > URL-safe. The space savings are significant; they come at the cost of the > JWS parsing becoming [part before first period . part between first and last > period . part after last period] rather than the current [part before first > period . part between first and second period . part after second period > (with no other periods allowed)]. Opinions?
Personally, I think it would make sense to use a more orthogonal and general encoding of possible strategies, by doing something like HTTP's Transfer-Encoding. The transfer encoding could express any of 'deflate', 'non-b64u', 'b64u', 'deflate-b64u', and possibly other compression algorithms (snappy?). This allows flexibility for specific cases like a JWE value as JWS payload and larger payloads. Cheers, Dirkjan _______________________________________________ jose mailing list [email protected] https://www.ietf.org/mailman/listinfo/jose
