- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Jun 2017 05:15:15 +0000
- To: public-webrtc-logs@w3.org
@fippo Are you imagining a scenario where an Offer encapsulating an ICE restart might fork to a different destination? In that situation, yes, the remote DTLS fingerprint could change - and the RTCIceTransport would actually be established to a different remote peer. In ORTC, you'd have to create a new RTCIceTransport (based on a new RTCIceGatherer) as well as a new RTCDtlsTransport (because you can't call start twice). So it wouldn't surprise me if this was also true in WebRTC 1.0. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1357#issuecomment-307297328 using your GitHub account
Received on Friday, 9 June 2017 05:15:21 UTC