Let's Encrypt engineers have been working on an implementation of the latest spec:
https://github.com/letsencrypt/pebble We'll take lessons learned from that when we build support into our production boulder software. We're also going to adapt the Python ACME library to support the latest version. On 02/07/2017 09:27 AM, Salz, Rich wrote: > I put the time period as six weeks, which takes us to just around IETF-98... > > PLEASE reply on list if you will review and/or are interested in working on > interop. > -- > Senior Architect, Akamai Technologies > Member, OpenSSL Dev Team > IM: [email protected] Twitter: RichSalz > > > -----Original Message----- > From: IETF Secretariat [mailto:[email protected]] > Sent: Tuesday, February 07, 2017 12:26 PM > To: [email protected]; [email protected] > Subject: IETF WG state changed for draft-ietf-acme-acme > > > The IETF WG state of draft-ietf-acme-acme has been changed to "In WG Last > Call" from "WG Document" by Rich Salz: > > https://datatracker.ietf.org/doc/draft-ietf-acme-acme/ > > > Comment: > As we agreed at IETF-97 (Seoul), we will have a slightly longer WGLC period > to encourage implementations and interop. > > Are there any volunteers to read and review this document? Please post to > [email protected]. > > Does anyone have an implementation in progress and would be interested in > doing interop at the IETF Hackathon at IETF-98 in Chicago? Please post to > [email protected] > _______________________________________________ > Acme mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/acme > _______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
