[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Big day for IPv6 - 1% native penetration
On Tue, Nov 27, 2012 at 11:28 AM, mike <mike at mtcc.com> wrote:
> On 11/26/12 8:59 PM, Mikael Abrahamsson wrote:
>> On Mon, 26 Nov 2012, Michael Thomas wrote:
>>> I don't see either Apple or Microsoft as being the hindrance. In fact,
>>> both of them seem pretty ready, fsvo "ready". Unlike ISP's by and large. But
>>> I'm pretty sure that both iPhones and Androids are pretty happy about being
>>> in v6 land since I see them showing up in my logs all the time, for the few
>>> providers that have lit up v6.
>> Not on the mobile side. Wifi yes, mobile no.
> You're saying there are no cellular v6 deployments? I'm about 99% certain
> you're wrong. I see v6 addresses in my apache logs all the time and they're
> definitely while they're not on wifi (my site uploads gps data while people
> are skiing,
> so they're usually on cellular).
>>> I'm all for bagging on those two, but it seems pretty unjustified here.
>> What they need to start doing is testing Apps for IPv6 only access
>> capabilitity. This doesn't work today, Apps like Waze, Spotify and others do
>> not work on IPv6 only access.
> Is this the app's fault? What are they doing wrong?
Yes, it is the app's fault.
They are either doing IPv4 literals or IPv4-only sockets
The IPv4 literal issues is when they do "wget http://192.168.1.1" ...
hard coding IPv4 addresses... instead of using an FQDN like "wget
http://example.com". Using an FQDN allows the DNS64 to work
The IPv4 literals fail since the IPv6-only host do not have an ipv4
address to bind to or an ipv4 route to follow. This is the issue that
i believe Skype has ... since they use IPv4 addresses as part of their
signalling. Another one is the URL re-director http://cs.co at Cisco.
For example http://cs.co/6017pZhN will bounce you via an IPv4
address literal .... which means an IPv6-only user gets a webpage that
tries to load an IPv4 address and fails.
The other issue is that the developers choose to use IPv4-only socket
APIs instead of a generic network socket APIs that would allow v4 or
v6. This is usually an education issue. This is what i think is
wrong with the Netflix Android app, they tried to do some low level
network tweaks using the Android NDK but in doing these tweaks they
only used IPv4 socket APIs and fail to work on IPv6 natively or via