Re: [Acme] Proposed ACME Charter Language

Bernd Eckenfels <ecki@zusammenkunft.net> Sun, 03 May 2015 00:51 UTC

Return-Path: <ecki@zusammenkunft.net>
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 98F2F1ABB1A for <acme@ietfa.amsl.com>; Sat, 2 May 2015 17:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 gdwQverSjKyp for <acme@ietfa.amsl.com>; Sat, 2 May 2015 17:51:51 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10F4A1A92EF for <acme@ietf.org>; Sat, 2 May 2015 17:51:51 -0700 (PDT)
Received: by wgyo15 with SMTP id o15so119961105wgy.2 for <acme@ietf.org>; Sat, 02 May 2015 17:51:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=xeALLgFrQic4GfkDOM4BV0lBkQPBE2Q/qfGPThvGYoY=; b=PgZd/pbmWqrr15FEGytPTZ87WgcVoEmyg02bNIznLEpxQcIU1xnzkAPSc/5x4MBdK+ GE9H0q1zuEwmeVuFX6+hA+eJzCwGBYvTEv4ZtsrgY+mrvtjX7DmfcY/MyMcb7uf0kFE8 hsULmaVqvQ8pqFQqWt7L40NMm7EgwUwlIjki2mHdnWlcvN1uRxF3hgO+9/fU1bhxa95i +iVMl0XN+CtBJVAvggNOOkOLr07TJrFBIdw5phxmxU2Vr3y99MO4UD1Iu48GjnOP2FJM 2dc6CXuVjCeJGIGSKm2gnnHvzYoAQ22kYNKyXIs6uuqu4956SC1+FV5mJROWeKoM/ZTX a7aw==
X-Gm-Message-State: ALoCoQnejunuuUaP1BSkcSIb1BsQMWYOLmIQRRQnlMVqO/shwU8PXVaEIhX5Duko1Fhxkv0FytPs
X-Received: by 10.194.104.164 with SMTP id gf4mr30400320wjb.102.1430614309752; Sat, 02 May 2015 17:51:49 -0700 (PDT)
Received: from localhost (HSI-KBW-046-005-194-024.hsi8.kabel-badenwuerttemberg.de. [46.5.194.24]) by mx.google.com with ESMTPSA id ha4sm4482581wib.0.2015.05.02.17.51.49 for <acme@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 02 May 2015 17:51:49 -0700 (PDT)
Date: Sun, 3 May 2015 02:51:47 +0200
From: Bernd Eckenfels <ecki@zusammenkunft.net>
To: acme@ietf.org
Message-ID: <20150503025147.00003d51.ecki@zusammenkunft.net>
In-Reply-To: <7bdd06af773e47679dca8827aacdedba@usma1ex-dag1mb4.msg.corp.akamai.com>
References: <6A9C3116-8CC9-472C-8AA8-F555D060834C@vigilsec.com> <55351EAB.1060905@cs.tcd.ie> <E81896AA-245F-48B7-9B38-86AC30D2F82A@vigilsec.com> <553523E4.2090808@cs.tcd.ie> <84718B26-1DA3-4D46-8B6F-B615806229D7@vigilsec.com> <CABcZeBOy2yBEMGMxcDy=E3fvc+OF1sZfvOV7twJHAvKqtrxtLg@mail.gmail.com> <D7F0C45A-B514-41A2-A220-5B6601BE582F@openca.org> <7bdd06af773e47679dca8827aacdedba@usma1ex-dag1mb4.msg.corp.akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/Bdm6M0DkNNnXmAUK-8Wqk_BOsGw>
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: Sun, 03 May 2015 00:51:52 -0000

Am Sat, 2 May 2015 22:20:45 +0000
schrieb "Salz, Rich" <rsalz@akamai.com>;:
> We seem to have a lot of enthusiasm, and probably a good consensus,
> for defining a new protocol. The target is online enrollment for
> servers, initially Web Servers although others can be supported.  The
> standard cert-request/cert data structures (i.e., PKCS 10 and 7) will
> be supported. 

I am quite sure the Charter will be finished once letsencrypt is live :)

> Am I wrong?  Is there an on-line certificate enrollment protocol
> that, say, multiple CA's support?

The question is, will ACME be the one?

But does that really matter? I would be happy with an open standard
only implemented by Lets Encrypt. 

(Yeah I am aware that this might not be the best oppinion on a planned
IETF WG, but the past discussion was not very encouraging.)

Gruss
Bernd