Re: [Acme] Proposed ACME Charter Language

Joseph Lorenzo Hall <joe@cdt.org> Thu, 14 May 2015 18:16 UTC

Return-Path: <jhall@cdt.org>
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 6DD451B2D4E for <acme@ietfa.amsl.com>; Thu, 14 May 2015 11:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.199
X-Spam-Level:
X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779] 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 1ZfSwH-GFMyg for <acme@ietfa.amsl.com>; Thu, 14 May 2015 11:16:49 -0700 (PDT)
Received: from mail-la0-f43.google.com (mail-la0-f43.google.com [209.85.215.43]) (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 F3D6C1B2D4B for <acme@ietf.org>; Thu, 14 May 2015 11:16:48 -0700 (PDT)
Received: by labbd9 with SMTP id bd9so79883605lab.2 for <acme@ietf.org>; Thu, 14 May 2015 11:16:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=XA9whPTAhcaN3SnUZutysMjcKfooyqIzeUgAnaMNsK0=; b=D7LwTGAfNxAEW4pfYDP5e8nMFBB5zBgnP6zrQTzhydYN459kKvvzbwu5hKXC8cPa4L 3DO0m/UH5w4tv8dYjRu/Wh++SSiOo9S4YwcBnDYiDhxmH2PfdhJVnttEF/yoAItY+db4 +z5JAItucPt72H/hRYksZrGD4mJmh7u/CTlqEb0FzJtzPhhoXqAoqhRAlNjzPrEBtUa5 hddyihDCZnzu3THTZeGpElryfRE0Kp9cFAgfMJo9CVSz4W7uA8XpkWsX+uj/Dkccx2qQ Xd5bhXcO7MavUnkaD5AN0Xt0pVxM7RIPUe8qil2yHt1TrgTaSdXVDBk21WYIyG4zMzaP FWIA==
X-Gm-Message-State: ALoCoQmxf9fcfaj422y5fIQGQqCX97ZmBgSsj9gFIrjePwjJ7QTXYL6n89YFtQUi8iV7fnuXxzaD
X-Received: by 10.112.180.137 with SMTP id do9mr4061860lbc.91.1431627407444; Thu, 14 May 2015 11:16:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.84.15 with HTTP; Thu, 14 May 2015 11:16:26 -0700 (PDT)
In-Reply-To: <20150514165733.GA1376@eff.org>
References: <CA+9kkMDB_sc6NLc4zqJAYZq6ELjHCd=6g_9CyH6zTH2cK+0apQ@mail.gmail.com> <36ae09b7c2bf4d60baca1e8d8ba9fd44@ustx2ex-dag1mb4.msg.corp.akamai.com> <20150514165733.GA1376@eff.org>
From: Joseph Lorenzo Hall <joe@cdt.org>
Date: Thu, 14 May 2015 14:16:26 -0400
Message-ID: <CABtrr-X-i-8cAYLBUGcZLiOVrjOcr2z0FvNCKzp-ZCe9yVFTSg@mail.gmail.com>
To: Peter Eckersley <pde@eff.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/OJgV_cnnM72V23uc-5f1ZcsfVR8>
Cc: "Salz, Rich" <rsalz@akamai.com>, Ted Hardie <ted.ietf@gmail.com>, "acme@ietf.org" <acme@ietf.org>
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: Thu, 14 May 2015 18:16:50 -0000

On Thu, May 14, 2015 at 12:57 PM, Peter Eckersley <pde@eff.org> wrote:
> On Wed, May 13, 2015 at 11:39:36PM +0000, Salz, Rich wrote:
>> > https://github.com/letsencrypt/acme-spec/issues
>>
>> I'd prefer if we just recorded issues there, but discussed them in the mailing list.
>
> Folks should also be aware that because letsencypt needs to move fast to
> get working and interoperable clients and servers for its launch,
> there's a fair chance that it will wind up with a deployed solution that
> diverges from the draft spec in various ways, and can't block on an IETF
> WG's deliberations.
>
> For that reason I think it's probably best if the WG and spec work
> doesn't start in earnest until after Let's Encrypt has launched (IIRC
> that was the consensus in Dallas, too).  And in the pre-launch period, a
> bug tracker is the most efficient and practical way for us to keep track
> of things that we absolutely need to fix/diverge from the draft spec on.

Heya, this reads as if the IETF WG work should block on the
letsencrypt launch and it seemed pretty clear in Dallas that while
letsencrypt is a motivating effort to spin up ACME that neither should
in the short-term be very eeply dependent on each other. (and this is
coming from someone who is very excited about both efforts)

Happy to be corrected if this was a misinterpretation or a mistake on my part.

best, Joe

> --
> Peter Eckersley                            pde@eff.org
> Chief Computer Scientist          Tel  +1 415 436 9333 x131
> Electronic Frontier Foundation    Fax  +1 415 436 9993
>
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme



-- 
Joseph Lorenzo Hall
Chief Technologist
Center for Democracy & Technology
1634 I ST NW STE 1100
Washington DC 20006-4011
(p) 202-407-8825
(f) 202-637-0968
joe@cdt.org
PGP: https://josephhall.org/gpg-key
fingerprint: 3CA2 8D7B 9F6D DBD3 4B10  1607 5F86 6987 40A9 A871