ndn-cxx (C++) with experimental (security) extensions
NDN Forwarding Daemon (NFD)
Named Data Link State Routing Protocol (NLSR)
Next-Generation NDN Repository
traffic dump (ndndump)
Content Store (table)
Pending Interest Table (PIT)
Forwarding Information Base (FIB)
Data security (signing) at the thin waist.
Routers announce name prefixes.
Congestion collapse doesn’t occur
<quote ref=”here“>Built on top of NDN’s basic Interest-Data communication model, Sync utilizes naming conventions to enable multiple parties to synchronize their datasets by exchanging data digests, so that individual parties can discover and retrieve new and missing data in a most efficient and robust manner. We expect that Sync’s role in the NDN architecture will evolve to one similar to TCP’s in the IP architecture.</quote>
Van Jacobson, Diana K. Smetters, James D. Thornton, Michael Plass, Nick Briggs, Rebecca Braynard; Networking Named Content; In Communications of the ACM; Volume 55, Issue 1; 2012-01; pages 117-124; paywalled.
Matthew Caesar, Tyson Condie, Jayanthkumar Kannan, Karthik Lakshiminarayanan, Ion Stoica, Scott Shenker; Routing on Flat Labels; In Proceedings of the ACM Special Interest Group on Communication (SIGCOMM); 2006-09-11; 12 pages; paywalled.
J.H. Saltzer, D. P. Reed, D. D. Clark; End-to-End Arguments in System Design; In Proceedings of the Second International Conference on Distributed Computing Systems (ICDCS); 1981-04-08-10; pages 509-512 (10 pages).
An unbounded namespace => how to maintain control over the routing table sizes?
Can lookup of variable-length, hierarchical names can be done at line rate?
[They] are working on efficient signatures, usable trust management, network security, content protection and privacy.
Avery Pennarun <firstname.lastname@example.org> via the README
iptables REDIRECT on client
multiplexer on server for outbound
multiplexer on client for inbound
<quote>sshuttle assembles the TCP stream locally, multiplexes it statefully over an ssh session, and disassembles it back into packets at the other end. So it never ends up doing TCP-over-TCP. It’s just data-over-TCP, which is safe.</quote>
<quote>After connecting to the remote server, sshuttle uploads its (python) source code to the remote end and executes it there. </quote>
<quote>Unlike most VPNs, sshuttle forwards sessions, not packets. That is, it uses kernel transparent proxying (`iptables REDIRECT` rules on Linux, or `ipfw fwd` rules on BSD) to capture outgoing TCP sessions, then creates entirely separate TCP sessions out to the original destination at the other end of the tunnel.</quote>
Merges Fast Forward, Double Vision, Tunnel Vision
redo (a make clone)
(ssh) shell access
PermitTunnel in sshd_config
IPv6, the code seems to be IPv4 “dotted quad” only.
Hongtao Yin, Haiyong Xie, Tina Tsou, Diego Lopez, Pedro Aranda, and Ron Sidi, “SDNi: A Message Exchange Protocol for Software Defined Networks (SDNS) across Multiple Domains,” Internet Draft, work in progress, 2012-06, draft-yin-sdn-sdni-00.