Thanks for pointing this out!
On 12/01/2017 04:06 AM, Sophie Herold wrote:
> camelCase
>
> - newKey
> - keyAuthorization
> - notBefore
> - notAfter
>
> kebab-case
>
> - (all directory fields)
> - terms-of-service-agreed
> - only-return-existing
> - external-account-binding
You forgot to
>
> That’s not right. Deployments rarely occur right as the draft is finished.
What isn't right? I expressed an opinion that entering last call for
specification text that hasn't been implemented by anyone seems like a
recipe for errata. My comment was also specific to implementations not
well true passports/ID cards are intresting although there's alayes the
problem about the access structure and so on. German ID cards for example
can only be read with a certificate from a "permission certificate
authority", which are most probably selected by the gov and I wouldnt
expect those
Good observation. I would be OK moving everything to camelCase [1], since
it seems like that's a more natural fit for programming language bindings.
This also seems like a less disruptive change than some other things we've
been doing lately (finalization). At best, it's a string change; at
We at Telia Company are working on an ACME server implementation that is
going to integrate with an existing CA system using external account
binding.
We're planning on using the OOB challenge type to signify pre-authorized
domains (in the existing CA system) as already validated challenges in the
