draft-ietf-acme-caa-03.txt   draft-ietf-acme-caa-04.txt 
ACME Working Group H. Landau ACME Working Group H. Landau
Internet-Draft August 30, 2017 Internet-Draft May 27, 2018
Intended status: Standards Track Intended status: Standards Track
Expires: March 3, 2018 Expires: November 28, 2018
CAA Record Extensions for Account URI and ACME Method Binding CAA Record Extensions for Account URI and ACME Method Binding
draft-ietf-acme-caa-03 draft-ietf-acme-caa-04
Abstract Abstract
The CAA DNS record allows a domain to communicate issuance policy to The CAA DNS record allows a domain to communicate issuance policy to
CAs, but only allows a domain to define policy with CA-level CAs, but only allows a domain to define policy with CA-level
granularity. However, the CAA specification also provides facilities granularity. However, the CAA specification also provides facilities
for extension to admit more granular, CA-specific policy. This for extension to admit more granular, CA-specific policy. This
specification defines two such parameters, one allowing specific specification defines two such parameters, one allowing specific
accounts of a CA to be identified by URI and 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 methods of domain control validation as defined by the ACME protocol
to be required. to be required.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 3, 2018. This Internet-Draft will expire on November 28, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
skipping to change at page 2, line 27 skipping to change at page 2, line 27
5.1. Limited to CAs Processing CAA Records . . . . . . . . . . 5 5.1. Limited to CAs Processing CAA Records . . . . . . . . . . 5
5.2. Restrictions Ineffective without CA Recognition . . . . . 5 5.2. Restrictions Ineffective without CA Recognition . . . . . 5
5.3. Mandatory Consistency in CA Recognition . . . . . . . . . 5 5.3. Mandatory Consistency in CA Recognition . . . . . . . . . 5
5.4. URI Ambiguity . . . . . . . . . . . . . . . . . . . . . . 6 5.4. URI Ambiguity . . . . . . . . . . . . . . . . . . . . . . 6
5.5. Authorization Freshness . . . . . . . . . . . . . . . . . 6 5.5. Authorization Freshness . . . . . . . . . . . . . . . . . 6
5.6. DNSSEC . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.6. DNSSEC . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.7. Use without DNSSEC . . . . . . . . . . . . . . . . . . . 7 5.7. Use without DNSSEC . . . . . . . . . . . . . . . . . . . 7
5.8. Restrictions Supercedable by DNS Delegation . . . . . . . 8 5.8. Restrictions Supercedable by DNS Delegation . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Normative References . . . . . . . . . . . . . . . . . . . . 8 7. Normative References . . . . . . . . . . . . . . . . . . . . 8
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 8 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
This specification defines two parameters for the "issue" and This specification defines two parameters for the "issue" and
"issuewild" properties of the Certification Authority Authorization "issuewild" properties of the Certification Authority Authorization
(CAA) DNS resource record [RFC6844]. The first, "account-uri", (CAA) DNS resource record [RFC6844]. The first, "account-uri",
allows authorization conferred by a CAA policy to be restricted to allows authorization conferred by a CAA policy to be restricted to
specific accounts of a CA, which are identified by URIs. The second, specific accounts of a CA, which are identified by URIs. The second,
"validation-methods", allows the set of validation methods supported "validation-methods", allows the set of validation methods supported
skipping to change at page 8, line 29 skipping to change at page 8, line 29
6. IANA Considerations 6. IANA Considerations
None. As per the CAA specification, the parameter namespace for the None. As per the CAA specification, the parameter namespace for the
CAA "issue" and "issuewild" properties has CA-defined semantics. CAA "issue" and "issuewild" properties has CA-defined semantics.
This document merely specifies a RECOMMENDED semantic for parameters This document merely specifies a RECOMMENDED semantic for parameters
of the names "account-uri" and "validation-methods". of the names "account-uri" and "validation-methods".
7. Normative References 7. Normative References
[I-D.ietf-acme-acme] [I-D.ietf-acme-acme]
Barnes, R., Hoffman-Andrews, J., and J. Kasten, "Automatic Barnes, R., Hoffman-Andrews, J., McCarney, D., and J.
Certificate Management Environment (ACME)", draft-ietf- Kasten, "Automatic Certificate Management Environment
acme-acme-07 (work in progress), June 2017. (ACME)", draft-ietf-acme-acme-12 (work in progress), April
2018.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC2119, March 1997,
rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC Resource Identifier (URI): Generic Syntax", STD 66,
3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/info/rfc3986>. <https://www.rfc-editor.org/info/rfc3986>.
[RFC6844] Hallam-Baker, P. and R. Stradling, "DNS Certification [RFC6844] Hallam-Baker, P. and R. Stradling, "DNS Certification
Authority Authorization (CAA) Resource Record", RFC 6844, Authority Authorization (CAA) Resource Record", RFC 6844,
DOI 10.17487/RFC6844, January 2013, <https://www.rfc- DOI 10.17487/RFC6844, January 2013,
editor.org/info/rfc6844>. <https://www.rfc-editor.org/info/rfc6844>.
Appendix A. Examples Appendix A. Examples
The following shows an example DNS zone file fragment which nominates The following shows an example DNS zone file fragment which nominates
two account URIs as authorized to issue certificates for the domain two account URIs as authorized to issue certificates for the domain
"example.com". Issuance is restricted to the CA "example.net". "example.com". Issuance is restricted to the CA "example.net".
example.com. IN CAA 0 issue "example.net; \ example.com. IN CAA 0 issue "example.net; \
account-uri=https://example.net/account/1234" account-uri=https://example.net/account/1234"
example.com. IN CAA 0 issue "example.net; \ example.com. IN CAA 0 issue "example.net; \
 End of changes. 12 change blocks. 
18 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/