- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 05 Jul 2017 13:21:06 +0000
- To: public-webrtc-logs@w3.org
I'll reiterate the idea I mentioned in [here](https://bugs.chromium.org/p/webrtc/issues/detail?id=7933): If we used the same random id for both the stream and the track in this case, then the remote browser could omit creating a stream in this case. Unless we care about this edge-case in non-browser end-points, we might not even need to involve ietf. Unless there's something in ietf that says stream ids and track ids are in the same namespace? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1448#issuecomment-313100858 using your GitHub account
Received on Wednesday, 5 July 2017 13:21:12 UTC