I'd say T-Mo is a great example of why net neutrality is a bad idea. From a purely network engineering point of view, it's efficient to bring those streaming services into the carrier's network instead of sending it over the Internet. Net neutrality prevents the carrier from doing something that makes total technical sense and benefits the customer.
Not really; data passing from the general internet onto the carrier's network (or any wired network) is much much cheaper than that data passing over the limited and contested cellular airwaves. Even if t-mobile has their own cdn servers for the streaming services, the data still has to make the much more expensive hop.
It's really just a marketing technique. Even though music streaming can use a significant amount of data, it's at a safely capped rate. It's probably a lot more effective to market "unlimited music streaming" to the general populace than "500mb more data".
Mobile links are in fact quite often backhaul limited. Especially as you make cell sectors smaller (and in particular with T-Mo, which uses higher frequencies and needs to deploy smaller cells), getting data off the cell sites can become a significant bottleneck: http://www.pcworld.com/article/251838/analyst_mobile_network...
Not yet, but with SD cards now at 512GB capacity, its not out of the realm of possibility to do caching of popular content at-scale across your tower infrastructure.
You're mistaken. Nothing about net neutrality as it is commonly understood prevents the carrier from serving streaming services from their own network. Nothing at all.
