I would switch DNS to a pure tree and add discoverability as also locality-aspects. By which I mean, put the TLD at the front, not xyz.com, but /com/xyz. And in

I would switch DNS to a pure tree and add discoverability as also locality-aspects. By which I mean, put the TLD at the front, not xyz.com, but /com/xyz. And in the first levels you would automatically get a listing of all valid entries back. Similar I would add local entries, like postal codes and states. So people could do something like /usa/texas/ and get a list of all cities, or /usa/postalcode/90210/ and you would get a list of all companies and websites in the area. I would also change HTTP to be modular, allowing to add new sub-protocols which would be automatically compatible with old clients. So we could do something like http/imap or http/ftp on top of http, and unprepared clients would still be somewhat compatible to this, but adapted clients could fully utilize those protocols. Thing is, http is not the most perfect protocol, but it's a very pragmatic and straight forward one, which IMHO is the main reason why it succeeded, where other protocols failed. SO instead of adding another batch of protocols that barely anyone will use and support, it would be better to high jack the existing solution, and slowly extend it. Also, I would make it Illegal to have proprietary protocols, data formats and obfuscated apps. Give the people the power they deserve. You can't open the cloud and business, but at least networks should be balanced for all involved sides.