Synthesise the IPv6 address a NAT64 gateway maps an IPv4 destination to, and size the translator's state table.
RFC 6052 embeds the IPv4 address in the low bits of a NAT64 prefix. With a /96 the whole address fits in the last two groups, so the mapping is a direct hex conversion. Each translated flow consumes a state entry and a port on the translator. IPv6-only networks reach the legacy internet through NAT64, and the translator's state table — not bandwidth — is what fails first under load.
NAT64
With the well-known /96 prefix the 32-bit IPv4 address is appended directly, giving prefix::a.b.c.d in hex form.
With the well-known /96 prefix the 32-bit IPv4 address is appended directly, giving prefix::a.b.c.d in hex form. RFC 6052 embeds the IPv4 address in the low bits of a NAT64 prefix. With a /96 the whole address fits in the last two groups, so the mapping is a direct hex conversion. Each translated flow consumes a state entry and a port on the translator.
IPv6-only networks reach the legacy internet through NAT64, and the translator's state table — not bandwidth — is what fails first under load.
This calculator takes 4 inputs: IPv4 destination, NAT64 prefix, Concurrent sessions, State per session. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.