[Acme] Fwd: New Version Notification for draft-barnes-acme-03.txt

Richard Barnes <rlb@ipv.sx> Mon, 06 July 2015 23:27 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 []) by ietfa.amsl.com (Postfix) with ESMTP id E22F71A1AA8 for <acme@ietfa.amsl.com>; Mon, 6 Jul 2015 16:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id q_MFz5M4_I-i for <acme@ietfa.amsl.com>; Mon, 6 Jul 2015 16:27:06 -0700 (PDT)
Received: from mail-vn0-f52.google.com (mail-vn0-f52.google.com []) (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 101ED1A1A66 for <acme@ietf.org>; Mon, 6 Jul 2015 16:27:05 -0700 (PDT)
Received: by vnbf7 with SMTP id f7so13973886vnb.0 for <acme@ietf.org>; Mon, 06 Jul 2015 16:27:05 -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:content-type; bh=s1fYOIDDRKARtr2WOUhT7HuUkKwDN3KSMlV9Q2u+Hzk=; b=BJ0++NbzudYRiRBXBA+7ww+c70hvvrLu/tcacDDtIrhwAhkZKN5FAofqrlc73tdY4j qZo0517hahHcEZoXCdHPqUrdj0gPBfNYhbzee78LO70uww9B96vgEL/FOL5eVJIuf5HS 1NBpYulVeHMWG12femuwm8xvO25Zkmag2jEf44PEM5RcRQhbCRI0dBsn/O6fsdKw20GB P3reAqVwJgh4NqSw8Y1oUqWpxK0EfKun77Kl5CRQ9nZUgPB9VRlCmqCILeWKVAr68hiY 7MV0Yz+e0kWuxeHE0+xlthxsIX6YdBskyR8trF+wVb8l4PonnGmg//ZfiqPmrMP98ESj 9QXQ==
X-Gm-Message-State: ALoCoQmFGP2bbtEFD7aWcL3QBzxEL25T0ie5bl38v9r4gb32KjGFF92vbwNt7STILHK3OxTXf0FK
MIME-Version: 1.0
X-Received: by with SMTP id ep9mr1537618vdc.38.1436225225195; Mon, 06 Jul 2015 16:27:05 -0700 (PDT)
Received: by with HTTP; Mon, 6 Jul 2015 16:27:05 -0700 (PDT)
In-Reply-To: <20150706232337.20824.52894.idtracker@ietfa.amsl.com>
References: <20150706232337.20824.52894.idtracker@ietfa.amsl.com>
Date: Mon, 6 Jul 2015 19:27:05 -0400
Message-ID: <CAL02cgRAY0-zWLNgBi8Qf2Y5QPOjLJ5gzeWdNcGtOyFZ=4OS-g@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "acme@ietf.org" <acme@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/xRN0BgRMhQVfaVq-RImvInJSyHE>
Subject: [Acme] Fwd: New Version Notification for draft-barnes-acme-03.txt
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: <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: Mon, 06 Jul 2015 23:27:09 -0000

FYI, I have posted a new version of draft-barnes-acme, just *barely*
within the I-D deadline :)

I recommend *not* reading the diff for this one -- it's nearly as long
as the document itself.  While the broad outlines of the protocol are
basically the same as when we discussed it in Dallas, the Let's
Encrypt team contributed a lot of lessons learned that have made
things more robust.

Looking forward to some good discussion in Prague, but of course,
please don't hold your comments until then!


---------- Forwarded message ----------
From:  <internet-drafts@ietf.org>;
Date: Mon, Jul 6, 2015 at 7:23 PM
Subject: New Version Notification for draft-barnes-acme-03.txt
To: James Kasten <jdkasten@umich.edu>;, Richard Barnes <rlb@ipv.sx>;,
Jacob Hoffman-Andrews <jsha@eff.org>;

A new version of I-D, draft-barnes-acme-03.txt
has been successfully submitted by Richard Barnes and posted to the
IETF repository.

Name:           draft-barnes-acme
Revision:       03
Title:          Automatic Certificate Management Environment (ACME)
Document date:  2015-07-06
Group:          Individual Submission
Pages:          56
URL:            https://www.ietf.org/internet-drafts/draft-barnes-acme-03.txt
Status:         https://datatracker.ietf.org/doc/draft-barnes-acme/
Htmlized:       https://tools.ietf.org/html/draft-barnes-acme-03
Diff:           https://www.ietf.org/rfcdiff?url2=draft-barnes-acme-03

   Certificates in the Web's X.509 PKI (PKIX) are used for a number of
   purposes, the most significant of which is the authentication of
   domain names.  Thus, certificate authorities in the Web PKI are
   trusted to verify that an applicant for a certificate legitimately
   represents the domain name(s) in the certificate.  Today, this
   verification is done through a collection of ad hoc mechanisms.  This
   document describes a protocol that a certificate authority (CA) and
   an applicant can use to automate the process of verification and
   certificate issuance.  The protocol also provides facilities for
   other certificate management functions, such as certificate

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat