NDN-NP: Named Data Networking Next Phase - Project Timeline

The Named Data Networking Next Phase project (NDN-NP) is the next iteration of a collaborative project (one of the three Future Internet Architecture Awards) for the research, development, and testbed deployment of a new Internet architecture that replaces IP with a network layer that routes directly on content names. For more information see http://www.named-data.net/ and the Named Data Networking Next Phase proposal.

Sponsored by:
National Science Foundation (NSF)

Principal Investigator: kc claffy

Funding source:  CNS-1345286 Period of performance: May 1, 2014 - April 30, 2018.

Timeline for the Proposed Efforts

Description Date Status
Network Environment - Open mHealth (UCLA)
Review limitations in current IP-based architecture for Open mHealth needs. Year 1 done
Design namespace, repository, trust and communication model for use cases, e.g., diabetes or PTSD treatment Year 1; updated in Year 2 done
Repository implementation providing backing storage for prototype applications. Year 1 done
Integrate named data networking into the Ohmage mobile data collection framework. Year 2 done
Pilot user-facing application using NDN, for beta testing by Open mHealth project team. Year 2 done
Finish and document the NDNFit driver application Year 3 done
Network Environment - Enterprise Building Automation & Management (UCLA)
Review limitations in current IP-based architecture, for Facilities Management needs. Year 1 done
Design NDN namespace, repository, trust and communication model for use cases, such as energy management, new building commissioning, feedback control. Year 1; updated in Year 2 done
Implement low-level NDN applications, such as energy management data gathering. Year 1 done, done
Preliminary embedded platform support. Year 2 done
Integrate "live" UCLA building data into the NDN testbed, mirroring data from 10-20 UCLA buildings. Year 2 done
Implement high-level NDN application for enterprise building monitoring, based on the above data, applying distributed 3D visualization work done in the first FIA project. Year 2 done
Re-connect the campus data to our Mini-EBAMS testbed, and complete the design, implementation, demonstration, and documentation of approaches to trust, aggregation, access control, and visualization that leverage hierarchical naming of real UCLA building sensors and their data. Year 3 done
Demonstrate system integration of IoT devices that use native NDN communication. Year 3 done
Application Cluster - Mobile Multimedia (UIUC / UCLA)
Mobile-aware, web-based conferencing based on WebRTC. Year 1 done
Design namespace and communication model for peer-to-peer 3D gaming and visualization and one or more vehicle-to-vehicle prototype applications. Year 1 in progress, done
File sharing platform, second revision. Year 1 done, done
Networked 3D environment demonstration in BAS/BMS and gaming contexts. Year 2 done
Design of information-maximizing synchronization, forwarding and caching suitable for mobile applications, and integration into end-to-end vehicle-to-vehicle demonstrations. Year 1; demo in Year 2 done
Finalize the NDN team's primary videoconferencing tool: Flume Year 3 done, roadmap
Investigate the NDN-based data catalog's applicability to climate and physics communities. Year 3 done, done
Investigate integration of the catalog with layer 2 reservation systems Year 3 done
Resolve, implement, and document NLSR physical and logical interface discovery Year 3 done
Resolve, re-implement, and document NLSR use of sync to retrieve routing updates Year 3 done
Evaluating hyperbolic routing in mini-NDN and testbed Year 3 done
Library Development for Application-Driven Research (UCLA / Washington University)
Release general-purpose C++ reference library. Year 1 done
Java library with mobile support, focused on requirements of Open mHealth environment. Year 1 done
Enhanced key generation, signing, publishing, and revocation library support. Year 1 done, tutorial
Support for common trust models expressed in naming Year 1 done
Framework for encryption-based access control for our specific environments. Year 1 done
Preliminary library for embedded devices and port of routing daemon (focus on BAS/BMS needs). Year 2 done
Python bindings and/or native support; support for C# bindings and Javascript library. Year 1, Year 2 Python, JS
Prototype apache httpd-style server-side publishing support for dynamic web applications. Year 1 done
Update trust models based on network environment experience Year 2 in progress, done
Improved autoconfiguration support Year 3 done, done
Congestion control Year 3 done, done
Security (University of Michigan / Colorado State University)
Develop common framework for key management and deployment Year 1 done
Define naming conventions and data formats to assist application developers with trust models Year 2 done
Implement cross-certifying model (SDSI) to accommodate realistic trust relationships Year 2
Develop library and client tools to enable transparent generation, publication, and validation of keys Year 2 in progress
Improved automation of certificate management. Year 3 done
Data signing and verification based on schematized trust. Year 3 done
Encryption/decryption using name-based access control. Year 3 done
Routing and Forwarding Strategy (University of Memphis / University of Arizona / UCLA)
Sketch a design for each of the three inter-domain routing approaches and choose the most promising one based on simulation. Year 1 NLSR, Hyperbolic Graph Generator Hyperbolic Forwarding Scenario
Design and implement forwarding strategies for local area networks. Year 1 done
   - Autoconfig: geolocation-based router selection Year 2 in progress
   - Design readvertise Year 2 done
   - Readvertise end-host routes into NLSR Year 2, Year 3 done
Implement chosen routing design and evaluate it using internal testbed at Memphis. Year 2 done
Deploy routing protocol on the NDN testbed. Year 2 Link State Done, Current Status
   - Localhop scope definition Year 2 done
   - Localhop scope restriction in strategy Year 2 done
   - NACK in multicast strategy Year 2 done
   - ASF strategy does not check whether out record exists before calculating RTT Year 2 done
   - NLSR Developer's Guide. Year 3 done
   - NLSR face discovery. Year 3 done
Deploying Hyperbolic Routing Year 2, Year 3 done
Geohyperbolic routing. Year 3 done
Tools (University of Memphis)
New Mini-NDN features
   - enabled security. Year 3 done
   - cluster edition. Year 3 done
   - WiFi capability.(proof-of-concept) Year 3 done
Porting NLSR to ndnSIM. Year 3
Scalable Forwarding (Washington University)
Integrate scalable FIB, PIT and CS into NDN-curated CCNx code base. Year 1 done
Release operational, scalable NDN node prototype in Open Network Lab for external evaluation. Year 1 done
Develop initial release of distributed router platform. Year 1 done
Release and support distributed NDN node prototype in Open Network Lab for external evaluation. Year 1 done
Design and release initial modular strategy layer interface, and exemplar strategies. Year 1 done
Design and release revised modular strategy layer interface, and exemplar strategies. Year 2 @Patrick
Revise and release distributed router platform code base. Year 2 done
Publish study of distributed router evaluation. Year 2
   - Scalable Name-based packet forwarding Year 2 done
   - Reliably scalable name prefix lookup Year 2 done
   - Scalable pending interest table design Year 2 done
Publish study and evaluation of synchronization implementation alternatives Year 2
   - RoundSync Year 3 done
   - Sync Survey Year 3 done
   - Scalable Name-based Sync Year 3 done
Education and Outreach (Colorado State University)
Incorporate new NDN material into courses at NDN collaborating institutions Year 1 Zhang (UCLA), Wang (UMemphis), Gersch (CSU)
Publish NDN educational material to encourage integration by other instructors Year 1,Year 2 done, done, done, done
Continue biweekly seminar series on architecture insights; integrate code review Year 1,Year 2 Held seven seminars
Host two annual community workshops Year 1,Year 2 NDN Comm 2014 | NDN Comm 2015 | NDN Comm 2017
Evaluation (CAIDA / UC San Diego)
Clarify description of architecture Year 1 done
Interview representatives of chosen environments for feedback on NDN application usability and responsiveness to our criteria Year 2 done
Survey internal and community users of our cluster of mobile application for feedback on NDN application usability and responsiveness to our criteria Year 2 done
Brainstorm new applications that would be easier to develop given current architecture Year 2 done
Last Modified