In "Colitti-A_strategy_for_IPv6_adoption.Z8ri.pdf" Google states: |Peering instead of transit | |- Avoid bad routes by not taking transit | - We don't have an IPv6 transit provider | - But we peer with almost everybody | |- Avoid suboptimal routing by peering with user networks directly | - Guarantees better service and low latency | - Since both networks care, IPv6 issues get fixed | |- We're happy to peer with - or close - to you | - Aggressive, user-driven rollout | - Check peeringdb and/or email peering@ FWIW, I already sent them an email asking them to peer with M-Net. Maybe interesting for sixxs: |IPv6 Trusted Tester program | | - IPv6 access to most Google web properties | - Works by DNS resolver IPv4 address | - If the user's DNS resolver is in a whitelist, it will receive AAAA answers => sixxs could possibly provide a whitelisted dns resolver for its users (With e.g. dnsmasq you can say 'use resolver foo as default, but bar for *.google.com) Also interesting: Colitti-Global_IPv6_statistics_-_Measuring_the_current_state_of_IPv6_for_ordinary_users.xD5A.pdf According to this paper 50% of the observed successfull IPv6 connections in their field test came from Mac-OS users behind an Airport Extreme, which Apple ships with preconfigured 6to4 routing.