Expanding on Fred's concerns about ways in which NAT66 can be
defeated, the NAT66 discussion only covered in detail a very specific
deployment in which a NAT66 translator (or perhaps a few) are placed
between an "edge" network and the "core". That deployment scenario is
the one we usually think of, as it's the usual deployment model for
NAT in IPv4. If there is a chance NAT66 might be deployed in other
scenarios, some of which might be unanticipated in the current NAT66
docs. I think it's important to analyze other NAT66 deployments -
multiple NAT66 in a path, routing that results in the use of multiple
paths, NAT66-inverse at a destination that "unNATs" the effect of a
NAT66 - so we fully understand the effects of NAT66.
- Ralph
_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66