W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > December 2018

[webrtc-pc] Clarifications of certificate expiry (#2045)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Thu, 20 Dec 2018 15:06:10 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-393084928-1545318369-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc:

== Clarifications of certificate expiry ==
A few items could be clarified:

- Computation of the certificate expires value refer to "current time". This could be better defined as you suggested. This should be consistent with the one in the expires future check)
- When the "current time" is actually computed as part of generateCertificate call (call time of generateCertificate, generation of the keying material, creation of the RTCCertificate objects/resolution of the promise)
- If we compare the expires value to a DOMHighResTimeStamp that performance API is providing/defining, we could consider making RTCCertificateExpiration a DOMHighResTimeStamp. We would lose EnforceRange so probably not worth it.
- When the "current time" is executed in the expires future check (one "current time" for all certificate expires checks or one current time per certificate expires check).

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2045 using your GitHub account
Received on Thursday, 20 December 2018 15:06:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 9 October 2019 15:15:00 UTC