said by DrCable :

well of course because those peers fully expect you to reply but you are not going to since you dropping the packet out right.

don't drop/deny the packet. un set the RST flag or find a way to ignore the RST flag so you can use the data in that packet to connect to that peer so they know you are there and will send you data.

said by Karl Bode :

I think you'll need to get them to acknowledge it actually exists, first.

I've yet to get an official comment confirming these measures in any markets.

said by Qumahlin :

While you are correct that sandvine is in use and has been for quite some time, it is not used "on" a CMTS. Sandvine works hand in hand with the PacketCable protocol and acts as an application gateway.

This thread is going to garner hate towards sandvine because everyone is basing one users experiences to how things will always work and assuming Sandvine is something installed specifically to block/throttle p2p...that is not the case as there FAR CHEAPER solutions to that issue, many already built into current CMTS's which would negate the need of ever having a Sandvine box and policy server.

Sandvine is an integral application used by quite a few providers that HELPS with bandwidth for P2P, gaming, VOIP, etc. Are there cases where it will cause you to get lower P2P speeds, yes, but there are also cases where it will help with your general latency and will IMPROVE your p2p download speeds.

Sandvine even has a profile for Xbox Live clients (whether this is in use widespread is not known to me, but I know it was used at one point in my area)

Sandvines use at Comcast is not primarily as a P2P blocker, anyone who tells you that is lying or uninformed.

said by funchords :

You might be absolutely right about that. I haven't tried that approach.

(PS: I think this exercise is entertaining, but ultimately the solution is to get Comcast to implement this correctly AND support it, or remove it altogether.)