Differences

This shows you the differences between two versions of the page.

--- ipv6 [2010/09/10 10:19] – faltin
+++ ipv6 [2022/09/07 08:16] (current) – fix link to mailing lists morten
@@ Line 1: / Line 1: @@
 ====== IPv6 address mechanims in NAV ======
-The basis for
+[[http://www.uninett.no/|UNINETT]] has made available statistics on the number of IPv6-active hosts in the
-[[https://ow.feide.no/gigacampus:ipv6status|UNINETT's IPv6 statistics]]
+Norwegian universities and university colleges.
-is data collected by NAV (Network
+[[https://ow.feide.no/gigacampus:ipv6status_english|The statistics are available online]].
-Administration Visualized).  This document describes the system in use by NAV
+The basis for the statistics is data collected by NAV (Network Administration Visualized).
-.5 (but being improved in 3.6).
 ===== Data structures =====
@@ Line 29: / Line 28: @@
 First defined in RFC 1213, later revised in RFC 4293.
-IPv4 address mappings are collected from ipNetToMediaTable.  This table has
+IPv4 address mappings are collected from ''ipNetToMediaTable''.  This table has
 been deprecated in the revised IP-MIB.  The revised MIB contains
-ipNetToPhysicalTable, which maps both IPv4 and IPv6 addresses, but
+''ipNetToPhysicalTable'', which maps both IPv4 and IPv6 addresses.  (:!: NAV versions prior to 3.6 did not support the revised table)
-unfortunately, NAV 3.5 does not support this table.
 ==== IPv6-MIB ====
@@ Line 39: / Line 37: @@
 deprecated.  Still in use by several vendors, though.
-IPv6 address mappings are collected from ipv6NetToMediaTable.
+IPv6 address mappings are collected from ''ipv6NetToMediaTable''.
 ==== CISCO-IETF-IP-MIB ====
@@ Line 46: / Line 44: @@
 (finally published in RFC 4293).
-IPv6 address mappings are collected from cInetNetToMediaTable.
+IPv6 address mappings are collected from ''cInetNetToMediaTable''.
 ===== Algorithm =====
@@ Line 62: / Line 60: @@
 Statistics on IPv6 usage are obtained by examining NAVs ARP database table.
-The number of active IP addresses of each address family (v4, v6) at any given
+The number of active IP addresses of each address family (v4, v6), and the number of unique MAC addresses in use at any given
 time can be extracted from this table and used to create aggregate statistics
-across [[https://ow.feide.no/gigacampus:ipv6status||a number of NAV installations in the Norwegian NREN]].
+across [[https://ow.feide.no/gigacampus:ipv6status|a number of NAV installations in the Norwegian NREN]].  The numbers in UNINETT's published graphs count the number of unique MAC addresses seen, so users employing IPv6 privacy extensions should only be counted once per institution.
 ===== Machine Tracker =====
-The IPv6 data is of course utilized several places in NAV, in particular in [[macinetracker|the Machine tracker]] where a NAV user can
+The IPv6 data is of course utilized several places in NAV, in particular in [[machinetracker|the Machine tracker]] where a NAV user can
 track the whereabouts of IPv6 and IPv4 addresses.
 ===== Further information =====
-If you would like to implement your own solution for IPv6 deployment statistics, easiest way to go is to first install
+If you would like to implement your own solution for IPv6 deployment statistics, easiest way to go is first to install
-NAV. Alternatively you could implement your own IPv6 SNMP collection scheme based on the ipv6NetToMediaTable. For
+NAV. Alternatively you could implement your own IPv6 SNMP collection scheme based on the ''ipv6NetToMediaTable''. For
-code details, do not heisitate to contoct the NAV team at [[https://postlister.uninett.no/sympa/info/nav-users|nav-users]].
+code details, please contact the NAV team at our [[mailinglists]].