[Servercert-wg] Ballot SC18 version 2: Phone Contact with DNS CAA Phone Contact

Mon Apr 15 13:46:08 MST 2019

Wayne,

The ballot appendix says: “The entire parameter value of the MUST be a valid Global Number as defined in RFC 3966 section 5.1.4, or it cannot be used. “

RFC 3966 defines “Global number” as a “thing” in section 5.1.4 , but I might have messed up the reference:

5.1.4.  Global Numbers

   Globally unique numbers are identified by the leading "+" character.

   Global numbers MUST be composed with the country (CC) and national

   (NSN) numbers as specified in E.123 [E.123] and E.164 [E.164].

   Globally unique numbers are unambiguous everywhere in the world and

   SHOULD be used.

Is the reference too weak or broken?  I suppose I can include a definition in the BRs for “Global Number” so there is no confusion.  

Doug

From: Wayne Thayer <wthayer at mozilla.com> 
Sent: Monday, April 15, 2019 4:18 PM
To: Doug Beattie <doug.beattie at globalsign.com>; CA/B Forum Server Certificate WG Public Discussion List <servercert-wg at cabforum.org>
Subject: Re: [Servercert-wg] Ballot SC18 version 2: Phone Contact with DNS CAA Phone Contact

Doug - I noticed what looks like a minor typo in the appendix: "The entire parameter value of the MUST be a valid Global Number..." Of the what?

Thanks,

Wayne

On Fri, Apr 12, 2019 at 12:07 PM Doug Beattie via Servercert-wg <servercert-wg at cabforum.org <mailto:servercert-wg at cabforum.org> > wrote:

Updates from last version: Added ADN to the acronym list in section 1.6.2

=============================

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 of the 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-12   15:30 Eastern

End Time: Not before 2018-04-19   15:30 Eastern

Vote for approval (7 days)

Start Time: TBD

End Time: TBD

_______________________________________________
Servercert-wg mailing list
Servercert-wg at cabforum.org <mailto:Servercert-wg at cabforum.org> 
http://cabforum.org/mailman/listinfo/servercert-wg

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