| |||||||||||||
How not to get a protocol implementation mergedHow not to get a protocol implementation mergedPosted Jan 21, 2011 7:33 UTC (Fri) by Imroy (guest, #62286)In reply to: How not to get a protocol implementation merged by pukunui Parent article: How not to get a protocol implementation merged
> the first place that IPv4 addresses will run out and where operators will need to offer IPv6 addresses is the mobile space.
Maybe I'm understanding it wrong, but it appears that this protocol is a tunnelling/encapsulation protocol for transporting low-level packets between base stations and their components. It's not involved with the actual internet connectivity of the mobile phones - in the current 2.5G/3G network structure that happens in a specific component (with even more encapsulation - http://laforge.gnumonks.org/weblog/2009/10/27/#20091027-i...). So these base stations and other parts talking UDPCP will likely have private IPv4 addresses and would not cause a problem for IPv6 migration.
Of course, we'd like to move *everything* to IPv6 in the distant (or not so distant) future. But until then I don't see this IPv4-only implementation posing any problems.
(Log in to post comments)
|
|||||||||||||