1 / 21

The NSF Future Internet Architecture (FIA) Program

The NSF Future Internet Architecture (FIA) Program. Successor to 5 years of FIND and NetSE Future Internet Summit – Fall 2009 FIA solicitation 2010 Four awards Fall 2010 Named Data Networking – UCLA NEBULA – University of Pennsylvania eXpressive Internet Architecture – CMU

nicola
Download Presentation

The NSF Future Internet Architecture (FIA) Program

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. The NSF Future Internet Architecture (FIA) Program • Successor to 5 years of FIND and NetSE • Future Internet Summit – Fall 2009 • FIA solicitation 2010 • Four awards Fall 2010 • Named Data Networking – UCLA • NEBULA – University of Pennsylvania • eXpressive Internet Architecture – CMU • MobilityFirst – Rutgers • See <http://www.nets-fia.net/>

  2. The NEBULA Future Internet Architecture:A Research Agenda

  3. A Comprehensive Architecture • NEBULA is an architecture for the cloud-based future Internet • Cloud is 1960s computing utility • Requires a new kind of net • Key goals • More secure and reliable • Deployable and evolvable • Truly clean slate • Co-design Tech, Econ and Policy IMP Front and Back, CRS-1

  4. NEBULA: A Network Architecture to Enable Security NDP – NEBULA Data Plane – distributed multiple-path establishment and policy enforcement (availability and policy enforcement) NVENT - NEBULA Virtual and Extensible Networking Techniques – extensible control plane (extensibility + policy specification and entry) NCore – NEBULA Core – redundantly connected high-availability routers (availability)

  5. Enforcing policy at high speed? • Data plane must check that path is authorized • Data plane must check that path was followed • This is a hard technical problem • Status quo not even close (BGP only advisory) • Target environment rules out previous techniques • Backbone speeds preclude digital signatures • Federated nature of Internet precludes central root of trust, pre-configured shared secrets, etc.

  6. NDPin a nutshell • Use cryptography for: • Proof of consent (PoC) –route authorized? • Proof of path (PoP) – route followed?

  7. NDP Research Questions: • Must NDP run on all paths? • Realm management (roughly AS-like?) • Mapping to intra-domain/inter-domain? • Economic / policy implications? • Public-key infrastructure challenges • Revocation, etc. • Control of enforcement

  8. NEBULA Virtual and Extensible Network Techniques (NVENT) • Secure control plane for naming, path exchange, etc. • Service access • New service injection • Generalized path discovery for specifying policies, multiple paths and dynamic path construction via NDP Application Interface request paths Service Discovery (Database) Network Services NDP (policy1) IPV6 NDP (policy2)

  9. NVENT Research Questions: • How do NVENT nodes peer? • What is the right division between roles of NVENT: 1) API, 2) Policy/Consent server, 3) means for introducing and offering new services / slicing up services? • Policy specification and management? • (Soft)-state management versus dynamics? • Changes in dynamics if routers more resilient?

  10. Ncore redundancy: paths • High availability via redundant high-throughput links • A routing complex from multiple chassis • Sufficient capacity for easy VM replication/migration

  11. Process i (Line Card B) Process j (Line Card C) Process m (Line Card K) Line Card G Line Card A Availability Middleware Fabric Resource and Fabric Management Line Card F Line Card K Ncore redundancy: software • High- availability router control software • Ideas from distributed systems and cluster computing External (e.g., OpenFlow) Internal Open Source Internal Proprietary

  12. Ncore Research Questions: • What are the scalability barriers? • What are the technical/economic tradeoffs among redundancy: 1) inside routers, 2) inside data centers and 3) between routers? • Algorithms and Interfaces for path management • Interfaces with NDP and NVENT

  13. NEBULA Architectural Choices

  14. NEBULA Research Questions: • Can we design the overall system for Byzantine Faults? • E.g., an entire nation’s routers “go bad”… • Economic implications for (new?) industry? • Customer demand for NEBULA features? • How does NEBULA interact with regulatory requirements? • Nebula policies, versus, e.g., Net Neutrality?

  15. Realization Progress and Plan • Router emulation environment • Currently on Cisco-provided cluster in San Jose • Extend to LTS cluster and other PIs/institutions • Cisco-provided access to CRS-1 for experimentation • NVENT, NDP and Ncore designed for multiple iterations of independent development • Elements of NEBULA architecture can (and will) be independently developed and incrementally deployed

  16. Acknowledgements • NEBULA is supported by the National Science Foundation under its Future Internet Architecture program • NEBULA is also supported by Cisco Systems

  17. Thank you!

  18. www.internet2.edu

  19. The NEBULA Team

  20. NDP and NVENT roles:

More Related