We actively monitored the IPv6 networks throughout the meeting and we have some statistics to share as a result.
Everyone likes lists so we'll start with the top 25 domains queried on the IPv6 networks during the meeting. The results are not purely indicative of where people were pointing their web browsers to because of reverse DNS which accounts for arin.net being the number one domain on the list.
The most widely used protocol was HTTP following by DNS and various mail and instant messaging protocols. We saw very little SSH and other such traffic which implies that not many people were attempting to do work over the IPv6 networks. The fact that NAT-PT breaks most (if not all) VPN clients probably has something to do with that. Throughput on the IPv6 networks was greatest during the IPv6 Main Event on Tuesday evening though the following throughput graph does make it apparent that people were using the IPv6 only networks throughout the meeting.
This next graph show the number of hosts sending data over the IPv6 networks. It shows both local and remote hosts. This gives a clear picture of when the network was in use during the meeting. You can clearly see the spike in usage during the IPv6 Main Event.
The next graph show protocol usage. Unfortunately HTTP dominates this graph making it difficult to determince what other protocols were used. We'll post individual protocol graphs in an attempt to make up for that.
Here's a graph of HTTP traffic only. HTTP was the dominate protocol in use. The huge spike on Monday was a certain systems admin downloading Linux ISOs.
Email protocols were the second most popular application protocol used on the Ipv6 network. The following graphs show traffic for SMTP, POP3 and IMAP.
Here's a graph depicting DNS traffic during the meeting. Again, there is a clear spike during the IPv6 Main Event.
The following graphs show the various packet sizes seen during the meeting.