Unfortunately, it was up to me...
Read the header.
Very careful attention.
All else is payload.
TCP/IP,
rules for communication
on modern networks.
OSI Model.
Nice academic theory,
no practical use.
802.3,
then IP, then TCP.
Why all these checksums?
Ethernet cable
must be wired correctly or
frame errors will rule.
Fragment offset says,
"Put this here, more is to come."
Ah, reassembly.
To you, to me, to
you, to me, to you, to me,
it's a routing loop.
Multicast IP,
powerful if your routers
speak IGMP.
Destination is
unreachable. Mystery
solved, ICMP.
SYN, ACK/SYN, ACK. Go!
Circuit is reliable.
Stop now. FIN, FIN, ACK.
Advertise windows
if you have memory so
TCP goes fast.
Urgent pointer? I
do not care. Non-compliant
implementation.
Domain Name System,
what is IP for this name?
Or, name for IP?
IN-ADDR.ARPA.
A strange name for a domain!
What is my real name?
SOA record,
so many cryptic numbers
adjusting timeouts.
Japanese art form,
abused by engineer for
examples at work.
First, five syllables.
Second line has seven more.
The last line has five.
Also see: my page of more serious TCP/IP stuff.
Also see: my pictures from Japan.
|
||||||||||||
|
||||||||||||
