Re: [Acme] Considerations about ACME BoF

"Salz, Rich" <rsalz@akamai.com> Tue, 31 March 2015 14:28 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA1951ACD6B for <acme@ietfa.amsl.com>; Tue, 31 Mar 2015 07:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level:
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQAWf7jgEaiw for <acme@ietfa.amsl.com>; Tue, 31 Mar 2015 07:28:28 -0700 (PDT)
Received: from prod-mail-xrelay02.akamai.com (prod-mail-xrelay02.akamai.com [72.246.2.14]) by ietfa.amsl.com (Postfix) with ESMTP id 287BA1ACD55 for <acme@ietf.org>; Tue, 31 Mar 2015 07:28:28 -0700 (PDT)
Received: from prod-mail-xrelay02.akamai.com (localhost [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 4B7472856B; Tue, 31 Mar 2015 14:28:27 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (prod-mail-relay07.akamai.com [172.17.121.112]) by prod-mail-xrelay02.akamai.com (Postfix) with ESMTP id 2C0CE28548; Tue, 31 Mar 2015 14:28:27 +0000 (GMT)
Received: from email.msg.corp.akamai.com (usma1ex-cas1.msg.corp.akamai.com [172.27.123.30]) by prod-mail-relay07.akamai.com (Postfix) with ESMTP id 280C88004B; Tue, 31 Mar 2015 14:28:27 +0000 (GMT)
Received: from USMA1EX-DAG1MB2.msg.corp.akamai.com (172.27.123.102) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.913.22; Tue, 31 Mar 2015 10:26:29 -0400
Received: from USMA1EX-DAG1MB2.msg.corp.akamai.com ([172.27.123.102]) by usma1ex-dag1mb2.msg.corp.akamai.com ([172.27.123.102]) with mapi id 15.00.0913.011; Tue, 31 Mar 2015 10:26:29 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Scott Rea <Scott.Rea@DigiCert.com>, Yaron Sheffer <yaronf.ietf@gmail.com>, "acme@ietf.org" <acme@ietf.org>
Thread-Topic: [Acme] Considerations about ACME BoF
Thread-Index: AQHQaJrriZrpKvFfaUeYZKWDqH6NxJ0wsF8AgAUDEwCAAIYUgIAAT+iAgAAikjA=
Date: Tue, 31 Mar 2015 14:26:28 +0000
Message-ID: <ae50ee46cdba4ccb9a7d1e415759cf67@usma1ex-dag1mb2.msg.corp.akamai.com>
References: <551569F6.8020507@openca.org> <55157164.80805@cs.tcd.ie> <5519A5B6.9010707@DigiCert.com> <551A162F.9020105@gmail.com> <551A5937.1070608@DigiCert.com>
In-Reply-To: <551A5937.1070608@DigiCert.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.33.211]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/wvaY7mULW2lF4DYrlZx-XVjrNt4>
Subject: Re: [Acme] Considerations about ACME BoF
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 14:28:31 -0000

> b) Getting a server certificate for a cloud server within seconds, and with no
> manual intervention is possible today with a little scripting on the server and
> an appropriate API from one of the existing CAs. If your current provider
> cannot do that for you, then I suggest you shop around a little.

Great.  Will you, or the other existing CA's bring the API forward for the potential WG to consider?