150 likes | 173 Views
Early thoughts on an architecture for network management. Karen Sollins MIT CSAIL FIND PI Meeting Arlington, VA, April 7, 2009. 4/07/09. Sollins/CSAIL. 1. The project. Model-based Diagnosis in the Knowledge Plane Collaborative with John Wroclawski (USC/ISI)
E N D
Early thoughts on anarchitecture for networkmanagement Karen Sollins MIT CSAIL FIND PI Meeting Arlington, VA, April 7, 2009 4/07/09 Sollins/CSAIL 1
The project Model-based Diagnosis in the Knowledge Plane Collaborative with John Wroclawski (USC/ISI) One year of FIND funding - supplemented with REU supplement industrial support from Intel and Cisco Center for Bits and Atoms (non-Nets NSF funding) DETER 4/07/09 Sollins/CSAIL Sollins/CSAIL 2
What is network management Identifying, reporting, mitigating, solving problems with network behaviors Improving network behaviors Informing clients of options, making predictions of network behavior 4/07/09 Sollins/CSAIL Sollins/CSAIL Sollins/CSAIL 3 3
What this talk is NOT about: what we did 3 PhDs at MIT: George Lee, Model-based statistical diagnosis Rob Beverly, Machine learning, where, when, how, and how to expand one’s horizons Ji Li, Organizing in the Knowledge plane PhD level student, Arun Visnawathan, (USC), reputation based weighting in statistical aggregation of perspectives REU, Jenny Liu (MIT), diagnosing multidomain experiment problems in DETER 4/07/09 Sollins/CSAIL Sollins/CSAIL Sollins/CSAIL 4 4
What this talk IS about:Where do we go from here Is network management a problem? What are the challenges? Is an architectural approach important/necessary? What have we learned to date? Where do we go from here? 4/07/09 Sollins/CSAIL Sollins/CSAIL Sollins/CSAIL 5 5
Is network management a problem? Two perspectives In enterprise or ISP Significant data collection Ongoing monitoring Specialized, targeted tools Still difficult to address non-localizable problems Consider the traveling employee In security context, may apply NAC/NAP to verify clean, trustworthy access In net mgmt. context, internal support has little opportunity to support traveling employee Hear this from enterprises, service providers, network manufacturers 4/07/09 Sollins/CSAIL Sollins/CSAIL Sollins/CSAIL 6 6
The challenges Scaling Geography or topology Time Duplication collection of same data in different tool contexts duplication of analyses Non-localizable questions Policy boundaries Identification of constrained information to be shared Incentives, cost-benefit analysis Performance: management must stay in the background Availability in the face of imperfectly working network 4/07/09 Sollins/CSAIL Sollins/CSAIL Sollins/CSAIL 7 7
Why architectural? Integration and independence of underlying information model Ability to integrate new tools, capabilities, information: extensibility Ability to (re)organize computations (mgmt apps and monitoring/measurement) adaptively based on function, topology, geography, performance, policy Framework in which to evaluate and negotiate incentives for controlled cooperation Federation: policy and technology 4/07/09 Sollins/CSAIL Sollins/CSAIL Sollins/CSAIL 8 8
The Knowledge Plane Knowledge Plane applications Knowledge Plane infrastructure The networks: data and control planes 4/07/09 Sollins/CSAIL Sollins/CSAIL 9
Where we are: KP organizing framework Decomposing, organizing and locating computations to meet organizational, performance, and policy criteria Functional (refinement), Structural (hierarchical or concatenated), Physical/topological, Policy Application of statistical machine learning for analysis, diagnosis, prediction Incomplete, incorrect, inconsistent, misleading, poorly understood, what is needed is only available through inference Adaptation to include additional capabilities in analysis as available Parameterizable, extensible, abstractable 4/07/09 Sollins/CSAIL Sollins/CSAIL Sollins/CSAIL 10 10
But that’s not all: Information/knowledge mgmt • An Information plane • Policy framework • Incentives framework Sollins/CSAIL Sollins/CSAIL 11 11
Information Plane Information publication and discovery: announcements and requests Question of whether identification required: attributes, metadata, identifiers? Ontology(ies) and conformance for understanding and reconciling Underpinnings: storage, distribution, rendezvous, delivery Region abstraction: supports topology, geography, policy/administrative organization 4/07/09 Sollins/CSAIL Sollins/CSAIL 12
Policy Framework Federated environment, at best Roles: publisher, domain of applicability, subscriber. Note each may be sets or defined by other descriptors. Permitted or denied behaviors Trustworthy enforcement or accountability/recourse mechanism Note: a key challenge is conflict resolution or at least exposure - a tussle 4/07/09 Sollins/CSAIL Sollins/CSAIL 13
Incentives Costs and benefits to whom Metrics: absolute or relative, may be monetary, but may be others, e.g. reputation, trust, risk Individualized? Static/dynamic: frequency of re-evaluation Scope of metrics: diminishing returns or network effect? Timing: possibility of performing offline, in order to allow for policy evaluation in this context Hope: to enable controlled and understood cooperation 4/07/09 Sollins/CSAIL Sollins/CSAIL 14
A broader insight • A new underlying paradigm: information (or content) based networking • Balancing control: move from sender controlled to control at “both” (or all) ends • Release from location dependence: “who” matters more than “where” • Generalize communication paradigm: release from simultaneity requirement • Some talks I heard here: Estrin, Jain, Allman, Snoeren, Schulzrinne, Talpade, Ng (only from yesterday)… • Other related projects: CCN (Jacobson), PSIRP (Trossen/Nikander) Sollins/CSAIL