<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Calibri">Actalis "abstains" on this ballot.</font><br>
</p>
<br>
<div class="moz-cite-prefix">Il 19/07/2018 17:02, Tim Hollebeek via
Public ha scritto:<br>
</div>
<blockquote type="cite"
cite="mid:BN6PR14MB11061CC8A6A9605A99B2151E83520@BN6PR14MB1106.namprd14.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:62683804;
mso-list-type:hybrid;
mso-list-template-ids:-1495097140 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Administrivia:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph"
style="margin-left:0in;mso-list:l0 level1 lfo1">This ballot
is being cross-posted to the CABF public mailing in line
with the consensus from last Thursday’s call that it is
important everyone is aware of the ballot, and that not
everyone is on the SCWG list yet.<o:p></o:p></li>
<li class="MsoListParagraph"
style="margin-left:0in;mso-list:l0 level1 lfo1">I promised
an IETF independent stream draft for the same proposal, so
it can get feedback from those at IETF. I still intend to
do so, but I am working with a colleague on setting up a
github account for DigiCert IETF efforts to make it easier
for others to collaborate with us on IETF submissions. I
anticipate we will have that set up and the draft submitted
some time next week. The IETF draft will allow IETF to
review the method and make suggested improvements. It
should not block adoption of the current proposal by CABF.
DigiCert intends to submit a ballot to adopt IETF’s
improvements once the IETF process is complete.<o:p></o:p></li>
</ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ballot SC2: CAA Contact Property and
Associated Validation Methods<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The following motion has been proposed by
Tim Hollebeek of DigiCert and endorsed by Bruce Morton of
Entrust and Doug Beattie of GlobalSign.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">--- MOTION BEGINS ---<o:p></o:p></p>
<p class="MsoNormal">This ballot modifies the “Baseline
Requirements for the Issuance and Management of
Publicly-Trusted Certificates” as follows, based on Version
1.5.7:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Add Section 3.2.2.4.13: Domain Owner Email
published in DNS<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Confirm the Applicant's control over the
FQDN by (i) sending an email to a DNS domain name holder, (ii)
including a Random Value in the email, and (iii) receiving a
confirming response utilizing the Random Value. The CA MUST
send the email to an email address found in the CAA Contact
property record as defined in Appendix B.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Each email MAY confirm control of multiple
FQDNs, provided the email address used is a DNS contact email
address for each FQDN being confirmed. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Add Section 3.2.2.4.14: Domain Owner Phone
published in DNS<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Confirm the Applicant's control over the
FQDN by calling the DNS domain name holder phone number and
obtaining a response confirming the Applicant's request for
validation of the FQDN. The CA MUST place the call to a phone
number identified in the CAA Contact property record as
defined in Appendix B.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Each phone call SHALL be made to a single
number and MAY confirm control of multiple FQDNs, provided
that the phone number is identified by the DNS contact as a
valid contact method for every Base Domain Name being verified
using the phone call.<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Add Section 3.2.2.4.15: Domain Owner Email
published in TXT record<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Confirm the Applicant's control over the
FQDN by (i) sending an email to a DNS domain name holder, (ii)
including a Random Value in the email, and (iii) receiving a
confirming response utilizing the Random Value. The CA MUST
send the email to an email address found in the DNS TXT record
as defined in Appendix B.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Each email MAY confirm control of multiple
FQDNs, provided the email address used is a DNS contact email
address for each FQDN being confirmed. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">##### 3.2.2.4.16 Domain Owner Phone
published in TXT record<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Confirm the Applicant's control over the
FQDN by calling the DNS domain name holder phone number and
obtaining a response confirming the Applicant's request for
validation of the FQDN. The CA MUST place the call to a phone
number identified in the DNS TXT record defined in Appendix B.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Each phone call SHALL be made to a single
number and MAY confirm control of multiple FQDNs, provided
that the phone number is identified by the DNS contact as a
valid contact method for every Base Domain Name being verified
using the phone call.<o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Add Appendix B: CAA Contact Tag<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The syntax for the contact property is
similar to the iodef property. It allows domain owners to
publish contact information in DNS in addition to WHOIS for
the purpose of validating domain control.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">CAA contact Property<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">contact <URL> : The contact property
entry specifies the authorized means of contacting the holder
of the domain or another party who is authorized to approve
issuance of certificates for the domain.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The contact property specifies a means of
contacting the domain holder, or another party that is
authorized to approve issuance of certificates for the domain
in question.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The contact property takes a URL as its
parameter. The following URL scheme types SHOULD be
implemented:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">mailto: An SMTP email address where the
domain holder or other authorized party can be contacted.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">tel: A telephone number where the domain
holder or other authorized party can be contacted.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Schemes other than "mailto:" or "tel:" MUST
NOT be used. Telephone numbers MUST include the country code
and be global phone numbers as defined by RFC 3966.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The following is an example where the
holder of the domain specified the contact property using both
an email address and a phone number.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">$ORIGIN example.com<o:p></o:p></p>
<p class="MsoNormal">. CAA 0 issue “ca.example.net”<o:p></o:p></p>
<p class="MsoNormal">. CAA 0 contact
“<a class="moz-txt-link-freetext" href="mailto:domainowner@example.com”">mailto:domainowner@example.com”</a><o:p></o:p></p>
<p class="MsoNormal">. CAA 0 contact
“<a class="moz-txt-link-freetext" href="tel:+1-310-555-1212”">tel:+1-310-555-1212”</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">## Support for Legacy Systems<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Some systems still do not have sufficient
support for CAA records. To allow users of those systems to
specify contact information, a legacy format using text
records is allowed. The CAA contact property SHOULD be used
instead of TXT records, where feasible.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The DNS TXT record MUST be placed on the
"_caa_contact" subdomain of the domain being validated. The
DNS record MUST be named "domain-authorization-email" or
"domain-authorization-phone". The value of
"domain-authorization-email" MUST contain a valid email
address, or it cannot be used. The value of
"domain-authorization-phone" must be a global phone number,
including country code, as defined in RFC 3966 or it cannot be
used. <o:p></o:p></p>
<p class="MsoNormal">--- MOTION ENDS ---<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">A comparison of the changes can be found
at: <a
href="https://github.com/cabforum/documents/compare/SC2-CAA-Contact?expand=1"
moz-do-not-send="true">https://github.com/cabforum/documents/compare/SC2-CAA-Contact?expand=1</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The procedure for approval of this ballot
is as follows:<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Discussion (7+ days)<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Start Time: 2018-07-11 10:30am EST<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">End Time: 2018-07-19 11:00am EST<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Vote for approval (7 days)<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Start Time: 2018-07-19 11:00am EST<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">End Time: 2018-07-26 11:00am EST<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Public mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Public@cabforum.org">Public@cabforum.org</a>
<a class="moz-txt-link-freetext" href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a>
</pre>
</blockquote>
<br>
</body>
</html>