1. Minimal Internet Architecture Henning Schulzrinne (scribe)

2. Core goals Application-neutral: transparent support for any exchange of data; Minimalist: core infrastructure focuses on providing services that have to be handled there; Cost effective: deployed and operated at low cost; Trustworthy: optional identity assurance at all levels; Developer-friendly: small number of abstractions & uniform APIs; Introspective: observe and modify the behavior of network elements; Complete: Integrating storage and computation Self-configuring: network elements can self-assemble into a functioning network; Self-diagnosing: users and operators can readily find the source of difficulties; Self-healing: encourage redundancy, automatic fail-over and multi-homing; Scalable: > tens of billions of nodes Efficient: supporting a wide range of network and end system capabilities; Evolvable: defer and revisit technology choices later.

3. MIA Overview network API internetworking layer signaling (install state & code) language binding Hypothesis: network elements can offer communication (global) computation storage Hypothesis: network elements can offer communication (global) computation storage everywhere fast & low cost general- purpose CPU common functionality modules (e.g., pub-sub, CDN) common functionality modules (e.g., pub-sub, CDN)

4. Network node example RE PIC PE PIC storage & computation multiple computation & storage providers

5. MIA “Deliver packets from point A to B” – where A and B are globally unique identifiers datagrams device-centric protocols content-based networks human-centered protocols name translation routing signaling (path-state mgt.) MAC & PHY name translation routing libraries

6. New common services Name mapping – unify ARP, DHCP, DNS, DHTs, LoST (geo), LIS, LISP, … Identity assurance (see Shibboleth) – optional component provides geo location identity (name, organization, pseudonym, attributes) bonding?