If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...
If you have a not-so-usual solution for your problems but need to justify it to your boss...
If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...
...then 'No Bugs' Hare on Soft.ware might be the right place for you.
Your mileage may vary. Batteries not included

Assorted Rants Tagged ‘IP’, page 1:

Packet Loss for an App-Level Developer. Part II. Last Mile, Wi-Fi, and Summary

Quote: “Burstable packet loss. May be caused by a neighbor preparing his breakfast”
Another Quote: “if there is a NAT device on the way from your Client to your Server – a sudden IP change can occur with absolutely no notification to Client whatsoever.”

Packet Loss for an App-Level Developer. Part I. Router Failures, BGP Convergence Time, AQM, Traffic Shapers.

Quote: “All the routers, switches (actually – pretty much each and every device which forms Internet infrastructure) – are allowed to drop each and every packet.”
Another Quote: “TCP, when it observes a dropped packet, interprets it as an indication of congestion – and slows down.”

UDP from MOG Perspective

Quote: “you may think of UDP as of an analog of good old C: you can do pretty much everything, but it is not because the language helps you – it is rather because it doesn’t stand in the way :-)”
Another Quote: “As most of the routers (including pretty much every backbone router out there) are not configured to support multicast, it makes multicast over the public Internet hopeless :-(“

Part V: UDP of 64 Network DO’s and DON’Ts for Game Engines

Quote: “In general, lag and jitter are not specific to UDP, and manifest themselves for absolutely any Internet connection.”
Another Quote: “If you need a globally-reachable server with single-digit-ms lag for all the players, it is simply not possible”