On Thu, Aug 13, 2015 at 2:40 AM, Rob Stradling <[email protected]> wrote: > On 13/08/15 02:58, yan wrote: > <snip> >> >> I see James is already fixing this: >> https://github.com/letsencrypt/acme-spec/pull/217/files. > > > Shouldn't that work be happening at... > > https://github.com/ietf-wg-acme/acme > > ...now?
Yes, thanks for pointing that out. I have closed that PR. To be clear: The "letsencrypt/acme-spec" repo is still open for the moment, but at this point, the only changes being accepted are minor clarifications or critical fixes. (Once Let's Encrypt gets stable, I expect that repo to close down and any deltas against -04 to be proposed against the IETF document.) Since there's an implementation-side fix for this issue (using the proper account key), this is not a critical fix. Anything novel needs to be discussed on this list and done in the IETF repo, as you note. --Richard > > -- > Rob Stradling > Senior Research & Development Scientist > COMODO - Creating Trust Online > _______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
