RFC 862
Echo Protocol
Echo Protocol π¦
okay bestie, this is RFC 862 π and it's giving classic ARPANET energy. It was written by J. Postel at ISI and dated May 1983. The category is a standard for the ARPA Internet community π, and the header doesn't list anything it obsoletes or updates, so it's a clean slate π§
Hosts on the ARPA Internet that choose to implement an Echo Protocol are expected to adopt and implement this standard β¨
An echo service is lowkey the most useful debugging and measurement tool ever π Its whole thing is that it sends back to the originating source any data it receives. So you send data in, it bounces right back to you. Iconic π
TCP Based Echo Service πΈ
okay so the first flavour is a connection based application on TCP π A server listens for TCP connections on TCP port 7. Once a connection is established, any data received is sent back. This keeps going until the calling user terminates the connection. main character energy π
UDP Based Echo Service π«Ά
and the second flavour is a datagram based application on UDP π A server listens for UDP datagrams on UDP port 7. When a datagram is received, the data from it gets sent back in an answering datagram. no cap, it's the same bounce-back idea, just with datagrams instead of a connection π
π¦ where this page comes from
- ietf: rfc862 1983-05
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms