| Exam 300-101 | Question id=455 | Infrastructure Services |
Which methods of deployment can you use when implementing NAT64?
| A. |
stateless | |
| B. |
stateful | |
| C. |
manual | |
| D. |
automatic | |
| E. |
static | |
| F. |
functional | |
| G. |
dynamic |
While stateful and stateless NAT64 perform the task of translating IPv4 packets into IPv6 packets and vice versa, there are important differences. The following table provides a high-level overview of the most relevant differences.
Differences Between Stateless NAT64 and Stateful NAT64
| Stateless NAT64 | Stateful NAT64 |
|---|---|
| 1:1 trtanslation | 1:N translation |
| No conservation of IPv4 address | Conserves IPv4 address |
| Assures end-to-end address transparency and scalability | Uses address overloading, hence lacks in end-to-end address transparency |
| No state or bindings created on the translation | State or bindings are created on every unique translation |
| Requires IPv4-translatable IPv6 addresses assignment (mandatory requirement) | No requirement on the nature of IPv6 address assignment |
| Requires either manual or DHCPv6 based address assignment for IPv6 hosts | Free to choose any mode of IPv6 address assignment with Manual, DHCPv6, SLAAC |