1 / 13

PURSUIT Architecture

PURSUIT Architecture. Mikko Särelä 19.9.2011 T-110.6210 . Fundamentals of the Internet Collaboration Reflected in forwarding and routing Cooperation Reflected in trust among participants Endpoint-centric services (mail, FTP, even web) Reflected in E2E principle

geri
Download Presentation

PURSUIT Architecture

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. PURSUIT Architecture MikkoSärelä 19.9.2011 T-110.6210

  2. Fundamentals of the Internet Collaboration Reflected in forwarding and routing Cooperation Reflected in trust among participants Endpoint-centric services (mail, FTP, even web) Reflected in E2E principle  IP, full end-to-end reachability Are the Fundamentals Still Valid? • Reality in the Internet Today • Phishing, spam, viruses • There is no trust any more! • Current economics favor senders • Receivers are forced to carry the cost of unwanted traffic • Information-centric services • Do endpoints really matter? • Endpoint-centric services move towards information retrieval through, e.g., CDNs •  IP with middle boxes & significant decline in trust in the Internet vs.

  3. Observation: It's All About Information • Internet Tomorrow: • Proliferation of dissemination & retrieval services, e.g., • context-aware services & sensors • aggregated news delivery • augmented real life • Personal information tenfold in the next ten years (IBM, 2008) • Increase of personalized video services • e.g., YouTube, BBC iPlayer • Vision recognized by different initiatives & individuals • Internet of Things, Van Jacobson, D. Reed • Lack of interworking of silo solutions will slow innovation and development speed • Internet Today: • In 2006, the amount of digital information created was 1.288 X 10^18 bits • 99% of Internet traffic is information dissemination & retrieval (Van Jacobson) • HTTP proxying, CDNs, video streaming, … • Akamai’s CDN accounts for 15% of traffic • Between 2001 and 2010, information will increase 1million times from 1 petabyte (10^15) to 1 zettabyte (10^21) • Social networking is information-centric • Most solutions exist in silos • overlays over IP map information networksonto endpointnetworks

  4. Hypothesis: Increased Information Requires Information-centric Network Approaches Application developers care about information concepts • Creation of information topologies of various kinds -> Endpoint-centric networking structures are inadequate • Topological network changes too slow in timescale • Topological network boundaries too restrictive • Topological network boundaries often not aligned with information topologies • Overlaying possible but restricted in (developer) scalability -> If it is all about information, why not route on information?

  5. Why not? • Why not route on information?

  6. Main Design Principles • Information is multi-hierarchically organised • Information semantics are constructed as directed acyclic graphs (DAGs) • Information scoping • Mechanisms are provided that allow for limiting reachability of information to parties • Scoped information neutrality • Within each information scope, data is only delivered based on a given (rendezvous) identifier. • The architecture is receiver-driven • No entity shall be delivered data unless it has agreed to receive those beforehand. Information reachability/ scoping Information Hierarchies Communication Model

  7. Information Concepts • Information • Smallest something • Information collections • Sets of semantically similar information • Information networks • Sets of information under some common governance • Information producer • Entity publishing information to a particular network • Information consumer • Entity subscribing to information in a particular network

  8. Grouping Information Networks

  9. Architectural processes • Rendezvous • The process of resolving higher level identifiers to lower level identifiers within a given scope. • Three simple cases: link-local, intra-domain, inter-domain • Topology management and formation • Management of data delivery topologies and forwarding graphs • Forwarding • Data delivery within a single administrative domain or across multiple domains. • Temporal forwarding identifiers for each publisher and subscriber are derived via the rendezvous and topology management processes • Various routing and forwarding protocols can be used, for example a new protocol replacing IP or IP-based overlays

  10. AS Rendezvous AS Rendezvous Create delivery path Subscribe Topology Topology Publish Configure Forwarding path Forwarding node Forwarding node Forwarding node Forwarding node Data Forwarding Architecture Overview AS Topology Forwarding edge nodes Subscriber Publisher

  11. Service Model and API We have considered four different classes of network services • A low-level page model that exposes network forwarding and rendezvous/topology formation functions • A mid-level memory object model • Memory pages are mapped to publications • A mid-level channel model • Various high-level service models including shared state and document models Higher-level APIs Channel API Memory Object API Low-level page API

  12. Node Architecture: Component Wheel • Components may be decoupled in space, time, and context • Layerless protocol suite • Applications may insert or request new components to the wheel at runtime • Implemented as helper functions • The components are attached to the local blackboard (BB) • Components are attached to the local blackboard, sharing publications, state • Pub/sub is used to signal changes to blackboard state

  13. Component Wheel Interactions

More Related