[ale] OT: FCC and ISP

[Scott Plante]

I don't like the idea of my ISP going around to different websites, i.e. content providers, and saying "we're going to slow down your traffic unless you pay us." But what about a situation where a video streaming site says to an ISP, "Hey, we've got a lot of users using your service--how about if we park a rack of servers with copies of our most popular videos in your datacenter and pay you for the hosting." Those videos would be much faster than the competitors and it'd also save the website on their own bandwidth costs. Or say the website has a datacenter 2 blocks from the ISPs and says, "How about you run fiber directly to our datacenter and we'll route the traffic to your customers over that instead of the backbone. You can charge us so long as it's a good bit less less than what we pay for our regular internet bandwidth." Those kind of arrangements seem to be sensible and a good way to cut costs all around. 


I'm afraid writing rules on net neutrality that disallow the first but allow the second and third, and take care of the other cases I haven't thought of could get pretty tricky. Does anyone know what the recently struck down rules would have said about these three scenarios? 


Scott 

----- Original Message -----

From: "Boris Borisov" <bugyatl at gmail.com> 
To: "Atlanta Linux Enthusiasts" <ale at ale.org> 
Sent: Thursday, January 16, 2014 9:26:53 AM 
Subject: [ale] OT: FCC and ISP 


This is a little bit related with my previous post for Comcast latency/jitter problem. I know is against ale group rules but I feel it is important. 

http://www.theverge.com/2014/1/14/5307650/federal-court-strikes-down-net-neutrality-rules 

_______________________________________________ 
Ale mailing list 
Ale at ale.org 
http://mail.ale.org/mailman/listinfo/ale 
See JOBS, ANNOUNCE and SCHOOLS lists at 
http://mail.ale.org/mailman/listinfo 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20140116/68a93443/attachment-0001.html>