ccnxcon 2012: session #7: redundancy elimination for content-centric networking

COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

1

Redundancy Elimination for Content Centric Networking Diego Perino, Matteo Varvello, Krishna P. N. Puttaswamy Bell Labs, Alcatel-Lucent CCNx Community Meeting September 13th 2012, Sophia Antipolis, France


2

Redundancy Elimination (RE) today

Redundancy Elimination (RE) is a compelling mechanism used to identify and remove redundant bytes transferred in a network (up to 60%)

Commercial RE products for:

•  Enterprise networks

•  Data centers

•  ISP links

Researchers have proposed to provide RE as a:

•  Primitive IP-layer service

•  End-host solution


3

Redundancy Elimination (RE) today

Fingerprint store

Fingerprint computation

Packet store

Packet store

Encoding of the packet Decoding of the packet

Synchronized


4

AGENDA

1.  ICN-RE design

2. CCN/NDN implementation of ICN-RE

3. Numerical evaluation

4. RE as an ICN deployment scenario

5. Conclusions


5

ICN-RE design

markers

chunk

fingerprints

files

Intra-server redundancy is the main contributor to the overall redundancy

offload the task of redundancy identification and chunking to the source

Content Analysis Encoding

Hash(chunk)= chunk fingerprint

0x234acdf0

0x234acdf0 0x654dfg0

0x456ggt5

…

Manifest file

Decoding

0x234acdf0 0x456ggt5 0x454fdh0

Modifications to ICN naming and caching

In the following we focus on an extension of the CCN/NDN approach


6

Interest packet: the fingerprint is accommodated at the end of the naming tree or can replace chunking information

/bell_labs/page1.html/chunk1/0x234acdf0

CCN/NDN implementation of ICN-RE

/bell_labs/page1.html/0x234acdf0

Data Packet: the fingerprint only is used to address a chunk

CCN/NDN ICN-RE /bell_labs/page1.html/chunk1

Interest packet: hierarchical naming scheme

Data Packet: the whole content name is used to address a chunk

/bell_labs/page1.html/chunk1 ICN-RE CCN/NDN 0x234acdf0


7

CCN/NDN implementation of ICN-RE (cont d)

•  CS is indexed using chunk fingerprint. ICN-RE does not required synchronized caches at sender and receiver side

/bell_labs/page1.html/chunk1

/bell_labs/page1.html/chunk1

•  PIT is indexed using chunk fingerprint and not whole content name

0x234acdf0

0x234acdf0


8

ICN-RE Evaluation – potential bandwidth savings

•  ICN-RE can save up to 40-50% at university and 30-35% at enterprise

Vanilla ICN

(optimistic)

•  Between 15 and 40% of additional bandwidth saving w.r.t. vanilla ICN 247 452 612 1,110 1,425

Average chunk size [Bytes]


9

ICN-RE Evaluation – naming overhead

• Naming-number of Interest/chunk exchanges trade-off

•  1-7% of overhead for the manifest file (16 Bytes fingerprints)

25%

27% 30%


10

•  Complexity

• Resiliency

•  Extensible chunking

•  Storage Efficiency

•  End-user performance

ICN-RE vs Today s RE designs

• Deployability

• RE efficiency

ICN is an interesting approach for network wide redundancy

elimination in today s network!


11

Conclusions • We have proposed an ICN design that supports redundancy elimination

• We have shown it can save between 15% and 40% of additional bandwidth with respect to vanilla ICN

•  ICN-RE is lightweight and support line-speed up to 100 Gbps

•  ICN is a interesting approach for network wide RE

On-going and future work •  Implementation of ICN-RE in the CCNx prototype

•  ICN to support other data compression

techniques as data deduplication

•  Extensive experimental evaluation

Diego Perino, Matteo Varvello, Krishna P. N. Puttaswamy, ICN-RE: Redundancy Elimination for Information-Centric Networking, in Proc. ICN'2012, Helsinki, Finland, August, 2012


12

ccnxcon 2012: session #7: redundancy elimination for content-centric networking

Technology

icn naming

htmlchunk1 icn

chunk ccnndn icn

efficiency icn

performance icn

ccnndn 0x234acdf0 copyright

chunk bell

packet synchronized