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/ipv6-wg@ripe.net/
[ipv6-wg] RIPE NCC Makes Record Number of IPv6 Allocations
- Previous message (by thread): [ipv6-wg] RIPE NCC Makes Record Number of IPv6 Allocations
- Next message (by thread): [ipv6-wg] RIPE NCC Makes Record Number of IPv6 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Arien Vijn
arien.vijn at ams-ix.net
Fri Dec 14 11:26:38 CET 2007
On 14 Dec 2007, at 11:15, <michael.dillon at bt.com> <michael.dillon at bt.com> wrote: [...] > In order to evaluate the strength/weakness of a company's > IPv6 deployment, it seems to me that a better measure is > the amount of traffic going through IPv6 public peering > points Please see: https://www.ams-ix.net/technical/stats/sflow_stats_ipv6.html That is native IPv6 based on the ethertype in sFlow samples. > and the amount of IPv6 encapsulated in IPv4 that > travels though IPv4 peering points. That would mean that we have to look into the frame content. Which is controversial as we might get on a slippery slope there. -- Arien
- Previous message (by thread): [ipv6-wg] RIPE NCC Makes Record Number of IPv6 Allocations
- Next message (by thread): [ipv6-wg] RIPE NCC Makes Record Number of IPv6 Allocations
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]