Aaron Gable <aaron=40letsencrypt....@dmarc.ietf.org> wrote:
> This draft is implemented by both the Boulder and Pebble ACME server
> implementations, with the exception of the "invalidProfile" error
> type. The code supporting profile selection is deployed in Let's
> Encrypt's environments, but the functionality is gated behind a feature
> flag which has not yet been enabled. I have locally augmented clients
> to support requesting profiles, but have not yet upstreamed such
> changes to open-source ACME client projects.
> I'm not yet asking for working group adoption, but I would like to kick
> off a first round of edits, suggestions, and feedback.
I think we should adopt your document.
Please do not elevate adoption higher than it is.
It only says, "This is a problem we with to work on", and says nothing about
intent to publish that solution, or in fact, any solution.
--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
_______________________________________________ Acme mailing list -- acme@ietf.org To unsubscribe send an email to acme-le...@ietf.org
