summaryrefslogtreecommitdiff
path: root/doc/rfc/rfc71.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/rfc71.txt
parentea76e11061bda059ae9f9ad130a9895cc85607db (diff)
doc: Add RFC documents
Diffstat (limited to 'doc/rfc/rfc71.txt')
-rw-r--r--doc/rfc/rfc71.txt42
1 files changed, 42 insertions, 0 deletions
diff --git a/doc/rfc/rfc71.txt b/doc/rfc/rfc71.txt
new file mode 100644
index 0000000..8c374c5
--- /dev/null
+++ b/doc/rfc/rfc71.txt
@@ -0,0 +1,42 @@
+
+
+
+
+Network Working Group Tjaart Schipper
+Request for Comments #71 25 September 1970
+ UCLA-CCN
+
+
+ Reallocation in Case of Input Error
+
+
+In case of reading a message from the IMP, it may be impossible for the
+receiving NCP to determine the length of the message if an input error
+occurs. The following protocol will be used at the CCN-Host at UCLA to
+resynchronize flow control.
+
+If an input error is detected and the NCP can find the intended link
+number, it will send a GVB with frac = O to the sending Host and disregard
+further incoming messages on that link. When the RET has been received, a
+new ALL will be sent.
+
+If the sending Host is not waiting for a RFNM when the GVB arrives, it will
+send the RET immediately. If it is waiting for a RFNM corresponding to the
+message with the error or a RFNM corresponding to a following message, it
+will send the RET after the RFNM has been received.
+
+In this way, the receiving Host will know that the link is clear before it
+issues a new ALL.
+
+TS/rb.
+
+
+
+
+ [ This RFC was put into machine readable form for entry ]
+ [ into the online RFC archives by Alexandra Weikert 7/97]
+
+
+
+
+