If you're going to use conviction and the voice of 'authority' to try to get your points across in a review, it would serve you well to know what you're talking about. For one thing, there's no "minimum legal" IP packet size, and, if there were, it would be 20 bytes (the size of an IP header), not 64. I can very well send a 28 byte ping, though it won't give me time statistics under UNIX/Linux, since they embed a 1-byte UNIX timestamp (though Windows uses an internal tick clock [which is wildly inaccurate] to measures its RTT).
Second, I don't know what "layers" of the "TCP/IP" stack you're talking about, but I don't have them on my computer. For a start, there's no "TCP/IP stack." I'm not sure where that gem got started, but it's a real peeve of mine. An IP stack, sure, but TCP has very little to do with IP itself. It's just another transport protocol (number SIX, in fact). ICMP, IP protocol number ONE, is much more integral to IP than any transport protocol. Second, the only "layers" to IP might be whatever you want to stack ontop of it, but there's nothing inherently layered about IP itself.
Usually, when someone uses that kind of language, they're referring to the OSI model, where Layer 1-3 would mean Physical, Data Link, and Network, and, not, as I guess you were attempting to go for (?), 'IP, TCP, and Session.'
As far as the predictability stupid comments go, particularly the one I've seen re-iterated time and time again about "MY LAN CARDZ SEEZ ONE MILLISECONDS SO HOW CAN IT IMPROEVS THE INTERNET???," uh. Yeah, sure. Your LAN is 0.2 ms. Now, think that through. A connection to the internet generally isn't, particularly under load.