[Servercert-wg] Ballot SC4 version 5: CAA Contact Property and Associated E-mail Validation Method

[Tim Hollebeek]

Ballot SC4: CAA Contact Property and Associated E-mail Validation Method

Purpose of Ballot: Increasingly, contact information is not available in
WHOIS due to concerns about potential GDPR violations.  This ballot
specifies a method by which domain holders can publish their contact
information via DNS, and how CAs can use that information for validating
domain control.

The following motion has been proposed by Tim Hollebeek of DigiCert and
endorsed by Bruce Morton of Entrust and Doug Beattie of GlobalSign.

--- MOTION BEGINS ---

This ballot modifies the "Baseline Requirements for the Issuance and
Management of Publicly-Trusted Certificates" as follows, based on Version
1.6.0:

Add Section 3.2.2.4.13: Email to DNS CAA Contact

Confirming the Applicant's control over the FQDN by sending a Random Value
via email and then receiving a confirming response utilizing the Random
Value. The Random Value MUST be sent to an email address identified as a CAA
contactemail property record as defined in Appendix B.

 

Each email MAY confirm control of multiple FQDNs, provided that the DNS
contactemail email address is the same for each ADN being validated.

 

The Random Value SHALL be unique in each email. The email MAY be re-sent in
its entirety, including the re-use of the Random Value, provided that its
entire contents and recipient SHALL remain unchanged. The Random Value SHALL
remain valid for use in a confirming response for no more than 30 days from
its creation. The CPS MAY specify a shorter validity period for Random
Values.

 

Note: Once the FQDN has been validated using this method, the CA MAY also
issue Certificates for other FQDNs that end with all the labels of the
validated FQDN. This method is suitable for validating Wildcard Domain
Names.

Add Appendix B: DNS Contact Properties

The contactemail property allows domain owners to publish contact
information in DNS in addition to WHOIS for the purpose of validating domain
control.

CAA contactemail Property

 

contactemail <rfc6532emailaddress> :  The contactemail property specifies an
emailaddress that can be used to perform domain validation.

The contactemail property takes an email address as its parameter.  The
entire parameter value of the MUST be a valid email address as defined in
RFC 6532 section 3.2, with no additional padding or structure, or it cannot
be used.

 

The following is an example where the holder of the domain specified the
contact property using an email address.

 

$ORIGIN example.com

.              CAA 0 issue "ca.example.net"

.              CAA 0 contactemail "domainowner at example.com"

 

--- MOTION ENDS ---

*** WARNING ***: USE AT YOUR OWN RISK.  THE REDLINE BELOW IS NOT THE
OFFICIAL VERSION OF THE CHANGES (CABF Bylaws, Section 2.4(a)):

 

A comparison of the changes can be found at:
https://github.com/cabforum/documents/compare/Ballot-SC4---CAA-CONTACT-email
?diff=unified&expand=1

The procedure for approval of this ballot is as follows:

Discussion (7+ days)

Start Time: 2018-10-10 3:50pm Eastern

End Time: Not before 2018-10-17 3:50pm Eastern

Vote for approval (7 days)

Start Time: TBD

End Time: TBD

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20181010/a8b88252/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4940 bytes
Desc: not available
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20181010/a8b88252/attachment.p7s>