Re: [Acme] ACME BoF in Dallas -- call for agenda items, issues, speakers

Ted Hardie <ted.ietf@gmail.com> Thu, 12 February 2015 19:37 UTC

Return-Path: <ted.ietf@gmail.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 F02E51A3B9B for <acme@ietfa.amsl.com>; Thu, 12 Feb 2015 11:37:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 9Bnit-Iy0RqP for <acme@ietfa.amsl.com>; Thu, 12 Feb 2015 11:37:39 -0800 (PST)
Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) (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 962691A1C02 for <acme@ietf.org>; Thu, 12 Feb 2015 11:37:39 -0800 (PST)
Received: by iecrd18 with SMTP id rd18so14434052iec.5 for <acme@ietf.org>; Thu, 12 Feb 2015 11:37:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5eMV4BYSv8fKpz4sh5BI8wqIefMtQEZVtAcQ/WxHvh8=; b=A7TWxanjt19sXLnSAN8XBKjswMai0TvsNlP/NmFSdSeFRJrydmb0L+bvxG3XIUgapp K/GU62uPeDUvjOMpiCyjeEFgb6uKhUWC1uHyOFCD7rXs0oFEpo6SkS1BIOOMjP1PUfg+ 8m2M3hl3Q/vdhh1VZNRZTusNTnsLXErlLiQehIIhU2iBHJvei7xneqonQOPJs+hC71wi oGNArbklljas4cISeuAK4x0xkUHmvllN5qMPFzKSspYwPoHSzrdH4u9PbXVrAZ6YBtvX whksGWxlABWLlirGa7aJMlHWruvyX+4GDN+kebDqCaJhkm2pBmg1Cvm6PK90Pde9WvgZ FKUg==
MIME-Version: 1.0
X-Received: by 10.43.139.133 with SMTP id iw5mr10383274icc.4.1423769859090; Thu, 12 Feb 2015 11:37:39 -0800 (PST)
Received: by 10.42.35.81 with HTTP; Thu, 12 Feb 2015 11:37:39 -0800 (PST)
In-Reply-To: <CAL02cgT17dXRh9pgWvegWrsDqOSTcxVJWVSyUSyXFTsk1noRsg@mail.gmail.com>
References: <bee6e93c6ea94b7cbb7ed32db177f421@ustx2ex-dag1mb2.msg.corp.akamai.com> <CAL02cgT17dXRh9pgWvegWrsDqOSTcxVJWVSyUSyXFTsk1noRsg@mail.gmail.com>
Date: Thu, 12 Feb 2015 11:37:39 -0800
Message-ID: <CA+9kkMDoaw=minR5M1ty5bbz7xgY4PXQ3iw1v1fqejVBXx3hqg@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary=001a11c2f622b1728e050ee940bb
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/DJz_gVarWRMaCJgh4LcWMnSv0cI>
Cc: "Salz, Rich" <rsalz@akamai.com>, "acme@ietf.org" <acme@ietf.org>
Subject: Re: [Acme] ACME BoF in Dallas -- call for agenda items, issues, speakers
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: Thu, 12 Feb 2015 19:37:43 -0000

On Thu, Feb 12, 2015 at 11:08 AM, Richard Barnes <rlb@ipv.sx> wrote:

> I would be happy to give an overview of draft-barnes-acme-*, and some of
> the design rationales for what's in there.
>
> It would be good to have some input form other folks who have designed and
> deployed cert automation stuff, e.g., CAs and hosting/server/CDN operators.
>
> In terms of goals for the BoF, it wouldn't be unreasonable to try to get
> some agreement around scope -- what certificate management are we trying to
> automate, what's missing in existing RFCs, and what solutions have people
> come up with already?
>
> ​Hi Richard,

The BoF description is here:

"Discussion of work that is going on with automated certificate management.
Let's Encrypt will obviously be a primary discussion point, but we hope to
have other CAs and other stakeholders represented."

The Let's Encrypt goal is given as "The entire enrollment process for
certificates occurs painlessly during the server’s native installation or
configuration process, while renewal occurs automatically in the
background."​, so one bound to the scope is there.   Other potential work
on the topic can certainly brought forward, and I think one reason for
approving the BoF is to get the gap analysis discussed.

That said, we only have one hour, so if folks can identify missing elements
and discuss them on the list, we may be able to make some progress before
the BoF itself.

regards,

Ted





> On Thu, Feb 12, 2015 at 10:57 AM, Salz, Rich <rsalz@akamai.com> wrote:
>
>>  Our BoF for the Dallas IETF next month was approved. The chairs are Ted
>> Hardie (on cc) and myself. Remote access will be available via jabber and
>> meetecho.
>>
>>  As Stephen said, this is a non-WG-forming BoF, but it’s quite likely
>> that the WG will form before we have a chance to hold another BoF.
>>
>>
>>
>> This note is to solicit agenda topics, open issues, people who want to
>> make a presentation, and so on.  We only have an hour, so presentations
>> will likely be short and the bulk of the time will be open mic and
>> capturing issues.
>>
>>
>>
>> And if anyone is in an early mood to volunteer to take notes, I’ll buy
>> you a beverage after the BoF J
>>
>>
>>
>> --
>>
>> Principal Security Engineer, Akamai Technologies
>>
>> IM: rsalz@jabber.me Twitter: RichSalz
>>
>>
>>
>> _______________________________________________
>> Acme mailing list
>> Acme@ietf.org
>> https://www.ietf.org/mailman/listinfo/acme
>>
>>
>