First draft of Slideshow for a mesh and content Centric Networking workshop at Solid State Depot, the Boulder Hackerspace (http://boulderhackerspace.com/). Check out the meetup for future events (http://www.meetup.com/Solid-State-Depot-The-Boulder-Hackerspace/) and feel free to email ryan@nei.ghbor.net with any questions/comments/ideas.
More than Just Lines on a Map: Best Practices for U.S Bike Routes
Mesh and Content Centric Networking
1. Content Centric Mesh Networking
Ryan Bennett - Nei.ghbor.Net
Setting up encrypted, scaleable networking infrastructure to annoy
the NSA
2. Overview
➲ Understand Basic Networking
➲ Learn about ad-hoc, mesh, and content
centric networks
➲ Learn how to install and configure nodes as
part of an encrypted, Peer-to-Peer, scalable
network infrastructure
➲ Plan further exploration
3. Long-term goal
➲ A robust, global accessible, but locally
focused network
➲ The Internet gave us a global village, the
'Nei.ghbor.Net' aims to give us a
neighborhood village.
➲ Resource-sharing, alert systems,
organizational tools, civic engagement.
➲ Uncensorable, anonymous, strong
encrypted
4. The Present Situation
➲ Everything you do on the internet is
watched
➲ Your ability to engage is blunted by ISP
bottlenecks and
liable to get lost in the noise.
➲ IP – the 'thin waist' of the internet
➲ ISP hierarchy, exchange points, undersea
fibreoptics
5. Ad-hoc and Mesh Networking
➲ Ad-hoc connects to devices in range
➲ Mesh protocols stitch this into a routable
network
➲ (Potentially) Routerless
➲ OSLR, Babel, Batman-adv, Serval...
CJDNS!
6. CJDNS
➲ Started by Caleb James Delisle on
r/DarkNetPlan
➲ 'Web of Trust' Encryption/ per session keys
➲ Works over IPv4 tunnel/ad-hoc
➲ Static IPv6 via brute force keygen
➲ Test network 'Hyperboria'
➲ #hyperboria on EFNet
➲ Pros: ubiquitous crypto, link-agnostic, quick
➲ Cons: bottlenecks, no windows/openWRT
7. Content Centric Networking
➲ Spearheaded by Van Jacobson at PARC in
response to
Internet hiccoughs (especially with viral
video)
➲ Reimagines 'thin waist' as named content
vs named routes
➲ Endless lateral game of 'go-fish'
➲ Caching by design
➲ Bittorrent at the router level
➲ Establishes naming structure rules,
conventions are up to us:
8. CCNx Pros and Cons
➲ Pros:
'serverless' networked applications; scaleable
distribution of popular content; simplified code
for sourcing data; Stable development and
adoption expectations
➲ Cons:
version 0.7 (Alpha by PARC standards); No
windows/OpenWRT support (yet); first request
for data takes longer than traditional IP;
Completely new networking ecosystem with
few established 'best practices'
9. Putting the 'Work' in Workshop
➲ Setting up CJDNS
https://github.com/cjdelisle/cjdns#how-to-
install-cjdns
➲ -peering via LAN/Nei
➲ -testing hyperboria connectivity
➲ Setting up CCNx
➲ http://blog.rungeek.com/post/1711470902/project-c
➲ Config file via CJDNS IPv6
➲ Test with CCNChat
10. Further Development
➲ Geographical Content Naming Convention
➲ Lat/Lng to MGRS (Military Grid Reference
System)
➲ SE/FT/13/42/77/12/<app>/<content>
➲ Javascript API/Platform
➲ NDN-js and Web-RTC/Websocket