|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Fri, 19 Oct 2007 16:53:03 -0600 From: Sean Figgins <sean@labrats.us> To: Nanog <nanog@nanog.org> In-Reply-To: <471915FF.5090509@spaethco.com> Errors-To: owner-nanog@merit.edu Eric Spaeth wrote: > It's worth noting that the traffic Comcast is filtering is called out in > their Terms of Use in the "PROHIBITED USES AND ACTIVITIES" section, > paragraph xiv. http://www.comcast.net/terms/use.jsp That section could be applied to every application that you would run on your computer that access the Internet. The "program, equipment or servers... that provide network content or any other services" clause is really quite laughable. Clearly, this would apply to every p2p application out there, but it would also apply to many other, such as video conference, net meeting, online games, remote access to your PC (VNC/RDP/goto-my-pc), AIM, IRC, etc. I'm sure it probably could be applied to every possible IP aware application. Eric Spaeth wrote: > With rate-shaping they would need to have the P2P identification widget > in-line with the data path to be able to classify and mark traffic so > that it can be queued/throttled appropriately. The Sandvine, in particular, is designed to be placed in-line like this. It does, however, deploy a technology to shunt the traffic through the device in the event that the server craters. Many network devices do this now. -Sean (Please respond only to the list)
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |