- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Apr 2018 16:53:22 +0000
- To: public-webrtc-logs@w3.org
After a brief discussion on the RTCWeb WG mailing list, it seems clear that we will have to be prepared that at least the other peer may support less than 65535 streams. So, in order to inform the user application about the maximum amount of channels that can be created, I propose to add a new attribute to `RTCSctpTransport`:
```
interface RTCSctpTransport {
...
readonly attribute unsigned short maxChannelId;
...
}
```
where `maxChannelId` is the minimum of the negotiated amount of incoming and outgoing streams (@tuexen is that correct to determine the maximum channel ID?).
We would need to add a check to all places where a data channel is being created or an ID is being assigned to comply with this maximum. (Furthermore, having this attribute will make channel ID exhaustion tests easier to write.)
Comments? :slightly_smiling_face:
--
GitHub Notification of comment by lgrahl
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1829#issuecomment-381196414 using your GitHub account
Received on Friday, 13 April 2018 16:53:25 UTC