![Page 1: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/1.jpg)
1 Challenge the future
Globally Accesible Names in
Named Data Networking
19-4-2013
Network Architectures and Services
Ir. Niels van Adrichem
Dr. ir. Fernando Kuipers
![Page 2: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/2.jpg)
2 Challenge the future
Outline
• Named Data Networking
• Problem Statement
• Proposal
• Measurements
![Page 3: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/3.jpg)
3 Challenge the future
Named Data Networking
• Route-and-cache by name
• Rely on next hop to either
• Deliver ContentObject (from cache)
• Send out Interest to a node closer to the information
Introduction
V. Jacobson, D. K. Smetters, J. Thornton, M. F. Plass, N. Briggs, and R. Braynard, “Networking Named Content,” CoNEXT 2009, 2009.
![Page 4: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/4.jpg)
5 Challenge the future
Problem
• 200 million routable domain names
• Excluding routable subdomains
• Plus a more expensive string prefix over bit-wise prefix match
• Compare to 450.000 IP subnets over 45.000 ASes
• 500 x complexity increase
• Too large for global routing tables!
Excessive global routing table size
![Page 5: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/5.jpg)
6 Challenge the future
Problem
• Compulsory participation in routing discovery to share data
• Difficult due to disconnection of routing scopes
• Too complex for end-users to configure and maintain
Content availability
![Page 6: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/6.jpg)
7 Challenge the future
Proposal
• Decouple user-registered names from routable names
• Routable names aggregate to underlying topology
• User-registered names translate into location-dependent
names
• Receiving sites rename to original names
Map context-related names to routable names
![Page 7: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/7.jpg)
8 Challenge the future
Mapping
![Page 8: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/8.jpg)
9 Challenge the future
Mapping
DNS
![Page 9: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/9.jpg)
10 Challenge the future
Mapping
DNS
![Page 10: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/10.jpg)
11 Challenge the future
Mapping DNS
![Page 11: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/11.jpg)
12 Challenge the future
Mapping Functionality of entry-points
![Page 12: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/12.jpg)
13 Challenge the future
Signing and Authenticity
• CCNx / NDN signs each ContentObject
• Changing the name invalidates signature
![Page 13: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/13.jpg)
14 Challenge the future
Signing and Authenticity
• CCNx / NDN signs each ContentObject
• Changing the name invalidates signature
1. Ignore signatures while renamed
![Page 14: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/14.jpg)
15 Challenge the future
Signing and Authenticity
2. Encapsulate ContentObject into a new one
![Page 15: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/15.jpg)
16 Challenge the future
Renaming and Signing Cost
• Measured 3.600 RTTs using ccnping 1
• Regular CCNx
• Renaming CCNx
• Encapsulating and re-signing CCNx
Experiments
1. Cheng Yi, “ccnping” ,On-line: https://github.com/NDN-Routing/ccnping
![Page 16: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/16.jpg)
17 Challenge the future
Renaming and Signing Cost
• Ping RTT Averages: Penalty:
• CCNx: 2.338 ms
• CCNx Renaming 5.327 ms +2.989
• CCNx Encapsulation and 9.031 ms +3.704
re-signing
Results
![Page 17: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/17.jpg)
18 Challenge the future
Take-home message
• Decreased global routing table complexity
• From 200 million to 45.000 forwarding entries
• Compared to 450.000 entries in IP
• Enabled content sharing using context-related names
• Without the necessity to apply routing discovery
• Both by applying mapping and renaming of context-related
names to routable names
![Page 18: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/18.jpg)
19 Challenge the future
Recursive Name Generation
By applying path-vector routing discovery
![Page 19: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/19.jpg)
20 Challenge the future
Recursive Name Generation
By applying path-vector routing discovery
![Page 20: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/20.jpg)
21 Challenge the future
Recursive Name Generation
/ISP-A.net/routerBob/PC/Camera /ISP-B.net/routerBob2/TV/Camera
By applying path-vector routing discovery
![Page 21: Globally Accesible Names in Named Data Networking · 2014-05-08 · Challenge the future 3 Named Data Networking •Route-and-cache by name •Rely on next hop to either •Deliver](https://reader036.vdocument.in/reader036/viewer/2022070717/5edd683aad6a402d66687d49/html5/thumbnails/21.jpg)
22 Challenge the future
Implementation Online
https://github.com/TUDelftNAS