DigiCert votes NO on Ballot SC-74.
The ballot is insufficiently clear about whether punctuation, capitalization, etc have to match exactly, and RFC 3647, which is Informative and was never intended to be used this way, is inconsistent itself in its use of capitalization and punctuation. There needs to be additional clarity about exactly what the requirements are if we want to do this. -Tim From: Servercert-wg <servercert-wg-boun...@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@cabforum.org> Subject: [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 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://url.avanan.click/v2/___https:/lists.cabforum.org/pipermail/servercert-wg/2023-November/004070.html___.YXAzOmRpZ2ljZXJ0OmE6bzozYzI2MWQxMjUxYTQyZjkzZjc5ZTc2YWM0MDc3NmJhNzo2OjBhNTk6YTQwZDgwNmE5Y2VkY2QwMTc1MTQyYTk2MTIyNTVmODBhNTM0YzIzOTI3MzE2ZDgwMDg3ZmVhMTAyMjcxZGQ2ODpoOkY> 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://url.avanan.click/v2/___https:/github.com/cabforum/servercert/pull/503___.YXAzOmRpZ2ljZXJ0OmE6bzozYzI2MWQxMjUxYTQyZjkzZjc5ZTc2YWM0MDc3NmJhNzo2OmRmMzM6MDJlYjIwNGZmZjg3NjExOWMzM2IyODU3MjM3NGNjMWU0ZjBhYzExOTRhZmZmZjE5ZjY0OTZmNmU0YTljNmIyYjpoOkY> . 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://url.avanan.click/v2/___https://github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae___.YXAzOmRpZ2ljZXJ0OmE6bzozYzI2MWQxMjUxYTQyZjkzZjc5ZTc2YWM0MDc3NmJhNzo2OmIzOTE6ZDUwNjAwMjUzNmFmM2Y4YzAwNTc2NmVjODkwNWRkYjM4YWY5ODE3NmMzYWI5OTBmOTJkNGZmOWJmODc1MDA4NTp0OkY <https://url.avanan.click/v2/___https:/github.com/cabforum/servercert/compare/c4a34fe2292022e0a04ba66b5a85df75907ac2a2...f6a90e2a652fbb7a2d62a976b70f4af3adce8dae___.YXAzOmRpZ2ljZXJ0OmE6bzozYzI2MWQxMjUxYTQyZjkzZjc5ZTc2YWM0MDc3NmJhNzo2OjQzY2I6YjYyNzliYTI4Y2FlZWVmNjMyYjg3ZGRkZDVlMDg5NjNjZmY2ZjBlZjA0YzE5ZGM0NDllNmQxNGJlYTI0MDIzNzpoOkY> 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
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Servercert-wg mailing list Servercert-wg@cabforum.org https://lists.cabforum.org/mailman/listinfo/servercert-wg
