Re: [Acme] Proposed ACME Charter Language

Richard Barnes <rlb@ipv.sx> Thu, 14 May 2015 18:19 UTC

Return-Path: <rlb@ipv.sx>
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 31F061B2D69 for <acme@ietfa.amsl.com>; Thu, 14 May 2015 11:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 cyOyHhnbyiPY for <acme@ietfa.amsl.com>; Thu, 14 May 2015 11:19:31 -0700 (PDT)
Received: from mail-la0-f50.google.com (mail-la0-f50.google.com [209.85.215.50]) (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 71D001B2D67 for <acme@ietf.org>; Thu, 14 May 2015 11:19:29 -0700 (PDT)
Received: by labbd9 with SMTP id bd9so80010825lab.2 for <acme@ietf.org>; Thu, 14 May 2015 11:19:28 -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:date :message-id:subject:from:to:cc:content-type; bh=KenXyi/h+Hp+kI9YjKCJyoc/Tc2lBmG7qNdI/R0ECkc=; b=YLJNmW7CiZvxI5GSN7qbXV1bO3tzTbfzDDgh1s1MtsF8R87VPL3/ZIsWXlFUDOE2dC xZ72r/OTtz+EGg6sTs1DXxGV9x4VhlfzKqUYRp4sitzoR8YhXSMTvGtcB/Hp/2zo3Pik FOgHK9/iW6vNqgLiSNQZC1ughHuNHP+fcKXvbq5sOqDkQQvFRfgiTfwIDuT+6cqrYXIu p4maWs4WazoIXxPNhKWRVNKHbKMLGp2xVZNfwEX+n5oZPMXRf2EktsJ8iWkGDHFQpyjW 1GKQy0WME7P9XbH5wumoZzEXLd84CvGRu3PBLQv7MqciqbJEdysK7b3pNCcDXlBOfeus f6Kg==
X-Gm-Message-State: ALoCoQlG48mRqOwRpMiRRy0EVOYYjVREQgeLRlwo68t0XWiYFsjF6sE2rsLFqu2PI3lYbjQ0TJb5
MIME-Version: 1.0
X-Received: by 10.152.5.7 with SMTP id o7mr4104822lao.51.1431627568100; Thu, 14 May 2015 11:19:28 -0700 (PDT)
Received: by 10.25.214.162 with HTTP; Thu, 14 May 2015 11:19:27 -0700 (PDT)
In-Reply-To: <CABtrr-X-i-8cAYLBUGcZLiOVrjOcr2z0FvNCKzp-ZCe9yVFTSg@mail.gmail.com>
References: <CA+9kkMDB_sc6NLc4zqJAYZq6ELjHCd=6g_9CyH6zTH2cK+0apQ@mail.gmail.com> <36ae09b7c2bf4d60baca1e8d8ba9fd44@ustx2ex-dag1mb4.msg.corp.akamai.com> <20150514165733.GA1376@eff.org> <CABtrr-X-i-8cAYLBUGcZLiOVrjOcr2z0FvNCKzp-ZCe9yVFTSg@mail.gmail.com>
Date: Thu, 14 May 2015 14:19:27 -0400
Message-ID: <CAL02cgQqir-BwZ6mMbJcs8BNXR_vaArUJy5XdWSFFY=EKJOQ4w@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Joseph Lorenzo Hall <joe@cdt.org>
Content-Type: multipart/alternative; boundary=089e01419d8aa5d13805160ec4aa
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/1Idk_m4LSMs1val04Ptb3DQX4pg>
Cc: "Salz, Rich" <rsalz@akamai.com>, Ted Hardie <ted.ietf@gmail.com>, Peter Eckersley <pde@eff.org>, "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:19:33 -0000

On Thu, May 14, 2015 at 2:16 PM, Joseph Lorenzo Hall <joe@cdt.org>; wrote:

> 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.
>

Nope, this matches my understanding.  The two efforts can proceed
independently, and we'll try to square them up in good time.

--Ricahrd



>
> 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
>
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>