Re: [Acme] ACME draft is now in WGLC.

Jacob Hoffman-Andrews <jsha@eff.org> Tue, 07 February 2017 17:41 UTC

Return-Path: <jsha@eff.org>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC7E129591 for <acme@ietfa.amsl.com>; Tue, 7 Feb 2017 09:41:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.002
X-Spam-Level:
X-Spam-Status: No, score=-7.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eff.org
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 DHFxvLb_fxTl for <acme@ietfa.amsl.com>; Tue, 7 Feb 2017 09:41:09 -0800 (PST)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E65D129592 for <acme@ietf.org>; Tue, 7 Feb 2017 09:41:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=wktxm6vqpV2y0hSG6elb8vxQ4WCcTfAUGu4ENwv1bAk=; b=2ydGO9GSXq4XEgde96XSHYH8FCbOgdNhyvdRHSQY1pU0j2HINy1KBZzyvID8NOQuTyA76JjJz762ofmobm+DGGTTgxzfpGePlDfNvQWj9K4Vc7JCbZpMEGd214uZWHEkMTD2dPJnwCumRtVPhDH3d0hmioYd4PBMODoqm6I0oGQ=;
Received: ; Tue, 07 Feb 2017 09:41:10 -0800
To: "Salz, Rich" <rsalz@akamai.com>, "acme@ietf.org" <acme@ietf.org>
References: <8473d9ba84894d49b2f2232370d66b46@usma1ex-dag1mb3.msg.corp.akamai.com>
From: Jacob Hoffman-Andrews <jsha@eff.org>
Message-ID: <3a52cc35-f9ab-ad17-d5dc-c54c7f47a219@eff.org>
Date: Tue, 7 Feb 2017 09:41:08 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <8473d9ba84894d49b2f2232370d66b46@usma1ex-dag1mb3.msg.corp.akamai.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/DoLV3syYOu0P-R5TIzNEs09EOEQ>
Subject: Re: [Acme] ACME draft is now in WGLC.
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 07 Feb 2017 17:41:12 -0000

Let's Encrypt engineers have been working on an implementation of the
latest spec:

https://github.com/letsencrypt/pebble

We'll take lessons learned from that when we build support into our
production boulder software. We're also going to adapt the Python ACME
library to support the latest version.

On 02/07/2017 09:27 AM, Salz, Rich wrote:
> I put the time period as six weeks, which takes us to just around IETF-98...
>
> PLEASE reply on list if you will review and/or are interested in working on interop. 
> --  
> Senior Architect, Akamai Technologies
> Member, OpenSSL Dev Team
> IM: richsalz@jabber.at Twitter: RichSalz
>
>
> -----Original Message-----
> From: IETF Secretariat [mailto:ietf-secretariat-reply@ietf.org] 
> Sent: Tuesday, February 07, 2017 12:26 PM
> To: draft-ietf-acme-acme@ietf.org; acme-chairs@ietf.org
> Subject: IETF WG state changed for draft-ietf-acme-acme
>
>
> The IETF WG state of draft-ietf-acme-acme has been changed to "In WG Last Call" from "WG Document" by Rich Salz:
>
> https://datatracker.ietf.org/doc/draft-ietf-acme-acme/
>
>
> Comment:
> As we agreed at IETF-97 (Seoul), we will have a slightly longer WGLC period to encourage implementations and interop.
>
> Are there any volunteers to read and review this document?  Please post to acme@ietf.org.
>
> Does anyone have an implementation in progress and would be interested in doing interop at the IETF Hackathon at IETF-98 in Chicago?  Please post to acme@ietf.org
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>