CARVIEW |
Select Language
HTTP/2 200
date: Thu, 17 Jul 2025 03:28:33 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 07:28:33 GMT
cache-control: public, max-age=14400
server: cloudflare
cf-ray: 9606a65e89bbc1c7-BLR
content-encoding: gzip
alt-svc: h3=":443"; ma=86400
RFC 347 - Echo process
Report a datatracker bug
Network Working Group Jon Postel Request for Comments : 347 Computer Science UCLA-NMC NIC 10426 30 May 72 Categories: Standard Processes Echo Process I suggest that for debugging and measurement purposes those hosts which are willing implement an "Echo" process. This echo process would listen for a request for connection and execute the Initial Connection Protocol (ICP) as specified in NIC 7104 the "Current Network Protocols" notebook. Upon completion of the ICP the echo process would wait for data from the network. When the data is received from the network it is echoed at once, (and the buffer space is re-allocated). By echoed I mean that the data received is sent back over the network, bit for bit with no modification by the echo process. The echo process is terminated by closing the network connections. Note that BBN-TENEX has had such an echo process available for use for a long time. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by BBN Corp. under the ] [ direction of Alex McKenzie. 12/96 ] [Page 1]
Datatracker
RFC 347
RFC
- Unknown
Document | Document type |
RFC
- Unknown
May 1972 Report errata
This RFC is labeled as "Legacy"; it was published before a formal source was recorded.
This RFC is not endorsed by the IETF and has no formal standing in the
IETF standards process.
|
|
---|---|---|---|
Select version | |||
Authors |
Email authors |
||
RFC stream | Legacy | ||
Other formats |