RFC 7:Host-Imp Interface
RFC-Ref

host


Click on the red underlined text to get to the source

... This paper is concerned with the preliminary software design of the Host IMP interface. Its main purpose is on the one hand to define ...


... * prepares a 16 bit Host heading (1 bit: trace, 2 bits ...
... 8 bits: link identification no., 5 bits: destination host) * inserts a 16 bits ...
... +- -+ |8080 (max host message length) - 32 (heading + marking)| |-------------------------------------------------------| ...
... They should be large enough for containing the maximum host message text + heading and marking (1006 + 4 = 1010 bytes). ...


... III-1. Why is there not a simple control procedure between the HOST and the IMP? What happens if a message, issued from the HOST ...
... HOST and the IMP? What happens if a message, issued from the HOST, reaches the IMP with an error due to the transmission? ...
... From the BBN specifications it appears that this error will be transmitted as far [as] the receiving HOST. In that case must an HOST ...
... HOST. In that case must an HOST-HOST control procedure be provided? ...
... In that case must an HOST-HOST control procedure be provided? III-2. Where will the special channel ...
... one program to another, etc... HOST (Sigma 7) <--|/|--> Outside world Users |/| | |/| ...



Google
Web
RFC-Ref