summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc863.txt
diff options
context:
space:
mode:
authorThomas Voss <mail@thomasvoss.com> 2024-11-27 20:54:24 +0100
committerThomas Voss <mail@thomasvoss.com> 2024-11-27 20:54:24 +0100
commit4bfd864f10b68b71482b35c818559068ef8d5797 (patch)
treee3989f47a7994642eb325063d46e8f08ffa681dc /doc/rfc/rfc863.txt
parentea76e11061bda059ae9f9ad130a9895cc85607db (diff)
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc863.txt')
-rw-r--r--doc/rfc/rfc863.txt58
1 files changed, 58 insertions, 0 deletions
diff --git a/doc/rfc/rfc863.txt b/doc/rfc/rfc863.txt
new file mode 100644
index 0000000..a841f82
--- /dev/null
+++ b/doc/rfc/rfc863.txt
@@ -0,0 +1,58 @@
+
+
+Network Working Group J. Postel
+Request for Comments: 863 ISI
+ May 1983
+
+
+
+ Discard Protocol
+
+
+
+
+This RFC specifies a standard for the ARPA Internet community. Hosts on
+the ARPA Internet that choose to implement a Discard Protocol are
+expected to adopt and implement this standard.
+
+A useful debugging and measurement tool is a discard service. A discard
+service simply throws away any data it receives.
+
+TCP Based Discard Service
+
+ One discard service is defined as a connection based application on
+ TCP. A server listens for TCP connections on TCP port 9. Once a
+ connection is established any data received is thrown away. No
+ response is sent. This continues until the calling user terminates
+ the connection.
+
+UDP Based Discard Service
+
+ Another discard service is defined as a datagram based application on
+ UDP. A server listens for UDP datagrams on UDP port 9. When a
+ datagram is received, it is thrown away. No response is sent.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Postel [Page 1]
+