commit | 2e78f09c1a722eea9b30eb457246c4a770e9c2d0 | [log] [tgz] |
---|---|---|
author | Victor Boivie <boivie@webrtc.org> | Fri Sep 03 12:15:02 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 06 10:24:06 2021 |
tree | 7a61fc0c354e69d983e983c1056df6ce63c6b8a8 | |
parent | b02ed8f0260a26eb4f8011f5049721996a8214a9 [diff] |
dcsctp: Increase RTO limits The previous limits were taken from Oracles SCTP stack[1] as they were more up-to-date than the suggested ones in RFC4960. However, after having evaluated them for a while, it's evident that they are a bit too aggressive and likely have their origin from a wired LAN network. Let's do a re-take. These values have been taken from Solaris TCP stack[2]. They are even less aggressive than Linux defaults. This can be iterated even more, and is always possible to override by the client. It's generally the increase of rto_min that is helping here, as the delayed SACK and RTT jitter require that the RTO.min is quite much higher than the delayed SACK timeout of the peer (which isn't in control by us, but one can assume it's 200ms or less). And with a too low RTO.min, it's increased risk of getting spurious retransmissions and decreasing the congestion window. [1] https://docs.oracle.com/cd/E93309_01/docs.466/SIGTRAN/GUID-2136614F-4BED-407C-87B0-7EE10E0FF534.htm [2] https://docs.oracle.com/cd/E19120-01/open.solaris/819-2724/chapter4-69/index.html Bug: webrtc:12943 Change-Id: I9678ac4396286a55c251c5f57589379da70fd27d Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/231139 Reviewed-by: Harald Alvestrand <hta@webrtc.org> Commit-Queue: Victor Boivie <boivie@webrtc.org> Cr-Commit-Position: refs/heads/main@{#34927}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.