[saag] Notes from ACME meeting

"Salz, Rich" <rsalz@akamai.com> Thu, 23 July 2015 20:43 UTC

From: "Salz, Rich" <rsalz@akamai.com>
To: "saag@ietf.org" <saag@ietf.org>
Thread-Topic: Notes from ACME meeting
Thread-Index: AdDFh00iJAavv9mAT3S2bZSZ9Ze4AQ==
Date: Thu, 23 Jul 2015 20:43:34 +0000
Message-ID: <2e63858c77364914b9425ae8f97d558a@ustx2ex-dag1mb2.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_2e63858c77364914b9425ae8f97d558austx2exdag1mb2msgcorpak_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/kUvZbVNixBLvVx_Fpk7Rmb_sm7I>
Subject: [saag] Notes from ACME meeting
Precedence: list

ACME had its first WG meeting today (directly after the SAAG meeting).

Richard Barnes reviewed changes to the ACME draft since the BoF at the last IETF. We adopted that document, with strong consensus. Richard Barnes pulled off his "LetsEncrypt" t-shirt to reveal an IETF-93 t-shirt underneath.

John Mattson presented some use cases. There was some discussion, with the consensus being that further work is needed before considering adoption.

Mike Jones presented a "base64-less" proposal that has just been accepted by the JOSE as a WG document.  Consensus was that the ACME messages are small enough that we don't need the efficiency gains offered by this new format. Thanks to Mike for agreeing to come present on short notice.

Phill Hallam-Baker gave an overview of his OmniPublish protocol, which is intended to address "everything" that's needed when a new service is deployed, including certificates, firewall, etc. Consensus is that this is a superset of ACME, and that it could be a useful source of requirements for ACME, if not immediately, then in the next version.

--
Senior Architect, Akamai Technologies
IM: richsalz@jabber.at Twitter: RichSalz

[saag] Notes from ACME meeting Salz, Rich