Open
Bug 1381145
Opened 8 years ago
Updated 2 years ago
Enable SCTP ndata to prevent data channel send queue monopolisation
Categories
(Core :: WebRTC: Networking, defect, P4)
Core
WebRTC: Networking
Tracking
()
NEW
People
(Reporter: lgrahl, Unassigned)
Details
(Keywords: dev-doc-needed)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36 OPR/46.0.2597.19 (Edition beta)
Expected results:
Without the SCTP ndata extension (see https://tools.ietf.org/html/draft-ietf-tsvwg-sctp-ndata-11), a large data channel message will
monopolise the SCTP association. Support for the extension should already be in the code base (introduced by the changes for bug 979417) but usrsctp needs to be updated.
Updated•8 years ago
|
Rank: 35
Priority: -- → P3
Comment 1•7 years ago
|
||
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Comment 2•7 years ago
|
||
This will require documentation updates; possibly to RTCDataChannel.send() but definitely to the section "Understanding message size limits" at https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Using_data_channels#Understanding_message_size_limits
Keywords: dev-doc-needed
Reporter | ||
Comment 3•7 years ago
|
||
If I understood Michael correctly, the code base (usrsctp/master) already uses ndata for normal data chunks when receiving but sending is currently not enabled (and not completely implemented).
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•