1 / 6

Summary&Conclusions of Clean Slate

Stacks v. Heaps Role Based Architectures, Control Plane deconstruction of layers Virtualisation Software v. hardware Declarative/metarouting high level languages for systems on networks Privacy preserving network measurement Distributed or in archives Radical Wireless Net stuff

mercedes
Télécharger la présentation

Summary&Conclusions of Clean Slate

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. Stacks v. Heaps Role Based Architectures, Control Plane deconstruction of layers Virtualisation Software v. hardware Declarative/metarouting high level languages for systems on networks Privacy preserving network measurement Distributed or in archives Radical Wireless Net stuff Power saving - need more info on traffic Mobility - use vehicular info to trade-off differently See next … Can people send me slides to dist to attendees Do we mind putting agenda/attendee (NOT email of course) and/or slides on web? Who needs the bus (6.30) - or walk to castle, then jesus (now)? Summary&Conclusions of Clean Slate

  2. Adjacency - what is a network (graphs, queues, links etc)??? Jon. Crowcroft Computer Lab University of Cambridge

  3. Wireless Mesh (multiple overlapping mesh and radio?) And Packet v. Connection v. (say) swarms (see later)? There is no connection How to build a testbed What are the interesting questions? Shared Media v. Pt2Pt v. Switches (NBMA) etc etc

  4. Net folk often draw clouds - this is not a crazy abstraction Encapsulate a notion of “useful adjancy” Usefulness defined by Community (policy in AS sense) Reachability (in same comms protocol role/layer sense) Information rate (e.g. spectrum, or lambda) (SIR Can recurse/nest, or merge/split Spectrum management for incumbent, community mesh, C^3 Multipath, multi-radio, distributed MIMO Mpls LSRs Etc etc etc - so what is the Computer Science instantiation of this architecture clouds

  5. Is my mad idea to replace packets and circuits with A pure network layer version of bittorrent Using cross layer net coding (if needed) No sender/receiver Pub/sub or event/notify, but as first class net ADU is net object (e.g. in end system, but also in net) (e.g. imagine rabin fingerprint/coded object being net coded in XORS in the air sense Or 10Mbyte or 1Gbyte MTU/MSS packet in photonics case Swarms (tm:)

  6. Cloud is a fuzzier notion of a net than a “Set” Basically, convolves performance AND reachability I.e. like a potential well w/ depth… Other than that…I havnt got a clue :-) Questions?

More Related