Content Addressable NDN Repository - proposal
Upcoming SlideShare
Loading in...5
×
 

Content Addressable NDN Repository - proposal

on

  • 285 views

 

Statistics

Views

Total Views
285
Views on SlideShare
285
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial LicenseCC Attribution-NonCommercial License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Content Addressable NDN Repository - proposal Content Addressable NDN Repository - proposal Presentation Transcript

  • Content Addressable NDN Repository proposal Junxiao Shi, 2013-09-24
  • Problem: caching relies on exact Name • Local router has /repo/file1/version1 in its cache • Consumer wants /repo/file1/version2 • File contents are similar, but local router can’t find it due to different Names cache remote routerlocal routerconsumer /repo/file1/version1 /repo/file1/version2 Internet LAN
  • Solution Overview • Publisher segments files using Rabin fingerprints. • Repository indexes segments by SHA256 hashes. • Metadata records segment hashes. • Consumer retrieves metadata, requests segments by hash from neighbors, and downloads missing segments with application-defined name. • Benefit: save Internet bandwidth, shorten download completion time • Suitable scenario: files with similar segments are sitting around neighbors, such as software updates
  • repo remoteconsumerneighbor /repo/file1/version2 Internet LAN /repo/file1/version2/metadata Signed by publisher Content: hashes of segments /%C1.R.SHA256/<hash> Signature ignored
  • Trust Model • The consumer can trust the file if it trusts the signature on metadata. • The signatures on segments retrieved by hash are ignored. /repo/file1/version2/metadata publisher’s signature
  • Implementation & Testing • Implementation: modified repo, custom publisher and consumer tools • Simple test scenario • Many versions of a software's source code in uncompressed TAR format are stored in a remote repo. There should be similarities among those versions. • Several machines in the local area network each retrieves one version of the source code. Some blocks should be obtained from local area network instead of from the remote repo.