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

Richard Barnes <rlb@ipv.sx> Thu, 29 January 2015 02:35 UTC

MIME-Version: 1.0
In-Reply-To: <20150129023217.18836.2032.idtracker@ietfa.amsl.com>
References: <20150129023217.18836.2032.idtracker@ietfa.amsl.com>
Date: Wed, 28 Jan 2015 21:34:57 -0500
Message-ID: <CAL02cgR-V1T5exZmMP6yG4Bv2A+JZf2n0JG6XunQcoA8MbU68w@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: "acme@ietf.org" <acme@ietf.org>
Content-Type: multipart/alternative; boundary="001a113683ea7e3cfc050dc155c5"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/QNfEWEUWw5yuVOodmEEQr54Avr8>
Subject: [Acme] Fwd: New Version Notification for draft-barnes-acme-01.txt
Precedence: list

Hey all,

FYI, I have just submitted two versions of ACME as I-Ds.  The -00 version
is the protocol as we first announced it, with a few bug fixes.  Version
-01 is a redesign with a more RESTful architecture.

FWIW, I think the -01 version is the current implementation target for
Let's Encrypt.  But I wanted to get both versions in the archive so that
people can compare and contrast.

--Richard


---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Wed, Jan 28, 2015 at 9:32 PM
Subject: New Version Notification for draft-barnes-acme-01.txt
To: Alex Halderman <jhalderm@eecs.umich.edu>, James Kasten <
jdkasten@umich.edu>, Richard Barnes <rlb@ipv.sx>, Seth Schoen <
schoen@eff.org>, Peter Eckersley <pde@eff.org>



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

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

Abstract:
   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
   revocation.




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

[Acme] Fwd: New Version Notification for draft-ba… Richard Barnes