Earlier quoted context omitted.
Things like that makes me wish NDN[1] would succeed. Essentially in this network instead using addressing to address hosts, they address the data. This brings interesting properties, since routers are aware what data is being transferred they can start caching it. In the end no CDNs are needed (network takes care of it) so people can host data themselves without worrying of it getting too popular. [1] https://named-d…
Sounds exactly like https://ipfs.io .
NDN on the other hand is a network protocol that is capable to run without TCP/IP (it's actually designed to be able to replace it). They actually built a testbed: https://named-data.net/ndn-testbed/
Similarly to TCP/IP you can build application that utilize the protocol. In fact I suspect implementing IPFS in NDN would be much easier than in TCP/IP.
In fact looks like someone did just that: https://named-data.net/publications/techreports/ndn-tr-27-nd...
and source code: https://github.com/named-data/NDNFS