I've got a PR adding application/pem-certificate-chain: https://github.com/ietf-wg-acme/acme/pull/276.
Note that I chose "pem-certificate-chain" rather than "pem-cert-list", because it has different semantics. A certificate chain MUST start with an end-entity certificate, while a certificate list (which has no MIME type defined at present) can have any type of certificates in any order. For instance, it's common to have a list of trust anchors in PEM format concatenated in a single file. That would be considered a "certificate list" but not a "certificate chain." What do you all think? Thanks, Jacob On 02/16/2017 06:57 PM, Clint Wilson wrote: > > +1 for application/pem-cert-list. > > > On Thu, Feb 16, 2017, 5:11 PM Salz, Rich <[email protected] > <mailto:[email protected]>> wrote: > > I think you need application/pem-cert-list, which is a collection > of PEM certificates as defined in RFC 7468. > > Should be easy to add that as an appendix to the draft. > > I suggest cert-list not chain, to show that no ordering is implied. > > _______________________________________________ > Acme mailing list > [email protected] <mailto:[email protected]> > https://www.ietf.org/mailman/listinfo/acme > > > > _______________________________________________ > Acme mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/acme
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
