Re: [v6ops] reclassify 464XLAT as standard instead of info

[Erik Kline <[e-mail]>]

https://android.googlesource.com/platform/external/android-clat/

On 20 September 2017 at 21:54, Alexandre Petrescu
<[e-mail]> wrote:
> No need to stress terms like billions; that's what modem manufacturers put
> on the market too routinely.  Maybe we can talk trillions of IoT devices.
> Maybe we can use the SI prefixes, like exa, or peta.
>
> That aside, I would like to ask you whether the CLAT src on Android is
> something I could look at?
>
> Alex
>
>
> Le 20/09/2017 à 08:03, Erik Kline a écrit :
>>
>> There seem to be some misconceptions flying around here.
>>
>>> Well, I dont think 464XLAT is deployed anywhere else than on cellular.
>>> These
>>> are the big numbers that the Original Poster talked about: miliions of
>>> users
>>> - they are on cellular.
>>
>>
>> 464xlat is a client-side bit of code (the NAT64+DNS64 in the network
>> is the "other half").  It is primarily implemented in mobile devices,
>> and primarily in Android, to be more specific.
>>
>> As such, the number of 464xlat capable nodes is numbered in the
>> /billions/.
>>
>> There are also some wifi (and wired) networks that are IPv6-only with
>> NAT64+DNS64; mobile networks aren't the only ones.
>>
>> NAT64+DNS64 is easily the single most successful IPv6 transition
>> technology on the planet ([a] if one excludes "dualstack", [b] queue
>> the Sean Spicer jokes).  464xlat can help ease things on the client
>> side, but it's not the only way to do it (cf. iOS).
>>
>