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
Eric Vyncke (evyncke) evyn...@cisco.com writes:
464XLAT is contained within a host, so, you will need an
implementation for all your end host (laptop, tablets, ...)
I cannot see anything in RFC 6877 preventing a CLAT gateway serving more
than one host.
Bjørn
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
On 11/25/2013 05:20 AM, Dick Visser wrote:
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).
When it was first being considered there was a non-zero number of us who
made
* Dick Visser
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
This is implemented in Android - its wireless hotspot feature works just
fine using IPv6-only + 464XLAT as the upstream mobile
Tore Anderson t...@fud.no writes:
* Dick Visser
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
This is implemented in Android - its wireless hotspot feature works just
fine using
