Careful resume: seed a redial's congestion state from the previous connection

Open
#815 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
rust
Domain
networking

Research direction

No files, tests, or entry points are named. Start by tracing how QUIC connections establish congestion state and how clients perform automatic redials, then determine what state can safely persist for the exact same IP address. Done should include a defined behavior for reusing the previous window, pacing rate, and RTT without applying it to other addresses.

Written by the indexing model from the issue text.

Description

I have clients that automatically redial QUIC connections after they've been severed.

Ideally there could be some way of remembering the previous congestion control state (window size, pacing rate, rtt, etc) so we don't have to start with conservative defaults (ex. the 333ms default initial RTT). This would only be relevant when connecting to the exact same IP address.

Dominant language
Rust
Stars
454
Forks
98
Avg merge
2d 8h
Merged PRs (30d)
19

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from n0-computer/noq

All issues in n0-computer/noq

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.