| 12 | ||Resource trust and reputation management||1|| |
| 13 | ||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|| |
| 14 | ||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|| |
| 15 | ||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|| |
| 16 | ||Defining and tracking demarcations between network infrastructure and user's infrastructure||1|| |
| 17 | ||Defining, monitoring, and delivering on service level agreements||1|| |
| 18 | ||Security monitoring and event management||1|| |
| 19 | ||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|| |
| 20 | ||Making multiple security mechanisms and authorization styles work together, particularly for federated networks||1|| |
| 21 | ||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|| |
| 22 | |
| 23 | |
| 24 | |
| 25 | |
| 26 | |
| 27 | |