On 11/04/2017 18:53, Gervase Markham wrote:
On 11/04/17 17:34, Ryan Sleevi wrote:
Can you clarify what issues you believe this to be related?
That is a fair question. And also hard work to answer <sigh> :-)
Given that Symantec has a routine habit of exceeding any reasonable
deadline for response, at what point do you believe it is appropriate for
the Mozilla Root Store to begin discussing what steps can or should be
taken with respect to the documented and supported incidents, which
Symantec has not provided counter-factual data?
Yes, fair enough. Rick and Steve: I will be taking Symantec's statements
to this group as of one week from today as the sum total of what you
have to say on the subjects under discussion. After that point, we will
draw conclusions based on the available data and decide on what course
of action we may take. I hope that by then you will be able to answer my
8 questions, and provide responses or comments to any of Ryan's or other
people's questions that you wish to address.
Kathleen is on vacation this week, and so no decisions could be taken
until next week at the earliest anyway.
Please consider the fact that this is Easter week, and most of the
industry, including many people (on both the Browser and Symantec sides
of the process) are likely to be unavailable for precisely this week of
the entire year.
In general, sending deadline mails (by paper, e-mail, process server or
otherwise) to anyone during a public holiday demanding actions during
that holiday is considered morally deficient at a minimum.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy