2015FNF-张北川-命名数据网络(NDN)

Named Data Networking

(NDN)

Beichuan Zhang

The University Of Arizona

Evolution of Communication Networks

1

Evolution of Communication Abstractions

2

Telephony: build a path

IP: connect to a server

NDN: retrieve a content

The mismatch that NDN addresses

Application semantics and connectivity reality vs. network architecture

•Application support with complicated middleware •Mobility •Security

•Management

The network architecture is already causing problems, and will be more so in the emerging areas: •The very large, e.g., big data sciences

•The very small, .e.g., Internet of Things (IoT)

3

IP: Delivering packets to endpoints

Source Address Destination Address 4

NDN: Retrieving Named Data

Content Name Content Name

5

It makes no difference how and where the data is retrieved,

e.g., through a link, from memory, locally computed, or any combination of these.

Address Independence

IP addresses were assumed to be abundant, unique,

and fixed, but not any more.

•Address exhaustion

•NAT (public vs. private, v6 vs. v4)

•Mobility support

•Address management

Using application-generated names as network layer identifiers eliminates the above problems.

6 Location Independence

Content can be supplied by anyone from anywhere, as long as the name matches and the signature verifies. •Fault tolerance

•Load balancing

•Mobility support

7

Content Distribution Example

36.7M

Views

IP needs large infrastructure

and complicated technical

solutions.

8 Content Distribution Example

36.7M

Views

NDN’s multicast and caching

are native and built-in.

9

Data-centric Security

In NDN, Data are required to carry signatures

•Integrity

•Provenance

Secure the content, not the container nor the channel. Force app developers to think about security from the beginning.

10 NDN is a new communication abstraction

From point-to-point conversations to distributed

content production, dissemination, and consumption.

E.g.,

•Transport

•Forwarding strategy

•Security

•Name-based forwarding

A superset of what IP provides, and matches that of applications.

11

The NDN Project

Brief Background

•Started in 2010 as an NSF-sponsored Future Internet

Architecture project.

•Currently a team of 8 universities led by Lixia Zhang

(UCLA) and Van Jacobson.

•A growing research community of Information-Centric

Networking (ICN) across US, Europe, and Asia. •Increasing interests from the industry, including Cisco,

Huawei, Samsung, Intel, Panasonic, Verisign, Toyota. •NDN Consortium created in August 2014 to facilitate

long-term technology development.

•Annual NDN Community meetings.

12 Application-driven Arch Development

Vehicle

Networking

Distributed

Storage

Video

Streaming

Vehicular Network

Conferencing

Building Management

13

Smart Home

Mobile Health

Big-data Science

Running Code

NDN Platform Release

•NFD: the NDN forwarder.

•Libraries and language wrappers, supporting C/C++,

Java, Python, Javascript.

•Core applications.

Runs on Linux, Mac, Windows, Android, OpenWRT, Raspberry Pi, etc.

Source code available at /named-data Open source license, contributions are welcome.

14

NDN Testbed

Deployable now as an overlay (TCP, UDP) or on Layer 2.

27 nodes across 4 continents and growing.

15

Growing Community

NDN Consortium

•Created in August 2014 to facilitate long-term

technology development.

•Currently 17 academic members and 10 industrial

members.

NDN Community Meeting

•Annual meeting to exchange ideas and results.

•August 2014 (87 participants from 31 institutions) •September 2015 (99 participants from 49 institutions)

16

Hype Cycle of Net/Comm Tech

17

SDN

NDN