Well, to be honest that wasn't even clear to me ;-) I just am reading up on the RFC and it looks like it doesn't have to be on the end host necessarily:
http://tools.ietf.org/html/rfc6877#section-6.5 Time for me to read the rfcs in their entirety On 25 November 2013 15:22, Eric Vyncke (evyncke) <evyn...@cisco.com> wrote: > Dick > > 464XLAT is contained within a host, so, you will need an implementation for > all your end host (laptop, tablets, ...) > > But, I am sure that you already know that ;-) > >> -----Original Message----- >> From: ipv6-ops-bounces+evyncke=cisco....@lists.cluenet.de >> [mailto:ipv6-ops-bounces+evyncke=cisco....@lists.cluenet.de] On >> Behalf Of Dick Visser >> Sent: lundi 25 novembre 2013 14:20 >> To: ipv6-ops@lists.cluenet.de >> Subject: 'Upgrading' NAT64 to 464XLAT? >> >> hi guys >> >> We've been running a NAT64/DNS64 set-up for a while now on some parts >> of >> our office network. >> This seems to work well, but it doens't work for everything (e.g. >> Skype >> etc). >> If those apps were working, it would be possible to actually use if >> for >> production. >> I was reading about 464XLAT, and from what I understand, this is more >> or >> less NAT64, but with some sort of local (RFC1918) IPv4 in the mix. >> >> For phones this is done using a special daemon that provides a local >> IPv4 address. >> I'd like to 'upgrade' out existing NAT64/DNS64 setup to do 464XLAT, >> but >> there aren't many docs about how to set 464XLAT to begin with. >> I've seen https://sites.google.com/site/tmoipv6/464xlat, and I asked >> around here and there. >> A schema with actual addresses would be nice, but I can't find that. >> >> Since we have an office set-up with, I assume I should configure the >> IPv6-only VLAN so that RFC1918 addresses are handed out on it as >> well? >> >> What I don't understand, if a device gets an RFC1918 IPv4 address, >> and a >> global IPv6 address, how would it be possible that apps that support >> IPv6-only use the IPv6 path? I can imagine that some applications >> still >> prefer to take the IPv4 path? >> >> >> Thanks!! >> >> >> >> >> >> -- >> Dick Visser >> System & Networking Engineer >> TERENA Secretariat >> Singel 468 D, 1017 AW Amsterdam >> The Netherlands > -- Dick Visser System & Networking Engineer TERENA Secretariat Singel 468 D, 1017 AW Amsterdam The Netherlands