Just hours after word spread that a group of CU research students and associate professors issued some test results showing that Comcast's traffic shaping was throttling more than just P2P upstream apps, they've agreed to reassess their findings. (See University Study Takes Comcast to Task .)
As a "special notice" on the site put it late Monday afternoon:
Comcast has approached us to better understand our test, the equipment we used and the results of our analysis. We understand that their current network management techniques should not be producing the results we found and that they are not blocking access to any Web sites or email applications. We are committed to working together and will update our analysis once we have additional information. Thank you.
You're welcome. But things have changed even since then. The above message was removed as of early Tuesday morning, replaced with this:
A note regarding our findings: Further experiments have led us to believe that our initial conclusions that indicated Comcast's responsibility for dropping TCP SYN packets and forging TCP SYN, ACK and RST (reset) packets was incorrect. Our experiments were conducted from behind a network address translator (NAT). The anomalous packets were generated when the outbound TCP SYN packets exceeded the NAT's resources available in it's state table. In this case, TCP SYN, ACK and RST packets were sent. We would like to thank Don Bowman, Robb Topolski, Neal Krawetz, and Comcast engineers for bringing this to our attention. We sincerely apologize for any inconvenience that this posting may have caused.
And what of those findings detailed in that posting? Like the "special notice" posted earlier, they've been removed as well.
— Jeff Baumgartner, Site Editor, Cable Digital News