Last Call: <draft-ietf-acme-caa-06.txt> (CAA Record Extensions for Account URI and ACME Method Binding) to Proposed Standard

The IESG <> Wed, 27 March 2019 16:46 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 446A5120285; Wed, 27 Mar 2019 09:46:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-ietf-acme-caa-06.txt> (CAA Record Extensions for Account URI and ACME Method Binding) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
CC:, Daniel McCarney <>,,,,
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <>
Date: Wed, 27 Mar 2019 09:46:00 -0700
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Mar 2019 16:46:01 -0000

The IESG has received a request from the Automated Certificate Management
Environment WG (acme) to consider the following document: - 'CAA Record
Extensions for Account URI and ACME Method Binding'
  <draft-ietf-acme-caa-06.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 mailing lists by 2019-04-10. Exceptionally, comments may be
sent to instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.


   The CAA DNS record allows a domain to communicate issuance policy to
   CAs, but only allows a domain to define policy with CA-level
   granularity.  However, the CAA specification also provides facilities
   for extension to admit more granular, CA-specific policy.  This
   specification defines two such parameters, one allowing specific
   accounts of a CA to be identified by URI and one allowing specific
   methods of domain control validation as defined by the ACME protocol
   to be required.

The file can be obtained via

IESG discussion can be tracked via

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