IETF blog post on ACME
Richard Barnes <rlb@ipv.sx> Tue, 12 March 2019 20:38 UTC
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3E1D12426A for <ietf@ietfa.amsl.com>; Tue, 12 Mar 2019 13:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.com
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 Mcg6PvkkBLLY for <ietf@ietfa.amsl.com>; Tue, 12 Mar 2019 13:38:33 -0700 (PDT)
Received: from mail-ot1-x342.google.com (mail-ot1-x342.google.com [IPv6:2607:f8b0:4864:20::342]) (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 7342C12008A for <ietf@ietf.org>; Tue, 12 Mar 2019 13:38:33 -0700 (PDT)
Received: by mail-ot1-x342.google.com with SMTP id i12so3735247otp.12 for <ietf@ietf.org>; Tue, 12 Mar 2019 13:38:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=AYvWuIxj2O/xEZeK2JWjybrlwvge2i7SFx7cxFR7Aik=; b=DEHrfsq2bKgZF89wBgGZaFJwadCNpYOWEIfZDmK2pybUBlXQwr5d5J6FfKI4m1pI3E Bwl7AkO+AyeVhLgodFjMTcl5PXtL++TRVjQV0hAOZfsYCehRLL9dRyl6E46NlTq8SawI c59JT7gISwbG9mGDTIJmkfPeSdoSnn0VeRCX4hwcp/GwLl65A4cBPNUAjnyfeEtQbq1Q EOFJboYrQWJ+KLLXqRcpjFBlUAkh6//6GCFUTGhqv+OtqQAUyxG/SUqKlNTX4ZjoM5sh 2I1P6Yjm6D3PxyDHZZ1dPdFpkMncfBAFpxKFEo1UNZkz8fywTxIEFNSYw8skKeDyJelu HSEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=AYvWuIxj2O/xEZeK2JWjybrlwvge2i7SFx7cxFR7Aik=; b=jyVNDxb5wWfQ3tssvO2xTAhtry7kRqCZPZosX8tkFYWaTLK4wGbPxUy8ONfsoDRcyb ZztFwc9ZKNNugfhb6WxcXm12t/PdnRDqHBb2tGfdVnNI9mh5HBJVA5+jH4eF1ppbBYw9 aIrgbx4gtJTZZwZdtaTZkBNYZSe2suMt4rFW/vC6UAvMbgRTu/521HytgXVMYXAownRr 3QEIJ/Ob4AhOdJ9FYik8W5q0fDRplJgk+H1s4pA3OzArTIXih/t0cpKbMU54x1Rojq2j EAFSbYjEMAkhiQ+kMo66sTCT0P4p1MXo+QfUf72Mnw0xPe3pOqFQ/4vdeRROA81ZI5Ah OMMA==
X-Gm-Message-State: APjAAAXLLbLOsQyPoozK+DNIM+g5ig66Bg5ViP+w/+RsqBRW1xViDj4i VMDBjR0ysR1jjzAYbuJtzHUhH20sqrV0URJmuZPrqFUY
X-Google-Smtp-Source: APXvYqzPEiE+UrC+LociQSxbwMWHcjQK4Zn8y+O9o6XB10uEhiOMgkjgHz1mW58afbxc1AnHTp63REXGUSwzPuaR/ws=
X-Received: by 2002:a9d:768f:: with SMTP id j15mr23853971otl.116.1552423112361; Tue, 12 Mar 2019 13:38:32 -0700 (PDT)
MIME-Version: 1.0
From: Richard Barnes <rlb@ipv.sx>
Date: Tue, 12 Mar 2019 13:38:21 -0700
Message-ID: <CAL02cgRD6nXG_eQXQRe7a4wwfQqg_vOjdJRMZi7ee2W2odb7nQ@mail.gmail.com>
Subject: IETF blog post on ACME
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002769980583ebacd5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f7jzS-V6D4xIgXsGFELx1zx0Kn4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2019 20:38:35 -0000
Hey all, In honor of ACME finally being published as an RFC, my co-authors and I wrote a quick blog post announcing ACME and why it matters: https://www.ietf.org/blog/acme/ The tl;dr is: - Certificates are necessary to make secure applications scale - Getting a certificate used to be hard, but ACME makes it easy - Now we can encrypt all the things! For those of you more at the networking layer, think of it like DHCP -- long ago, IP address assignment was manual and slow, and we needed an automated way of handing out addresses to make the Internet scale. Same thing here, but for the PKI. Sincere thanks to the many contributors to this work! --Richard
- IETF blog post on ACME Richard Barnes
- Re: IETF blog post on ACME Lloyd Wood
- Re: IETF blog post on ACME Richard Barnes
- Re: IETF blog post on ACME Eric Rescorla
- Re: IETF blog post on ACME Eric Rescorla
- Re: IETF blog post on ACME Jana Iyengar
- Re: IETF blog post on ACME Paul Wouters
- Re: IETF blog post on ACME Carsten Bormann
- Re: IETF blog post on ACME Lloyd Wood
- Internet standards (Re: IETF blog post on ACME) Carsten Bormann
- Re: Internet standards (Re: IETF blog post on ACM… Kathleen Moriarty
- Re: IETF blog post on ACME Spencer Dawkins at IETF
- Re: IETF blog post on ACME S Moonesamy
- Re: IETF blog post on ACME Richard Barnes
- Re: IETF blog post on ACME S Moonesamy
- Re: IETF blog post on ACME Carsten Bormann
- two-step standards process (was: IETF blog post o… Keith Moore
- Re: two-step standards process (was: IETF blog po… Michael Richardson