From 4c98f8aa896d49df52ba6b9a0aca488e00c41d63 Mon Sep 17 00:00:00 2001
From: "David M. Syzdek" <david@syzdek.net>
Date: Sat, 8 Feb 2020 17:06:54 -0900
Subject: docs: adding standards

---
 docs/TR-143.pdf | Bin 0 -> 1583697 bytes
 docs/rfc862.txt |  57 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 57 insertions(+)
 create mode 100644 docs/TR-143.pdf
 create mode 100644 docs/rfc862.txt

(limited to 'docs')

diff --git a/docs/TR-143.pdf b/docs/TR-143.pdf
new file mode 100644
index 0000000..2ba55a2
Binary files /dev/null and b/docs/TR-143.pdf differ
diff --git a/docs/rfc862.txt b/docs/rfc862.txt
new file mode 100644
index 0000000..016389b
--- /dev/null
+++ b/docs/rfc862.txt
@@ -0,0 +1,57 @@
+
+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]
+
-- 
cgit v1.2.3