I'm not sure how helpful this is, but we've typically found that allowing a
client to specify certificate delivery in one of 3 formats addresses >99%
of use-cases. I would shy away from connecting this to the MIME parameter
and would prefer something along the lines of what Richard offered as an
ex
In general, the root of a chain is often "out of band" and you don't send it.
The receiving party gets a cert chain, and validates everything to make sure
that it lists up to a root that is in their local trust store. They maintain
and decide what's in that trust store, via out-of-band mechanis
Hi Richard and Daniel,
I agree that this is a minor point which shouldn't delay the base
specification. Having it as an extension is totally fine for me. It's
just that I'm not happy with the situation that I as a client
developer have to ask the user for both the ACME endpoint *and* an URL
of the
My feelings are similar to Richard's. There are probably some niche
usecases for this feature that merit thought but I think it would benefit
from larger design discussion. Given that we're very close to finishing the
base specification and there hasn't been significant demand for this to
date I th
Hi Felix,
Thanks for reflecting this back to the list. The concrete implementation
concerns are helpful.
I'm concerned that the need here is more than just a simple MIME
parameter. The MIME parameter is just an aspect of the media type; it just
tells you what's in the object you're looking at.
