describe how to demultiplex QUIC and WebRTC
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.8k
- Forks
- 320
- Avg merge
- 11d 15h
- Merged PRs (30d)
- 1
Description
It should be possible to differentiate between QUIC and WebRTC by looking at the QUIC bit (0x40) of the first byte of the packet.
Running QUIC and WebRTC on the same socket would make address discovery easier.
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
No file or test is named; start by locating the relevant networking specification pages for QUIC and WebRTC in this repository. Document how the first-byte QUIC bit distinguishes the protocols and explain the benefit of sharing a socket for address discovery.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100