NDN Project Progress Report. March 20, 2012 AsiaFI NDN Research Workshop

Transcription

1 NDN Project Progress Report March 20, 2012 AsiaFI NDN Research Workshop

2 Named Data Networking (NDN) NSF FIA 3 year project

3 Lixia Zhang (lead) Jim Thornton (manager) Deborah Estrin (advisor) Van Jacobson (architect) Tarek Abdelzaher Jeff Burke K Claffy Patrick Crowley Dmitri Krioukov Dan Massey Paul Ohm Christos Papadopoulos Katie Shilton Gene Tsudik Ersin Uzun Lan Wang Edmund Yeh Beichuan Zhang

4 1. What the project is trying to accomplish. 2. How we are going about it. 3. Progress in many areas. 4

5 Requirements to consider Security Availability and resilience Better management Economic viability Meet society s needs Support for tomorrow s computing Exploit tomorrow s networking Support tomorrow s applications Fit for purpose (it meets the fundamental goals) 2 Requirements slide from Dave Clark s FIA Planning Meeting presentation 5

6 Rephrased as Questions Does it solve today s hard problems? Diverse user/application needs poorly served now Can it be made real? Cost to grow, manage, diagnose, fix, maintain, plan Will it survive success? Internet scale speed, users, devices, Does it promote security & privacy? Will the world let it thrive? Non-technical factors: social, political, economic,... Does it enable the future? What kind of future? Unforeseen technologies, applications, social/economic structures,... 6

7 Major Areas Applications Security and Privacy Routing Forwarding Strategy Scalable Forwarding Network Management and Monitoring Evaluation and Assessment Fundamental Theory Social Values in Design 7

8 Major Areas Applications Security and Privacy Routing Forwarding Strategy Scalable Forwarding Recent Demo Network Management and Monitoring Evaluation and Assessment Fundamental Theory Social Values in Design 8

9 NDN for Media What about User Generated Content? Super Bowl stadium AT&T customers uploaded 40% more than downloaded John Donovan cited by Joan Marsh in Lessons from the Super Bowl, AT&T Public Policy Blog, February 8, Lixia Zhang, Jeff Burke 9

10 Audio Conference Tool Server-less conferencing Multipoint media distribution Participant discovery Used for project meetings Prototype based on open-source tools (ACT) Testbed: NDN Overlay Testbed

11 NDN for Internet of Things: Lighting Control Testbed: UCLA Film & TV Studio #1 Jeff Burke, UCLA 11

12 Challenges of IP in Lighting Systems Modern lighting control transitioning to IP/Ethernet, but: Security relies upon physical network segregation, VLANs, firewalls. IP-based addressing irrelevant to applications, with naming scattered across layers and protocols. Configuration is brittle for dynamic systems Devices come & go in some applications (U-Home, entertainment) Interoperability for devices/controllers more common Certain building systems incorporate mobile devices (U-Home) Patches, firmware updates, etc. require Internet access 12

13 Application-specific Naming Many possible names - Manufacturer-assigned: /lighting/etc/0041f31c493ef01a - Controller-assigned: /<controller_root>/<port#>/<chan#> - Physical location: /enterprise_root/<controller_id>/<fixture_id> - Region of Responsibility: /room_root/region/wall_west/downlight - Designer-assigned: /app_root/piano_spotlight Naming dealt with in one place in the architecture compare with: VLAN 4 IP Port 4722 Universe 2 Channel 1 Descriptive name or URI *Example related work: IS4 by OrRz and Culler (2010), A System for Managing Physical Data in Buildings.

14 Authenticated interests Recall the two packet types: Interests are anonymous, data is signed. Naming conventions are up to the app, so include a signature. Protect against replay attacks with state / counter. Use symmetric keys or hash chains for faster per-packet signatures. Interest signed by app UCLA/boelter/3551/lights/fixture /41/rgb-8bit-hex/FAF87F/<state>/<signature> Data NDN ACK signed by light Architectural Lighting Control App Security collaborators: Gene Tsudik, Paolo Gas7, Yanbin Lu at UC Irvine.

15 End-to-end Working Application Embedded Linux Controller Application naming and name assignment Bootstrapping trust and configuration Signed interests Exploration of alternatives to signatures

16 Security: Routing customers & peers pop core... 16

17 BigCo/NetOps/SFpop/OSPF/rtr731/pid345/LSP#678 signed by The name in one Link State Packet generated by the SFpop IGP routing process on rtr731. BigCo/NetOps/SFpop/OSPF/rtr731/pid345 signed by signed by The name of the routing process cert (given to the process when the router creates it). This name must match the bold part of each packet's name. BigCo/NetOps/SFpop/rtr731 The name of the router cert (given gured). signed by * g/employee975 The name of the cert of the employee who last gured the router. (This key signs the entire g as well as the router's signing key.) * g The name of the cert that is the root of trust for guration. 17

18 Routing: Link State 10 OSPF-N: OSPF Extensions for NDN Beichuan Zhang, Lan Wang

19 OSPF-N Two new types of Opaque Link State Advertisement (LSA): NDN Adjacency NDN Name (prefix information) OSPF-N configuration manager at node builds routing table and exports to ccnd Implemented on Quagga OSPF suite Running on 10 sites of our overlay testbed

20 Routing: Local Bootstrap ccnx-dhcp: Bootstrap edge node s minimal configuration for IP overlay connectivity Default router unicast address Routable NDN prefix Dynamic discovery search process 1. Broadcast query on local segment 2. SRV DNS lookup 3. CNAME DNS lookup

21 Routing: Greedy Routing Routing on hyperbolic metric space embedding of network topology by greedy navigation on coordinates Dmitri Krioukov

22 Greedy Routing for NDN overlay testbed Study of NDN testbed overlay topology Hyperbolic coordinates assigned based on Internet ASs Good routing performance All paths successful with node min. degree 2 links to closest nodes 94% successful with core node failure at min degree 3 node min. degree 3 case

23 Routing: Simulation Basic ns-3 simulator working Being used to simulate different forwarding strategies and compare performance Soon to be released Lixia Zhang, Beichuan Zhang

24 Scalable Forwarding Challenge: Patrick Crowley

25 Scalable Forwarding: Baseline WashU Open Network Lab (ONL) Controlled experimental infrastructure

26 Scalable Forwarding: Baseline Comparison WashU Open Network Lab (ONL) Controlled experimental infrastructure

27 Scalable Forwarding: Baseline Results CCNx (95% confidence) HTTP/Squid (95% confidence)

28 Scalable Forwarding: Opportunities CCNx: one software optimization to eliminate duplicate decodes

29 Scalable Forwarding: Baseline Results Software Sustained Rate CCNx Mbps CCNx modified 246 Mbps lighttpd/squid 865 Mbps

30 Scalable Forwarding: GENI Deployment Supercharged PlanetLab Platform (SPP) Nodes Chassis: Line cards DRAM CPU/NPU TCAM 200 Mbps Internet2 links

31 NDN Testbed Context GENI SPPs in I2 PoPs PARC UCLA Salt Lake City UCI NDN clients on EC2 CAIDA/UCSD Arizona ColoState NEU Washington DC Kansas UIUC WashU Memphis Atlanta Between SPPs: I2, udp SPPs and campuses: I2, udp Campuses and clients: Internet, tcp Houston Campus NDN nodes

32 NDN Live Demonstration Goals Demo Feature Large-scale, wide-area operation Mix of content distribution and interactive apps Visualization of both app-level and net-level activity Demonstrate both steady-state and react-to-change modes Something IP+HTTP cannot do Realization All 4 US time zones, ~300 machines 4 distinct services Visualization Web App Drop links during app sessions Video streaming, multipath routing

33 NDN Testbed & Live Visualization NDN Gateway routers at 10 project sites GENI SPPs at I2 Pops On-site laptop homed off UCLA gateway Client hosts homed off gateway routers per router for demonstration Link bandwidth (kb/s) shown on interactive monitoring map

34 Demo Phase 1: Interactive App Chat with someone live

35 Demo Phase 2: Video Streaming One client homed off each of 10 gateways Each client retrieving the same mpeg file Only one copy of data on any link Automatic multi-path route switching On-site client shows video delivery

36 Demo Phase 3: Robo-Chat Participation of 250 clients Three robo-servers feeding text into chat

37 Demo Phase 4: File Transfer Retrieve a file from repository homed off WashU gateway Robust under link/route outage

38 Demo Phase 5: Live Audio/Video Delivery of live audio and video from studio across town at UCLA Jeff Burke s Center for Research in Engineering, Media and Performance Server at studio homed off REMAP gateway Laptop on-site homed off UCLA gateway

39 Information on NDN is available at named-data.net including progress summary with details Information on CCNx is available at GPL d open-source release of our base research prototype.