<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
h4
{mso-style-priority:9;
mso-style-link:"Heading 4 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.Heading4Char
{mso-style-name:"Heading 4 Char";
mso-style-priority:9;
mso-style-link:"Heading 4";
font-family:"Calibri Light",sans-serif;
color:#2E74B5;
mso-fareast-language:NO-BOK;
font-style:italic;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></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]-->
</head>
<body lang="NO-BOK" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Buypass votes YES.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Mads
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Servercert-wg <servercert-wg-bounces@cabforum.org>
<b>On Behalf Of </b>Wayne Thayer via Servercert-wg<br>
<b>Sent:</b> fredag 1. februar 2019 19:30<br>
<b>To:</b> CA/B Forum Server Certificate WG Public Discussion List <servercert-wg@cabforum.org><br>
<b>Subject:</b> [Servercert-wg] Voting Begins: Ballot SC7: Update IP Address Validation Methods CAB Forum x<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">Purpose of Ballot: </span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Ballot 169 removed Method 11 ("Any Other Method") from 3.2.2.4 and replaced it with explicit validation methods, but it's sibling in 3.2.2.5 item 4 is still in the Baseline Requirements.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">This ballot removes 3.2.2.5 item 4 and replaces it with an explicit list of IP validation methods.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">The intention is that, moving forward, IP validation methods will be handled in the same way as domain-name validation methods, and CAs that want to use new methods or variants of existing methods must bring them to
the Forum for scrutiny, first.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">The following motion has been proposed by Wayne Thayer of Mozilla and endorsed by Doug Beattie of GlobalSign and Tim Hollebeek of DigiCert.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">-- MOTION BEGINS -- </span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates” as follows, based on Version 1.6.2:</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<i><span style="font-size:11.0pt;color:black">Add the following to the table in section 1.2.2:</span></i><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Compliance: 2019-08-01; Section 3.2.2.5; Summary Description: CAs MUST follow revised validation requirements in section 3.2.2.5 and MUST keep a record of IP Address validation methods used.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<i><span style="font-size:11.0pt;color:black">Add the following definitions to section 1.6.1:</span></i><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">IP Address:</span></b><span style="font-size:11.0pt;color:black"> A 32-bit or 128-bit label assigned to a device that uses the Internet Protocol for communication.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">IP Address Contact:</span></b><span style="font-size:11.0pt;color:black"> The person(s) or entity(ies) registered with an IP Address Registration Authority as having the right to control how one or more IP Addresses
are used.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">IP Address Registration Authority:</span></b><span style="font-size:11.0pt;color:black"> The Internet Assigned Numbers Authority (IANA) or a Regional Internet Registry (RIPE, APNIC, ARIN, AfriNIC, LACNIC).</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<i><span style="font-size:11.0pt;color:black">Replace Baseline Requirements section 3.2.2.5, in its entirety, with the following text:</span></i><o:p></o:p></p>
<h4 style="mso-margin-top-alt:12.0pt;margin-right:0cm;margin-bottom:2.0pt;margin-left:0cm">
<span style="color:black">3.2.2.5. Authentication for an IP Address</span><o:p></o:p></h4>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">This section defines the permitted processes and procedures for validating the Applicant’s ownership or control of an IP Address listed in a Certificate.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">The CA SHALL confirm that prior to issuance, the CA has validated each IP Address listed in the Certificate using at least one of the methods specified in this section.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Completed validations of Applicant authority may be valid for the issuance of multiple Certificates over time. In all cases, the validation must have been initiated within the time period specified in the relevant
requirement (such as Section 4.2.1 of this document) prior to Certificate issuance. For purposes of IP Address validation, the term Applicant includes the Applicant's Parent Company, Subsidiary Company, or Affiliate.
</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">After July 31, 2019, CAs SHALL maintain a record of which IP validation method, including the relevant BR version number, was used to validate every IP Address.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Note: IP Addresses verified in accordance with this section 3.2.5 may be listed in Subscriber Certificates as defined in section 7.1.4.2 or in Subordinate CA Certificates via iPAddress in permittedSubtrees within the
Name Constraints extension. CAs are not required to verify IP Addresses listed in Subordinate CA Certificates via iPAddress in excludedSubtrees in the Name Constraints extension prior to inclusion in the Subordinate CA Certificate.
</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">3.2.2.5.1. Agreed-Upon Change to Website</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Confirming the Applicant's control over the requested IP Address by confirming the presence of a Request Token or Random Value contained in the content of a file or webpage in the form of a meta tag under the "/.well-known/pki-validation"
directory, or another path registered with IANA for the purpose of validating control of IP Addresses, on the IP Address that is accessible by the CA via HTTP/HTTPS over an Authorized Port. The Request Token or Random Value MUST NOT appear in the request.
</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">If a Random Value is used, the CA SHALL provide a Random Value unique to the certificate request and SHALL not use the Random Value after the longer of (i) 30 days or (ii) if the Applicant submitted the certificate
request, the timeframe permitted for reuse of validated information relevant to the certificate (such as in Section 4.2.1 of this document).
</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">3.2.2.5.2. Email, Fax, SMS, or Postal Mail to IP Address Contact</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Confirming the Applicant's control over the IP Address by sending a Random Value via email, fax, SMS, or postal mail and then receiving a confirming response utilizing the Random Value. The Random Value MUST be sent
to an email address, fax/SMS number, or postal mail address identified as an IP Address Contact.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Each email, fax, SMS, or postal mail MAY confirm control of multiple IP Addresses.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">The CA MAY send the email, fax, SMS, or postal mail identified under this section to more than one recipient provided that every recipient is identified by the IP Address Registration Authority as representing the
IP Address Contact for every IP Address being verified using the email, fax, SMS, or postal mail.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">The Random Value SHALL be unique in each email, fax, SMS, or postal mail.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">The CA MAY resend the email, fax, SMS, or postal mail in its entirety, including re-use of the Random Value, provided that the communication's entire contents and recipient(s) remain unchanged.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">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, in which case the CA MUST follow its
CPS.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">3.2.2.5.3. Reverse Address Lookup</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Confirming the Applicant’s control over the IP Address by obtaining a Domain Name associated with the IP Address through a reverse-IP lookup on the IP Address and then verifying control over the FQDN using a method
permitted under BR Section 3.2.2.4.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">3.2.2.5.4. Any Other Method</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Using any other method of confirmation, including variations of the methods defined in BR Section 3.2.2.5, provided that the CA maintains documented evidence that the method of confirmation establishes that the Applicant
has control over the IP Address to at least the same level of assurance as the methods previously described in version 1.6.2 of these Requirements.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">CAs SHALL NOT perform validations using this method after July 31, 2019. Completed validations using this method SHALL NOT be re-used for certificate issuance after July 31, 2019. Any certificate issued prior to August
1, 2019 containing an IP Address that was validated using any method that was permitted under the prior version of this section 3.2.2.5 MAY continue to be used without revalidation until such certificate naturally expires.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">3.2.2.5.5. Phone Contact with IP Address Contact</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Confirming the Applicant's control over the IP Address by calling the IP Address Contact’s phone number and obtaining a response confirming the Applicant's request for validation of the IP Address. The CA MUST place
the call to a phone number identified by the IP Address Registration Authority as the IP Address Contact. Each phone call SHALL be made to a single number.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:black">In the event that someone other than an IP Address Contact is reached, the CA MAY request to be transferred to the IP Address Contact.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:black">In the event of reaching voicemail, the CA may leave the Random Value and the IP Address(es) being validated. The Random Value MUST be returned to the CA to approve the
request.</span><o:p></o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:black">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. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><b><span style="font-size:11.0pt;color:black">3.2.2.5.6 ACME “http-01” method for IP Addresses</span></b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:black">Confirming the Applicant's control over the IP Address by performing the procedure documented for an “http-01” challenge in draft 04 of “ACME IP Identifier Validation Extension,”
available at </span><a href="https://tools.ietf.org/html/draft-ietf-acme-ip-04#section-4" target="_blank"><span style="font-size:11.0pt;color:#1155CC">https://tools.ietf.org/html/draft-ietf-acme-ip-04#section-4</span></a><span style="font-size:11.0pt;color:black">.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><b><span style="font-size:11.0pt;color:black">3.2.2.5.7 ACME “tls-alpn-01” method for IP Addresses</span></b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm;margin-bottom:.0001pt"><span style="font-size:11.0pt;color:black">Confirming the Applicant's control over the IP Address by performing the procedure documented for a “tls-alpn-01” challenge in draft 04 of “ACME IP Identifier Validation
Extension,” available at </span><a href="https://tools.ietf.org/html/draft-ietf-acme-ip-04#section-4" target="_blank"><span style="font-size:11.0pt;color:#1155CC">https://tools.ietf.org/html/draft-ietf-acme-ip-04#section-4</span></a><span style="font-size:11.0pt;color:black">.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<b><span style="font-size:11.0pt;color:black">-- MOTION ENDS --</span></b><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">*** WARNING ***: USE AT YOUR OWN RISK. THE REDLINE BELOW IS NOT THE OFFICIAL VERSION OF THE CHANGES (CABF Bylaws, Section 2.4(a)):</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">A comparison of the changes can be found at:</span><a href="https://github.com/dougbeattie/documents/compare/master...dougbeattie:SC14---Phone-validation-updates" target="_blank"><span style="font-size:11.0pt;color:black;text-decoration:none">https://github.com/wthayer/documents/compare/wthayer:master...Ballot-SC7</span></a><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">The procedure for approval of this ballot is as follows:</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Discussion (7+ days)</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Start Time: 2019-01-24 01:00 UTC</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">End Time: Not before 2019-01-31 01:00 UTC</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Vote for approval (7 days)</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">Start Time: 2019-02-01 19:00 UTC</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:8.0pt;margin-left:0cm">
<span style="font-size:11.0pt;color:black">End Time: 2019-02-08 19:00 UTC</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>