Future Internet with Information Centric Networks

(1)

Future Internet with

Information Centric

Networks

(2)

(3)

(4)

(5)

Motivation

• _{Networking was introduced for}

resource sharing

– Named hosts

(6)

The Problem

ISP

(7)

Communication Vs

Distribution

Communication

Distribution

Naming

Endpoints

Content

(8)

Motivation

• _{Movement of content}

– Predicted global IP trafc in 2014: 64 exabytes/month (4 fold from 2009)

(1)

– 180 exabytes of content created in 2006 (2)

– Global mobile trafc will double every year (mostly streaming content) (2)

– Current solutions: P2P and CDNs

• _{Location orientation of content}

– Content associated with named hosts

• Sender orientation

– Sender can send anywhere

• Securing content

– Point-to-point model

(9)

Motivation

• _{Mobility and multi-homing}

– Device mobility is the norm

– Multiple attachments

– Mobility currently based on routing or indirection

• _{Adaptation to disruptions}

– Challenged networks – sparse connectivity, high-speed mobility, disruptions

• _{Problems with network based}

caching

– DRM issues

(10)

Known Architectures

• _{Architectures}

– _{Sienna (Publish/Subscribe)}

– _{Data Oriented Networking Architecture (DONA)}

– _{Publish Subscribe Internet Routing Paradigm (PSIRP)} – _{Network of Information (NetInf)}

– Content Centric Networking (CCN)

• _{Operation Diferentiation}

– _Naming – _Security – _Routing – _Caching

– Content existence knowledge

(11)

Today

src

dst

Path determined by global routing, not local choice

Structural asymmetry precludes market mechanisms and

encourages monopoly formation

(12)

Producer

Consumer

? a/b/c

(13)

Producer

(14)

Producer

Consumer

a/b

• Packets say ‘what’ not

‘where’ (no src or dst)

• Forwarding decision is local

• Upstream performance is measurable

? a/b/c /e

(15)

We envision replacing this:

ISP

(16)

ISP

(17)

Content Centric Networks – Operation

Interest Data

Check Content Store

Check Pending Interests Table

Check Forwarding Information Base

(18)

Content Centric Networks – Stack

• _{Change of network abstraction from “named hosts” to}

“named content”

• _{Security built-in: secures content and not the hosts}

• _{Mobility is present by design}

• _{Can handle static as well as dynamic content}

• _{Use of 2 messages: Interest and Data Object}

(1)

(19)

Content Centric Networks – Architecture

• _{Each CCN entity has 3 main data structures}

– Content Store, Pending Interest Table, Forwarding Information Base

• _{Uses multicast/broadcast}

• _{Uses “longest prefx matching” lookup for content names}

Content Store

Pending Interest Table (PIT)

Forwarding Information Base (FIB)

CCN Forwarding Engine

Face 1 CCN Forwarding

(20)

Content Centric Networks – Messages

• Purpose of messages

– Interests request for content

– Data serves these requests

• No fxed length felds and uses an XML encoding

(21)

Content Centric Networks – Names

• _{Core of CCN uses content names for}

forwarding

• _{Applications can interpret names the}

way they want

/uni-bremen.de/comnets/lecture/Kommunikationsnetze-I.pdf/v1/s0

(22)

Content Centric Networks - CS

• Uses “longest prefx matching”

• Implements policies such as LRU or LFU for content replacement

• Content do not necessarily have to be persistent (only cached)

(23)

Content Centric Networks – PIT

• _{Uses “longest prefx matching”}

• _{An entry may point to multiple faces}

(24)

Content Centric Networks – FIB

• _{Uses “longest prefx matching”}

• _{Similar to IP FIB}

• _{Destination may have number of faces}

... ...

Prefix

/uni-bremen.de/comnets 1, 2

... ...

Forwarding Faces

(25)

(26)

(27)

Routing

• _{Three general approaches}

–

_{Name Resolution Routing (NRR)}

–

_{Content-based Routing (CBR)}

–

_{Name-based routing (NBR)}

• _{Two phases}

–

_{Routing of NDO requests}

(28)

Name-Based Routing

• Client asks for a data object sending interest packets

which are routed toward the publisher of the name

prefx using longest-prefx matching in the

forwarding information base (FIB) of each node.

• The FIB is built using routing protocols of the

Internet.

• _{When a note receives multiple requests for the same}

NDO, only the frst is forwarded to the source.

• When a copy of the data object is encountered on

(29)

Content Centric Network (CCN)

(30)

CCN packets

There are two CCN packet types:

interest (similar to http “get”) and data

(31)

CCN node model

Get

(32)

Publish-Subscribe Internet Routing

Paradigm (PSIRP)

(33)

(34)

(35)

(36)

Forwarding on Bloomed link

ids

• The FI encodes the network links (rather than the nodes) on the path of interest between the producer and consumers

• FI is encoded in a probabilistic data structure called a Bloom flter that routers use for selecting interfaces on which to

forward an NDO.

– _{Bloom flters encode source route-style forwarding information into}

packet headers, enabling forwarding without depending on end-to-end addressing.

– _{Routers do not need to keep forwarding state. Forwarding}

decisions are simple and forwarding tables are small, potentially allowing faster, smaller, and more energy-efcient switches.

• The use of Bloom flters result in a certain number of false positives; in this case this means forwarding on some

(37)

Pub/Sub Routing using Link ID and FI

zFilter: FI Bloom Filter

(38)

(39)

Name Resolution Routing

• Use a Name Resolution Service (NRS) that stores the bindings from object names to topology-based locators

pointing to corresponding storage locations in the network.

• Three conceptual routing phases:

– _{Routing the request message to the responsible NRS node where}

the object name is translated into one or multiple source addresses

– _{Routing the request message to the source address(es)} – _{Routing the data from the source(s) to the requester.}

• All phases can potentially use diferent routing algorithms.

– _{A name-based routing method might be used for the frst phase.} – _{The second and third phases might use a topology-based routing}

like IP.

– _{There are multiple alternatives to loosely or tightly integrate the}

(40)

(41)

Content-Based Security

• _{Name-content mapping verifcation via}

per-data packet signature

–

_{Data packet is authenticated with digital signature}

(42)

Basic ICN forwarding

• _{Consumer ‘broadcasts’ an ‘interest’ over}

any & all available communications media:

get ‘/rutgers/ECE544/Lecture06-14.pdf’

• _{Interest identifes a}

_{collection of data - all}

data

items whose name has the interest as

a prefx.

• _{Anything that hears the interest and has an}

element of the collection can respond with

that data:

(43)

Basic ICN transport

• _{Data that matches an interest}

‘consumes’ it.

• _{Interest must be re-expressed to get}

new data. (Controlling the

re-expression allows for trafc

management and environmental

adaptation.)

• _{Multiple (distinct) interests in same}

(44)

Caching

• _{Storage for caching NDOs is an}

integral part of the ICN service.

• _{All nodes potentially have caches;}

requests for NDOs can be satisfed by

any node holding a copy in the cache.

• _{ICN combines caching at the network}

edge as in P2P and other overlay

(45)