The Transport-Info HTTP Header
draft-ohanlon-transport-info-header-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Piers O'Hanlon , James Gruessing | ||
| Last updated | 2020-09-04 (Latest revision 2020-03-03) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
|
||
| 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
The Transport-Info header provides a mechanism to transmit network transport related information such as current delivery rate and round-trip time, from a server or a client. This information has a wide range of uses such as client monitoring and diagnostics, or allowing a client to adapt to current network conditions. Note to Readers _RFC Editor: please remove this section before publication_ Source code and issues for this draft can be found at https://github.com/bbc/draft-ohanlon-transport-info-header [1].
Authors
Piers O'Hanlon
James Gruessing
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)