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.

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

Jump to bottom

Add subprotocol negotiation #144

Merged
merged 6 commits into from
Dec 12, 2023
Merged

Add subprotocol negotiation #144

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
293eea9
Add subprotocol negotiation
vasilvv Nov 7, 2023
72edef7
Clarify what server puts in the response
vasilvv Nov 20, 2023
b022842
Clarify what do subprotocols mean
vasilvv Nov 20, 2023
985897f
Update draft-ietf-webtrans-http3.md
vasilvv Nov 28, 2023
150f4b2
Update draft-ietf-webtrans-http3.md
vasilvv Dec 12, 2023
c1385cb
Update draft-ietf-webtrans-http3.md
vasilvv Dec 12, 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
22 changes: 22 additions & 0 deletions draft-ietf-webtrans-http3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,6 +197,28 @@ The `webtransport` HTTP Upgrade Token uses the Capsule Protocol as defined in
HTTP-DATAGRAM}} is not required by WebTransport and can safely be ignored by WebTransport
endpoints.

## Subprotocol Negotiation

WebTransport over HTTP/3 offers a subprotocol negotiation mechanism, similar to
TLS Application-Layer Protocol Negotiation Extension (ALPN) {{?RFC7301}}; the
intent is to simplify porting pre-existing protocols that use QUIC and rely on
this functionality.

The user agent MAY include a `WebTransport-Subprotocols-Available` header field
in the CONNECT request, enumerating the possible subprotocols. If the server
receives such a header, it MAY include a `WebTransport-Subprotocol` field in
a successful (2xx) response. If it does, the server SHALL include a single
subprotocol from the client's list in that field. Servers MAY reject the request
if the client did not include a suitable subprotocol.

Both `WebTransport-Subprotocols-Available` and `WebTransport-Subprotocol` are
Structured Fields {{!RFC8941}}. `WebTransport-Subprotocols-Available` is a List
of Tokens, and `WebTransport-Subprotocol` is a Token. The token in the
`WebTransport-Subprotocol` response header field MUST be one of the tokens
listed in `WebTransport-Subprotocols-Available` of the request. The semantics
of individual token values is determined by the WebTransport resource in
question, and are not registered in IANA's "ALPN Protocol IDs" registry.

DavidSchinazi marked this conversation as resolved.
Show resolved Hide resolved
## Limiting the Number of Simultaneous Sessions

This document defines a SETTINGS_WEBTRANSPORT_MAX_SESSIONS parameter that allows
Expand Down
Loading