A New Way to look at Networking

Ye olde, but still worth watching: Van Jacobson's Google Talk from 2006, "A New Way to look at Networking": [VIDEO]

Any bashing on Named Data Networking? [LINK] Rather than the system getting less reliable exponentially as it scales up, it gets more reliable exponentially as it scales up. [VIDEO] Integrity and trust are properties of the data; not of the way that you obtain ​it. [VIDEO] There's no routing. You get rid of all of the routing chatter. You get rid of all of the routing brittleness. [LINK] We wanted to turn around the incentive structure where right now senders have a lot of power and receivers have basically nothing, they have to eat what they're fed. [LINK]

Very good reading. I'd also recommend Van Jacobson's talk [VIDEO] You'll learn some good stories about internet history. He has done a lot of work on TCP congestion control, especially the fast retransmission idea by using duplicate ACKs. There is an interesting thing about TCP. A lot of popular TCP implementation use city names, e.g. TCP Reno, TCP Vegas, TCP Westwood. TCP Westwood is a very interesting implementation. It has very intelligent way to estimate bandwidth, (not just based on duplicate ACKs). You may find this paper very interesting. [LINK]

In what ways is this different/similar from "content centric networking"? [VIDEO] (Google Tech Talk from Van Jacobsen on CCN many years ago)

Named-data networking is literally what this is describing, except NDN works as a replacement for TCP, not HTTP. In the long term I'd rather have it work at a lower level and not have to think about it much. [VIDEO]

NDN is the way p2p no huge IP infrastructure between nodes interest packets at narrow waist (like human attention, scarce) sign all packets, more secure, easier to trust|not hash for pointers, no surprises in containers crypto apply more cryptography, less web3 baloney broadcast radio native, no emulation of copper wire data, closer to where you want, find faster, keep content you want w/out intermediation, need to find "where" within IP/udp/tcp addresses [LINK] node to node [LINK] more application, less security hassle [LINK] hash name the data [VIDEO] data integrity w/out need to trust foreign server

Consider a society that has left Earth. If light takes minutes to travel between locations, is a chatty protocol what you want? Or do you need a whole host of different application-level solutions to this problem? There's a different lens to look at it. There's an old tech talk that got me out of the IP-shaped box a lot of us are trapped in: [VIDEO] I got Gemini 1.5 Pro to summarize the transcript, which I butchered a bit to fit in a text box: The Problem: The Internet is treated as a binary concept: You're either connected or not, leading to issues with mobile devices and seamless connectivity. The focus on connections (TCP/IP conversations) hinders security: Security is tied to the pipe, not the data, making it difficult to address issues like spam and content integrity. Inefficient use of resources: Broadcasting and multi-point communication are inefficient as the network is unaware of content, leading to redundant data transmission. The Proposed Solution: Data-centric architecture: Data is identified by name, not location. This enables: Trust and integrity based on data itself, not the source. Efficient multi-point communication and broadcasting. Seamless mobility and intermittent connectivity. Improved security against spam, phishing, and content manipulation. Key principles: Data integrity and trust are derived from the data itself through cryptographic signatures and verification. Immutable content with versioning and updates through supersession. Data segmentation for