February 25, 2015 – Dan York Media

Feb 25

Verizon Wireless At 56% IPv6 In Latest World IPv6 Launch Measurements

By Dan York

Some amazing percentages of IPv6 deployment in the February 2015 World IPv6 Launch measurements. As I wrote about on the Deploy360 blog, Verizon Wireless now is showing 56% IPv6 deployment and T-Mobile USA just crossed over 50% IPv6.

If you read the notes on the bottom of the measurements page you can see that Google, Facebook, Akamai, LinkedIn and Yahoo! are all measuring the amount of the amount of IPv6 they are seeing to their sites and reporting that back to the World IPv6 Launch project.

The key point for application developers is that all those people on those networks will be able to natively connect over IPv6 – if your application works over IPv6.

And a reason for caring may be… speed!

If a network is deployed with IPv6 in the main network, as I understand T-Mobile USA has now done, then connections from IPv6 clients can do directly to IPv6 servers. But connections to legacy IPv4 services will need to go through a gateway. Gateways typically introduce some degree of latency / delay, even at a microscopic level.

If your application works with IPv6 then you won’t need to worry about any v6/v4 gateways with any potential delays.

The reality that these measurements show is that IPv6 is very real today – will your app work over IPv6?

P.S. the goal of this book is to help!

IPv6, World IPv6 Launch

Feb 25

Verizon Wireless At 56% IPv6 In Latest World IPv6 Launch Measurements

By Dan York

The key point for application developers is that all those people on those networks will be able to natively connect over IPv6 – if your application works over IPv6.

And a reason for caring may be… speed!

If your application works with IPv6 then you won’t need to worry about any v6/v4 gateways with any potential delays.

The reality that these measurements show is that IPv6 is very real today – will your app work over IPv6?

P.S. the goal of this book is to help! 🙂

IPv6, World IPv6 Launch

Feb 25

Google Finally Kills Off GoogleTalk and XMPP (Jabber) Integration

By Dan York in Standards

GoogleTalk is dead, Jim!

By way of a comment to a post I wrote back in May 2013 about Google seeming to kill off XMPP/Jabber support in Google+ Hangouts (spoiler: They did!), I learned from a friend that the GoogleTalk API was officially deprecated as of February 23, 2015. I confirmed this by finding a Google+ post from Google's Mayur Kamat.

Now, this is not a surprise. Google has been clear that Hangouts was the replacement and also that Hangouts does not support XMPP:

Googletalk end

Still, I'm sad to see the XMPP integration die off. It is just a continuation of the descent of messaging services into walled gardens ... a topic I've been writing about for many years.

UPDATE: Please see the post "No, it’s not the end of XMPP for Google Talk" on the XMPP Standards Foundation site. The XSF notes that XMPP is still used inside of Google and that XMPP federation can still occur with a third-part XMPP client. However, because Google does not support the secure use of XMPP via TLS, many public XMPP servers will not connect to its server. I join the XSF in wishing that Google would embrace secure messaging and better federation. However, given that their product direction is for Hangouts, which does NOT support XMPP, I'm skeptical that we'll ever see any better federation at this point.

On that note, it was really no surprise to see the media reports about Microsoft killing off Google and Facebook chat support in its Outlook.com service. Microsoft made this Google integration available back in May 2013, but today Microsoft really has no choice: