idnits 2.17.1 draft-shoemaker-caa-ip-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** There is 1 instance of too long lines in the document, the longest one being 8 characters in excess of 72. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (September 13, 2017) is 2410 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2818 (Obsoleted by RFC 9110) ** Obsolete normative reference: RFC 6844 (Obsoleted by RFC 8659) Summary: 4 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Shoemaker 3 Internet-Draft ISRG 4 Intended status: Standards Track September 13, 2017 5 Expires: March 17, 2018 7 Certification Authority Authorization (CAA) Validation for IP Addresses 8 draft-shoemaker-caa-ip-01 10 Abstract 12 The Certification Authority Authorization (CAA) RFC specifies a 13 method for users to restrict which Certificate Authorities (CAs) are 14 authorized to issue certificates for their DNS domain names. This 15 document extends that specification to provide a method for holders 16 of IP addresses to do the same. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on March 17, 2018. 35 Copyright Notice 37 Copyright (c) 2017 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 3. Mechanism . . . . . . . . . . . . . . . . . . . . . . . . . . 2 55 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 56 4.1. Certification Authority Restriction Properties . . . . . 3 57 5. Normative References . . . . . . . . . . . . . . . . . . . . 3 58 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 60 1. Introduction 62 This document describes an extension to RFC 6844 [RFC6844] which 63 allows for the use of Certification Authority Authorization DNS 64 Records to be used to restrict issuance of certificates to IP 65 addresses instead of just DNS names. This is done by defining a new 66 lookup mechanism for IPv4 and IPv6 addresses as previously a 67 mechanism only existed for DNS names. 69 2. Terminology 71 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 72 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 73 and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 74 [RFC2119]. 76 3. Mechanism 78 Before issuing a certificate containing a IP address a compliant CA 79 MUST check for the relevant CAA Resource Record set. If such a 80 record set exists a CA MUST NOT issue a certificate unless the 81 records in the set are consistent with the request and the policies 82 of the CA. 84 A certificate request MAY specify more than one IP address in which 85 case CAs MUST verify the CA Resource Record set for all the IP 86 addresses specified in the request. 88 As defined in RFC 2818 [RFC2818] IP addresses in certificates must 89 match exactly with the requested URI so CAs MUST NOT consider CAA 90 records with the "issuewild" tag to be part of the relevant Resource 91 Record set for a IP address. 93 Unlike the mechanism defined in RFC 6844 [RFC6844] this mechanism 94 doesn't involve climbing the DNS tree and only requires querying a 95 single DNS name. The relevant Resource Record set for a given IP 96 address is found by querying the reverse mapping zone for the IP for 97 CAA records. 99 Given a certificate request containing the IPv6 address "2001:db8::1" 100 the relevant query for the reverse mapping within the IP6.ARPA 101 [RFC3596] zone would be: 103 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. IN CAA 105 And for a request containing the IPv4 address "192.0.2.1" the 106 relevant query for the reverse mapping within the IN-ADDR.ARPA 107 [RFC1034] zone would be: 109 1.2.0.192.in-addr.arpa. IN CAA 111 When doing queries CAs SHOULD either use a resolver that chases CNAME 112 records or manually chase CNAMEs themselves in order to allow for 113 zone delegations [RFC2317]. 115 4. IANA Considerations 117 4.1. Certification Authority Restriction Properties 119 Change the contents of the Meaning column for the "issue" Tag to say 120 "Authorization Entry by Domain or IP address" and add "draft- 121 shoemaker-caa-ip" to the References column. 123 5. Normative References 125 [RFC1034] Mockapetris, P., "Domain names - concepts and facilities", 126 STD 13, RFC 1034, DOI 10.17487/RFC1034, November 1987, 127 . 129 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 130 Requirement Levels", BCP 14, RFC 2119, 131 DOI 10.17487/RFC2119, March 1997, . 134 [RFC2317] Eidnes, H., de Groot, G., and P. Vixie, "Classless IN- 135 ADDR.ARPA delegation", BCP 20, RFC 2317, 136 DOI 10.17487/RFC2317, March 1998, . 139 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, 140 DOI 10.17487/RFC2818, May 2000, . 143 [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, 144 "DNS Extensions to Support IP Version 6", STD 88, 145 RFC 3596, DOI 10.17487/RFC3596, October 2003, 146 . 148 [RFC6844] Hallam-Baker, P. and R. Stradling, "DNS Certification 149 Authority Authorization (CAA) Resource Record", RFC 6844, 150 DOI 10.17487/RFC6844, January 2013, . 153 Author's Address 155 Roland Bracewell Shoemaker 156 ISRG 158 Email: roland@letsencrypt.org