You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
maxsharabayko
changed the title
Section "Why not RTP" on multiplexing
Section "Why not RTP" on multiplexing in QUIC Datagrams
Mar 28, 2022
Section 11.4 "Why not RTP" of the QuicR Arch document has the following statement:
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:
The text was updated successfully, but these errors were encountered: