Changes between Version 9 and Version 10 of OperationsIssues

Timestamp:

02/21/08 01:14:46 (16 years ago)

Author:

Mike Patton

Comment:

Added a couple of my own concerns and incremented ones already here that were on my list.

OperationsIssues

@@ -5 +5 @@
 
 ||'''Issue''' ||'''On your Top 10 List?'''||
-||Tracking changes to the network ||1||
+||Tracking changes to the network.  What's the procedure for contributing and does the NOC need to know?  What about reclaiming a contribution?||2||
 ||Observing current network state ||1||
 ||Collecting network measurements ||1||
-||Making network measurements available to users||1||
+||Making network measurements available to users.  Tools that access the archive need to evolve as formats, precision, and other details evolve.  But access to historical data needs to be maintained as well.||2||
 ||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||
+||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.  Over time, the original experimenter may have moved on and other users come and go.||2||
 ||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" infrastructure.  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||
+||Separating the "production" infrastructure from the "experimental" infrastructure.  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?||2||
 ||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||
 ||Defining and tracking demarcations between network infrastructure and user's infrastructure||1||
@@ -21 +21 @@
 ||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||
+||Distinguishing component failure from outside network failure that prevents contacting a working component.||1||
+||Keeping stable routing (both internal and with external peers) as internal topologies change quickly with experiments coming and going.||1||
 
 
-
-
-
-