[Servercert-wg] [EXTERNAL]Re: [cabf_validation] Underscores, DNSNames, and SRVNames

[Bruce Morton]

Hi Wayne,

We support the deprecation of underscore certificates. In fact, our plan will be to revoke all underscore certificates with more than 30 days validity on the proposed date of 15 January 2019 and discontinue issuance of underscore certificates on the same date.

However, we do feel that the schedule is very aggressive to allow CAs to ban the use of underscores, communication with Subscribers and allow Subscribers time to change domain names or policies to allow wildcard certificates. Further, we feel that the 30 day certificate will not be useful to our Subscribers and do not plan to implement this requirement.

We would request that the date of 15 January 2019 be moved out to 31 March 2019. This will allow for better response to the requirement of deprecating underscore certificates and still meet your full implementation deadline of 30 April 2019.

Thanks, Bruce.

From: Servercert-wg [mailto:servercert-wg-bounces at cabforum.org] On Behalf Of Wayne Thayer via Servercert-wg
Sent: October 25, 2018 4:50 PM
To: Doug Beattie <doug.beattie at globalsign.com>
Cc: CA/B Forum Server Certificate WG Public Discussion List <servercert-wg at cabforum.org>
Subject: [EXTERNAL]Re: [Servercert-wg] [cabf_validation] Underscores, DNSNames, and SRVNames

WARNING: This email originated outside of Entrust Datacard.
DO NOT CLICK links or attachments unless you trust the sender and know the content is safe.
________________________________
Here is an updated draft ballot that reflects discussion on the list and this morning's call.

It was pointed out that - even if the discussion period starts today and is kept to 7 days - this ballot won't become effective until roughly 8-December, and of course there are concerns with mandating revocations during holiday change freezes, so I moved the revocation date from 1-December to 15-January.

I also fixed the logic forbidding underscores when a wildcard can be used.

I'm still looking for two endorsers.

- Wayne

Ballot SC## - Sunset of Underscores in DNSNames

Purpose of Ballot

Ballot 202 included a provision creating a permanent exception permitting the underscore character to be used in SAN fields of type DNSName. Since that ballot failed in 2017, the practice has continued despite being non-compliant with RFC 5280. This ballot creates a brief sunset period intended to allow Subscribers who are relying on FQDNs containing underscores to transition away from them, either by changing the name or deploying a wildcard certificate.

The following motion has been proposed by Wayne Thayer of Mozilla and endorsed by xxx of yyy and xxx of yyy.

--- MOTION BEGINS ---
Add the following language to BR section 7.1.4.2.1 (Subject Alternative Name Extension):

Prior to April 1, 2019, certificates containing underscore characters (“_”) in domain labels in DNSName entries MAY be issued as follows:
* DNSName entries MAY include underscore characters such that replacing all underscore characters with hyphen characters (“-“) would result in a valid domain label, and;
* Underscore characters MUST NOT be placed in the left most domain label, and;
* Such certificates MUST NOT be valid for longer than 30 days.

All certificates containing an underscore character in any DNSName entry and having a validity period of more than 30 days MUST be revoked prior to January 15, 2019.

After April 30, 2019, underscore characters (“_”) MUST NOT be present in DNSName entries.

--- MOTION ENDS ---

This ballot proposes a Final Maintenance Guideline. A comparison of the changes can be found at: <TBD>


The procedure for approval of this ballot is as follows:

Discussion (7-21 days)
Start Time: 2018-10-xx, 7:00 am Eastern Time
End Time: Not before 2018-11-xx, 7:00 am Eastern Time

Vote for approval (7 days)
Start Time: 2018-xx-xx, 7:00 am Eastern Time
End Time: 2018-xx-xx, 7:00 am Eastern Time
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20181026/bdf4cbcd/attachment-0001.html>