IPv6 on mobile networks, was Update to BCP-38?

[cb.list6 at gmail.com (Ca By)]

On Thu, Oct 3, 2019 at 12:40 PM John R. Levine <johnl at iecc.com> wrote:

> In article <d3f78384-9b25-c4c4-495f-5dcc0e0c1925 at satchell.net>,
> Stephen Satchell <nanog at nanog.org> wrote:
> > My AT&T cell phone has both IPv4 and IPv6 addresses.  The IPv4 address
> > is from my access point; the IPv6 address appears to be a public address.
>
> My AT&T cellphone (via MVNO Tracfone) has a 10/8 IPv4 address and IPv6
> address 2600:380:28be:8b34:2504:2096:6ac7:6262.  But when I connect to a
> web site that reports the connecting address, it says I'm
> 2600:387:a:9a2::8.
>
> What's going on there?  Those are both within at&t's 2600:300::/24', but
> am I behind a NAT66?  An aggressive web cache?
>

This is a unique proxying feature of AT&T

Tmobile US, VZ, and Sprint all have IPv6, but only AT&T has this behavior
afaik.



> --
> Regards,
> John Levine, johnl at taugh.com, Primary Perpetrator of "The Internet for
> Dummies",
> Please consider the environment before reading this e-mail. https://jl.ly
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20191003/6020fdad/attachment.html>