Re: [Acme] Specify which JWS serialization is used

[Jörn Heissler <[e-mail]>]

On Sun, Mar 04, 2018 at 07:45:36 -0600, Logan Widick wrote:
> Good catch. Should it be 415 (Unsupported Media Type) plus which of the
> following (or which combination of the following):
> 
>    - A new problem document field (tentatively named
>    "supportedSerializations": an array of media type strings)?
>    - A new directory field (tentatively named "supportedSerializations": an
>    array of media type strings)?
>       - Should this go in the directory's "meta" object, or in the
>       directory object itself?
>    - A HTTP header?
>    - Something else?

I like the directory approach with meta. Then a client could
use this information before sending the first POST. Else the client
would need to change an internal state after receiving the error
message. For my own client, I'm planning to support the OpenPGP smart
card. It takes 3 seconds to generate a signature. If a signature is
wasted to find out that the default serialization is not supported, it
would be annoying. Having to write a configuration file "use compact by
default for CA foo" would be stupid too.

This, and the problem document field. "supportedSerializations" sounds
fine.

Should the two features be OPTIONAL?

I don't like HTTP headers, it's quite complicated to parse them correctly.
JSON is so much easier.


Or... specify that flattened MUST BE used :-)

Cheers
Joern Heissler