- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Dec 2023 15:15:07 +0000
- To: public-webrtc-logs@w3.org
> What's the model that forces you to assume two underlying transports? https://datatracker.ietf.org/doc/html/rfc8445#section-9 doesn't seem to assume that the transport is changed - the RTCIceTransport represents "the ICE transport layer for the RTP or RTCP component of a transceiver or group of transceivers". A new set of candidate pairs, which ICE starts on from scratch, is a new transport in exactly the same way that a new non-bundled m-section is a new transport. Exactly the same state carries over in each of those cases (ie; the certs and basically nothing else). You still need to do a new DTLS handshake, you still need to establish new SRTP keys, you still need to carry out a new SCTP handshake (if you're using datachannel), etc. You can try to abstract that away (eg; with RTCIceTransport), but that's really what is going on under the hood. -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2914#issuecomment-1856035535 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 14 December 2023 15:15:09 UTC