Relaying HTTP from IPv4 to IPv6
draft-wing-behave-http-46-relay-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dan Wing | ||
| Last updated | 2009-10-26 | ||
| 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 IPv6-only hosts become commonplace, it is desirable to still have IPv4 clients access those IPv6-only hosts. Due to the size of the IPv4 and IPv6 address spaces, this has proven difficult using pure IP address translation. Rather than trying to support all IP protocols, or even all TCP or UDP applications, this document proposes a mechanism for an IPv4 HTTP client to connect to an IPv6-only HTTP server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)