HTTP Connect - Tunnel Protocol For WebRTC
draft-hutton-httpbis-connect-protocol-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Andrew Hutton , Justin Uberti , Martin Thomson | ||
| Last updated | 2014-06-27 | ||
| Replaced by | RFC 7639 | ||
| 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 | Replaced by draft-ietf-httpbis-tunnel-protocol | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-hutton-httpbis-connect-protocol-00.txt
Abstract
This document describes a mechanism to enable HTTP Clients to provide an indication within a HTTP Connect request as to which protocol will be used within the tunnel established to the Server identified by the target resource. The tunneled protocol is declared using the Tunnel- Protocol HTTP Request header field. Label usage relating to the use of HTTP Connect by WebRTC clients (e.g. turn, webrtc) are described in this document.
Authors
Andrew Hutton
Justin Uberti
Martin Thomson
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)