[Cscwg-public] Voting period begins: Ballot CSC-14 - Convert Code Signing Baseline Requirements to RFC 3647 Framework

[Corey Bonnell]

Hi Inigo,

Thanks for raising the formatting issue to the group’s attention.



I checked the Bylaws and section 2.4 (8) says:



“The set of changes are limited to:

* The cover page,

* The Table of Contents,

* The year in the “Copyright” information,

* Footers with page numbers



The Chair or Vice-Chair of a CWG is also allowed to perform the following

changes, unless the ballot explicitly updates this information:

* The Guideline version number,

* Headers/Footers with version numbers,

* The table with document revisions or Document History,

* The table with Relevant Dates.”



Given this, we will be unable to fix the formatting issue without a separate
ballot. That being said, the formatting issue doesn’t materially impact the
content of the document, so we will still be voting “Yes” to this ballot.



Thanks,

Corey



From: Inigo Barreira <Inigo.Barreira at sectigo.com>
Sent: Friday, May 20, 2022 11:13 AM
To: Corey Bonnell <Corey.Bonnell at digicert.com>; cscwg-public at cabforum.org
Subject: RE: Voting period begins: Ballot CSC-14 - Convert Code Signing
Baseline Requirements to RFC 3647 Framework



Sectigo votes YES pending formatting fixes in section 6.2.7.4.2 (page 38 and
39)



De: Cscwg-public < <mailto:cscwg-public-bounces at cabforum.org>
cscwg-public-bounces at cabforum.org> En nombre de Corey Bonnell via
Cscwg-public
Enviado el: martes, 17 de mayo de 2022 19:30
Para:  <mailto:cscwg-public at cabforum.org> cscwg-public at cabforum.org
Asunto: [Cscwg-public] Voting period begins: Ballot CSC-14 - Convert Code
Signing Baseline Requirements to RFC 3647 Framework



CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know the
content is safe.



Convert Code Signing Baseline Requirements to RFC 3647 Framework



Purpose of this ballot:

RFC 3647 defines a standard framework for outlining the obligations of
participants in a PKI. Following the recommended framework as specified in
RFC 3647 allows for easier comparison of “The Baseline Requirements for the
Issuance and Management of Publicly‐Trusted Code Signing Certificates”
with other policy documents, most notably work products of other CA/Browser
Forum working groups and individual Certification Authority Certificate
Policies and Certification Practice Statements. This ballot restates all
existing obligations and requirements that are contained in The Baseline
Requirements for the Issuance and Management of Publicly‐Trusted Code
Signing Certificates” in the outline recommended by RFC 3647.



The following motion has been proposed by Corey Bonnell of DigiCert and
endorsed by Ian McMillan of Microsoft and Dimitris Zacharopoulos of HARICA.



MOTION BEGINS

This ballot updates the “Baseline Requirements for the Issuance and
Management of Publicly‐Trusted Code Signing Certificates” version 2.8 by
replacing the entirely of the content of the document with the attached
document.

MOTION ENDS

The procedure for approval of this ballot is as follows:

Discussion (7 days)

Start Time: 2022-05-10 16:45 UTC

End Time: 2022-05-17 17:30 UTC



Vote for approval (7 days)

Start Time: 2022-05-17 17:30 UTC

End Time: 2022-05-24 17:30 UTC





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/cscwg-public/attachments/20220520/23563a29/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4990 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/cscwg-public/attachments/20220520/23563a29/attachment-0001.p7s>