Rotate CID after inactivity

Open
#669 0 comments 0 reactions 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
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
networking

Research direction

No file or test is named. Start by locating the QUIC connection-ID handling and the path that sends after inactivity, then review how NAT rebinding is detected or represented. Done means the project has a defined inactivity rule and rotates the CID before sending when that rule applies, with coverage for the relevant cases.

Written by the indexing model from the issue text.

Description

compliance

Whenever there's some inactivity there's a chance that we might have had a NAT rebinding or similar. In this case we really should rotate the CID before sending again.

Figuring out when to rotate the CID is the tricky part.

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.