enterprise IPv6 only client computers and IPv4 connectivity

[Ted Mittelstaedt]

On 4/30/2013 12:03 AM, Mikael Abrahamsson wrote:
>
> Hi,
>
> If an enterprise today would decide that they're going to run IPv6 only
> on their LAN,

They wouldn't.

This is a self-defeating question.  In other words, if you seriously
contemplated doing this you would know whether you could do it or not.

You would start small, with ONE IPv6-only system, and find some
proprietary translator/proxy/whatever box, and test it with all your
apps.  Almost certainly many would break.  So you would work with the
developer and they would write fixes into their code and you would
try it again.  After about 6 months to a year you might have something 
that would work.

Most likely you would not be able to interest someone large like Cisco
as they already have their own testers.  You would have to find some
small outfit and be willing to pay $$$ to them to get them to do it.
I can think of several of the open source/closed source firewall vendors
that might be interested if you offered enough money.

Ted

> they would have recent Win7|Win8|OSX|Ubuntu clients on
> their client computers, what mechanism would they use to access IPv4
> Internet?
>
> My thinking immediately went to DS-lite, NAT64/DNS64 and MAP-E, but I
> NAT64/DNS64 isn't "good enough" without 464XLAT, and DS-lite and MAP-E
> requires additional software on most of these operating systems, right?
> Are these kinds of client software even available?
>
> What other mechanism could be used to achieve IPv4 Internet reachability
> over IPv6 only access for end-systems? HTTP proxy or SOCKS-proxy also
> sounds too cumbersome.
>