Redundancy Elimination for Content-Centric Networking Diego Perino, Matteo Varvello, Krishna P. N. Puttaswamy (Bell Labs, Alcatel-Lucent)

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
1
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

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
2
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

3. Redundancy Elimination (RE) today
Fingerprint
store
Packet
store
Synchronized
Packet
store
Decoding of the packet
Encoding of the packet
Fingerprint computation
3
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

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
4
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

5. ICN-RE design
Intra-server redundancy is the main contributor to the overall redundancy
offload the task of redundancy identification and chunking to the source
files
0x234acdf0 0x234acdf0 0x454fdh0 0x456ggt5
Hash(chunk)= chunk fingerprint
fingerprints
0x234acdf0
0x654dfg0
… chunk
Decoding
Content Analysis
Encoding
Modifications to ICN naming and caching
0x456ggt5
markers Manifest file focus on an extension of the CCN/NDN approach
In the following we
5
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

6. CCN/NDN implementation of ICN-RE
Interest packet: the fingerprint is accommodated at the end of the naming
hierarchical naming scheme
tree or can replace chunking information
ICN-RE
CCN/NDN /bell_labs/page1.html/chunk1
/bell_labs/page1.html/0x234acdf0
/bell_labs/page1.html/chunk1/0x234acdf0
Data Packet: the fingerprint onlyname is used to address a chunk
whole content is used to address a chunk
0x234acdf0
/bell_labs/page1.html/chunk1
CCN/NDN
ICN-RE
6
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

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
• PIT is indexed using chunk fingerprint and not whole content name
/bell_labs/page1.html/chunk1
0x234acdf0
/bell_labs/page1.html/chunk1
0x234acdf0
7
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

8. ICN-RE Evaluation – potential bandwidth savings
Vanilla ICN
(optimistic)
247 452 612 1,110 1,425
• ICN-RE can save up to 40-50% at university and 30-35% at enterprise
• Between 15 and 40% of additionalchunk size [Bytes] w.r.t. vanilla ICN
Average bandwidth saving
8
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

9. ICN-RE Evaluation – naming overhead
25%
27%
30%
• Naming-number of Interest/chunk exchanges trade-off
• 1-7% of overhead for the manifest file (16 Bytes fingerprints)
9
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

10. ICN-RE vs Today s RE designs
• Complexity
• Resiliency
• Extensible chunking
• Storage Efficiency
ICN is an interesting approach
• End-user performance for network wide redundancy
elimination in today s
network!
• Deployability
• RE efficiency
10
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

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
11
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

12. 12
COPYRIGHT © 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.