The RFC Archive
 The RFC Archive   RFC 347   « Jump to any RFC number directly 
 RFC Home
Full RFC Index
Recent RFCs
RFC Standards
Best Current Practice
RFC Errata
1 April RFC



IETF RFC 347

Echo process

Last modified on Thursday, March 13th, 1997

Permanent link to RFC 347
Search GitHub Wiki for RFC 347
Show other RFCs mentioning RFC 347







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 top


Echo process RFC TOTAL SIZE: 1377 bytes PUBLICATION DATE: Thursday, March 13th, 1997 LEGAL RIGHTS: The IETF Trust (see BCP 78)


RFC-ARCHIVE.ORG

© RFC 347: The IETF Trust, Thursday, March 13th, 1997
© the RFC Archive, 2024, RFC-Archive.org
Maintainer: J. Tunnissen

Privacy Statement