On Thu, May 14, 2015 at 12:57 PM, Peter Eckersley <p...@eff.org> wrote: > On Wed, May 13, 2015 at 11:39:36PM +0000, Salz, Rich wrote: >> > https://github.com/letsencrypt/acme-spec/issues >> >> I'd prefer if we just recorded issues there, but discussed them in the >> mailing list. > > Folks should also be aware that because letsencypt needs to move fast to > get working and interoperable clients and servers for its launch, > there's a fair chance that it will wind up with a deployed solution that > diverges from the draft spec in various ways, and can't block on an IETF > WG's deliberations. > > For that reason I think it's probably best if the WG and spec work > doesn't start in earnest until after Let's Encrypt has launched (IIRC > that was the consensus in Dallas, too). And in the pre-launch period, a > bug tracker is the most efficient and practical way for us to keep track > of things that we absolutely need to fix/diverge from the draft spec on.
Heya, this reads as if the IETF WG work should block on the letsencrypt launch and it seemed pretty clear in Dallas that while letsencrypt is a motivating effort to spin up ACME that neither should in the short-term be very eeply dependent on each other. (and this is coming from someone who is very excited about both efforts) Happy to be corrected if this was a misinterpretation or a mistake on my part. best, Joe > -- > Peter Eckersley p...@eff.org > Chief Computer Scientist Tel +1 415 436 9333 x131 > Electronic Frontier Foundation Fax +1 415 436 9993 > > _______________________________________________ > Acme mailing list > Acme@ietf.org > https://www.ietf.org/mailman/listinfo/acme -- Joseph Lorenzo Hall Chief Technologist Center for Democracy & Technology 1634 I ST NW STE 1100 Washington DC 20006-4011 (p) 202-407-8825 (f) 202-637-0968 j...@cdt.org PGP: https://josephhall.org/gpg-key fingerprint: 3CA2 8D7B 9F6D DBD3 4B10 1607 5F86 6987 40A9 A871 _______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
