Aaron Gable 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
The authorization system in ACME includes a number of different challenges.
dns-01 and http-01 establish control over a name,
bp-nodeid is a different kind of name (I didn't understand the nature of this
beast, so i can't name it)
abandonned draft-ietf-acme-telephone-01 authorizes telep