Looking at a trace that I got from Geoff Huston a month or two ago,
there are 25486 IPv6 TCP sessions of which 10748 have a 6to4 source
address.
That's surprisingly high, showing that the answer depends greatly on
the point of observation, and explains why operators really need
to try to run a decent 6to4 relay service as long as so many
such clients are observed. Which is why disabling 6to4 in clients
has to be the priority; it's far too soon to decommission the
relays.
Regards
Brian Carpenter
On 2011-07-29 09:12, Tim Chown wrote:
On 28 Jul 2011, at 21:51, Michel Py wrote:
Lorenzo,
Lorenzo Colitti wrote:
http://www.google.com/intl/en/ipv6/statistics/
Thanks for the update.
Clarification: in your stats, is AS12322's traffic classified as native
or as 6to4/teredo?
Hi,
I just ran a search through our Netflow logs of the most recent flows
attempting to traverse our enterprise border and this showed:
2002::/16 (6to4):
Summary: total flows: 562468, total bytes: 6.2 G, total packets: 11.0 M
2001::/32 (Teredo):
Summary: total flows: 1363887, total bytes: 4.9 G, total packets: 10.1 M
Other:
Summary: total flows: 23681562, total bytes: 483.1 G, total packets: 546.9 M
Teredo appears skewed by one host's behaviour which I'll be looking into,
otherwise it's about what I'd expect with around 1% by volume being 6to4.
Tim
------------------------------------------------------------------------
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf