Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers
RFC 6146
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2025-01-16
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes stateful NAT64 translation, which allows IPv6-only clients to contact IPv4 servers using unicast … Received changes through RFC Editor sync (changed abstract to '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.') |
|
2015-10-14
|
(System) | Notify list changed from behave-chairs@ietf.org, draft-ietf-behave-v6v4-xlate-stateful@ietf.org to (None) |
|
2014-05-06
|
(System) | Posted related IPR disclosure: Hitachi, Ltd.'s Statement about IPR related to RFC 6146 |
|
2011-04-28
|
Cindy Morgan | State changed to RFC Published from RFC Ed Queue. |
|
2011-04-27
|
(System) | RFC published |