nanog mailing list archives
Re: 5G roadblock: labor
From: Ca By <cb.list6 () gmail com>
Date: Fri, 3 Jan 2020 14:27:17 -0800
On Fri, Jan 3, 2020 at 2:17 PM William Herrin <bill () herrin us> wrote:
On Fri, Jan 3, 2020 at 2:11 PM Ca By <cb.list6 () gmail com> wrote:You are not using ipv4 today. The scenario you describe, using facetime (iOS) on T-Mobile US, you arenot using ipv4 on the device. T-Mobile does not assign ipv4 addresses to iOS or Android devices in default scenarios, has not for years.If the far end of your facetime call is v4-only, you may need nat64 inthe cloud.... but otherwise no v4 in the flow, and no v4 on the device. AFAIK, that's not correct. T-Mobile does provide IPv4 *on the device* but translates it to IPv6 (464xlat) before the packets leave the device for the network. Regards, Bill Herrin
Eh. True. Semantics, to a degree. T-Mobile does not assign an ipv4 address to the handset. That said, T-Mobile assigns a v6 to the handset, the handset then does 464xlat as you said, assigning itself a special v4 address to v4->v6 nat on handset. And, Bob is your uncle, as they say.
-- William Herrin bill () herrin us https://bill.herrin.us/
Current thread:
- Re: 5G roadblock: labor, (continued)
- Re: 5G roadblock: labor Christopher Morrow (Jan 03)
- Re: 5G roadblock: labor Mark Tinka (Jan 03)
- Re: 5G roadblock: labor Andrey Kostin (Jan 03)
- Re: 5G roadblock: labor Mark Tinka (Jan 03)
- Re: 5G roadblock: labor Mark Tinka (Jan 03)
- Re: 5G roadblock: labor Sabri Berisha (Jan 03)
- Re: 5G roadblock: labor Ca By (Jan 03)
- Re: 5G roadblock: labor William Herrin (Jan 03)
- Re: 5G roadblock: labor Ca By (Jan 03)
- Re: 5G roadblock: labor Joe Hamelin (Jan 06)