Macro Trends, Architecture, and the
Hidden Nature of Complexity
(and what does this have to do with SDN?)
David Meyer (wit...
Agenda
• Too many words, too many slides 
– This talk is about thinking about SDN (and networking) in new ways
• A Couple...
Danger Will Robinson!!!
This talk might be controversial/provocative
(and perhaps a bit “sciencey”) 3
Premise/Goal/Context of this Talk
• Clearly systems approaches to biology, medicine, engineering, and neuroscience face co...
A Couple of Macro Trends
5
Trend: The Evolution of Intelligence
R-complex (Reptilian Brain) to Neocortex  Hardware to Software
SOFTWAREHARDWARE
• Ke...
Trend: Open Source
(hardware *and* software)
• Community building is a core Open Source objective
• Code is the coin of th...
Trend: Engineering artifacts are no
longer the source of sustainable
advantage and/or innovation
http://en.wikipedia.org/w...
Coming to a Network Near You…
Trend: Deep Learning
9
V1
V2
V4
Agenda
• A Couple of Macro Trends
• SDN Context: Problem Space and Hypothesis
• Complexity, Layered Architectures, and SDN...
Oh Yeah, This Talk Was Supposed To
Have Something To Do With SDN
• Well then, what was the SDN problem space?
• Network ar...
Maybe this is the problem?
12
Or This?
(Note Layering)
Many protocols, many touch points, few open interfaces or abstractions,..
Network is Robust *and*...
BTW, Complexity Isn’t Inherently “Bad”
Increasing number of policies, protocols, configurations and interactions (well, an...
Agenda
• A Couple of Macro Trends
• SDN Context: Problem Space and Hypothesis
• Complexity, Layered Architectures, and SDN...
Connecting Complexity, Design, and
Robustness
“In our view, however, complexity is most
succinctly discussed in terms of f...
Robustness is a Generalized
System Feature
• Scalability is robustness to changes to the size and
complexity of a system a...
Just so we’re all talking about the
same things – a few definitions
• Robustness is the preservation of a certain property...
Robust Yet Fragile
Human complexity
 Metabolism
 Regeneration & repair
 Immune/inflammation
 Microbe symbionts
 Neuro...
Robust Fragile
 Metabolism
 Regeneration & repair
 Healing wound /infect
 Obesity, diabetes
 Cancer
 AutoImmune/Infl...
Summary: Understanding RYF is The Challenge
• It turns out that managing/understanding RYF
behavior is the most essential ...
efficient
BTW, can we tell this story in a
“Low Dimensional” space?
wasteful
fragile
efficient
robust
22
* do cheap things engineers recommend
Example: Airline
Security Architectures
costly
fragile
cheap
robust
Secure
cockpits*...
Secure
cockpits
Alternatives
costly
fragile
cheap
robust
$millions
0 deaths
Invade
Bomb
Drone strike
X-ray
$ trillions
???...
Slow
Flexible
Fast
Inflexible
Architecture
(constraints that
deconstrain)
General Special
Universal Laws and Architectures...
Multiply
Survive
Phage
lifecycle
InfectLyse
slow
fragile
fast
robust
Survive
Multiply
thin
small
thick
big
Laws
So What is...
Architectures
• What we have learned is that there are universal
architectural building blocks found in systems that scale...
Layered architectures 101
Apps
OS
HW
Operating System
Apps
OS
Hardware
Digital
Lumped
Distributed
Slide courtesy John Doyl...
OS
Diverse
Deconstrained
(Hardware)
Deconstrained
(Applications)
DiverseHorizontal
App
Transfer
Horizontal
HW Transfer
Lay...
OS
Layered architectures
Minimal
diversity
and
change
Apps
OS
HW
Slide courtesy John Doyle
30
Diverse
Deconstrained
Deconstrained
Diverse
Horizontal
Transfer
Horizontal
Transfer
diversity and change
diversity and cha...
Diverse
Deconstrained
(Hardware)
Deconstrained
(Applications)
DiverseHorizontal
App
Transfer
Horizontal
HW Transfer
Layere...
Diverse
Deconstrained
(Hardware)
Deconstrained
(Applications)
Diverse
Layered architectures
Constrained
and hidden
Apps
OS...
Fast
Slow
Flexible Inflexible
General Special
Apps
OS
HW
Overlaying Tradeoffs
Unconstrained/Diverse
Unconstrained/Diverse
...
Fast
Slow
Flexible Inflexible
General Special
Apps
OS
HW
Slide courtesy John Doyle
35
control feedback
RNA
mRNA
RNAp
Transcription
Other
Control
Gene
Amino
Acids
Proteins
Ribosomes
Other
Control
Translation
M...
Fast
Costly
Slow
Cheap
Flexible Inflexible
General Special
HGT
DNA repair
Mutation
DNA replication
Transcription
Translati...
fan-in
of diverse
inputs
fan-out
of diverse
outputs
Diverse
function
Diverse
components
Universal
Control
Universal Archit...
Bowties 101
Constraints that Deconstrain
Schematic of a “Layer”
For example, the reactions and metabolites of core
metabol...
But Wait a Second
(Can we apply this to the Internet?)
The Protocol Hourglass idea appears to have originated with Steve D...
Layering of Control
The Nested Bowtie/Hourglass
Architecture of the Internet
41
Flows within Layers
IP Packets
Connections...
NDN Hourglass
42
See Named Data Networking, http://named-data.net/
Layered architectures make robustness and
Evolvability compatible
?
Diverse
Deconstrained
(Hardware)
Deconstrained
(Applic...
Of Course, in Practice Things are More Complicated
The Nested Bowtie/Hourglass Architecture of Metabolism
See Csete, M. an...
Agenda
• A Couple of Macro Trends
• SDN Context: Problem Space and Hypothesis
• Complexity, Layered Architectures, and SDN...
OF/SDN is One Point in a Larger
Design Space
• But not the only one
• The larger space includes
– Compute, Storage, and Ne...
FP/SDN
Properties:
-- Complete Separation of CP and FP
-- Centralized Control
-- Open Interface/programmable Forwarding Pl...
Bowties/Hourglasses?
OF/SDN?
OL/SDN
CP/SDN
• OF/SDN?
• CP/SDN makes existing control planes programmable
• OL/SDN is an ap...
Agenda
• A Couple of Macro Trends
• SDN Context: Problem Space and Hypothesis
• Complexity, Layered Architectures, and SDN...
So The Future: Where’s it All Going?
50
But More Seriously….
• Current Events
– ONF: Table Typing Patterns (TTPs)
– IETF: Model Driven Everything (I2RS, …)
– Ever...
Where To From Here?
• Robust systems “might be” intrinsically hard to understand
– RYF complexity is an inherent property ...
Q&A
Thanks!
53
Upcoming SlideShare
Loading in …5
×

Macro Trends, Architecture, and the Hidden Nature of Complexity (and what does this have to do with SDN?)

1,683 views

Published on

Published in: Science, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,683
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Bode Sensitivity Integral: This equality shows that if sensitivity to disturbance is suppressed at some frequency range, it is necessarily increased at some other range.
  • (i). Every device is different; no common way of thinking about the data plane(ii). Myopic view (box view vs network view)(iii). Configuration and policy deeply intertwined  network is database of record and the like
  • Weaver: Problems of Simplicity, Problems of Disorganized Complexity, Problems of Organized Complexity
  • Bowties for flows w/in layers, and Hourglasses for layering of control
  • OF/SDN is a polar architectural design point; complete separation of control and data planesCP/SDN is adds programmability in an incremental way to conventional control planes; some targeted separation (e.g., PCE)/centralizationOL/SDN (Overlay/SDN) retains the control plane architecture of CP/SDN but adds a new, logically centralized control plane (“over” CP/SDN)
  • Macro Trends, Architecture, and the Hidden Nature of Complexity (and what does this have to do with SDN?)

    1. 1. Macro Trends, Architecture, and the Hidden Nature of Complexity (and what does this have to do with SDN?) David Meyer (with John Doyle) CTO and Chief Scientist, Brocade Director, Advanced Technology Center, University of Oregon Senior Research Scientist, Department of Computer Science, University of Oregon dmm@{brocade.com,uoregon.edu,cs.uoregon.edu,1-4-5.net,…} http://www.1-4-5.net/~dmm/talks/macro_trends_complexity_and_sdn.pdf 1
    2. 2. Agenda • Too many words, too many slides  – This talk is about thinking about SDN (and networking) in new ways • A Couple of Macro Trends • SDN Context: Problem Space and Hypothesis • Complexity, Layered Architectures, and SDN • A Perhaps Controversial View • Summary and Q&A if we have time 2
    3. 3. Danger Will Robinson!!! This talk might be controversial/provocative (and perhaps a bit “sciencey”) 3
    4. 4. Premise/Goal/Context of this Talk • Clearly systems approaches to biology, medicine, engineering, and neuroscience face converging challenges • Why? – Because modern science, technology, and culture create dauntingly complex but similar and overlapping problems in these domains  Convergent Evolution (a topic in and of itself) – SDN has given us a new tool with which to understand/experiment with network architectures • Goal: To convince you that we are at a point in the history of network technology at which integrated theories (and methods) applicable to all complex networked systems, including the Internet/SDN, are needed, and that the approach we should take is to concentrate on the organizational principles of complex systems. • High Level Ideas/Hard Problems – Provably hard tradeoffs • Initially Speed vs. Generality – Layering • Layering is a candidate universal architecture that seems to give us the ability engineer the speed/flexibility tradeoff – Horizontal Transfer (H*T) • HGT, HAT – BTW, why are there (necessarily) hard tradeoffs? • Top down requirements coupled with bottom up constraints (HW)  hard tradeoffs • Turing , Shannon and Bode, … • And how is all of this connected to SDN and the Internet? 4
    5. 5. A Couple of Macro Trends 5
    6. 6. Trend: The Evolution of Intelligence R-complex (Reptilian Brain) to Neocortex  Hardware to Software SOFTWAREHARDWARE • Key Architectural Features of Scalable/Evolvable Systems • Turing, Bode, and Shannon • RYF-Complexity (behavior) • Layered Architecture • Bowties and Hourglasses • Horizontal Transfer (H*T) • Protocol Based Architectures Once you have HW its all about code… 1 6
    7. 7. Trend: Open Source (hardware *and* software) • Community building is a core Open Source objective • Code is the coin of the realm • Engineering systems are as important as artifacts Putting this all together  7
    8. 8. Trend: Engineering artifacts are no longer the source of sustainable advantage and/or innovation http://en.wikipedia.org/wiki/Aeroelasticity - Flutter • Engineering Systems1 • Culture • People/Process • Multi-disciplinary Approaches Perhaps surprisingly, the “hyper-scale” and open source communities have taught me that actual artifacts (in our case network applications as well as HW/SW) are ephemeral entities and that the only source of sustainable advantage/innovation consists of 1 Note that our Engineering Systems evolve using the same mechanisms that are used to build artifacts. This is architecturally analogous to Horizontal Gene Transfer (HGT) and the acquisition of anti-bacterial resistance in the bacteria biosphere; the same mechanisms used to create the artifact (plasmid) are used to evolve the “Engineering System” (transcriptional network). Consider: Horizontal Application Transfer? 8
    9. 9. Coming to a Network Near You… Trend: Deep Learning 9 V1 V2 V4
    10. 10. Agenda • A Couple of Macro Trends • SDN Context: Problem Space and Hypothesis • Complexity, Layered Architectures, and SDN • A Perhaps Controversial View • Summary and Q&A if we have time 10
    11. 11. Oh Yeah, This Talk Was Supposed To Have Something To Do With SDN • Well then, what was the SDN problem space? • Network architects, engineers and operators are being presented with the following challenge: – Provide state of the art evolvable network infrastructure and services while minimizing TCO –  better, faster, cheaper, choose 3? – Evolvability and scalability? Horizontal Application Transfer? • SDN Hypothesis: It is the lack of ability to innovate in the underlying network coupled with the lack of proper network abstractions results in the inability to keep pace with user requirements and to keep TCO under control. – Is this true? Hold that question… • Note future uncertain: Can’t “skate to where the puck is going to be” because curve is unknowable (this is a consequence, as we will see, of the “software world” coupled with Moore’s law and open- loop control). – That is, there is quite a bit of new research that suggests that such uncertainty is inevitable • So given this hypothesis, what was the problem? 11
    12. 12. Maybe this is the problem? 12
    13. 13. Or This? (Note Layering) Many protocols, many touch points, few open interfaces or abstractions,.. Network is Robust *and* Fragile  The network is RYF-complex 13
    14. 14. BTW, Complexity Isn’t Inherently “Bad” Increasing number of policies, protocols, configurations and interactions (well, and code) Domain of the Fragile Domain of the Robust 14
    15. 15. Agenda • A Couple of Macro Trends • SDN Context: Problem Space and Hypothesis • Complexity, Layered Architectures, and SDN • A Perhaps Controversial View • Summary and Q&A if we have time 15
    16. 16. Connecting Complexity, Design, and Robustness “In our view, however, complexity is most succinctly discussed in terms of functionality and its robustness. Specifically, we argue that complexity in highly organized systems arises primarily from design strategies intended to create robustness to uncertainty in their environments and component parts.” See Alderson, D. and J. Doyle, “Contrasting Views of Complexity and Their Implications For Network-Centric Infrastructures”, IEEE TRANSACTIONS ON SYSTEMS, MAN, AND CYBERNETICS—PART A: SYSTEMS AND HUMANS, VOL. 40, NO. 4, JULY 2010 16
    17. 17. Robustness is a Generalized System Feature • Scalability is robustness to changes to the size and complexity of a system as a whole • Evolvability is robustness of lineages to large changes on various (usually long) time scales • Other system features cast as robustness – Reliability is robustness to component failures – Efficiency is robustness to resource scarcity – Modularity is robustness to component rearrangements • Not surprisingly, these are the same features we’re seeking from the network 17
    18. 18. Just so we’re all talking about the same things – a few definitions • Robustness is the preservation of a certain property in the presence of uncertainty in components or the environment – Systems Biology: Biological systems are robust if their important functions are insensitive to the naturally occurring variations in their parameters • Limits the number of designs that can actually work in the real environment • Examples: Negative autoregulation and exact adaptation in bacterial chemotaxis • Fragility is the opposite of robustness – Both need to be specified in terms of a system, a property and a set of perturbations • A system can have a property that is robust to one set of perturbations and yet fragile for a different property and/or perturbation  the system is Robust Yet Fragile – Or the system may collapse if it experiences perturbations above a certain threshold (K-fragile) • For example, a possible RYF tradeoff is that a system with high efficiency (i.e., using minimal system resources) might be unreliable (i.e., fragile to component failure) or hard to evolve – Another example: HSRP (VRRP) provides robustness to failure of a router/interface, but introduces fragilities in the protocol/implementation – Complexity/Robustness Spirals • Summary: Software, and SDN in particular, creates all kinds of RYF tradeoffs 18
    19. 19. Robust Yet Fragile Human complexity  Metabolism  Regeneration & repair  Immune/inflammation  Microbe symbionts  Neuro-endocrine  Complex societies  Advanced technologies  Risk “management”  Obesity, diabetes  Cancer  AutoImmune/Inflame  Parasites, infection  Addiction, psychosis,…  Epidemics, war,…  Disasters, global &!%$#  Obfuscate, amplify,… Accident or necessity? RYF Behavior is found everywhere 19
    20. 20. Robust Fragile  Metabolism  Regeneration & repair  Healing wound /infect  Obesity, diabetes  Cancer  AutoImmune/Inflame  Fat accumulation  Insulin resistance  Proliferation  Inflammation • Fragility Hijacking, side effects, unintended… • DDOS, reflection, spoofing, … • Of mechanisms evolved for robustness • Complexity control, robust/fragile tradeoffs • Math: robust/fragile constraints (“conservation laws”) Accident or necessity? Both Slide courtesy John Doyle 20
    21. 21. Summary: Understanding RYF is The Challenge • It turns out that managing/understanding RYF behavior is the most essential challenge in technology, society, politics, ecosystems, medicine, etc. This means… – Understanding Universal Architectural Principles – Managing spiraling complexity/fragility – Not predicting what is likely or typical • But rather understanding what is catastrophic (fat tailed) –  understanding the hidden nature of complexity • BTW, it is much easier to create the robust features than it is to prevent the fragilities – With, as mentioned, poorly understood “conservation laws” 21
    22. 22. efficient BTW, can we tell this story in a “Low Dimensional” space? wasteful fragile efficient robust 22
    23. 23. * do cheap things engineers recommend Example: Airline Security Architectures costly fragile cheap robust Secure cockpits*$millions 0 deaths Stopping hijacking Theorem: C £ 1 R 23
    24. 24. Secure cockpits Alternatives costly fragile cheap robust $millions 0 deaths Invade Bomb Drone strike X-ray $ trillions ??? deaths Original slide courtesy John Doyle 24
    25. 25. Slow Flexible Fast Inflexible Architecture (constraints that deconstrain) General Special Universal Laws and Architectures (Turing) Layering, Formal Systems, Hard Tradeoffs ideal Original slide courtesy John Doyle 25
    26. 26. Multiply Survive Phage lifecycle InfectLyse slow fragile fast robust Survive Multiply thin small thick big Laws So What is Universal? • Laws, constraints, tradeoffs – Robust/fragile – Efficient/wasteful – Fast/slow – Flexible/inflexible • Architecture • Hijacking, parasitism, predation 26
    27. 27. Architectures • What we have learned is that there are universal architectural building blocks found in systems that scale and are evolvable. These include – Layered Architectures – Bowties and Hourglasses – Horizontal Transfer (H*T) – Protocol Based Architectures – Massively distributed with robust control loops 27
    28. 28. Layered architectures 101 Apps OS HW Operating System Apps OS Hardware Digital Lumped Distributed Slide courtesy John Doyle SDN Controller/Network OS?28
    29. 29. OS Diverse Deconstrained (Hardware) Deconstrained (Applications) DiverseHorizontal App Transfer Horizontal HW Transfer Layered architectures Apps OS HW H*T Slide courtesy John Doyle 29
    30. 30. OS Layered architectures Minimal diversity and change Apps OS HW Slide courtesy John Doyle 30
    31. 31. Diverse Deconstrained Deconstrained Diverse Horizontal Transfer Horizontal Transfer diversity and change diversity and change Slide courtesy John Doyle 31
    32. 32. Diverse Deconstrained (Hardware) Deconstrained (Applications) DiverseHorizontal App Transfer Horizontal HW Transfer Layered architectures Apps OS HW Maximal diversity and change Slide courtesy John Doyle 32
    33. 33. Diverse Deconstrained (Hardware) Deconstrained (Applications) Diverse Layered architectures Constrained and hidden Apps OS HW Core Protocols Slide courtesy John Doyle 33
    34. 34. Fast Slow Flexible Inflexible General Special Apps OS HW Overlaying Tradeoffs Unconstrained/Diverse Unconstrained/Diverse Constrained Slide courtesy John Doyle 34
    35. 35. Fast Slow Flexible Inflexible General Special Apps OS HW Slide courtesy John Doyle 35
    36. 36. control feedback RNA mRNA RNAp Transcription Other Control Gene Amino Acids Proteins Ribosomes Other Control Translation Metabolism Products Signal transduction ATP DNA New gene Fast Costly Slow Cheap Flexible Inflexible General Special HGT DNA repair Mutation DNA replication Transcription Translation Metabolism Signal… Layered Architecture Slide courtesy John Doyle 36
    37. 37. Fast Costly Slow Cheap Flexible Inflexible General Special HGT DNA repair Mutation DNA replication Transcription Translation Metabolism Signal… Layered Bacteria Apps OS HW Slide courtesy John Doyle 37
    38. 38. fan-in of diverse inputs fan-out of diverse outputs Diverse function Diverse components Universal Control Universal Architectural Principles • Hourglasses for layering of control • Bowties for flows within layers BowtieHourglass Slide courtesy John Doyle Universal Carriers H*TRaw materials Information 38
    39. 39. Bowties 101 Constraints that Deconstrain Schematic of a “Layer” For example, the reactions and metabolites of core metabolism, e.g., ATP metabolism, Krebs/Citric Acid Cycle, … form a “metabolic knot”. That is, ATP is a Universal Carrier for cellular energy. See Kirschner M., and Gerhart J., “Evolvability”, Proc Natl Acad Sci USA , 95:8420–8427, 1998. 39 1. Processes L-1 information and/or raw material flows into a “standardized” format (the L+1 abstraction) 2. Provides plug-and-play modularity for the layer above 3. Provides robustness but at the same time fragile to attacks against/using the standardized interface 4. H*T
    40. 40. But Wait a Second (Can we apply this to the Internet?) The Protocol Hourglass idea appears to have originated with Steve Deering. See Deering, S., “Watching the Waist of the Protocol Hourglass”, IETF 51, 2001, http://www.iab.org/wp-content/IAB-uploads/2011/03/hourglass-london-ietf.pdf. See also Akhshabi, S. and C. Dovrolis, “The Evolution of Layered Protocol Stacks Leads to an Hourglass-Shaped Architecture”, http://conferences.sigcomm.org/sigcomm/2011/papers/sigcomm/p206.pdf. Bowtie Architecture Hourglass Architecture 40
    41. 41. Layering of Control The Nested Bowtie/Hourglass Architecture of the Internet 41 Flows within Layers IP Packets Connections Datagrams Ports TCP/UDP Connections Datagrams Ports RESTHTTP(S) REST LayeringofControl/Abstractions HTTP Bowtie Input: Ports, Datagrams, Connections Output (abstraction): REST TCP/UDP Bowtie Input: IP Packets Output (abstraction): Ports, Datagrams, Connections
    42. 42. NDN Hourglass 42 See Named Data Networking, http://named-data.net/
    43. 43. Layered architectures make robustness and Evolvability compatible ? Diverse Deconstrained (Hardware) Deconstrained (Applications) Diverse Constrained/ Hidden Apps OS HW Minimal diversity SDN Controller? 43
    44. 44. Of Course, in Practice Things are More Complicated The Nested Bowtie/Hourglass Architecture of Metabolism See Csete, M. and J. Doyle, “Bowties, metabolism and disease”, TRENDS in Biotechnology, Vol. 22 No. 9, Sept 2004 44
    45. 45. Agenda • A Couple of Macro Trends • SDN Context: Problem Space and Hypothesis • Complexity, Layered Architectures, and SDN • A Perhaps Controversial View • Summary and Q&A if we have time 45
    46. 46. OF/SDN is One Point in a Larger Design Space • But not the only one • The larger space includes – Compute, Storage, and Network Programmability – Security and Energy • My model: “SDN continuum” – http://www.ietf.org/id/draft-haleplidis-sdnrg-layer-terminology-03.txt 46
    47. 47. FP/SDN Properties: -- Complete Separation of CP and FP -- Centralized Control -- Open Interface/programmable Forwarding Plane -- Examples: OF, ForCES, various control platforms OL/SDN Properties: -- Retains existing (simplified) Control Planes -- Programmable overlay control plane -- Examples: Various Overlay technologies CP/SDN Properties: -- Retains existing (distributed) Control Planes -- Programmable control plane -- Examples: PCE, I2RS,BGP-LS, vendor SDKs Physical and Virtual Resources (CSNSE) Control and Orchestration (overly simplified view) Apps Apps… Service Layers A Simplified View of the SDN Continuum May be repeated (stacked or recursive) 47 HAT
    48. 48. Bowties/Hourglasses? OF/SDN? OL/SDN CP/SDN • OF/SDN? • CP/SDN makes existing control planes programmable • OL/SDN is an application from the perspective of the Internet’s waist 48
    49. 49. Agenda • A Couple of Macro Trends • SDN Context: Problem Space and Hypothesis • Complexity, Layered Architectures, and SDN • A Perhaps Controversial View • Summary and Q&A if we have time 49
    50. 50. So The Future: Where’s it All Going? 50
    51. 51. But More Seriously…. • Current Events – ONF: Table Typing Patterns (TTPs) – IETF: Model Driven Everything (I2RS, …) – Everyone else (ETSI NFV, Cablelabs, …) – Open Source/*Everything* • http://www.opendaylight.org • http://www.openstack.org • http://opencompute.org/ • High Order Bit: – System(s) we’re building are inherently uncertain  cloudy crystal balls – Architect for change and rapid evolution – see XP/Agile methodologies for a clue – Increasing roles for s/w and programmability + Moore’s law  volatility/uncertainty – Lucky thing for many of us: we work primarily around the narrow waist, most stable place to be – “Above the waist” characterized by uncertainty, e.g., http://spotcloud.com/ • Conventional Technology Curves – S & F – Moore’s Law and the reptilian brain • Someone eventually has to forward packets on the wire – 400G and 1.2 T in the “near” term – Silicon photonics, denser core count, …. • The future is all about Software Ecosystems – Open Interfaces: Protocols, APIs, Code, Tool Chains – Open Control Platforms at every level – “Best of Breed” markets • Theoretical Frameworks – Systems thinking 51
    52. 52. Where To From Here? • Robust systems “might be” intrinsically hard to understand – RYF complexity is an inherent property of advanced technology – Software (e.g., SDN, NFV, Cloud, …) exacerbates the situation – And the Internet has reached an unprecedented level of complexity… • Nonetheless, many of our goals for the Internet architecture revolve around how to achieve robustness… – which requires a deep understanding of the necessary interplay between complexity and robustness, modularity, feedback, and fragility1 • which is neither accidental nor superficial – Rather, architecture arises from “designs” to cope with uncertainty in environment and components – The same “designs” make some protocols hard to evolve – Does SDN help or hurt, and can we build formal models that help us reason about “universal laws”? • Understanding these universal architectural features will help us achieve the scalability and evolvability (operability, deployability, understandability) we’re seeking from the Internet architecture today and going forward – Multi-disciplinary approaches provide a template of how we might go about this (e.g., Systems Biology) • BTW – SDN ~ DDN (DevOPs Defined Networking) – http://www.slideshare.net/mestery/next-gennetworkengineerskills 521 See Marie E. Csete and John C. Doyle, “Reverse Engineering of Biological Complexity”, http://www.cds.caltech.edu/~doyle/wiki/images/0/05/ScienceOnlinePDF.pdf
    53. 53. Q&A Thanks! 53

    ×