RFC 312 (rfc312) - Page 2 of 2


Proposed Change in IMP-to-Host Protocol



Alternative Format: Original Text Document



            3)  IMP-to-Host message type 10 will be defined to mean:
                "A Host-to-IMP message was too short (and cannot be
                identified)."

            4)  IMP-to-Host message type 11 will be defined to mean:
                "A Host-to-IMP message was too long; the message is
                identified by the 'source' and 'link number' bits
                of this error message."

            5)  IMP-to-Host message type 12 will be defined to mean:
                "A Host-to-IMP message with an illegal message type
                code was received; the message is identified by the
                'source' and 'link number' bits of this error message.
                (Note that the erroneous type code is not included in
                the error message.)"




   AAM/jm



       [ 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   ]