Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
draft-v6ops-rfc6146-bis-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Marcelo Bagnulo , Philip Matthews , Jordi Palet Martinez | ||
| Last updated | 2026-02-20 | ||
| Replaced by | draft-ietf-v6ops-rfc6146-bis | ||
| 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-v6ops-rfc6146-bis | |
| 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
This document describes stateful NAT64 translation, which allows IPv6-only clients to contact IPv4 servers using unicast UDP, TCP, or ICMP. One or more public IPv4 addresses assigned to a NAT64 translator are shared among several IPv6-only clients. When stateful NAT64 is used in conjunction with DNS64, no changes are usually required in the IPv6 client or the IPv4 server.
Authors
Marcelo Bagnulo
Philip Matthews
Jordi Palet Martinez
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)