| |||||||||||||
How not to get a protocol implementation mergedHow not to get a protocol implementation mergedPosted Jan 20, 2011 8:39 UTC (Thu) by ericc72 (guest, #41737)In reply to: How not to get a protocol implementation merged by pukunui Parent article: How not to get a protocol implementation merged
I'm not an expert on this stuff, but my understanding is that most mobile operators, when it comes to stuff done that needs an IP address, often just uses addresses in the private space so really this in not an issue with conflict with the number of public IP addresses. It is kind of like a lot of DSL connections, where you are getting issued a private IP address by the provider and they do NAT at their central office onto the public internet.
(Log in to post comments)
How not to get a protocol implementation merged Posted Jan 20, 2011 11:11 UTC (Thu) by foom (subscriber, #14868) [Link]
Well, T-mobile USA, at least, doesn't use official private addresses, because they would conflict with the addresses on users' network's when people are connected via cell and via Wifi. T-mobile instead uses (unrouteable, NATed) addresses in the 25.* network, which is assigned to the UK Ministry of defense. But yes, they don't have to worry about running out of addresses at least...
|
|||||||||||||