Thanks for the networking discussion, folks. I want to underscore this twice:
I see so many debates about the possible limitations of Lightning Network that miss this. It's not an end product set in stone, it will constantly evolve to address any issues that arise. That's not so easy to do in blockchain where much was set in stone in the genesis block.
Sohow would you take all this networking knowledge, and apply it to routing and network topology in Lightning? More to the point (and my original question), are the Lightning devs doing soand if so, how?
(Aside, or perhaps not: Shifting analogies around and down to the link layer, per OPs article, we no longer have only a broadcast network as with old Ethernet hubs. There is a reason I thought of Spanning Tree first.)
I see plenty of speculation about what LN will look like, topology-wise. Yet much of that depends not only on what potential links are available, but also on how nodes use them. I dont see how a simple look-up table would suffice. If you are connected to A, B, and C, and you want to reach Z, thats not an easy problem. Its not easy in the first instance; and however its answered now, I expect that could be fertile ground for optimization in the future.