Tracking Issue: QUIC 0.5-RTT Optimization
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
https://github.com/libp2p/go-libp2p/pull/1959 proposes to prioritize making 0.5-RTT data in QUIC usable to send Identify data immediately. This would cut off 1 RTT from the QUIC handshake, bringing the time it takes to establish a libp2p QUIC connection + run Identify from 2 to 1 RTTs.
Done Criteria:
- [ ] https://github.com/libp2p/specs/issues/498
- [ ] enable 0.5-RTT data in quic-go: https://github.com/lucas-clemente/quic-go/issues/3634
- [ ] introduce an `EarlyListener` interface that returns connections that are still handshaking, then use those for Identify
- [ ] write a blog post
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing PR #1959 and the linked libp2p specification issue and quic-go issue to understand the required 0.5-RTT behavior. Then trace how Identify currently uses connections and assess the proposed EarlyListener interface. Done means the specification, quic-go support, early Identify path, and blog post criteria are all completed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100