Hi, Dave, Le 29 oct. 2010 à 03:31, Dave Thaler a écrit : >> ... >> Another possibility is for the internal system to consider the "external" >> address >> provided by NAT-66 as a "virtual interface", similar to what would be >> obtained >> for example by a tunnel to the external gateway. That means the internal >> systems could learn the available address through some configuration >> function. > > That's what SAF is.
Agreed (what SAF "was", to be purist ;-)) I hope we can discuss once more, in Beijing, the relationship between "SAF + stateless NAT66", on one hand, and the "multihoming application of SAM" on the other hand (SAM/TRAM as it will now be called, for TRAnsparent Multihoming). As we noted already, they have much in common. In my understanding, SAM/TRAM is more complete in that: - It includes a mechanism for the right CPE selection in case of multihoming with PAs. - It permits a receiving host to know, when communicating with another host of its site, to know whether the source address used by the source application was its ULA or a global address. > >> Centralized DHCP servers come to mind, e.g. a DHCPv6 option providing the >> translation value. > > Yes, that's one valid SAF mechanism. Yes, idem for SAM parameters. Regards, RD _______________________________________________ nat66 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nat66
