[Servercert-wg] Voting begins: Ballot SC18 version 3: Phone

Tue Apr 30 06:06:33 MST 2019

Chunghwa Telecom Votes No on SC 18 version 3.

       Li-Chun 

From: Servercert-wg <servercert-wg-bounces at cabforum.org> On Behalf Of Doug Beattie via Servercert-wg
Sent: Wednesday, April 24, 2019 10:55 PM
To: CA/B Forum Server Certificate WG Public Discussion List <servercert-wg at cabforum.org>
Subject: Re: [Servercert-wg] Voting begins: Ballot SC18 version 3: Phone Contact with DNS CAA Phone Contact

GlobalSign votes NO on SC18.

It’s been pointed out that there is a lingering reference to contactemail that didn’t get updated for this ballot to contactphone.

We should let this ballot fail and then I will resubmit.  If there are any other items that need to be updated, please send them along.

Doug

From: Servercert-wg <servercert-wg-bounces at cabforum.org> On Behalf Of Doug Beattie via Servercert-wg
Sent: Wednesday, April 24, 2019 7:10 AM
To: CA/B Forum Server Certificate WG Public Discussion List <servercert-wg at cabforum.org>
Subject: Re: [Servercert-wg] Voting begins: Ballot SC18 version 3: Phone Contact with DNS CAA Phone Contact

GlobalSign votes yes on SC18

From: Servercert-wg <servercert-wg-bounces at cabforum.org> On Behalf Of Doug Beattie via Servercert-wg
Sent: Tuesday, April 23, 2019 5:11 PM
To: CA/B Forum Server Certificate WG Public Discussion List <servercert-wg at cabforum.org>
Subject: [Servercert-wg] Voting begins: Ballot SC18 version 3: Phone Contact with DNS CAA Phone Contact

Ballot SC18: Phone Contact with DNS CAA Phone Contact

Purpose of Ballot: This ballot will permit domain owners to publish phone numbers in a DNS CAA record for the purposes of performing domain validation.

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

--- MOTION BEGINS ---

This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates” as follows, based on Version 1.6.4. 

Add the following definition to section 1.6.1:

DNS CAA Phone Contact: The phone number defined in section B.1.2.

Add the following Acronym to section 1.6.2:

ADN      Authorization Doman Name

Add Section 3.2.2.4.17 as follows:

3.2.2.4.17 Phone Contact with DNS CAA Phone Contact 

Confirm the Applicant's control over the FQDN by calling the DNS CAA Phone Contact’s phone number and obtain a confirming response to validate the ADN. Each phone call MAY confirm control of multiple ADNs provided that the same DNS CAA Phone Contact phone number is listed for each ADN being verified and they provide a confirming response for each ADN. The relevant CAA Resource Record Set MUST be found using the search algorithm defined in RFC 6844 Section 4, as amended by Errata 5065 (Appendix A).

The CA MAY NOT be transferred or request to be transferred as this phone number has been specifically listed for the purposes of Domain Validation.   

In the event of reaching voicemail, the CA may leave the Random Value and the ADN(s) being validated.  The Random Value MUST be returned to the CA to approve the request.

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 section B.1.2 as follows:

B.1.2. CAA contactphone Property

SYNTAX: contactemail <rfc3966 Global Number> 

The CAA contactphone property takes a phone number as its parameter.  The entire parameter value MUST be a valid Global Number as defined in RFC 3966 section 5.1.4, or it cannot be used.  Global Numbers MUST have a preceding + and a country code and MAY contain visual separators.

The following is an example where the holder of the domain specified the contact property using a phone number.

$ORIGIN example.com.

    CAA 0 contactphone "+1 (555) 123-4567"

The contactphone property MAY be critical if the domain owner does not want CAs who do not understand it to issue certificates for the domain.

--- 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/dougbeattie/documents/compare/master...dougbeattie:SC18-v1-CAA-Phone-Validation

The procedure for approval of this ballot is as follows:

Discussion (7+ days)

Start Time: 2019-04-16   16:00 Eastern

End Time: Not before 2018-04-23   16:00 Eastern

Vote for approval (7 days)

Start Time: 2019-04-23   17:15 Eastern

End Time: 2019-04-30   17:15 Eastern

 <http://www.kamusm.gov.tr/sorumlulukreddi.jsp> Sorumluluk Reddi / Disclaimer

本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. 
Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20190430/9afb22d7/attachment-0001.html>