W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2016

[webrtc-pc] Clarify the processing of expires setting in generateCertificate

From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
Date: Sun, 23 Oct 2016 09:47:55 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-184680774-1477216072-sysbot+gh@w3.org>
foolip has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== Clarify the processing of expires setting in generateCertificate ==
When writing https://github.com/w3c/web-platform-tests/pull/4062 I 
tried this to get an expired certificate:

`RTCPeerConnection.generateCertificate({ name: "ECDSA", namedCurve: 
"P-256", expires: 0 }`

`DOMTimeStamp` is `unsigned long long`, and there's nothing in the 
spec that suggests that 0 shouldn't work. It works in Chrome, but not 
Firefox. This needs spec clarification or at least agreement on the 
right behavior since we now have two.

When writing tests for this, it would also be good to test -1, 0.1, 
NaN, Infinity, -Infinity and numbers around 2^31, 2^32, 2^63 and 2^64.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/879 using your GitHub account
Received on Sunday, 23 October 2016 09:48:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:49 UTC