4 ms·
I still think that NDN [0], Named Data Networking, is the proper successor to TCP/IP. TCP is oriented around streams, but NDN is oriented around blobs of data a
by lidHanteyk 6y ago
I still think that NDN [0], Named Data Networking, is the proper successor to TCP/IP. TCP is oriented around streams, but NDN is oriented around blobs of data and names which represent them; as such, NDN is much closer to the application-level concerns that we care about.
The main problem is that namespacing is an extremely political process in any system, including NDN, and so we cannot have nice things.
[0] https://named-data.net/ https://named-data.net/
- ChristianBundy 6y agoAre there ways to try NDN-like networks today? I spend most of my time building P2P stuff and the "how do I connect my computer to yours" is consistently a major pain point. STUN/TURN can help, but there are so many edge-cases that hurt my brain to think about.
- zamadatix 6y agoI think NDN is largely orthogonal to the problems presented in the article.
- wmf 6y agoAgreed; any NDN implementation would still need a handshake, flow control, in-order delivery, etc.