dcsctp: Add Data Tracker

The Data Tracker's purpose is to keep track of all received DATA chunks
and to ACK/NACK that data, by generating SACK chunks reflecting its view
of what has been received and what has been lost.

It also contains logic for _when_ to send the SACKs, as that's different
depending on e.g. packet loss. Generally, SACKs are sent every second
packet on a connection with no packet loss, and can also be sent on a
delayed timer.

In case partial reliability is used, and the transmitter has decided
that some data shouldn't be retransmitted, it will send a FORWARD-TSN
chunk, which this class also handles, by "forgetting" about those
chunks.

Bug: webrtc:12614
Change-Id: Ifafb0c211f6a47872e81830165ab5fc43ee7f366
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/213664
Commit-Queue: Victor Boivie <boivie@webrtc.org>
Reviewed-by: Tommi <tommi@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#33676}
5 files changed
tree: 00e7fd47c4b3d4f3359e01f63251ce96304c27dc
  1. .clang-format
  2. .git-blame-ignore-revs
  3. .gitignore
  4. .gn
  5. .vpython
  6. AUTHORS
  7. BUILD.gn
  8. CODE_OF_CONDUCT.md
  9. DEPS
  10. DIR_METADATA
  11. ENG_REVIEW_OWNERS
  12. LICENSE
  13. OWNERS
  14. PATENTS
  15. PRESUBMIT.py
  16. README.chromium
  17. README.md
  18. WATCHLISTS
  19. abseil-in-webrtc.md
  20. api/
  21. audio/
  22. build_overrides/
  23. call/
  24. codereview.settings
  25. common_audio/
  26. common_video/
  27. data/
  28. docs/
  29. examples/
  30. g3doc.lua
  31. g3doc/
  32. license_template.txt
  33. logging/
  34. media/
  35. modules/
  36. native-api.md
  37. net/
  38. p2p/
  39. pc/
  40. presubmit_test.py
  41. presubmit_test_mocks.py
  42. pylintrc
  43. resources/
  44. rtc_base/
  45. rtc_tools/
  46. sdk/
  47. stats/
  48. style-guide.md
  49. style-guide/
  50. system_wrappers/
  51. test/
  52. tools_webrtc/
  53. video/
  54. webrtc.gni
  55. webrtc_lib_link_test.cc
  56. whitespace.txt
README.md

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.

Development

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.

More info