Skip to main content

Applying Per-Session Limits for WebTransport
draft-thomson-webtrans-session-limit-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
Authors Martin Thomson , Eric Kinnear
Last updated 2023-10-03 (Latest revision 2023-04-01)
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

Limits to how a WebTransport session uses QUIC resources like streams or data can help limit the effect that one WebTransport session has on other uses of the same HTTP/3 connection. This describes mechanisms for limiting the number of streams and quantity of data that can be consumed by each WebTransport session.

Authors

Martin Thomson
Eric Kinnear

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)