<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Oct 23, 2021 at 10:33 AM Michael Thomas <<a href="mailto:mike@mtcc.com">mike@mtcc.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
<div>
<p>So I'm curious how the mobile operators deploying ipv6 to the
handsets are dealing with ipv4. The simplest would be to get the
phone a routable ipv4 address, but that would seemingly exacerbate
the reason they went to v6 in the first place. </p></div></blockquote><div dir="auto">First, consider that the 3 major cell carriers in the usa each have 100 million customers. Also, consider they all now have a home broadband angle. Where do 100 million ipv4 addresses come from? Not rfc 1918, not arin, … and we are just talking about customer ip addresses, not considering towers, backend systems, call centers, retail …. </div><div dir="auto"><br></div><div dir="auto">So the genesis of 464xlat / rfc 6877 is that ipv4 cannot go where we need to go, the mobile architecture must be ipv6 to be comply with the e2e principle and not constrain the scaling of the customers / edge. Other cell carriers believe in operating many unique ipv4 networks … like a <a href="http://10.0.0.0/8">10.0.0.0/8</a> per metro, but even that breaks down and cannot scale… and you end up with proxies / nats / sbcs everywhere just to make internal apps like ims work, which is a lot of state. </div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div><p dir="auto">Are carriers
NAT'ing somewhere along the line? If so, where? Like does the
phone encapsulate v4 in 4-in-6? Or does the phone get a net 10
address and it gets NAT'd by the carrier? </p></div></blockquote><div dir="auto"><br></div><div dir="auto">~80% of traffic goes to fb, goog, yt, netflix, bing, o364, hbomax, apple tv, … all of which are ipv6. So, only 20% of traffic requires nat, when you have ipv6. I am hoping tiktoc and aws move to be default on for ipv6 soon. </div><div dir="auto"><br></div><div dir="auto">The nats dont scale well and take the brunt of attacks, so services that require nat suffer. Real shame, but they have a path to improve performance by deploying ipv6. Thats why performance driven companies use ipv6 (fb, goog, akamai, …)</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div><p dir="auto"><br>
</p>
<p>It seems also for mobile carriers there is incentive for as much
transit as possible for native v6 to the servers. Or is the
deployment of v6 mainly within the carrier network itself and it's
NAT'd somewhere?</p>
<p>Basically what does a typical v6/v4 architecture look like for a
mobile carrier these days?</p>
<p>Mike<br>
</p>
<p><br>
</p>
<div>On 10/23/21 8:13 AM, Brian Johnson
wrote:<br>
</div>
<blockquote type="cite">
<br>
<div><br>
<blockquote type="cite">
<div>On Oct 23, 2021, at 8:30 AM, Ca By <<a href="mailto:cb.list6@gmail.com" target="_blank">cb.list6@gmail.com</a>>
wrote:</div>
<br>
<div>
<div class="gmail_quote" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<div dir="auto" style="font-family:Helvetica">87% of mobiles in the usa are
ipv6</div>
<div dir="auto" style="font-family:Helvetica"><br>
</div>
<div dir="auto" style="font-family:Helvetica">
<div style="font-family:Helvetica"><a href="https://www.worldipv6launch.org/measurements/" target="_blank" style="font-family:Helvetica">https://www.worldipv6launch.org/measurements/</a></div>
<br>
</div>
<div dir="auto" style="font-family:Helvetica"><br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
Agreed. When they have to connect to an IPv4 only host, they do
some type of AFTR. These devices have never known a world
outside of this situation. That is a major difference.</div>
<div>
<div><br>
</div>
<br>
<blockquote type="cite">
<div>
<div class="gmail_quote" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<div dir="auto" style="font-family:Helvetica"><br>
</div>
<div dir="auto" style="font-family:Helvetica"><br></div></div></div></blockquote></div></blockquote></div><div><blockquote type="cite"><div><blockquote type="cite"><div><div class="gmail_quote" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><div dir="auto" style="font-family:Helvetica">
</div>
<blockquote class="gmail_quote" dir="auto" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;font-family:Helvetica;border-left-color:rgb(204,204,204)"><br>
--<span style="font-family:Helvetica"> </span><br>
Bryan Fields<br>
<br>
727-409-1194 - Voice<br>
<a href="http://bryanfields.net/" rel="noreferrer" target="_blank" style="font-family:Helvetica">http://bryanfields.net</a></blockquote>
</div>
</div>
</blockquote>
</div>
<br>
</blockquote>
</div>
</blockquote></div></div>