Le 26 oct. 2010 à 19:04, Christian Huitema a écrit : > The NAT66 draft enables NAT to rewrite the IPv6 header in a "checksum > compatible" way. NAT66 don't have to go fetch the UDP or TCP header and whack > the checksum. That is certainly a simplification, but it comes at a cost. > Since there is a simple mapping between internal and external subnets, the > external addresses carry information about the internal topology. How is that > as a tradeoff?
In my understanding, a NAT66 doesn't hides the internal topology (while the stateful NAT66 does, and does better regarding privacy). Any CPE that includes a FW having a stateful processing anyway, I personally have doubts that that there is a need for stateless NAT66's in CPEs. But if people believe they know whet they do with NAT66's, and prefer to have them stateless, why not. It's up to them. RD _______________________________________________ nat66 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nat66
