>
> AFAIK, every JSON library out there marshalls {} as "{}", with no
> whitespace, and every JOSE library signs whatever string you give it.
I agree, I don't think the {} body will be an implementation challenge. We
can say that with some confidence because the existing draft already
includes a feature using this indicator:
https://tools.ietf.org/html/draft-ietf-acme-acme-14#section-7.3.3
I haven't seen anyone raising problems with this and there are definitely
implementations in the wild.
On Wed, Sep 5, 2018 at 12:57 PM, Richard Barnes <[email protected]> wrote:
>
>
> On Wed, Sep 5, 2018 at 12:53 PM Salz, Rich <[email protected]> wrote:
>
>>
>> - Because being generous in what you receive is harmful.
>>
>> https://tools.ietf.org/html/draft-iab-protocol-maintenance-00
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Diab-2Dprotocol-2Dmaintenance-2D00&d=DwMFaQ&c=96ZbZZcaMF4w0F4jpN6LZg&r=4LM0GbR0h9Fvx86FtsKI-w&m=lYcerr09XhdsUaFXXMZLv4sAfq3r-Nc2uKhaYjnBdpc&s=h1H5m5ejvoDCu-6t_gPl7-6njuU6OH8bsBhq-cGF6Zo&e=>
>>
>>
>>
>> Sorry, I disagree with King Martin in this case. :)
>>
>>
>>
>> I think mandating a specific requrest body is hard to get right.
>>
>
> Can you point to an implementation framework where this would be
> difficult? AFAIK, every JSON library out there marshalls {} as "{}", with
> no whitespace, and every JOSE library signs whatever string you give it.
>
_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme
