The report for the 1st NDN Community Meeting (NDNcomm) is available online now. This report, “The First Named Data Networking Community Meeting (NDNcomm)“, is a brief summary of the first NDN Community Meeting held at UCLA in Los Angeles, California on September 4-5, 2014. The meeting provided a platform for the attendees from 39 institutions across seven countries to exchange their recent NDN research and development results, to debate existing and proposed functionality in security support, and to provide feedback into the NDN architecture design evolution.
The workshop was supported by the National Science Foundation CNS-1457074, CNS-1345286, and CNS-1345318. We thank the NDNcomm Program Committee members for their effort of putting together an excellent program. We thank all participants for their insights and feedback at the workshop.
The Named Data Networking (NDN) Project offers a potential future Internet architecture designed as a distribution network.
The last post described how to deploy the NDN Forwarding Daemon (NFD) on a low-end box. This post describes how to get it connected.
The procedures and experiences in this post apply to any NDN node. If you aren’t using a low-end box, you may follow the official guide to install binary packages or compile from source. This post assumes you have ndn-cxx, nfd, and ndn-tlv-ping installed. You need access to two machines with NFD running; referred to as “local” and “remote”.
Connect to Another Machine
After installing NFD on your machine, you can connect to any other machine running NFD. Although NDN can run natively above Ethernet, there isn’t a global scale native NDN network yet because NDN is still in its early stage. Instead, NDN can run as an overlay network on top of a traditional IP network. You can specify the IP address and port number of the remote NFD, so that NDN packets get encapsulated into UDP or TCP packets and sent to the remote NFD.
To establish a connection, enter the following command:
To complement the existing NDN FAQ, we have started the NDN Video FAQ with three initial postings. The Video FAQ features on-camera answers to questions about NDN from faculty, students, staff, and industry colleagues.
The videos of the first part of the NDN tutorial at the recent ACM ICN Conference in Paris, France, are available here:
Tutorial #1 – https://vimeo.com/108870750
Tutorial #2 – https://vimeo.com/108870778
Manifests are proposed to be a special type of content in Named Data Networking that contains meta-information about other Data packets: a sequence of Data segments or completely independent information objects. While a great variety of useful meta-information exists, this document focuses on the case when manifest contains a list of Data packet names. For example, a manifest containing full names (prefix + digest of the packet) can be used by the consumer application for faster verification of data packets. Only the manifest object must be verified using the public key cryptography, whereas all other Data packets listed in the manifest can be verified by simple computation of the digest and comparison to the digest specified in already verified manifest. The purpose of this technical memo is to introduce the use of manifests for faster signing and verification of Data packets without requiring an additional round-trip delay for manifest fetching.
Read the full technical report on manifest embedding.
Named Data Networking (NDN) is a potential future Internet architecture designed as a distribution network. To access the NDN network from a Linux or Apple OSX machine, one can install the NDN Platform, a collection of software packages including the protocol stack and critical applications. The NDN Forwarding Daemon (NFD), a core component of the architecture, serves as a software router and runs both on the network routers as well as on end hosts to communicate with routers.
The NDN team provides periodic releases of the new platform, and binary packages are provided with each platform release. However, the development of NDN software, including NFD, happens much faster than platform releases, so users can download source code from GitHub. If a user wants to run bleeding edge software, those packages must be built from source code.
As a geeky low end box user, I’m thinking: can I run the NDN platform on a Linux box with only a small amount of memory? The box I’m talking about is an OpenVZ container from LowEndSpirit UK location, with only 128MB memory and no swap space. To make the challenge more interesting, I want to avoid apt-get, and run the bleeding edge version built from source code.
The Named Data Networking Consortium was launched today to promote and sustain research in the NDN future internet architecture! Please see below for more information or to join the consortium.
Press releases: UCLA. WUSTL. Univ. of Memphis.
Consortium information, including members and membership details.
We are pleased to announce the initial public release (version 0.2.0) of the NDN Forwarding Daemon (NFD). NFD is a network forwarder that implements the Named Data Networking (NDN) protocol. More details about NFD, release notes, HOWTOs, a FAQ and other useful resources are available at NFD’s official webpage.
Also available is the NFD developer’s guide, which provides a detailed description of the implementation internals.
An important goal of NFD is to support the broader community to experiment with the NDN architecture. Thus, the current release emphasizes modularity and extensibility over performance to allow easy experimentation with new protocol features, algorithms, data structures and applications. We invite all interested parties to experiment with the existing code and submit their contributions to NFD Redmine or directly to Gerrit Code Review in terms of new architecture features and performance improvements.
More detailed information about the NFD release
The NFD Team.