5 ms·

There are two recent, positive things Apple has done for IPv6: 1. They updated the Happy Eyeballs algorithm[1], which is what's caused the jump in the article.

There are two recent, positive things Apple has done for IPv6: 1. They updated the Happy Eyeballs algorithm[1], which is what's caused the jump in the article. 2. Apple will mandate IPv6 support in all apps starting early 2016[2]. [1] https://www.ietf.org/mail-archive/web/v6ops/current/msg22455.html https://www.ietf.org/mail-archive/web/v6ops/current/msg22455... [2] https://developer.apple.com/news/?id=08282015a https://developer.apple.com/news/?id=08282015a

digi_owl 11y ago
"Happy Eyeballs"? Is that the official name, or another case of Apple re-branding?
- thelibrarian 11y ago
  "Happy Eyeballs" (aka Fast Fallback) was created and named by Dan Wing and Andrew Yourtchenko of Cisco. And yes, "Happy eyeballs" is the official name (named because of how happy the eyes of the users will be when they see how fast their IPv6 connection falls back to an IPv4 connection when connecting to a host that does not support IPv6). https://en.wikipedia.org/wiki/Happy_Eyeballs https://en.wikipedia.org/wiki/Happy_Eyeballs
  - p1mrx 11y ago
    Happy Eyeballs is primarily designed let users with broken networks continue connecting to dual-stack web servers. In some cases, it also covers up brokenness on the server end (e.g. publishing AAAA records to nowhere), but that's arguably more of a bug than a feature. Back in 2011, content providers were terrified of enabling IPv6, because the data showed that ~0.1% of users would drop off the map due to broken networks. Happy Eyeballs helped to break the logjam.
- chkuendig 11y ago
  Nope, that's the actual title of IETF RFC 6555 https://tools.ietf.org/html/rfc6555 https://tools.ietf.org/html/rfc6555
sandGorgon 11y ago
Does anyone know the status in Android... And if there's an open bug for this?
- rwg 11y ago
  Android 4+ supports IPv6 on both the cellular and wireless Ethernet interfaces. It only supports stateless address auto-configuration (SLAAC), however, and does not support DHCPv6 at all. (There's a 3+ year old Android DHCPv6 bug that was declined/closed late last year for, IMHO, unconvincing reasons.)
  - sandGorgon 11y ago
    and what about the Happy Eyeball algorithm ? does Android implement it ?
soccerdave 11y ago
I'm curious. Does anyone know if Apples statement actually means you must fully support IPv6 or if you just can't submit an app with hardcoded IPv4 addresses? I just tested one of our apps that uses IPv4 only domain names and it passed according to the setup here "Test for IPv6 DNS64/NAT64 Compatibility Regularly": https://developer.apple.com/library/prerelease/ios/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW1 https://developer.apple.com/library/prerelease/ios/documenta...

digi_owl 11y ago

"Happy Eyeballs"? Is that the official name, or another case of Apple re-branding?

thelibrarian 11y ago
"Happy Eyeballs" (aka Fast Fallback) was created and named by Dan Wing and Andrew Yourtchenko of Cisco. And yes, "Happy eyeballs" is the official name (named because of how happy the eyes of the users will be when they see how fast their IPv6 connection falls back to an IPv4 connection when connecting to a host that does not support IPv6). https://en.wikipedia.org/wiki/Happy_Eyeballs https://en.wikipedia.org/wiki/Happy_Eyeballs
- p1mrx 11y ago
  Happy Eyeballs is primarily designed let users with broken networks continue connecting to dual-stack web servers. In some cases, it also covers up brokenness on the server end (e.g. publishing AAAA records to nowhere), but that's arguably more of a bug than a feature. Back in 2011, content providers were terrified of enabling IPv6, because the data showed that ~0.1% of users would drop off the map due to broken networks. Happy Eyeballs helped to break the logjam.
chkuendig 11y ago
Nope, that's the actual title of IETF RFC 6555 https://tools.ietf.org/html/rfc6555 https://tools.ietf.org/html/rfc6555

sandGorgon 11y ago

Does anyone know the status in Android... And if there's an open bug for this?

rwg 11y ago
Android 4+ supports IPv6 on both the cellular and wireless Ethernet interfaces. It only supports stateless address auto-configuration (SLAAC), however, and does not support DHCPv6 at all. (There's a 3+ year old Android DHCPv6 bug that was declined/closed late last year for, IMHO, unconvincing reasons.)
- sandGorgon 11y ago
  and what about the Happy Eyeball algorithm ? does Android implement it ?

soccerdave 11y ago

I'm curious. Does anyone know if Apples statement actually means you must fully support IPv6 or if you just can't submit an app with hardcoded IPv4 addresses? I just tested one of our apps that uses IPv4 only domain names and it passed according to the setup here "Test for IPv6 DNS64/NAT64 Compatibility Regularly": https://developer.apple.com/library/prerelease/ios/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html#//apple_ref/doc/uid/TP40010220-CH213-SW1 https://developer.apple.com/library/prerelease/ios/documenta...