| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 17 Jul 2025 09:27:25 GMT
content-type: text/html; charset=utf-8
content-security-policy: default-src 'self' 'unsafe-inline' data: https://datatracker.ietf.org/ https://www.ietf.org/ https://ietf.org/ https://analytics.ietf.org https://static.ietf.org; frame-ancestors 'self' ietf.org *.ietf.org meetecho.com *.meetecho.com
cross-origin-opener-policy: unsafe-none
referrer-policy: strict-origin-when-cross-origin
strict-transport-security: max-age=3600; includeSubDomains
vary: Cookie, Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
cf-cache-status: REVALIDATED
expires: Thu, 17 Jul 2025 13:27:25 GMT
cache-control: public, max-age=14400
server: cloudflare
cf-ray: 9608b40cdc0fc18d-BLR
content-encoding: gzip
alt-svc: h3=":443"; ma=86400
RFC 862 - Echo Protocol
Report a datatracker bug
Network Working Group J. Postel
Request for Comments: 862 ISI
May 1983
Echo Protocol
This RFC specifies a standard for the ARPA Internet community. Hosts on
the ARPA Internet that choose to implement an Echo Protocol are expected
to adopt and implement this standard.
A very useful debugging and measurement tool is an echo service. An
echo service simply sends back to the originating source any data it
receives.
TCP Based Echo Service
One echo service is defined as 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
continues until the calling user terminates the connection.
UDP Based Echo Service
Another echo service is defined as 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 is sent back in an answering
datagram.
Postel [Page 1]
Datatracker
RFC 862
RFC
- Internet Standard
| Document | Document type |
RFC
- Internet Standard
May 1983 Report errata |
|
|---|---|---|---|
| Select version | |||
| Authors |
Email authors |
||
| RFC stream | Legacy | ||
| Other formats |