Skip to content
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.

Register application/pem-certificate-chain. #276

Merged
merged 6 commits into from
Mar 13, 2017

Conversation

jsha
Copy link
Collaborator

@jsha jsha commented Mar 12, 2017

And update certificate section to use it. Also describe Link: rel="up" behavior
for pkix-cert.

jsha and others added 2 commits March 12, 2017 12:33
And update certificate section to use it. Also describe Link: rel="up" behavior
for pkix-cert.

Interoperability considerations: None

Published specification: draft-ietf-acme-acme
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should contain a note to the RFC editor to replace the value of the field with RFC XXXX, where XXXX is the assigned RFC number for this specification.

to a trusted root. Servers SHOULD NOT include self-signed trust anchors. The
client may request other formats by including an Accept header in its request.
For example, the client could use the media type `application/pkix-cert`
{{!RFC2585}} to request the end-entity certificate in DER format.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was the idea of removing content negotiation discussed on the list? I'm not seeing it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't remove content negotiation, just moved it lower in the section.

@bifurcation bifurcation merged commit 709a654 into ietf-wg-acme:master Mar 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants