IPv4/IPv6 Interoperation Using the HTTP CONNECT Method
draft-van-beijnum-v6ops-connect-method-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Iljitsch van Beijnum | ||
| Last updated | 2007-07-05 | ||
| 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
As of the deprecation of NAT-PT as a mechanism to allow IPv6-only hosts to connect to IPv4-only hosts, there is no longer a viable way to provide interoperation between IPv4-only and IPv6-only hosts connected to the internet. This document outlines a way to use the HTTP CONNECT method (better known as HTTPS proxying) to accomplish this interoperation for a large (but not the full) set of IP applications. The intent is to provide a base level usability for IPv6-only hosts to remove the need to provide IPv4 connectivity in all cases.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)