WT may not require H3 frames
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 890
- Forks
- 136
- Avg merge
- 14d 20h
- Merged PRs (30d)
- 2
Description
From a mail and a draft update from Lucas Pardue, one of the editors of WT, a minimal WT implementation could be:
| WebTranport |
| Punch | HTTP Semantics |
| Through | HTTP/3 |
| QUIC |
This may not apply to h3-webtransport, just in case you wanna know. :))
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked IETF mail and the draft update first, then inspect the repository's WebTransport and HTTP/3 handling. No file or test entry points are named in the issue. Done means establishing whether a minimal WebTransport implementation can avoid HTTP/3 frames and deciding what repository change, if any, follows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100