IETF Logo Mail Archive

Re: [Acme] Futures

Roland Shoemaker <roland@letsencrypt.org> Thu, 27 April 2017 17:06 UTC

Return-Path: <roland@letsencrypt.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 9C19D129B48 for <acme@ietfa.amsl.com>; Thu, 27 Apr 2017 10:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=letsencrypt.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 awqjUVvTPv3u for <acme@ietfa.amsl.com>; Thu, 27 Apr 2017 10:06:28 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (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 06CFB129B5D for <acme@ietf.org>; Thu, 27 Apr 2017 10:03:04 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id y33so31145193qta.2 for <acme@ietf.org>; Thu, 27 Apr 2017 10:03:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=letsencrypt.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=tHr3p9U8nIwhjzVTs6V2cZzvxjNTCMWAyPhIrcmpm0w=; b=avnWOImzktYNkK9EtsTcLVWSKgfm30XdiUYgJ5+Rn9E58nETZv8USby9byN+FqeVfI rMaVi6E1v0KpBK8HdceqM+IKXV5zUcd3+VfmTgtAdxAHJTDCsrjU4a00DWYPIusPQEcX Dh4txEOYGnr9ZPKe5DrLmFJkh11rjH8ceoddE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=tHr3p9U8nIwhjzVTs6V2cZzvxjNTCMWAyPhIrcmpm0w=; b=WhkN3J5Cxz4OfcN4Syzt7R5hRcnpEHtveT+XFirXAGBYV2cCdN3g1lJ998l4NrchUq y9gR5tQkcx/ltofGLT6+3xuMlvHwFveVDT8ukZRpf1c9Dab4bYtEXVmXSBLGFh49vjGM kRADgRdphUfGh2tPVuzC2LlG5BJF6d6t0DEM4riYzayT4UWEJRvKRoR1zXHugKqsEf9b V/EKtFlFwtFxBwcGlk/VdrVwKqIDMTVCKPl/CBo3GNtaV0AcqmnqLQB900hlCn+BDSA+ bBSdhDIP/JMNlNVnqslSRWgw6/MqCGN69DCK4We2QEC85zd5b2S5zpt2ekxJfJNzuVJR qNKg==
X-Gm-Message-State: AN3rC/6LyrmpaA4nXroI0ymuDwFxZLp1kobDvjshuxRnkAMqx8E1TqKN CkfIuhVMk/u916yn5chBGnMBhD/PcB/FZtc=
X-Received: by 10.237.60.98 with SMTP id u31mr6009079qte.224.1493312583848; Thu, 27 Apr 2017 10:03:03 -0700 (PDT)
MIME-Version: 1.0
References: <878ad4965b254e5aa7e58e8c812d1df1@usma1ex-dag1mb1.msg.corp.akamai.com>
In-Reply-To: <878ad4965b254e5aa7e58e8c812d1df1@usma1ex-dag1mb1.msg.corp.akamai.com>
From: Roland Shoemaker <roland@letsencrypt.org>
Date: Thu, 27 Apr 2017 17:02:53 +0000
Message-ID: <CAF1ySfEQ9EAkVGF=tfGayHxtNrCe9uQwGkv3AfpPP8+9CO56bQ@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>, ACME WG <acme@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c18fde0196c5a054e28ee3e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/djn4OJVhIPEofpVRizShnF9goCI>
Subject: Re: [Acme] Futures
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 27 Apr 2017 17:06:30 -0000

I'd be interested in getting draft-shoemaker-acme-ip (current draft:
https://www.ietf.org/id/draft-shoemaker-acme-ip-00.txt with a revision
coming in the very near future) adopted by the WG. We are currently
considering implementing the extension defined in it in the Let's Encrypt
server software Boulder and it would be good to get consensus from the
group that it is an appropriate path forward for validating IP addresses.

Thanks,
Roland

--
Software Engineer, Let's Encrypt
Internet Security Research Group / Linux Foundation

On Fri, Apr 21, 2017 at 7:01 PM Salz, Rich <rsalz@akamai.com> wrote:

> Having talked with the authors, we expect the base ACME draft to be ready
> for WGLC at least a month before the next IETF meeting.
>
>
>
> The CAA document, which we adopted, is very short and straightforward and
> seems like it can be handled easily over email.
>
>
>
> Does anyone have any new work items that would be ready to discuss in
> July?  Any rechartering discussion that looks promising?  If so, please
> post to the mailing list soon.
>
>
>
> Thanks,
>
> Rich and Ted’s Excellent ACME Adventure
>
>
>
>
>
> --
>
> Senior Architect, Akamai Technologies
>
> Member, OpenSSL Dev Team
>
> IM: richsalz@jabber.at Twitter: RichSalz
>
>
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>

v2.23.0 | Report a Bug | By Email