IETF Logo Mail Archive

Re: [Acme] Proposed ACME Charter Language

"Salz, Rich" <rsalz@akamai.com> Mon, 20 April 2015 15:49 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 3DCF31B2F39 for <acme@ietfa.amsl.com>; Mon, 20 Apr 2015 08:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 0rb7K20SzW3E for <acme@ietfa.amsl.com>; Mon, 20 Apr 2015 08:49:31 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (prod-mail-xrelay07.akamai.com [72.246.2.115]) by ietfa.amsl.com (Postfix) with ESMTP id 984931B2F38 for <acme@ietf.org>; Mon, 20 Apr 2015 08:49:31 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id B831447782; Mon, 20 Apr 2015 15:49:30 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (prod-mail-relay07.akamai.com [172.17.121.112]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id ABC7247780; Mon, 20 Apr 2015 15:49:30 +0000 (GMT)
Received: from email.msg.corp.akamai.com (usma1ex-cas2.msg.corp.akamai.com [172.27.123.31]) by prod-mail-relay07.akamai.com (Postfix) with ESMTP id A85498004F; Mon, 20 Apr 2015 15:49:30 +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; Mon, 20 Apr 2015 11:49: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; Mon, 20 Apr 2015 11:49:11 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Russ Housley <housley@vigilsec.com>, IETF ACME <acme@ietf.org>
Thread-Topic: [Acme] Proposed ACME Charter Language
Thread-Index: AQHQe34a4GgjPor2uU27hdlsHinWgp1WTZyA//+90YA=
Date: Mon, 20 Apr 2015 15:49:10 +0000
Message-ID: <1c23fc8d9c0841a5a4ddbe518131515f@usma1ex-dag1mb2.msg.corp.akamai.com>
References: <6A9C3116-8CC9-472C-8AA8-F555D060834C@vigilsec.com> <55351EAB.1060905@cs.tcd.ie>
In-Reply-To: <55351EAB.1060905@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.44.190]
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/7xRoB9qn8R2oYRmFZRQXPwOK6XY>
Subject: Re: [Acme] Proposed ACME Charter Language
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: Mon, 20 Apr 2015 15:49:33 -0000

 
> I think we really ought bottom out on this aspect before chartering - it'd be
> dumb of us to charter an ACME WG that has to fight all the CRMF battles over
> again, or the ASN.1 vs. whatever issues. So I hope lots of voices chime in and
> say what they think.

My employer gets thousands of certs from several commercial CA's.  Each one is a separate integration effort and none of them seem to look like any of the previous IETF RFC's.  The one exception is they all want a cert request, which of course predates the RFC's as it's PKCS.

v2.23.0 | Report a Bug | By Email