From 4bfd864f10b68b71482b35c818559068ef8d5797 Mon Sep 17 00:00:00 2001 From: Thomas Voss Date: Wed, 27 Nov 2024 20:54:24 +0100 Subject: doc: Add RFC documents --- doc/rfc/rfc71.txt | 42 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 doc/rfc/rfc71.txt (limited to 'doc/rfc/rfc71.txt') 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] + + + + + -- cgit v1.2.3