Re: [v6ops] v6ops-host-addr-availability: A Little Pushback

[Tore Anderson <[e-mail]>]

* STARK, BARBARA H

> Good point. OK, so I change my statement to say that translation
> (like 464XLAT) only applies in an IPv6-only network. I still contend
> that tethering is specific to "3GPP"-type-technology  wireless
> networks.

If you're running virtual machines on your computer, using software
such as VirtualBox, Parallels, KVM, or VMware Workstation; you are in
principle performing tethering.

> > OpenWrt, which most commonly has a wired upstream, does support
> > 464XLAT CLAT operation.
> 
> I think of OpenWRT as router software. I'm not aware of any pure
> hosts using it.

That's right. My point here was that regardless of your uplink being
something wired like Ethernet, DSL, whatever - if you're using OpenWrt
in your home gateway, you can still use 464XLAT as long as you have an
IPv6 uplink and access to a NAT64 service (there are serveral public
ones available over the Internet if you'd like to try it yourself).
I.e., cementing the point that the 464XLAT technology is not specific
to wireless ISPs.

> Do you use 464XLAT inside all the end hosts and offer IPv6-only to
> all hosts inside the data centers? Or do you use it at the edge, and
> provide IPv4 and IPv6 addresses to the hosts? The need to do
> translation (like 464XLAT) is listed in this draft as a justification
> for providing an IPv6 prefix to all end hosts inside all networks
> (including, presumably, inside data centers). I'm still not seeing
> that.

My core network provides NAT64/DNS64 service. Most of the IPv6-only
servers I have are happy with that, since it makes stuff like "git
clone https://github.com/foo/bar" work just fine. So no, far from all
of my IPv6-only servers are using 464XLAT.

However, a minority of the servers need to run software that tries to
do low-level IPv4 stuff directly and fails if it cannot - essentially
because stuff like "ping 8.8.8.8" doesn't work when the node is
IPv6-only. On those servers specifically we activate the 464XLAT CLAT
so that stuff like AF_INET sockets and "ping 8.8.8.8" starts working.
We do not need the server to have a dedicated prefix for this to work,
but it *does* need a second IPv6 address with a global scope.

Tore