Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Echo process (RFC0347)

IP.com Disclosure Number: IPCOM000003537D
Original Publication Date: 1972-May-30
Included in the Prior Art Database: 2000-Sep-13
Document File: 1 page(s) / 1K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Postel: AUTHOR

Abstract

Echo Process

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 100% of the total text.

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 ]