What major milestones stand in the way of a global production-ready ipfs network?

[misrab]

Thought it might be worth having the major hurdles listed in one place (don't think they are?)
e.g.
• DHT not yet scalable because x, y, z, see here for more info...
etc.

Thanks! (If this is a repeat, sorry! Just let me know and I'll close this issue)

[whyrusleeping]

This isnt a bad idea to have. I'll bite :)

• Thoughts on the next level of content routing for ipfs #162

  • Our use of the DHT for content routing is very inefficient, we need to find a new solution to this issue. This one is a must.

• The packet switching endeavour #143

  • Packet switched networks have a greatly increased connectivity and in general can be more reliable and efficient. This is a quite nice to have

• On "DialMe", NAT traversal, Relay, line switching, packet switching (libp2p protocols) #110

  • Relaying connections and connection requests (arguably can be done with the same code) are just about required for getting the level of connectivity between peers we need for a truly global ipfs network.

I'm sure i'll think of a few more, but thats a quick pass from me

[ghost]

I dunno, it's way too vague of a question. @misrab which use cases do you have in mind, and which grade of production-readiness?