HTTP Latency Metrics
draft-vinayak-http-latency-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Vinayak Hegde | ||
| Last updated | 2010-07-30 | ||
| 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 RFC will outline the different components of end-to-end HTTPS Latency Metrics. Each of these components is either a specific protocol or connection-oriented metrics. Taken together each of these components can reveal the characteristics of the application and the it's beaviour and interaction with the underlying protocol. This draft will however not cover the methodology or tools for measuring this and it is outside the scope of the current document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)