HTTP-initiated Network Tunnelling (HiNT)
draft-pardue-httpbis-http-network-tunnelling-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2019-04-21 (latest revision 2018-10-18) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-pardue-httpbis-http-network-tunnelling-01.txt
https://www.ietf.org/archive/id/draft-pardue-httpbis-http-network-tunnelling-01.txt
Abstract
The HTTP CONNECT method allows an HTTP client to initiate, via a proxy, a TCP-based tunnel to a single destination origin. This memo explores options for expanding HTTP-initiated Network Tunnelling (HiNT) to cater for diverse UDP and IP associations.
Authors
Lucas Pardue (lucaspardue.24.7@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)