WebAssembly / WebAssembly/WASI

TCP & UDP: TOS/TrafficClass

Open
#713 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P-sockets S-inactive
Dominant language
Rust
Stars
5.8k
Forks
333
Avg merge
2d 13h
Merged PRs (30d)
3

Description

Relevant socket options:

  • IP_TOS
  • IPV6_TCLASS
  • IP_RECVTOS
  • IPV6_RECVTCLASS
  • TCP_ECN_MODE
  • TCP_ENABLE_ECN

TODO:

  • 1 TOS field vs. separate DSCP and ECN fields
  • TCP: are ECN bits settable?
  • Receive per-packet value
  • Windows supports only the ECN bits

Contributor guide

Open the contributing guide

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.

Research direction

Start with the listed socket options: IP_TOS, IPV6_TCLASS, IP_RECVTOS, IPV6_RECVTCLASS, TCP_ECN_MODE, and TCP_ENABLE_ECN. Resolve how TOS, DSCP, and ECN should be represented, whether TCP ECN bits are settable, and how per-packet values are received, including Windows' ECN-only support. Done means the behavior and platform differences are specified clearly enough to implement.

Written by the indexing model from the issue text.

Assessment

Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.