- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2017 10:07:02 +0000
- To: public-webrtc-logs@w3.org
Marking it at risk sounds great to me if nobody currently has plans to implement.
If I came along and wanted to implement this, I think I'd want to change the spec in one of two ways. Either, return an object that is derived in the same way as https://w3c.github.io/webcrypto/Overview.html#concept-cached-object but is a new object every time. Or, change it to an attribute with this IDL:
```WebIDL
interface RTCCertificate {
readonly attribute DOMTimeStamp expires;
readonly attribute FrozenArray<RTCDtlsFingerprint> fingerprints;
readonly attribute object algorithm;
};
```
And implement it the same way as CryptoKey's algorithm attribute, which returns the same value every time.
The second option seems to most well aligned with Web Crypto, but if I knew crypto well perhaps I'd know of reasons to not do that.
Simply leaving the spec as-is, an unknowing implementer might come along and ship without pondering the options.
--
GitHub Notification of comment by foolip
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/881#issuecomment-284677468 using your GitHub account
Received on Tuesday, 7 March 2017 10:07:08 UTC