Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Chunghwa Telecom votes “Yes” on NS-003. Thanks. Li-Chun Chen Chunghwa Telecom -Original Message- From: Netsec On Behalf Of Ryan Dickson via Netsec Sent: Tuesday, April 30, 2024 4:57 AM To: Clint Wilson ; CABF Network Security WG Subject: [外部郵件]Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Google votes "Yes" on NS-003. On Tue, Apr 23, 2024 at 11:59 AM Clint Wilson via Netsec < <mailto:netsec@cabforum.org%20%3cmailto:netsec@cabforum.org> netsec@cabforum.org <mailto:netsec@cabforum.org> > wrote: Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: <https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e> https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e < <https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcabforum%2Fnetsec%2Fcompare%2Fc62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e=05%7C02%7Crealsky%40cht.com.tw%7C4754871dbe2c47e10f1e08dc688eedb1%7C54eb9440cf0345fe835e61bd4ce515c8%7C0%7C0%7C638500210295474559%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=WKNbjApmzhUIxkfDf8AEhxjX2%2B2j%2FoB9UQMM0GdqrO4%3D=0> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcabforum%2Fnetsec%2Fcompare%2Fc62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e=05%7C02%7Crealsky%40cht.com.tw%7C4754871dbe2c47e10f1e08dc688eedb1%7C54eb9440cf0345fe83
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Telia Company votes ‘Yes’ on Ballot NS-003 //Antti From: Netsec on behalf of Clint Wilson via Netsec Date: Tuesday, 23. April 2024 at 18.59 To: NetSec CA/BF Subject: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e <https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e> MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC smime.p7s Description: S/MIME cryptographic signature ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Buypass votes YES on Ballot NS-003. Regards Mads From: Netsec On Behalf Of Clint Wilson via Netsec Sent: Tuesday, April 23, 2024 5:59 PM To: NetSec CA/BF Subject: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA's NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional "SHOULD"-type stipulations, clarifying some of the language in the current NCSSRs such that it's easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the "Network and Certificate System Security Requirements" as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Google votes "Yes" on NS-003. On Tue, Apr 23, 2024 at 11:59 AM Clint Wilson via Netsec < netsec@cabforum.org> wrote: > Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli > Ponds-White of Amazon and David Kluge of Google Trust Services. > > *Purpose of Ballot* > > This ballot proposes a comprehensive restructuring of the Network and > Certificate System Security Requirements (NCSSRs), excepting Section 4. The > current structure of the document has proven to be challenging for creating > ballots, contains duplicated requirements, and separates similar > requirements across the document. These issues have led to inefficiencies > in managing and implementing security standards. Therefore, this proposal > aims to streamline the document's structure, eliminate redundancies, > improve comprehensibility, and enhance clarity and coherence. > > *Reasons for Proposal:* > > >- *Complexity in Ballot Creation*: The current document structure can >make it difficult to create and manage ballots efficiently, leading to >somewhat awkward updating processes, abandoned ballots, and a lack of >confidence that ballots effect the intended changes. >- *Redundancy*: Over time, some parts of the NCSSRs have touched on >the same topic, leading to some duplication across the document and further >to confusion and inconsistency in implementation. >- *Fragmentation*: Similar requirements for different parts of a CA’s >NCSSR-relevant infrastructure are scattered throughout the document, making >it somewhat more difficult for to locate and comprehend a complete picture >of these requirements effectively. >- *Minor Issues*: The document contains other, more minor issues that >also impede its usability and effectiveness, such as missing definitions, >unclear list structures, and requirements that are more optional than they >may currently appear. > > > *Benefits of the Updated Document Structure:* > > >- *Enhanced Clarity*: The revised structure should improve the clarity >and coherence of the document, making the requirements it represents easier >to understand, as well as result in greater consistency when implementing >or assessing its security requirements. >- *Future Updates*: A more granular document structure should improve >the process of creating and managing ballots in the future. Similarly, the >improved proximity of related requirements should hopefully aid in >identifying the areas the NCSSRs can most benefit from further attention. >- *Grouping and De-duplication of Similar Requirements*: By >consolidating duplicated requirements, the updated document should make it >much easier to find, comprehend, assess, and implement related > requirements. >- *Clearer Recommendations*: The updated document includes a number of >additional “SHOULD”-type stipulations, clarifying some of the language in >the current NCSSRs such that it’s easier to identify where the NCSSRs >impose a strict requirement as opposed to a strong recommendation. > > > Overall, this ballot proposal seeks to address existing challenges in > updating the current version of the NCSSRs and pave the way for future > improvements to the NCSSRs. > > *MOTION BEGINS* > > This ballot modifies the “Network and Certificate System Security > Requirements” as follows, based on version 1.7: > > > https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e > > *MOTION ENDS* > > The procedure for approval of this ballot is as follows: > > *Discussion Period* (14+ days) > > Start Time: 2024-April-09 16:00 UTC > End Time: 2024-April-23 15:59 UTC > > *Voting Period* (7 days) > > Start Time: 2024-April-23 16:00 UTC > End Time: 2024-April-30 16:00 UTC > ___ > Netsec mailing list > Netsec@cabforum.org > https://lists.cabforum.org/mailman/listinfo/netsec > ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
VikingCloud votes Yes on NS-003. Regards, Andrea Holland From: Netsec On Behalf Of Clint Wilson via Netsec Sent: Tuesday, April 23, 2024 11:59 AM To: NetSec CA/BF Subject: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs 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. Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC Company Registration Details VikingCloud is the registered business name of Sysxnet Limited. Sysxnet Limited is registered in Ireland under company registration number 147176 and its registered office is at 1st Floor, Block 71a, The Plaza, Park West Business Park, Dublin 12, Ireland. Email Disclaimer The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Sysxnet Limited is neither liable for the proper and complete transmission of the information contained
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Fastly votes Yes to ballot NS-003. - Wayne On Tue, Apr 23, 2024 at 8:59 AM Clint Wilson via Netsec wrote: > Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli > Ponds-White of Amazon and David Kluge of Google Trust Services. > > *Purpose of Ballot* > > This ballot proposes a comprehensive restructuring of the Network and > Certificate System Security Requirements (NCSSRs), excepting Section 4. The > current structure of the document has proven to be challenging for creating > ballots, contains duplicated requirements, and separates similar > requirements across the document. These issues have led to inefficiencies > in managing and implementing security standards. Therefore, this proposal > aims to streamline the document's structure, eliminate redundancies, > improve comprehensibility, and enhance clarity and coherence. > > *Reasons for Proposal:* > > >- *Complexity in Ballot Creation*: The current document structure can >make it difficult to create and manage ballots efficiently, leading to >somewhat awkward updating processes, abandoned ballots, and a lack of >confidence that ballots effect the intended changes. >- *Redundancy*: Over time, some parts of the NCSSRs have touched on >the same topic, leading to some duplication across the document and further >to confusion and inconsistency in implementation. >- *Fragmentation*: Similar requirements for different parts of a CA’s >NCSSR-relevant infrastructure are scattered throughout the document, making >it somewhat more difficult for to locate and comprehend a complete picture >of these requirements effectively. >- *Minor Issues*: The document contains other, more minor issues that >also impede its usability and effectiveness, such as missing definitions, >unclear list structures, and requirements that are more optional than they >may currently appear. > > > *Benefits of the Updated Document Structure:* > > >- *Enhanced Clarity*: The revised structure should improve the clarity >and coherence of the document, making the requirements it represents easier >to understand, as well as result in greater consistency when implementing >or assessing its security requirements. >- *Future Updates*: A more granular document structure should improve >the process of creating and managing ballots in the future. Similarly, the >improved proximity of related requirements should hopefully aid in >identifying the areas the NCSSRs can most benefit from further attention. >- *Grouping and De-duplication of Similar Requirements*: By >consolidating duplicated requirements, the updated document should make it >much easier to find, comprehend, assess, and implement related > requirements. >- *Clearer Recommendations*: The updated document includes a number of >additional “SHOULD”-type stipulations, clarifying some of the language in >the current NCSSRs such that it’s easier to identify where the NCSSRs >impose a strict requirement as opposed to a strong recommendation. > > > Overall, this ballot proposal seeks to address existing challenges in > updating the current version of the NCSSRs and pave the way for future > improvements to the NCSSRs. > > *MOTION BEGINS* > > This ballot modifies the “Network and Certificate System Security > Requirements” as follows, based on version 1.7: > > > https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e > > *MOTION ENDS* > > The procedure for approval of this ballot is as follows: > > *Discussion Period* (14+ days) > > Start Time: 2024-April-09 16:00 UTC > End Time: 2024-April-23 15:59 UTC > > *Voting Period* (7 days) > > Start Time: 2024-April-23 16:00 UTC > End Time: 2024-April-30 16:00 UTC > ___ > Netsec mailing list > Netsec@cabforum.org > https://lists.cabforum.org/mailman/listinfo/netsec > ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
SSL.com votes “Yes” on ballot NS-003. -Tom SSL.com From: Netsec On Behalf Of Clint Wilson via Netsec Sent: Tuesday, April 23, 2024 10:59 AM To: NetSec CA/BF Subject: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC smime.p7s Description: S/MIME cryptographic signature ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
TrustAsia votes YES on Ballot NS-003. Best regards, Rollin Yu > On Apr 23, 2024, at 23:59, Clint Wilson via Netsec > wrote: > > Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli > Ponds-White of Amazon and David Kluge of Google Trust Services. > > Purpose of Ballot > > This ballot proposes a comprehensive restructuring of the Network and > Certificate System Security Requirements (NCSSRs), excepting Section 4. The > current structure of the document has proven to be challenging for creating > ballots, contains duplicated requirements, and separates similar requirements > across the document. These issues have led to inefficiencies in managing and > implementing security standards. Therefore, this proposal aims to streamline > the document's structure, eliminate redundancies, improve comprehensibility, > and enhance clarity and coherence. > > Reasons for Proposal: > > Complexity in Ballot Creation: The current document structure can make it > difficult to create and manage ballots efficiently, leading to somewhat > awkward updating processes, abandoned ballots, and a lack of confidence that > ballots effect the intended changes. > Redundancy: Over time, some parts of the NCSSRs have touched on the same > topic, leading to some duplication across the document and further to > confusion and inconsistency in implementation. > Fragmentation: Similar requirements for different parts of a CA’s > NCSSR-relevant infrastructure are scattered throughout the document, making > it somewhat more difficult for to locate and comprehend a complete picture of > these requirements effectively. > Minor Issues: The document contains other, more minor issues that also impede > its usability and effectiveness, such as missing definitions, unclear list > structures, and requirements that are more optional than they may currently > appear. > > Benefits of the Updated Document Structure: > > Enhanced Clarity: The revised structure should improve the clarity and > coherence of the document, making the requirements it represents easier to > understand, as well as result in greater consistency when implementing or > assessing its security requirements. > Future Updates: A more granular document structure should improve the process > of creating and managing ballots in the future. Similarly, the improved > proximity of related requirements should hopefully aid in identifying the > areas the NCSSRs can most benefit from further attention. > Grouping and De-duplication of Similar Requirements: By consolidating > duplicated requirements, the updated document should make it much easier to > find, comprehend, assess, and implement related requirements. > Clearer Recommendations: The updated document includes a number of additional > “SHOULD”-type stipulations, clarifying some of the language in the current > NCSSRs such that it’s easier to identify where the NCSSRs impose a strict > requirement as opposed to a strong recommendation. > > Overall, this ballot proposal seeks to address existing challenges in > updating the current version of the NCSSRs and pave the way for future > improvements to the NCSSRs. > > MOTION BEGINS > > This ballot modifies the “Network and Certificate System Security > Requirements” as follows, based on version 1.7: > > https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e > > MOTION ENDS > > The procedure for approval of this ballot is as follows: > > Discussion Period (14+ days) > > Start Time: 2024-April-09 16:00 UTC > End Time: 2024-April-23 15:59 UTC > > Voting Period (7 days) > > Start Time: 2024-April-23 16:00 UTC > End Time: 2024-April-30 16:00 UTC > ___ > Netsec mailing list > Netsec@cabforum.org > https://lists.cabforum.org/mailman/listinfo/netsec smime.p7s Description: S/MIME cryptographic signature ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
SwissSign votes 'yes' on NS-003: Restructure of NCSSRs Mike Von: Netsec Im Auftrag von Clint Wilson via Netsec Gesendet: Dienstag, 23. April 2024 17:59 An: NetSec CA/BF Betreff: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA's NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional "SHOULD"-type stipulations, clarifying some of the language in the current NCSSRs such that it's easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the "Network and Certificate System Security Requirements" as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
GDCA votes YES on Ballot NS-003. Thanks. From: Clint Wilson via Netsec Date: 2024-04-23 23:59 To: NetSec CA/BF Subject: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Apple votes YES on Ballot NS-003. > On Apr 23, 2024, at 8:59 AM, Clint Wilson via Netsec > wrote: > > Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli > Ponds-White of Amazon and David Kluge of Google Trust Services. > > Purpose of Ballot > > This ballot proposes a comprehensive restructuring of the Network and > Certificate System Security Requirements (NCSSRs), excepting Section 4. The > current structure of the document has proven to be challenging for creating > ballots, contains duplicated requirements, and separates similar requirements > across the document. These issues have led to inefficiencies in managing and > implementing security standards. Therefore, this proposal aims to streamline > the document's structure, eliminate redundancies, improve comprehensibility, > and enhance clarity and coherence. > > Reasons for Proposal: > > Complexity in Ballot Creation: The current document structure can make it > difficult to create and manage ballots efficiently, leading to somewhat > awkward updating processes, abandoned ballots, and a lack of confidence that > ballots effect the intended changes. > Redundancy: Over time, some parts of the NCSSRs have touched on the same > topic, leading to some duplication across the document and further to > confusion and inconsistency in implementation. > Fragmentation: Similar requirements for different parts of a CA’s > NCSSR-relevant infrastructure are scattered throughout the document, making > it somewhat more difficult for to locate and comprehend a complete picture of > these requirements effectively. > Minor Issues: The document contains other, more minor issues that also impede > its usability and effectiveness, such as missing definitions, unclear list > structures, and requirements that are more optional than they may currently > appear. > > Benefits of the Updated Document Structure: > > Enhanced Clarity: The revised structure should improve the clarity and > coherence of the document, making the requirements it represents easier to > understand, as well as result in greater consistency when implementing or > assessing its security requirements. > Future Updates: A more granular document structure should improve the process > of creating and managing ballots in the future. Similarly, the improved > proximity of related requirements should hopefully aid in identifying the > areas the NCSSRs can most benefit from further attention. > Grouping and De-duplication of Similar Requirements: By consolidating > duplicated requirements, the updated document should make it much easier to > find, comprehend, assess, and implement related requirements. > Clearer Recommendations: The updated document includes a number of additional > “SHOULD”-type stipulations, clarifying some of the language in the current > NCSSRs such that it’s easier to identify where the NCSSRs impose a strict > requirement as opposed to a strong recommendation. > > Overall, this ballot proposal seeks to address existing challenges in > updating the current version of the NCSSRs and pave the way for future > improvements to the NCSSRs. > > MOTION BEGINS > > This ballot modifies the “Network and Certificate System Security > Requirements” as follows, based on version 1.7: > > https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e > > MOTION ENDS > > The procedure for approval of this ballot is as follows: > > Discussion Period (14+ days) > > Start Time: 2024-April-09 16:00 UTC > End Time: 2024-April-23 15:59 UTC > > Voting Period (7 days) > > Start Time: 2024-April-23 16:00 UTC > End Time: 2024-April-30 16:00 UTC > ___ > Netsec mailing list > Netsec@cabforum.org > https://lists.cabforum.org/mailman/listinfo/netsec smime.p7s Description: S/MIME cryptographic signature ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Sectigo votes yes De: Netsec En nombre de Clint Wilson via Netsec Enviado el: martes, 23 de abril de 2024 17:59 Para: NetSec CA/BF Asunto: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs 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. Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA's NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional "SHOULD"-type stipulations, clarifying some of the language in the current NCSSRs such that it's easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the "Network and Certificate System Security Requirements" as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536 388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC smime.p7s Description: S/MIME cryptographic signature ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
HARICA votes "yes" to ballot NS-003. On 23/4/2024 6:59 μ.μ., Clint Wilson via Netsec wrote: Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. *Purpose of Ballot* This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. _Reasons for Proposal:_ * *Complexity in Ballot Creation*: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * *Redundancy*: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * *Fragmentation*: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * *Minor Issues*: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. _Benefits of the Updated Document Structure:_ * *Enhanced Clarity*: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * *Future Updates*: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * *Grouping and De-duplication of Similar Requirements*: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * *Clearer Recommendations*: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. *MOTION BEGINS* This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e *MOTION ENDS* The procedure for approval of this ballot is as follows: *_Discussion Period_* (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC *_Voting Period_* (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
GlobalSign votes “Yes” on Ballot NS-003. Christophe From: Netsec On Behalf Of Clint Wilson via Netsec Sent: Tuesday, April 23, 2024 5:59 PM To: NetSec CA/BF Subject: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC smime.p7s Description: S/MIME cryptographic signature ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Disig votes "Yes" on NS-003 Best regards, Jozef Nigut Disig, a.s. From: Netsec On Behalf Of Clint Wilson via Netsec Sent: Tuesday, April 23, 2024 5:59 PM To: NetSec CA/BF Subject: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC smime.p7s Description: S/MIME cryptographic signature ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Kamu SM votes "Yes" on Ballot NS-003 Tuğba ÖZCAN Head Of e_signature Technologies Department TÜBİTAK/BİLGEM/Kamu SM Çamlıca Mahallesi 408. Cadde No: 136 C Blok 5. Kat Yenimahalle/Ankara Dahili:8543 tugba.oz...@tubitak.gov.tr Kimden: "Clint Wilson via Netsec" Kime: "NetSec CA/BF" Gönderilenler: 23 Nisan Salı 2024 18:59:16 Konu: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation : The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy : Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation : Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues : The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity : The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates : A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements : By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations : The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: [ https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e | https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e ] MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
TWCA votes yes. From: Netsec On Behalf Of Clint Wilson via Netsec Sent: Tuesday, April 23, 2024 11:59 PM To: NetSec CA/BF Subject: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Mozilla votes "yes" on this ballot. On Tue, Apr 23, 2024, 5:59 PM Clint Wilson via Netsec wrote: > Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli > Ponds-White of Amazon and David Kluge of Google Trust Services. > > *Purpose of Ballot* > > This ballot proposes a comprehensive restructuring of the Network and > Certificate System Security Requirements (NCSSRs), excepting Section 4. The > current structure of the document has proven to be challenging for creating > ballots, contains duplicated requirements, and separates similar > requirements across the document. These issues have led to inefficiencies > in managing and implementing security standards. Therefore, this proposal > aims to streamline the document's structure, eliminate redundancies, > improve comprehensibility, and enhance clarity and coherence. > > *Reasons for Proposal:* > > >- *Complexity in Ballot Creation*: The current document structure can >make it difficult to create and manage ballots efficiently, leading to >somewhat awkward updating processes, abandoned ballots, and a lack of >confidence that ballots effect the intended changes. >- *Redundancy*: Over time, some parts of the NCSSRs have touched on >the same topic, leading to some duplication across the document and further >to confusion and inconsistency in implementation. >- *Fragmentation*: Similar requirements for different parts of a CA’s >NCSSR-relevant infrastructure are scattered throughout the document, making >it somewhat more difficult for to locate and comprehend a complete picture >of these requirements effectively. >- *Minor Issues*: The document contains other, more minor issues that >also impede its usability and effectiveness, such as missing definitions, >unclear list structures, and requirements that are more optional than they >may currently appear. > > > *Benefits of the Updated Document Structure:* > > >- *Enhanced Clarity*: The revised structure should improve the clarity >and coherence of the document, making the requirements it represents easier >to understand, as well as result in greater consistency when implementing >or assessing its security requirements. >- *Future Updates*: A more granular document structure should improve >the process of creating and managing ballots in the future. Similarly, the >improved proximity of related requirements should hopefully aid in >identifying the areas the NCSSRs can most benefit from further attention. >- *Grouping and De-duplication of Similar Requirements*: By >consolidating duplicated requirements, the updated document should make it >much easier to find, comprehend, assess, and implement related > requirements. >- *Clearer Recommendations*: The updated document includes a number of >additional “SHOULD”-type stipulations, clarifying some of the language in >the current NCSSRs such that it’s easier to identify where the NCSSRs >impose a strict requirement as opposed to a strong recommendation. > > > Overall, this ballot proposal seeks to address existing challenges in > updating the current version of the NCSSRs and pave the way for future > improvements to the NCSSRs. > > *MOTION BEGINS* > > This ballot modifies the “Network and Certificate System Security > Requirements” as follows, based on version 1.7: > > > https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e > > *MOTION ENDS* > > The procedure for approval of this ballot is as follows: > > *Discussion Period* (14+ days) > > Start Time: 2024-April-09 16:00 UTC > End Time: 2024-April-23 15:59 UTC > > *Voting Period* (7 days) > > Start Time: 2024-April-23 16:00 UTC > End Time: 2024-April-30 16:00 UTC > ___ > Netsec mailing list > Netsec@cabforum.org > https://lists.cabforum.org/mailman/listinfo/netsec > ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
GoDaddy votes "Yes" on NS-003 Best, Brittany From: Netsec on behalf of Clint Wilson via Netsec Sent: Tuesday, April 23, 2024 8:59 AM To: NetSec CA/BF Subject: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
Re: [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Amazon Trust Services votes yes From: Netsec On Behalf Of Clint Wilson via Netsec Sent: Tuesday, April 23, 2024 8:59 AM To: NetSec CA/BF Subject: [EXTERNAL] [cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: * Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. * Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. * Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. * Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: * Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. * Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. * Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. * Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
[cabf_netsec] Voting Period Begins | Ballot NS-003: Restructure the NCSSRs
Ballot NS-003 is proposed by Clint Wilson of Apple and endorsed by Trevoli Ponds-White of Amazon and David Kluge of Google Trust Services. Purpose of Ballot This ballot proposes a comprehensive restructuring of the Network and Certificate System Security Requirements (NCSSRs), excepting Section 4. The current structure of the document has proven to be challenging for creating ballots, contains duplicated requirements, and separates similar requirements across the document. These issues have led to inefficiencies in managing and implementing security standards. Therefore, this proposal aims to streamline the document's structure, eliminate redundancies, improve comprehensibility, and enhance clarity and coherence. Reasons for Proposal: Complexity in Ballot Creation: The current document structure can make it difficult to create and manage ballots efficiently, leading to somewhat awkward updating processes, abandoned ballots, and a lack of confidence that ballots effect the intended changes. Redundancy: Over time, some parts of the NCSSRs have touched on the same topic, leading to some duplication across the document and further to confusion and inconsistency in implementation. Fragmentation: Similar requirements for different parts of a CA’s NCSSR-relevant infrastructure are scattered throughout the document, making it somewhat more difficult for to locate and comprehend a complete picture of these requirements effectively. Minor Issues: The document contains other, more minor issues that also impede its usability and effectiveness, such as missing definitions, unclear list structures, and requirements that are more optional than they may currently appear. Benefits of the Updated Document Structure: Enhanced Clarity: The revised structure should improve the clarity and coherence of the document, making the requirements it represents easier to understand, as well as result in greater consistency when implementing or assessing its security requirements. Future Updates: A more granular document structure should improve the process of creating and managing ballots in the future. Similarly, the improved proximity of related requirements should hopefully aid in identifying the areas the NCSSRs can most benefit from further attention. Grouping and De-duplication of Similar Requirements: By consolidating duplicated requirements, the updated document should make it much easier to find, comprehend, assess, and implement related requirements. Clearer Recommendations: The updated document includes a number of additional “SHOULD”-type stipulations, clarifying some of the language in the current NCSSRs such that it’s easier to identify where the NCSSRs impose a strict requirement as opposed to a strong recommendation. Overall, this ballot proposal seeks to address existing challenges in updating the current version of the NCSSRs and pave the way for future improvements to the NCSSRs. MOTION BEGINS This ballot modifies the “Network and Certificate System Security Requirements” as follows, based on version 1.7: https://github.com/cabforum/netsec/compare/c62a2f88e252de5c79b101fa3c9e9c536388639a...8bd66d27c07e30d1f4d9e6dd57b075bca499bf2e MOTION ENDS The procedure for approval of this ballot is as follows: Discussion Period (14+ days) Start Time: 2024-April-09 16:00 UTC End Time: 2024-April-23 15:59 UTC Voting Period (7 days) Start Time: 2024-April-23 16:00 UTC End Time: 2024-April-30 16:00 UTC smime.p7s Description: S/MIME cryptographic signature ___ Netsec mailing list Netsec@cabforum.org https://lists.cabforum.org/mailman/listinfo/netsec
