RFC 17:Some Questions Re: HOST-IMP Protocol
RFC-Ref

host


Click on the red underlined text to get to the source

... Some Questions Re: HOST-IMP Protocol ...
... link may be slow due to: i) Busy HOST (many jobs) ii) Much local I/O and/or CPU time ...
... ii) Much local I/O and/or CPU time between messages - is it that, if a HOST's user fails to use a link for 15 seconds, the HOST ...
... HOST's user fails to use a link for 15 seconds, the HOST network program must generate a dummy message merely to keep the link ...
... link open? 2. Steve Crocker, HOST Software, 1969 Apr 7, asks on page 2: "Can a HOST, as opposed to its IMP ...
... 2. Steve Crocker, HOST Software, 1969 Apr 7, asks on page 2: "Can a HOST, as opposed to its IMP, control RFNM's?" BBN, Report No. 1837, ...
... RFNM and then discovers it cannot, for some reason, complete timely delivery of the last received message to its HOST? This seems especially pressing since I don't recall seeing anywhere an IMP ...
... IMP constraint upon HOSTs that they must accept incoming messages within some specified maximum time. ...
... within some specified maximum time. 3. A HOST has to be prepared to repeat transmissions of a message into network (see, e.g., Page 17, BBN 1822) therefore why the ...
... Normally the times involved differ by many orders of magnitude but a high priority non-network HOST responsibility could delay next bit for a long time. ...
... archives by Marc Blanchett 3/00 ] Re: Some Questions Re: HOST-IMP Protocol ...
... IMP's link table will, in general, have no effect upon a Host transmission (or reception) at that IMP's site. Let us distinguish between non-use of a link ...
... link in- between messages and non-use of a link due to Host program delays in the middle of transmitting or receiving ...
... the middle of transmitting or receiving a message. When the Host transmits a message on a link for which an entry is not in the link ...
... link table, one will simply be inserted there. There is no need for "dummy" Host messages to keep a link "open" since a link is ...
... to occur) is there a possibility of resulting delay. Arbitrary delays introduced by Host programs are also not inconsistent with the link entry deletion procedure. A link ...
... delays was only intended to have hardware implications insofar as the Host/IMP interface is designed to transfer bits ...
... bits asynchronously between the Host and the IMP. ...
... IMP's output queue to the Host (i.e. just before a message is sent to the Host). If a destination ...
... queue to the Host (i.e. just before a message is sent to the Host). If a destination IMP ...
... destination IMP cannot then deliver that full message to the Host, at most one more message may possibly arrive at that IMP due to the ...
... RFNM. The new message will subsequently take its place at the end of the output queue to the Host thus guaranteeing the preservation of the proper message arrival sequence. ...
... The NOP message is a special control message which is available for use during initiation of communication between the Host and its IMP. The Host ...
... Host and its IMP. The Host may, of course, decline to send NOP messages during this period, but the first received message after IMP startup or after the ...
... IMP startup or after the Host ready indicator has gone on, may be discarded by the IMP. We do not require a Host ...
... Host ready indicator has gone on, may be discarded by the IMP. We do not require a Host to be prepared to repeat transmissions into the network. ...



Google
Web
RFC-Ref