Unbound Server Push (USP) for HTTP/QUIC
draft-pardue-quic-http-unbound-server-push-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Lucas Pardue | ||
| Last updated | 2019-01-02 (Latest revision 2018-07-01) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
This document defines an HTTP semantic extension, Unbound Server Push (USP), which allows HTTP resources to be pushed without the need for a prior HTTP request. HTTP/QUIC clients opt in to this feature via an HTTP/QUIC setting.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)