Download Future Internet with Information Centric Networks

Future Internet with Information
Centric Networks
Arsitektur Jaringan Terkini
Motivation
Motivation
Current Network
Motivation
• Networking was introduced for resource
sharing
– Named hosts
– Model is point-to-point
The Problem
ISP
ISP
Communication Vs Distribution
Communication
Distribution
Naming
Endpoints
Content
Security
Secure Process
Secure Content
Motivation
• Movement of content
–
–
–
–
Predicted global IP traffic in 2014: 64 exabytes/month (4 fold from 2009) (1)
180 exabytes of content created in 2006 (2)
Global mobile traffic 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
– TLS and SSL secures endpoints
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
– Security
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 Differentiation
–
–
–
–
–
–
Naming
Security
Routing
Caching
Content existence knowledge
Producer-consumer meeting
Today
X
dst
src
Path determined by global routing, not local choice
Structural asymmetry precludes market mechanisms and
encourages monopoly formation
NDN(Named Data Networking)
related to CCN approach
Producer
Consumer
NDN(Named Data Networking)
related to CCN approach
a/b/c/d
Producer
a/b/c/d
Data
Consumer
NDN(Named Data Networking)
related to CCN approach
a/b
Producer
Consumer
• Packets say ‘what’ not ‘where’ (no src or dst)
• Forwarding decision is local
• Upstream performance is measurable
We envision replacing this:
ISP
ISP
With THIS:
ISP
ISP
Content Centric Networks –
Operation
Interest
Data
Check Content Store
Check Pending
Interests Table
Check Forwarding
Information Base
Check Pending
Interests Table
Content Centric Networks – Stack
(1)
• 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) Van Jacobson, et al, Networking Named Content, CoNEXT 2009
Content Centric Networks –
Architecture
Face 1
Content Store
Wireless
Face 2
Pending Interest
Table (PIT)
Wired
CCN Forwarding
Logic
Face 3
Forwarding Information
Base (FIB)
Application
CCN Forwarding Engine
• Each CCN entity has 3 main data structures
– Content Store, Pending Interest Table, Forwarding Information Base
• Uses multicast/broadcast
• Uses “longest prefix matching” lookup for content names
Content Centric Networks – Messages
ContentName
ContentName
Selector
Signature
Nonce
Signature Information
Interest Packet
Data
Data Packet
• Purpose of messages
– Interests request for content
– Data serves these requests
• No fixed length fields and uses an XML encoding format
Content Centric Networks – Names
User/Application Name
Versioning &
Segmentation
/uni-bremen.de/comnets/lecture/Kommunikationsnetze-I.pdf/v1/s0
• Core of CCN uses content names for forwarding
• Applications can interpret names the way they
want
Content Centric Networks - CS
Name
Data
...
...
/uni-bremen.de/comnets/lecture/Kommunikationsnetze-I.pdf/v1/s0
...
...
...
Content Store
• Uses “longest prefix matching”
• Implements policies such as LRU or LFU for content
replacement
• Content do not necessarily have to be persistent (only cached)
Content Centric Networks – PIT
Prefix
Pending Faces
...
...
/uni-bremen.de/comnets/lecture/Kommunikationsnetze-I.pdf/v1/s1
2
...
...
PIT
• Uses “longest prefix matching”
• An entry may point to multiple faces
• Must time out and not held permanently
Content Centric Networks – FIB
Prefix
Forwarding Faces
...
...
/uni-bremen.de/comnets
1, 2
...
...
FIB
• Uses “longest prefix matching”
• Similar to IP FIB
• Destination may have number of faces
Content Centric Networks – Interest
Content Centric Networks – Data
Routing
• Three general approaches
– Name Resolution Routing (NRR)
– Content-based Routing (CBR)
– Name-based routing (NBR)
• Two phases
– Routing of NDO requests
– Routing of NDO back to the requester
Name-Based Routing
• Client asks for a data object sending interest packets
which are routed toward the publisher of the name
prefix using longest-prefix 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 first is forwarded to the source.
• When a copy of the data object is encountered on the
path, a data packet containing the requested object is
sent on the reverse path back to the client and all
nodes along the path cache a copy.
Content Centric Network (CCN)
Chart notes describe numbered steps
CCN packets
There are two CCN packet types:
interest (similar to http “get”) and data
(similar to http response). Both are
encoded in an efficient binary XML.
CCN node model
Get /parc.com/videos/
WidgetA.mpg/v3/s2
Publish-Subscribe Internet Routing
Paradigm (PSIRP)
Chart notes describe numbered steps
Content-based Publish-Subscribe
Routing
Content-based Pub/Sub Routing
Content-based Pub-Sub Routing
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 filter
that routers use for selecting interfaces on which to forward an
NDO.
– Bloom filters encode source route-style forwarding information into
packet headers, enabling forwarding without depending on end-toend 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-efficient switches.
• The use of Bloom filters result in a certain number of false positives;
in this case this means forwarding on some interfaces where there
are no receivers.
Pub/Sub Routing using Link ID and FI
zFilter: FI Bloom Filter
See chart notes for further description
Network of Information
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 different routing algorithms.
– A name-based routing method might be used for the first phase.
– The second and third phases might use a topology-based
routing like IP.
– There are multiple alternatives to loosely or tightly integrate the
phases in an ICN architecture.
Summary of characteristics of the ICN
approaches
Content-Based Security
• Name-content mapping verification via per-data
packet signature
– Data packet is authenticated with digital signature
ICN trust establishment by associating
content namespaces w/ public keys
Basic ICN forwarding
• Consumer ‘broadcasts’ an ‘interest’ over any
& all available communications media:
get ‘/rutgers/ECE544/Lecture06-14.pdf’
• Interest identifies a collection of data - all data
items whose name has the interest as a prefix.
• Anything that hears the interest and has an
element of the collection can respond with
that data:
HereIs ‘/rutgers/ECE544/presentation.pdf/p1’
<data>
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 traffic
management and environmental adaptation.)
• Multiple (distinct) interests in same collection
may be expressed (similar to TCP window).
Caching
• Storage for caching NDOs is an integral part of
the ICN service.
• All nodes potentially have caches; requests for
NDOs can be satisfied by any node holding a
copy in the cache.
• ICN combines caching at the network edge as
in P2P and other overlay networks with innetwork caching (e.g., transparent web
caches)
References
• A Survey of Information-Centric Networking, B.
Ahlgren, et. al. IEEE Communications Magazine,
July 2012
• Named Data Networking. IEEE CCW. Oct 10,
2011. www.named-data. based on Van Jacobson
• Bloom Filters
• http://billmill.org/bloomfilter-tutorial/
• http://en.wikipedia.org/wiki/Bloom_filter#Exampl
es