| Issue | On your Top 10 List?
|
| Tracking changes to the network | 1
|
| Observing current network state | 1
|
| Collecting network measurements | 1
|
| Making network measurements available to users | 1
|
| Archiving network measurements | 1
|
| Defining and supporting appropriate privacy policies for collected data. Different users have different privacy concerns, and operations supports all users, so there can be many conflicts. | 1
|
| Keeping user access policies up to date, especially for mobile users | 1
|
| Resource trust and reputation management | 1
|
| Separating the "production" infrastructure from the "experimental infrastrucutre. On a research network, how do you track when a status change is part of an experiment and decide whether it is something that needs operations action? | 1
|
| Notifying users of planned outages in a way that makes sure they know about any changes that will affect them (not by just sending mass emails) | 1
|
| Separating the "production" infrastructure from the "experimental infrastrucutre. On a research network, how do you track when a status change is part of an experiment and decide whether it is something that needs operations action? | 1
|
| Defining and tracking demarcations between network infrastructure and user's infrastructure | 1
|
| Defining, monitoring, and delivering on service level agreements | 1
|
| Security monitoring and event management | 1
|
| Backwards compatibility for tools (for example, accessing network performance data associated with software releases or hardware devices that are no longer active in the network) | 1
|
| Making multiple security mechanisms and authorization styles work together, particularly for federated networks | 1
|
| Communications with network administrators at user sites (in both directions). IT managers are very busy, and may not consider research network connections a high priority. | 1
|
