Thanks for the reference :) Yes, I would also add to your analysis the existing and in-development protocols for different and larger types of data such as media, software and such :

Bitmessage has a primitive protocol for expiring old data based on time to live, after which point the nodes can remove old messages for space for new ones. 

Maidsafe is a protocol loosely based on bittorrent but with a scheme for charging rent on the space. I have an old post with old ideas related to this in my "Agora" network system.

My idea is more from a perspective of converging the protocols and linking them together, as a fluid, seamless whole that is regulated by utilisation. In my conception, there is a need for nodes to have a challenge protocol to ensure data stores indeed have the data (replay attack resistant) and an insurance system that penalises contract breakers according to frequency and size of failures. It also relates to an in-band currency blockchain for enabling pay-on-the-line access points, as well as programmable to enable location obfuscation.

In particular, the insurance protocol is something both very necessary and quite disruptive as it develops. In the near future, records of reliability like credit records will disincentivise poor service provision, but once there is insurance and reporting systems, next you can move to human interacring actuarial systems as well, and the insurance busts out of the network and flattens insurance companies.

I mention this because as you think through this fluid, demand driven converging network, you realise that making and breaking network contracts with human factors will eventually become a problem. And it is only a small step to income insurance systems (aka UBI, the new fad word for this), and we go to another level. But blockchain systems would give the lowest possible administrative cost, while massively diminishing potential for fraud.