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 ]
Tore Anderson
tore at fud.no
Mon May 23 09:47:54 CEST 2016
* Vaibhav Bajpai <vaibhavbajpai at me.com> > 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 <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). Very cool, thanks for sharing! Unfortunately though, th websites mentioned in websites.txt that I host on my network and thus am the most interested in (www.e24.no, www.vg.no, www.news247.gr, www.sport24.gr, www.contra.gr) doesn't actually yield any useful graphs. www.vg.no shows the diagram and the map, but they're empty. The others just say «Oops! No data». Another suggestion: allow GET requests (/result?website=foo&asn=bar) to allow for direct linking and bookmarking. Tore
- 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 ]