- From: Tim Panton via GitHub <noreply@w3.org>
- Date: Fri, 20 Jun 2025 11:37:48 +0000
- To: public-webrtc-logs@w3.org
In my slides for the W3C meeting I had these as possible options:
`PeerConnection.setExpectedRemoteFingerprint()`
`PeerConnection.setExpectedRemoteCertificate()`
`new PeerConnection({remoteFingerprint:””}); // config field`
`RTCSessionDescription.fingerprint // property - settable?`
`RTCSessionDescription.set/getFingerprint() // syntax check etc`
But @alvestrand correctly pointed out that it is a transport issue really, although that makes the timing more difficult.
I like `PeerConnection.setExpectedRemoteFingerprint()` since it stays as far from SDP as possible
but `RTCSessionDescription.set/getFingerprint() // syntax check etc` is closest to current 'best practice'
--
GitHub Notification of comment by steely-glint
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3055#issuecomment-2991144616 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 June 2025 11:37:49 UTC