litespeedtech / litespeedtech/qmin
Do not require redundant REUSE_ENTRY command
- Dominant language
- C
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
[Section 7.1.1](https://tools.ietf.org/html/draft-tikhonov-quic-qmin-00#section-7.1.1) of the first draft states that
> If the encoded name component refers to an existing entry, this entry is reused as described in Section 7.1.2.
This is a wasted byte. The reuse of existing entry in this case is implied and should be inferred by the decoder.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with Section 7.1.1 of the linked QMIN draft and compare its handling of existing name entries with Section 7.1.2. Determine how the decoder should infer reuse without a redundant REUSE_ENTRY command, then verify the protocol behavior in the C implementation and its tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100