-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
congure_quic: initial import of QUIC congestion control #15952
Conversation
Maybe @larseggert also wants to take a look. |
7a11318
to
3b5f6ca
Compare
3b5f6ca
to
485b887
Compare
Rebased to current master, needs some adaptions to the changes done in #15951, so I am marking this WIP temporarily. |
Adapted tests for behavior changes of |
And added the new Kconfig stuff (which does not work properly yet, since dependency resolution of |
The test framework needed some rework (see #16111) to handle longer parameters, so I will base this PR now on that. |
95e5479
to
c6e9a42
Compare
Rebased to current master and dependencies and added #16119 as new dependency. |
ea01143
to
8b9d97f
Compare
I'm fine with this one going in only after feature freeze and clearing up the Murdock queue for now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good, Makefile.ci
needs two more entries.
2b7aab2
to
1bf241e
Compare
Contribution description
This provides an implementation for CongURE of the congestion control mechanism of the QUIC protocol as specified in
draft-ietf-quic-recovery
(version 34 at the opening of this PR). It has the advantage of having congestion control via loss and ECN already build in and also provides means for packet pacing, so perfect for SFR!Testing procedure
Tests are provided for which
riotctrl
(at least v0.2.2) is required for them to run. If installed,should succeed.
Issues/PRs references
Requires
#15951(merged),#16111, and #16119.(merged) When merged, I will adapt the test framework to use the turo framework introduced in #15950, which was the original idea to begin with (which is why it is already printing JSON strings).