News for hackers. Stuff that matters.

A comment on Why TCP Over TCP Is a Bad Idea (2001). Parent comment

Re:Why TCP Over TCP Is a Bad Idea (2001) by zrm on Saturday March 28, 2015 @09:54PM (#9283583)
Timeouts that short violate RFCs. Established TCP connections can't be abandoned unless idle for two hours four minutes (RFC5382 REQ-5) and even UDP timeouts normally have to be at least two minutes (RFC4787 REQ-5).

If people are violating the RFCs then applications that detect it should probably start notifying users exactly why their battery life is suffering.

[ Parent | on HN ]
Re:Why TCP Over TCP Is a Bad Idea (2001) by chias on Sunday March 29, 2015 @11:33AM (#9285159)
I see a lot of "should"s. When push comes to shove, though, a notification is not going to change the behavior of the network.

There's a lot of complaints I have about how some networks (especially mobile ones) deviate from RFCs and break specifications. A 30 second timeout is not nearly at the top.

[ Parent | on HN ]