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/address-policy-wg@ripe.net/
[address-policy-wg] 2007-08 New Policy Proposal (Enabling Methods for Reallocation of IPv4 Resources)
- Previous message (by thread): [address-policy-wg] 2007-08 New Policy Proposal (Enabling Methods for Reallocation of IPv4 Resources)
- Next message (by thread): [address-policy-wg] 2007-08 New Policy Proposal (Enabling Methods for Reallocation of IPv4 Resources)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Iljitsch van Beijnum
iljitsch at muada.com
Mon Oct 29 22:23:53 CET 2007
On 29 okt 2007, at 17:47, JORDI PALET MARTINEZ wrote: > The fact is that there is much more IPv6 traffic that what we believe, I'm quickly approaching my posting limit for the day (week?) but I can't resist telling you the following story: I recently found myself somewhere where BitTorrent is severely throttled. Although I can download over HTTP at megabytes per second, BitTorrent downloads wouldn't go faster than 10 kilobytes per second. Turns out that the newest Azureus (BitTorrent application) supports IPv6. Enabled this and lo and behold: I got about 75 peers, 5 of which were IPv6, the rest IPv4. Of the IPv6 peers, one had a regular IPv6 address, the other four 6to4 addresses. Even though the 70 IPv4 peers could only give me 10 kB/s, the 5 IPv6 peers pushed my download well beyond 100 kB/s. So under the right circumstances, a little IPv6 can go a long way.
- Previous message (by thread): [address-policy-wg] 2007-08 New Policy Proposal (Enabling Methods for Reallocation of IPv4 Resources)
- Next message (by thread): [address-policy-wg] 2007-08 New Policy Proposal (Enabling Methods for Reallocation of IPv4 Resources)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]