Hi all,

After looking at the boulder server and the node-acme 'restify'
branch, and some discussion on #letsencrypt, I am led to believe
that work to make ACME a REST-flavoured protocol is underway.

If this is the case, I have some questions/comments:

- When will we see an updated version of the spec (be it in a branch
  or otherwise?)

- The Retry-After header can be used with response status 503
  Service Unavailable and MAY be used with any 3xx response.  The
  use of the Retry-After header in the restify branch seems to be in
  violation of RFC 2616.

- I'm not sure that REST is a good semantics for ACME (what does
  revocation look like, for example?).  What was the motivation for
  switching to a REST-esque API?

Regards,

Fraser

_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme

Reply via email to