- From: Lorenzo Miniero via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Mar 2019 11:18:51 +0000
- To: public-webrtc-logs@w3.org
@ibc just summarized my main concerns here. In my case, my server is not a pure SFU, so while there may be scenarios with sendonly/recvonly PeerConnections, there will also be sendrecv PeerConnections hooked together where the respective MIDs may not match. Which means that regenerating RTP extensions on the way out would be the only way to include the proper MID there, something that as Iñaki pointed out is quite an annoying (but I guess at this point unavoidable) procedure. -- GitHub Notification of comment by lminiero Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1174#issuecomment-469642984 using your GitHub account
Received on Tuesday, 5 March 2019 11:18:53 UTC