[Servercert-wg] [EXTERNAL] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

[Bruce Morton]

Entrust votes Yes to ballot SC-74.


Bruce.

From: Servercert-wg <servercert-wg-bounces at cabforum.org> On Behalf Of Dimitris Zacharopoulos (HARICA) via Servercert-wg
Sent: Sunday, May 5, 2024 4:24 AM
To: CA/B Forum Server Certificate WG Public Discussion List <servercert-wg at cabforum.org>
Subject: [EXTERNAL] [Servercert-wg] [Voting Begins] Ballot SC-74 - Clarify CP/CPS structure according to RFC 3647

Voting begins for ballot SC-74. SC-74 - Clarify CP/CPS structure according to RFC 3647 Summary The TLS Baseline Requirements require in section 2. 2 that: "The Certificate Policy and/or Certification Practice Statement MUST be structured in

Voting begins for ballot SC-74.

SC-74 - Clarify CP/CPS structure according to RFC 3647
Summary

The TLS Baseline Requirements require in section 2.2 that:

"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."

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 SCWG Public Mailing List<https://urldefense.com/v3/__https:/lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html__;!!FJ-Y8qCqXTj2!cKscdErif35z9080I4qUNWiEBkbcvZAU-O348aNPTbBukz2D3MHzp0nkdYntRGQwKmkvU9BasOrNQkRehWXosH6umUupfg$> 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.

The following motion has been proposed by Dimitris Zacharopoulos (HARICA) and endorsed by Aaron Poulsen (Amazon) and Tim Hollebeek (Digicert).

You can view the github pull request representing this ballot here<https://urldefense.com/v3/__https:/github.com/cabforum/servercert/pull/503__;!!FJ-Y8qCqXTj2!cKscdErif35z9080I4qUNWiEBkbcvZAU-O348aNPTbBukz2D3MHzp0nkdYntRGQwKmkvU9BasOrNQkRehWXosH41qyhIwg$>.

Motion Begins

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:

  *   https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae<https://urldefense.com/v3/__https:/github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae__;!!FJ-Y8qCqXTj2!cKscdErif35z9080I4qUNWiEBkbcvZAU-O348aNPTbBukz2D3MHzp0nkdYntRGQwKmkvU9BasOrNQkRehWXosH5EAlr0SA$>

Motion Ends

This ballot proposes a Final Maintenance Guideline. The procedure for approval of this ballot is as follows:

Discussion (at least 7 days)

  *   Start time: 2024-04-25 16:30:00 UTC
  *   End time: on or after 2024-05-02 16:30:00 UTC

Vote for approval (7 days)

  *   Start time: 2024-05-05 8:30:00 UTC
  *   End time: 2024-05-12 8:30:00 UTC

Any email and files/attachments transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/servercert-wg/attachments/20240506/ef0e2e43/attachment-0001.html>