Voting Results of Ballot NS-003: Restructure the NCSSRs
The voting period for Ballot NS-003: Restructure the NCSSRs has ended and the
Ballot has Passed. The following votes were cast:
4 votes by Certificate Consumers
4 Yes votes: Apple, Google, Microsoft, Mozilla
0 No votes:
0 Abstain votes:
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
>
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
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.
Please note, this ballot has set a 2 week Discussion Period.
Purpose of Ballot
This ballot proposes a comprehensive restructuring of the Network and
removing the links or
updating them if others feel strongly. For the moment, I’ve left them as-is.
I’ll push these changes later today, after the NSWG call in case there’s
further discussion.
Cheers!
-Clint
>
>
>
>
> //Antti
>
> From: Netsec <mailto:netsec-bou
Hi all,
I’ve pushed an update for NS-003 to address feedback received and add the
effective date discussed at last meeting. I have a few questions outstanding
that I'd appreciate feedback on.
1. The effective date is currently set to 15 October 2024. I don’t think this
is quite the correct
Hi All,
The draft changes we’ve been working on have been updated to address all
outstanding feedback that I’m aware of. The current PR is at
https://github.com/cabforum/netsec/compare/offline-hsms.
I’m interested in any final feedback prior to allocating a ballot number and
commencing an
n to put words in your mouth). Especially 3.a
>> is quite overloaded; quite the interesting challenge to figure out an
>> appropriate balance of specificity here that would provide enough detail of
>> 1) what’s actually expected and 2) the scope those expectations apply to
&
say I think that
> restructuring the NCSSRs, as this draft attempts to do, will help enable and
> hasten fixes to the myriad of (mostly) small and (some) big issues latent in
> the current NCSSRs — I don’t believe I could have drafted such a set of
> requirements while fitti
