Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 0449

Current flow-control scheme for IMPSYS

Pages: 1
Unclassified
Updates:  0442

ToP   noToC   RFC0449 - Page 1
Network Working Group                                       Dave Walden
RFC # 449                                                   BBN-NET
NIC # 14133                                                 Jan. 6, 1973
Updates RFC 442


              The Current Flow-control Scheme for IMPSYS.
	

    While Vint's notes on IMPSYS flow-control from the March 16, 1972,
meeting (RFC 442) seem reasonably accurate and while he does cite our
Quarterly Technical Report #13, he might have done better to cite BBN's
two formal publications relevant to the IMPSYS flow-control scheme:

    1.  McQuillan et al, Improvements in the Design and Performance of
        the ARPA Network, Proceedings AFIPS 1972 FJCC, pp. 741-754.

    2.  BBN Report 1822, Specifications for the Interconnection of a
        Host and an IMP, December 1972 Revision, section 3, pp. 17-35.

Reference 2 is particularly important reading for NCP programmers -
things have recently changed somewhat.

    The inter-IMP acknowledgement mechanism, described in the last
section of Vint's RFC 442, is also described in reference 1 and an
almost identical mechanism is described in Appendix F of reference 2.
The acknowledgement is of only intellectual interest to most Hosts as it
is transparent to network users.  However, the description in reference
2 is of vital interest to so-called Very Distant Hosts.










       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by Alex McKenzie with    ]
       [ support from GTE, formerly BBN Corp.             9/99 ]