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

Tim Hollebeek tim.hollebeek at digicert.com
Mon Oct 15 23:23:47 UTC 2018


No.

 

Ballots do not automatically go into voting with the current Bylaws.  I
recommend refamiliarizing yourself with the modified voting rules we put in
place last year and just reconfirmed recently, that allow Ballots to be
updated and allow flexibility of the discussion period length.

 

And it is not entirely clear whether this is a final ballot or not at this
point.  Some people want to amend it to put the TXT methods back in.

 

Voting starts when the proposer reposts the ballot and announces the start
of voting.  That can happen anywhere between 7-21 days after discussion
begins, so cannot be predicted in advance.  Hence "TBD".

 

It will be replaced with the real voting start and end dates, once voting
starts.

 

-Tim

 

From: Richard Smith <rich at comodoca.com> 
Sent: Monday, October 15, 2018 11:38 AM
To: Tim Hollebeek <tim.hollebeek at digicert.com>; CA/Browser Forum Public
Discussion List <public at cabforum.org>; CA/B Forum Server Certificate WG
Public Discussion List <servercert-wg at cabforum.org>
Subject: RE: Ballot SC4 version 5: CAA Contact Property and Associated
E-mail Validation Method

 

<snip>

 

Vote for approval (7 days)

 

Start Time: TBD

 

End Time: TBD

</snip>

 

Why TBD?  Is this NOT a final ballot that is currently in discussion period
and going into voting period in two days?  If it IS then the voting start
and end time need to be specified.  If it's NOT then this:

<snip>

Discussion (7+ days)

 

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

 

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

</snip>

 

SHOULD also state TBD.  Please, we need to stop being so sloppy about these
things.  It creates confusion.

 

Regards,

Rich

 

From: Public <public-bounces at cabforum.org
<mailto:public-bounces at cabforum.org> > On Behalf Of Tim Hollebeek via Public
Sent: Wednesday, October 10, 2018 2:52 PM
To: CA/Browser Forum Public Discussion List <public at cabforum.org
<mailto:public at cabforum.org> >; CA/B Forum Server Certificate WG Public
Discussion List <servercert-wg at cabforum.org
<mailto:servercert-wg at cabforum.org> >
Subject: [cabfpub] Ballot SC4 version 5: CAA Contact Property and Associated
E-mail Validation Method

 

 

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
<mailto: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
<https://github.com/cabforum/documents/compare/Ballot-SC4---CAA-CONTACT-emai
l?diff=unified&expand=1> &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://lists.cabforum.org/pipermail/public/attachments/20181015/2f4e79a5/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4940 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/public/attachments/20181015/2f4e79a5/attachment-0003.p7s>


More information about the Public mailing list