This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] v4 versus v6 -- who connects faster?
- Previous message (by thread): [ipv6-wg] v4 versus v6 -- who connects faster?
- Next message (by thread): [ipv6-wg] v4 versus v6 -- who connects faster?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nico CARTRON
nicolas at ncartron.org
Mon May 23 14:15:22 CEST 2016
Hi Vaibhav, On 23 May 2016 at 08:51:27, Vaibhav Bajpai (vaibhavbajpai at me.com) wrote: Dear v6 WG, Here [a] is a toy v6 service I came up with during the RIPE Atlas hackathon over this weekend. Thought I share this along: [a] http://goo.gl/hbzbwD You enter a dual-stacked website (ALEXA top 10K) and it shows you the difference in TCP connect times over v4 and v6 as seen by all dual-stacked RIPE Atlas probes (~1.3K probes). You can also filter the visualisation from a specific origin-AS. This additional filter can be useful to view performance towards a website from a specific origin-AS (say DTAG). Disclaimer: This is an outcome of a 1.5d long hackathon project. As such, the codebase is possibly inundated with bugs. Please don’t see it as a production service :-) Nice job, congratulations. Out of curiosity, I tried accessing it from the NAT64 Wifi network at RIPE72, and http://dragon.eecs.jacobs-university.de:5000 seems not to work for some reason. Thoughts? Cheers, -- Nico -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ipv6-wg/attachments/20160523/de44aeaa/attachment.html>
- Previous message (by thread): [ipv6-wg] v4 versus v6 -- who connects faster?
- Next message (by thread): [ipv6-wg] v4 versus v6 -- who connects faster?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]