- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Jun 2017 18:43:12 +0000
- To: public-webrtc-logs@w3.org
An ICE restart doesn't completely blow away the ICE state; the existing ICE candidate pair continues to be used while the ICE restart is going on. So I think it would make more sense logically, and be simpler, for ICE restarts to not create new `RTCIceTransport` objects. But there's also a question of what happens when a new DTLS association is formed. We could say that when a remote description is applied that indicates a new DTLS association, you get a new `RTCDtlsTransport` object. But if we do that, we really need some way of informing the application. I'd be fine with just saying "the DTLS transport is like the ICE transport; multiple DTLS associations are conceptually handled by a single DTLS transport object". I think that's what people have assumed until now. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1357#issuecomment-307192134 using your GitHub account
Received on Thursday, 8 June 2017 18:43:19 UTC