diff options
author | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
---|---|---|
committer | Thomas Voss <mail@thomasvoss.com> | 2024-11-27 20:54:24 +0100 |
commit | 4bfd864f10b68b71482b35c818559068ef8d5797 (patch) | |
tree | e3989f47a7994642eb325063d46e8f08ffa681dc /doc/rfc/rfc347.txt | |
parent | ea76e11061bda059ae9f9ad130a9895cc85607db (diff) |
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc347.txt')
-rw-r--r-- | doc/rfc/rfc347.txt | 59 |
1 files changed, 59 insertions, 0 deletions
diff --git a/doc/rfc/rfc347.txt b/doc/rfc/rfc347.txt new file mode 100644 index 0000000..42efaa3 --- /dev/null +++ b/doc/rfc/rfc347.txt @@ -0,0 +1,59 @@ + + + + + + +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] + |