Re: [therightkey] Proposal: ACME list

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 20 November 2014 22:58 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: therightkey@ietfa.amsl.com
Delivered-To: therightkey@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7718C1A8707 for <therightkey@ietfa.amsl.com>; Thu, 20 Nov 2014 14:58:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 S3bYPUCwcd7s for <therightkey@ietfa.amsl.com>; Thu, 20 Nov 2014 14:58:45 -0800 (PST)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F72E1A8701 for <therightkey@ietf.org>; Thu, 20 Nov 2014 14:58:44 -0800 (PST)
Received: by mail-la0-f48.google.com with SMTP id s18so3348354lam.35 for <therightkey@ietf.org>; Thu, 20 Nov 2014 14:58:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Pc7Wl/v3k0YhP8tP5rKURfp7orMaUeiDnzgURzOkavY=; b=Rtctgrlqy1W8fkmRvWUTL/2qQ/hA6y7Ow1c+1GZVP5xTn814xvBEkhUmWIPZXuyhp3 rTx5OZVKNYObdzeHWHxi4k981C+DEkLpc4R6Uoly0jIebEb03zpsO1j6rjY7vsiNmZ/r qnD3a38UUapHKpxrv/hva8U4PEKNWtLHi9E0NcIiu/+GTuid3i6GDNGMj3SfOw92+3M8 09SUcuYSmVtycAiP4oO0N1uUTmreC+YKbwpeUzZM7XQnaj3D5jRs0yp7l7qZFULvwbJ6 Zeffo3jdXHCjYiiYjN0gBzIKVTUPfFYfw+OpkUj+NeXZUqIN3XTo6Pip1EhyRWweEDKK ymZg==
MIME-Version: 1.0
X-Received: by 10.112.93.231 with SMTP id cx7mr679215lbb.89.1416524322868; Thu, 20 Nov 2014 14:58:42 -0800 (PST)
Sender: hallam@gmail.com
Received: by 10.112.34.212 with HTTP; Thu, 20 Nov 2014 14:58:42 -0800 (PST)
In-Reply-To: <CAL02cgSGLLU2xT03USHFUD2gG-b5n-O9WfJ=iKM9Fwvou=-OnA@mail.gmail.com>
References: <CAL02cgSGLLU2xT03USHFUD2gG-b5n-O9WfJ=iKM9Fwvou=-OnA@mail.gmail.com>
Date: Thu, 20 Nov 2014 17:58:42 -0500
X-Google-Sender-Auth: G8hYtnuIhOX-AkbEwmeonFnBV3E
Message-ID: <CAMm+LwjVUfx+SDCLPOA2cTSOLC72f_63EbMNh-Da=O49kjejAA@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/therightkey/dic0NEIfGsIrapx-zbBUdpLU6-4
Cc: "therightkey@ietf.org" <therightkey@ietf.org>
Subject: Re: [therightkey] Proposal: ACME list
X-BeenThere: therightkey@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <therightkey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/therightkey>, <mailto:therightkey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/therightkey/>
List-Post: <mailto:therightkey@ietf.org>
List-Help: <mailto:therightkey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/therightkey>, <mailto:therightkey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Nov 2014 22:58:46 -0000

On Thu, Nov 20, 2014 at 5:03 PM, Richard Barnes <rlb@ipv.sx> wrote:
> As some of you may have heard, some of us have been working on a protocol to
> automate certificate management, including things like registration,
> enrollment, issuance, and revocation.
> <https://github.com/letsencrypt/acme-spec>
>
> There is some similarity to existing CA-proprietary issuance APIs, and to
> projects like SSLMate.
> <https://sslmate.com/>
>
> Would folks be interested in spinning up an IETF mailing list on this topic?
> It seems like we could probably get this in shape for a BoF in Dallas.

There is definitely a need for this to enable use of short liver certs
and to clean up the mess of existing proposals, none of which are
really viable as automated protocols.

I proposed this a while back:

http://tools.ietf.org/html/draft-hallambaker-omnipublish-00