According to Mark, TCP/IP is **WRONG WRONG WRONG WRONG WRONG** (did I get the correct number there, Mark?). No attempt at error recovery, much less error detection. And it has no flow control. And it seems to exhibit poor behavior across multiple slow links (i.e. from my house to his house).
Mark has experience with telephony protocols, which include things like error detection, error recovery, retransmission, duplication detection, flow control and a dozen other features that the designers of TCP/IP either left out or left to higher level protocols.
Amazingly enough, Mark actually likes the OSI Seven Layer Burrito™ protocol model.
Other **NOTE** to self: Don't even bring up the higher level protocols like SMTP or HTTP with Mark.