Re: [v6ops] draft-vf-v6ops-ipv6-deployment

[Alexandre Petrescu <[e-mail]>]

Le 24/03/2021 à 16:59, Gabor LENCSE a écrit :
> Dear Alex,
> 
> On 3/24/2021 4:12 PM, Alexandre Petrescu wrote: [...]
>> Does IPv6 mandate the use of DNS64 and NAT64?
> 
> Of course, not. :)

So I agree with you about that.

> There are several IPv4 as a Services solutions exist. We have
> covered the five most prominent ones 464XLAT, DS-Lite, MAP-E, MAP-T
> and lw4o6 in our I-D: 
> https://tools.ietf.org/html/draft-lmhp-v6ops-transition-comparison-06
> > Your ISP is likely using one of them.

For clarification - my ISP is called 'Free' (it has freedom features).

They offer me paid IPv4 and IPv6 native access at home on ADSL.  It's
one publicly routable IPv4 address and an IPv6 /56 prefix globally
routable prefix (a 'GUP' if I can say so, not a GUA'(ddress)).

Up to now, looking through the configuration interface of my freebox at
home I could not see the options that you mention (464XLAT, DSLITE,
MAP-E, MAP-T, lw4o6).  One might say that they are there invisible, but
I doubt that, I need a proof of it.  How can I check for presence of 
options 464XLAT, DSLITE, MAP-E, MAP-T or lw4o6?

The problems that appear when I try to browse IPv6 sites that absolutely
need IPv4 might be because I turned off the IPv4 stack on my computer's
interface (Windows Properties on the Interface, check off IPv4).  This
operation (turning off IPv4 in a computer) is possible only on Windows,
not on linux, AFAIR.  One cant do 'rmmod ipv4' in linux.

That also explains the fact that installing IPv4-IPv6 translation boxes
(NAT64, 464LAT, etc.) in a network is not sufficient to access IPv4
sites from an IPv6-only computer.

In order to access IPv4 sites from IPv6-only computers one also needs
the IPv4 stack to work ok on that computer and, moreover, it needs some
times software features in the Client that support the 64:: notation of
IPv6 addresses.  For example, thunderbird (a very modern MUA) does not
understand it and gets confused by it.  It takes it for an fqdn, and
does not even try to connect the translation boxes.

This means that if one wants to migrate more to IPv6 then one has to
think about the NAT64 and 464XLAT concepts more outside of the cellular
network concept.

And yes, I agree with you, NAT64 and 464XLAT are good tools to
migrate.  In particular, if one is on a smartphone or other computer
using an OS that cant turn off their IPv4 stacks.

Alex

> 
> Best regards,
> 
> Gábor
> 
> _______________________________________________ v6ops mailing list 
> [e-mail] https://www.ietf.org/mailman/listinfo/v6ops