Chunghwa Telecom votes "yes" to ballot SC13 version 5.
Li-Chun Chen
On 18/12/2018 1:55 π.μ., Tim Hollebeek via Public wrote:
Ballot SC13: CAA Contact Property and Associated E-mail Validation Methods
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 the following definitions to section 1.6.1:
DNS CAA Email Contact: The email address defined in section B.1.2.
DNS TXT Record Email Contact: The email address defined in section B.2.2.
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 a DNS CAA Email Contact. 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).
Each email MAY confirm control of multiple FQDNs, provided that each email
address is a DNS CAA Email Contact for each Authorization Domain Name being
validated. The same email MAY be sent to multiple recipients as long as all
recipients are DNS CAA Email Contacts for each Authorization Domain Name 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(s) 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 Section 3.2.2.4.14: Email to DNS TXT 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 a DNS TXT Record Email Contact for the
Authorization Domain Name selected to validate the FQDN.
Each email MAY confirm control of multiple FQDNs, provided that each email
address is DNS TXT Record Email Contact for each Authorization Domain Name
being validated. The same email MAY be sent to multiple recipients as long as
all recipients are DNS TXT Record Email Contacts for each Authorization Domain
Name 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(s) 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
These methods allow domain owners to publish contact information in DNS for the
purpose of validating domain control.
B.1. CAA Methods
B.1.1. CAA contactemail Property
SYNTAX: contactemail <rfc6532emailaddress>
The CAA contactemail property takes an email address as its parameter. The
entire parameter value 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 contactemail "[email protected]"
The contactemail property MAY be critical, if the domain owner does not want
CAs who do not understand it to issue certificates for the domain.
B.2. DNS TXT Methods
B.2.1. DNS TXT Record Email Contact
The DNS TXT record MUST be placed on the "_validation-contactemail" subdomain
of the domain being validated. The entire RDATA value of this TXT record 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.
--- 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 changes between version 5 and version 4 are here:
https://github.com/cabforum/documents/commit/92dd4a3a9afa38e9abf6765eb19e27508663ae61
The procedure for approval of this ballot is as follows:
Discussion (7+ days)
Start Time: 2018-12-10 17:30 Eastern
End Time: Not before 2018-12-17 17:30 Eastern
Vote for approval (7 days)
Start Time: 2018-12-17 19:00 Eastern
End Time: 2018-12-24 19:00 Eastern
_______________________________________________
Public mailing list
[email protected]
https://cabforum.org/mailman/listinfo/public
本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件.
如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任.
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.
_______________________________________________
Public mailing list
[email protected]
https://cabforum.org/mailman/listinfo/public
