For those you are wondering, this is a webserver that serves an HTML page in a single TCP packet. I guess ≤ 1500 bytes to avoid fragmentation - shows as 1.1KB in Chrome's network view. The HTML contains embedded JavaScript that runs a simple demo with animated ASCII and playing a LOUD changing audio tone.
Sure but on the actual internet how often are IP headers larger than 20 bytes because options are turned on? Not very often. The 20 bytes each for TCP and IPv4 is a pretty good assumption.
From the paper "IP Options are not an option" which is good quick read:
"We have studied the dependability of IP options-enabled
network packets in the Internet. We found that overall, approximately half of Internet paths drop packets with options"[1]
Sure I know how to view them. I guess the commenter meant the HTTP headers for just this site were 63 bytes. I thought they were speaking on average like they were for 40 bytes for TCP/IP headers.
This would be really great without the audio. Due to the sound of the audio my initial reaction is to be fascinated, followed immediately by discomfort.
You can visit the demonstration website here: http://packet.city/
You can see a screenshot of the demo here: http://www.p01.org/128b_raytraced_checkboard/