- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Sat, 17 Dec 2016 16:11:46 +0000
- To: public-ortc@w3.org
lgrahl has just created a new issue for https://github.com/w3c/ortc: == RTCSctpCapabilities maxMessageSize issues == I see two problems with the `maxMessageSize` attribute of `RTCSctpCapabilities`: 1. An unsigned short provides insufficient space. I'm not entirely sure what the maximum message size of SCTP effectively is, maybe @tuexen can add a statement to that. However, streaming APIs should be able to handle messages of arbitrary size (although the W3C API is not a streaming API, other implementations may provide one). 2. We should clarify that `0` indicates that the other peer can handle messages of any size. This is particularly important once [SCTP ndata](https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-08) will be deployed. For reference, here is the [SDP section relevant for WebRTC](https://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-19#section-6). Please view or discuss this issue at https://github.com/w3c/ortc/issues/626 using your GitHub account
Received on Saturday, 17 December 2016 16:11:52 UTC