NDN and friends
Named Data Networking (NDN) and related ICN designs improve delivery: fetch named data without depending on a host IP. That is valuable and still orthogonal to application / DevX label life cycle.
Two naming failures (do not conflate)
| Layer | What it names | Representative work |
|---|---|---|
Network / delivery |
How to fetch named data without host-IP coupling |
NDN / ICN (e.g. NSF Future Internet lines of work) |
Application / DevX |
How dependents stay correct when symbols, paths, or docs change |
Kythe / Sourcegraph; OpenRewrite; Unison CAS; |
A perfect delivery plane still treats /docs/v1 and /docs/v2 as unrelated names unless the application plane carries identity, pointers, and reverse consumers.
Deep links
-
HCI — Labels versus wires (Two naming failures)
-
connectome-fs (Where NDN fits)