<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
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;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
span.ui-provider
{mso-style-name:ui-provider;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:11.0pt;}
@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:687680426;
mso-list-type:hybrid;
mso-list-template-ids:-441829298 -834221142 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Aptos",sans-serif;
mso-fareast-font-family:Aptos;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt'>Hi Chris,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>I was taking a closer look at the ballot and specifically this section on caching the remote node CAA checks:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span class=ui-provider>A CA MAY reuse corroborating evidence for CAA record quorum compliance for a maximum of 398 days. After issuing a Certificate to a domain, remote Network Perspectives MAY omit retrieving and processing CAA records for the same domain or its </span><strong><span style='font-family:"Aptos",sans-serif'>subdomains </span></strong><span class=ui-provider>in subsequent Certificate requests from the same Applicant for up to a maximum of 398 days.</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>I think understand the first sentence – if you do a full check on a FQDN (the value that you will put into the SAN field), then you only need to do the normal CAA check for that FQDN from the primary node for 398 days. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>I don’t understand the references to domain and subdomains in the second sentence. Can you explain how this should work?<o:p></o:p></span></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'><span style='font-size:11.0pt'>You do a full MIC check on <a href="http://www.example.com">www.example.com</a> on day 1<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'><span style='font-size:11.0pt'>You find CAA records with permission to issue on example.com on primary and remote nodes so you issue<o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'><span style='font-size:11.0pt'>Day 100, customer wants to issue to shop.example.com<o:p></o:p></span></li><ul style='margin-top:0in' type=circle><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level2 lfo1'><span style='font-size:11.0pt'>This is a subdomain of example.com where we found the records permitting issuance on day 1. <o:p></o:p></span></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level2 lfo1'><span style='font-size:11.0pt'>What checks do we need to do for this request?<o:p></o:p></span></li></ul><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'><span style='font-size:11.0pt'>Day 150, Applicant wants to issue to x1.www.example.com (a subdomain of <a href="http://www.example.com">www.example.com</a> we issued on day 1):<o:p></o:p></span></li><ul style='margin-top:0in' type=circle><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level2 lfo1'><span style='font-size:11.0pt'>What checks would be required here?<o:p></o:p></span></li></ul></ul><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Maybe I’m reading too much into this…<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Thanks!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Doug<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Servercert-wg <servercert-wg-bounces@cabforum.org> <b>On Behalf Of </b>Chris Clements via Servercert-wg<br><b>Sent:</b> Friday, April 26, 2024 1:01 PM<br><b>To:</b> CA/B Forum Server Certificate WG Public Discussion List <servercert-wg@cabforum.org><br><b>Subject:</b> [Servercert-wg] Discussion Period Begins - Ballot SC-067 V2: "Require domain validation and CAA checks to be performed from multiple Network Perspectives"<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Purpose of Ballot SC-067 V2</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>This Ballot proposes updates to the <i>Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates</i> (i.e., TLS BRs) related to “Multi-Perspective Issuance Corroboration” (“MPIC”).</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Background</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- MPIC refers to performing domain validation and CAA checks from multiple Network Perspectives before certificate issuance, as described within the Ballot for the applicable validation methods in TLS BR Sections 3.2.2.4 and 3.2.2.5.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Not all methods described in TLS BR Sections 3.2.2.4 and 3.2.2.5 will require using MPIC.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- This work was most recently motivated by research presented at Face-to-Face 58 [1] by Princeton University, but has been discussed for years prior as well.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- The goal of this proposal is to make it more difficult for adversaries to successfully launch equally-specific prefix attacks against the domain validation processes described in the TLS BRs.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Additional background information can be found in an update shared at Face-to-Face 60 [2].</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Benefits of Adoption</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Recent publicly-documented attacks have used BGP hijacks to fool domain control validation and obtain malicious certificates, which led to the impersonation of HTTPS websites [3][</span><span style='font-family:"Arial",sans-serif;color:black'>4</span><span style='font-family:"Arial",sans-serif;color:#0E101A'>].</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Routing security defenses (e.g., RPKI) can mitigate the risk of global BGP attacks, but localized, equally-specific BGP attacks still pose a significant threat to the Web PKI [5][6].</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Corroborating domain control validation checks from multiple network perspectives (i.e., MPIC) spread across the Internet substantially reduces the threat posed by equally-specific BGP attacks, ensuring the integrity of domain validation and issuance decisions [5][7][8].</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Existing deployments of MPIC at the scale of millions of certificates a day demonstrate the feasibility of this technique at Internet scale [7][9].</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Intellectual Property (IP) Disclosure</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- While not a Server Certificate Working Group Member, researchers from Princeton University presented at Face-to-Face 58, provided academic expertise, and highlighted publicly-available peer-reviewed research to support Members in drafting this ballot.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- The Princeton University researchers indicate that they have not filed for any patents relating to their MPIC work and do not plan to do so in the future.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Princeton University has indicated that it is unable to agree to the CA/Browser Forum IPR agreement because it could encumber inventions invented by researchers not involved in the development of MPIC or with the CA/B Forum.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Princeton University has instead provided the attached IPR statement. Pursuant to the IPR statement, Princeton University has granted a worldwide royalty free license to the intellectual property in MPIC developed by the researchers and has made representations regarding its lack of knowledge of any other Princeton intellectual property needed to implement MPIC.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- The attached IPR statement has not changed since disclosed in Discussion Round 1.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:black'>- For clarity, Princeton University’s IPR statement is NOT intended to replace the Forum’s IPR agreement or allow Princeton to participate in the Forum in any capacity.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:black'>- Members seeking legal advice regarding this ballot should consult their own counsel.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Proposal Revision History</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Pre-Ballot Release #1 (work team artifacts and broader Validation Subcommittee collaboration) [10]</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>- Pre-Ballot Release #2 [11]</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>Previous versions of this Ballot</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> -</span><span style='font-family:"Arial",sans-serif;color:#0E101A'> Ballot Release #1 [12] (comparing Version 2 to Version 1) [13]. Note, some of the changes represented in the comparison are updates made by other ballots that have since passed (e.g., SC-069).</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:#0E101A'>References</span></b><span style='font-family:"Arial",sans-serif;color:#0E101A'>:</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[1] </span><a href="https://cabforum.org/wp-content/uploads/13-CAB-Forum-face-to-face-multiple-vantage-points.pdf"><span style='font-family:"Arial",sans-serif'>https://cabforum.org/wp-content/uploads/13-CAB-Forum-face-to-face-multiple-vantage-points.pdf</span></a><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[2] </span><a href="https://drive.google.com/file/d/1LTwtAwHXcSaPVSsqKQztNJrV2ozHJ7ZL/view?usp=drive_link"><span style='font-family:"Arial",sans-serif'>https://drive.google.com/file/d/1LTwtAwHXcSaPVSsqKQztNJrV2ozHJ7ZL/view?usp=drive_link</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[3] </span><a href="https://medium.com/s2wblog/post-mortem-of-klayswap-incident-through-bgp-hijacking-en-3ed7e33de600"><span style='font-family:"Arial",sans-serif'>https://medium.com/s2wblog/post-mortem-of-klayswap-incident-through-bgp-hijacking-en-3ed7e33de600</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[4] </span><a href="https://www.coinbase.com/blog/celer-bridge-incident-analysis"><span style='font-family:"Arial",sans-serif'>https://www.coinbase.com/blog/celer-bridge-incident-analysis</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[5] </span><a href="https://www.usenix.org/conference/usenixsecurity23/presentation/cimaszewski"><span style='font-family:"Arial",sans-serif'>https://www.usenix.org/conference/usenixsecurity23/presentation/cimaszewski</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[6] </span><a href="https://www.blackhat.com/docs/us-15/materials/us-15-Gavrichenkov-Breaking-HTTPS-With-BGP-Hijacking-wp.pdf"><span style='font-family:"Arial",sans-serif'>https://www.blackhat.com/docs/us-15/materials/us-15-Gavrichenkov-Breaking-HTTPS-With-BGP-Hijacking-wp.pdf</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[7] </span><a href="https://www.usenix.org/conference/usenixsecurity21/presentation/birge-lee"><span style='font-family:"Arial",sans-serif'>https://www.usenix.org/conference/usenixsecurity21/presentation/birge-lee</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[8] </span><a href="https://www.usenix.org/conference/usenixsecurity18/presentation/birge-lee"><span style='font-family:"Arial",sans-serif'>https://www.usenix.org/conference/usenixsecurity18/presentation/birge-lee</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[9] </span><a href="https://security.googleblog.com/2023/05/google-trust-services-acme-api_0503894189.html"><span style='font-family:"Arial",sans-serif'>https://security.googleblog.com/2023/05/google-trust-services-acme-api_0503894189.html</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[10] </span><a href="https://github.com/ryancdickson/staging/pull/6"><span style='font-family:"Arial",sans-serif'>https://github.com/ryancdickson/staging/pull/6</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[11] </span><a href="https://github.com/ryancdickson/staging/pull/8"><span style='font-family:"Arial",sans-serif'>https://github.com/ryancdickson/staging/pull/8</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[12] </span><a href="https://github.com/cabforum/servercert/pull/487"><span style='font-family:"Arial",sans-serif'>https://github.com/cabforum/servercert/pull/487</span></a><span style='font-family:"Arial",sans-serif;color:#0E101A'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>[13] </span><a href="https://github.com/cabforum/servercert/compare/6d10abda8980c6eb941987d3fc26e753e62858c0..5224983ef0a6f94c18808ea3469e7a5ae35746e5"><span style='font-family:"Arial",sans-serif'>https://github.com/cabforum/servercert/compare/6d10abda8980c6eb941987d3fc26e753e62858c0..5224983ef0a6f94c18808ea3469e7a5ae35746e5</span></a><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#0E101A'>The following motion has been proposed by Chris Clements and Ryan Dickson of Google (Chrome Root Program) and endorsed by Aaron Gable (ISRG / Let’s Encrypt) and Wayne Thayer (Fastly). </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:black'>— Motion Begins —</span></b><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:black'>This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates” (“Baseline Requirements”), based on Version 2.0.4.</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:black'>MODIFY the Baseline Requirements as specified in the following Redline:</span><o:p></o:p></p><p style='margin:0in'><a href="https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2..5224983ef0a6f94c18808ea3469e7a5ae35746e5"><span style='font-family:"Arial",sans-serif'>https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2..5224983ef0a6f94c18808ea3469e7a5ae35746e5</span></a><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:black'>— Motion Ends —</span></b><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:black'>This ballot proposes a Final Maintenance Guideline. The procedure for approval of this ballot is as follows:</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:black'>Discussion (at least 14 days)</span></b><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:black'>- Start: 2024-04-26 17:00:00 UTC</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:black'>- End no earlier than: 2024-05-10 17:00:00 UTC</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:#500050'> </span><o:p></o:p></p><p style='margin:0in'><b><span style='font-family:"Arial",sans-serif;color:black'>Vote for approval (7 days)</span></b><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:black'>- Start: TBD</span><o:p></o:p></p><p style='margin:0in'><span style='font-family:"Arial",sans-serif;color:black'>- End: TBD</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>