NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
draft-bagnulo-behave-nat64-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Marcelo Bagnulo , Philip Matthews , Iljitsch van Beijnum | ||
| Last updated | 2009-07-06 (Latest revision 2009-03-07) | ||
| Replaced by | draft-ietf-behave-v6v4-xlate-stateful | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-behave-v6v4-xlate-stateful | |
| 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
NAT64 is a mechanism for translating IPv6 packets to IPv4 packets and vice-versa. DNS64 is a mechanism for synthesizing AAAA records from A records. These two mechanisms together enable client-server communication between an IPv6-only client and an IPv4-only server, without requiring any changes to either the IPv6 or the IPv4 node, for the class of applications that work through NATs. They also enable peer-to-peer communication between an IPv4 and an IPv6 node, where the communication can be initiated by either end using existing, NAT-traversing, peer-to-peer communication techniques. This document specifies NAT64, and gives suggestions on how they should be deployed.
Authors
Marcelo Bagnulo
Philip Matthews
Iljitsch van Beijnum
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)