Hi
RFC 6296 defines IPv6-to-IPv6 Network Prefix Translation, which is basically NAT66. The difference to what we ususally do with NAT44 is that - as the name implies - it is a one to one mapping, not a one to many as in NAT44.
The main rule and goal still is to avoid any form of NAT where ever possible.
Silvia
Last Wiki Answer Submitted: May 22, 2012 5:54 pm by SilviaHagen565 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
One of the issues I’ve come across in my experience is deeper than this; it’s setting up a corporate network w/o subnetting and using dynamic IP addresses.
This combination makes it almost impossible to trace issues because you don’t know where machines are in a building. The largest corporate network I have seen this with is 1K machines – and when 100 of them are in the same room, and you have uneducated users, trying to figure out which machine(s) have software broadcast issues, for one example, render this impossible to trace without interrupting everyone’s work to gather the current IP address(es). Do away with NAT and dynamic IPs in your environment and you’ll be MUCH better equipped to deal with network issues.
One of the issues I’ve come across in my experience is deeper than this; it’s setting up a corporate network w/o subnetting and using dynamic IP addresses.
This combination makes it almost impossible to trace issues because you don’t know where machines are in a building. The largest corporate network I have seen this with is 1K machines – and when 100 of them are in the same room, and you have uneducated users, trying to figure out which machine(s) have software broadcast issues, for one example, render this impossible to trace without interrupting everyone’s work to gather the current IP address(es). Do away with NAT and dynamic IPs in your environment and you’ll be MUCH better equipped to deal with network issues.