Last Call: <draft-ietf-acme-acme-10.txt> (Automatic Certificate Management Environment (ACME)) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 21 March 2018 15:48 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 140F612E91F; Wed, 21 Mar 2018 08:48:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-acme-acme-10.txt> (Automatic Certificate Management Environment (ACME)) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: Yoav Nir <ynir.ietf@gmail.com>, draft-ietf-acme-acme@ietf.org, acme@ietf.org, ynir.ietf@gmail.com, Kathleen.Moriarty.ietf@gmail.com, acme-chairs@ietf.org
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <152164728107.7499.5317110410792682160.idtracker@ietfa.amsl.com>
Date: Wed, 21 Mar 2018 08:48:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5UfbD0P7LtNKnqWtmmsQ0voHSHg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 15:48:16 -0000

The IESG has received a request from the Automated Certificate Management
Environment WG (acme) to consider the following document: - 'Automatic
Certificate Management Environment (ACME)'
  <draft-ietf-acme-acme-10.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-04-18. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   Certificates in PKI using X.509 (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 certification 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.

   RFC EDITOR: PLEASE REMOVE THE FOLLOWING PARAGRAPH: The source for
   this draft is maintained in GitHub.  Suggested changes should be
   submitted as pull requests at https://github.com/ietf-wg-acme/acme
   [1].  Instructions are on that page as well.  Editorial changes can
   be managed in GitHub, but any substantive change should be discussed
   on the ACME mailing list (acme@ietf.org).




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-acme-acme/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-acme-acme/ballot/


No IPR declarations have been submitted directly on this I-D.

Last call has been extended an additional 2 weeks due to last call being issued during an IETF meeting.