<div dir="ltr">Let's Encrypt / ISRG votes Yes on Ballot SC-074.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 5, 2024 at 1:24 AM Dimitris Zacharopoulos (HARICA) via Servercert-wg <<a href="mailto:servercert-wg@cabforum.org">servercert-wg@cabforum.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><u></u>
<div>
Voting begins for ballot SC-74.<br>
<h1 id="m_1127590669766888415bkmrk-page-title">SC-74 - Clarify CP/CPS
structure according to RFC 3647</h1>
<h2 id="m_1127590669766888415bkmrk-summary">Summary</h2>
<p id="m_1127590669766888415bkmrk-the-tls-baseline-req">The TLS Baseline Requirements
require in section 2.2 that:</p>
<p id="m_1127590669766888415bkmrk-%22the-certificate-pol"><em>"The Certificate Policy
and/or Certification Practice Statement MUST be structured in
accordance with RFC 3647 and MUST include all material required
by RFC 3647."</em></p>
<p id="m_1127590669766888415bkmrk-the-intent-of-this-l">The intent of this language was
to ensure that all CAs' CP and/or CPS documents contain a similar
structure, making it easier to review and compare against the BRs.
However, there was some ambiguity as to the actual structure that
CAs should follow. After several discussions in the <a href="https://lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html" target="_blank">SCWG Public Mailing List</a> and F2F
meetings, it was agreed that more clarity should be added to the
existing requirement, pointing to the outline described in section
6 of RFC 3647.</p>
<p id="m_1127590669766888415bkmrk-the-following-motion">The following motion has been
proposed by Dimitris Zacharopoulos (HARICA) and endorsed by Aaron
Poulsen (Amazon) and Tim Hollebeek (Digicert). <br>
</p>
<p id="m_1127590669766888415bkmrk-you-can-view-and-com">You can view the github pull
request representing this ballot <a href="https://github.com/cabforum/servercert/pull/503" target="_blank">here</a>. <br>
</p>
<h2 id="m_1127590669766888415bkmrk-motion-begins">Motion Begins</h2>
<p id="m_1127590669766888415bkmrk-modify-the-%22baseline">MODIFY the "Baseline
Requirements for the Issuance and Management of Publicly-Trusted
TLS Server Certificates" based on Version 2.0.4 as specified in
the following redline:<br>
</p>
<ul id="m_1127590669766888415bkmrk-https%3A%2F%2Fgithub.com%2Fc">
<li><a href="https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae" target="_blank">https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae</a>
<br>
</li>
</ul>
<h2 id="m_1127590669766888415bkmrk-motion-ends">Motion Ends</h2>
<p id="m_1127590669766888415bkmrk-this-ballot-proposes">This ballot proposes a Final
Maintenance Guideline. The procedure for approval of this ballot
is as follows:</p>
<h4 id="m_1127590669766888415bkmrk-discussion-%2811%2B-days">Discussion (at least 7 days)</h4>
<ul id="m_1127590669766888415bkmrk-start-time%3A-2024-01-">
<li>Start time: 2024-04-25 16:30:00 UTC</li>
<li>End time: on or after 2024-05-02 16:30:00 UTC</li>
</ul>
<h4 id="m_1127590669766888415bkmrk-vote-for-approval-%287">Vote for approval (7 days)</h4>
<ul id="m_1127590669766888415bkmrk-start-time%3A-tbd-end-">
<li>Start time: 2024-05-05 8:30:00 UTC</li>
<li>End time: 2024-05-12 8:30:00 UTC</li>
</ul>
<br>
</div>
_______________________________________________<br>
Servercert-wg mailing list<br>
<a href="mailto:Servercert-wg@cabforum.org" target="_blank">Servercert-wg@cabforum.org</a><br>
<a href="https://lists.cabforum.org/mailman/listinfo/servercert-wg" rel="noreferrer" target="_blank">https://lists.cabforum.org/mailman/listinfo/servercert-wg</a><br>
</blockquote></div>