1 / 8

1. Process

1. Process. Gather Input Today Form Coherent Consensus Next two months. 2. CENs are Personal . Why are there so many electricity outages? Why did it take Amazon 4 days to recover from Amazon cloud failure? Why can’t I find out what’s wrong with my WiFi connection? .

rhea
Télécharger la présentation

1. Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 1. Process • Gather Input • Today • Form Coherent Consensus • Next two months

  2. 2. CENs are Personal • Why are there so many electricity outages? • Why did it take Amazon 4 days to recover from Amazon cloud failure? • Why can’t I find out what’s wrong with my WiFi connection?

  3. 3. Mid Point Summary ALERT

  4. A for Abstraction / Architecture • Functionality allocation: How to understand modularization in networks? • How to explain, predict, falsify? • What’s a logical unit on the network? • Graph clustering and dynamics aggregation • Sufficient statistics for graphs • Throughput < Delay < Security < Manageability • What non-performance metrics to use as objective functions? • Configuration complexity • Fairness metrics • Language and top down design of architecture decision • Scalable experiments and experiments at scale • State and awareness inside and outside of the network • Manage the crowd in unlicensed band • Approximate networks

  5. L for Limits • Characterize boundary of unknown behavior • Queueing, graph, information theory often ask intractable questions. What questions should be asked? • Non-convex optimization and local optima • Distributed optimization over combinatorial structures with stochastic dynamics across multiple coupled timescales • Long tail, non asymptotic results • Integration: communication + computation + control

  6. E for Evolvability • Evolvability and scalability • Theory for self correcting and under-specified networks • Het-Net of platforms, applications, user behaviors • Functional: Modularity, payoff/price of interface • Spatial: Centralized or distributed? Right level of hierarchy? • Economic incentive mechanisms • Pricing as a way to run feedback

  7. R for Robustness • Diagnosability and rebootability • Science of network management • Simulations we can believe in? Experiment design • Error bars • Optimal but fragile solutions • Sensitivity to configuration parameters • How to characterize black swan events? • Is there enough diversity for robustness? • How to quantify security and privacy metrics? • Low gain networks • Black swan events • Platform for unknown applications • Safety Security Privacy first

  8. T for Time • Delay/deadline as objective functions • How to enable interactive applications? Space doesn’t matter, time is tight. Delay much less understood than throughput. • Transient behavior: from convergence to equilibrium to invariant states during transient • How to carry out real time large-scale measurement, learning, visualization? • Real time application is hard, real time management even harder • Evolving graphs • How to accelerate network evolution?

More Related