Skip to content

add: quic muxer #271

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jan 24, 2023
Merged

add: quic muxer #271

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
69e3e08
add content for quic muxer
salmad3 Dec 7, 2022
783b916
Apply suggestions from code review
salmad3 Dec 12, 2022
bc4e17c
move quic muxer content to quic transport doc
salmad3 Dec 12, 2022
9bdb9d6
edits now that in transport doc
salmad3 Dec 12, 2022
cbf9454
Apply suggestions from code review
salmad3 Jan 12, 2023
d37b346
Apply suggestions from code review
salmad3 Jan 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 0 additions & 15 deletions content/concepts/multiplex/quic.md
View file
Open in desktop

This file was deleted.

7 changes: 7 additions & 0 deletions content/concepts/transports/quic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,13 @@ In addition, a client can make use of QUIC's 0 RTT feature for subsequent connec
when it has already communicated with a certain server. The client can then send
(encrypted) application data even before the QUIC handshake has finished.

### QUIC native multiplexing

A single QUIC packet can carry frames containing stream data from one or more
streams. Since QUIC packets can be decrypted even when they're received out of order, this solves the problem of [HoL blocking](/#key-challenges-with-tcp) that multiplexers applied on top of a TCP connection suffer from: If a packet that contains
stream data for one stream is lost, this only blocks progress on this one stream. All
other streams can still make progress.

## QUIC in libp2p

libp2p only supports bidirectional streams and uses TLS 1.3 by default.
Expand Down