Skip to content

Proposed text to permit work on adapting stream multiplexing to secure, reliable, and bidirectional byte stream substrates #240

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

Open
LPardue wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Proposed text to permit work on adapting stream multiplexing to secure, reliable, and bidirectional byte stream substrates #240

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
83201d2
Proposed text to permit work on adapting stream multiplexing elsewhere
LPardue Jun 9, 2025
fc168ff
small edits
LPardue Jun 9, 2025
af7a591
Refine text on security providers and TLS
LPardue Jun 16, 2025
ea13d78
Move text to fourth area
LPardue Jun 16, 2025
a213d6c
Proposed congestion control requirement to recharter (#241)
LPardue Jul 3, 2025
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
9 changes: 9 additions & 0 deletions charter/charter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,15 @@ It is chartered to pursue work in the areas detailed below:
to publicly document deployed proprietary extensions or to enable
wider experimentation with proposed new protocol features.

4. The fourth area of work is the specification of how QUIC stream
multiplexing and other application-oriented extensions (e.g. Datagram)
can be adapted to work over a reliable and bidirectional byte stream
substrate. When the substrate is insecure, TLS will be the default
security provider; no effort will be made to enable unprotected
communication without a security provider. Substrates must provide
congestion-management capabilities applicable to their deployment
environments.

Specifications describing how new or existing application protocols
use the QUIC transport layer, called application protocol mappings
below, need not be specified in the QUIC WG, although they can. The
Expand Down