Concerns with IPv4 Applications Accessing IPv6 Servers (NAT46)
draft-wing-behave-v4app-v6server-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dan Wing , Cameron Byrne | ||
| Last updated | 2010-02-24 | ||
| 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
Bump-in-the-Stack and Bump-in-the-API allow IPv4 applications to access IPv6 servers, using an in-host NAT46 translator. When used in conjunction with an in-network NAT64, it is also possible for the IPv4 application to access an IPv4 server via an IPv6-only network. This document describes how these functions work in detail, and discusses some concerns especially around IPv4 applications accessing IPv6 servers. These concerns can be reduced by not having IPv4 applications access IPv6 servers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)