Skip to content
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.

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

Section "Why not RTP" on multiplexing in QUIC Datagrams #36

Open
maxsharabayko opened this issue Mar 28, 2022 · 0 comments
Open

Section "Why not RTP" on multiplexing in QUIC Datagrams #36

maxsharabayko opened this issue Mar 28, 2022 · 0 comments

Comments

@maxsharabayko
Copy link
Contributor

Section 11.4 "Why not RTP" of the QuicR Arch document has the following statement:

QUIC adequately handles multiplexing, security, and transport feedback (except ack timestamps which require extensions proposed in drafts that have not yet been adopted by the QUIC WG).

The statement is not fully correct In the case of QUIC DATAGRAMS. They don't offer stream multiplexing according to the Internet-Draft Section 5.1. Multiplexing Datagrams:

Identifiers used to multiplex different kinds of datagrams, or flows
of datagrams, are the responsibility of the application protocol
running over QUIC to define. The application defines the semantics
of the Datagram Data field and how it is parsed.

@maxsharabayko maxsharabayko changed the title Section "Why not RTP" on multiplexing Section "Why not RTP" on multiplexing in QUIC Datagrams Mar 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant