chrisma...@belgacom.net (Chris Mason) writes: > Well, I did the research for you! > > - According to Gilbert Saint-Flour's web page, IND$FILE dates from 1983. > > - According to RFC 765, FTP dates from 1980.
re: http://www.garlic.com/~lynn/2012m.html#37 Why File transfer through TSO IND$FILE is slower than TCP/IP FTP ? minor nit, FTP predates tcp/ip ... in fact there are discussions about the difficulty of remapping FTP to TCP/IP from arpanet/host-to-host protocol. host-to-host supported separate data & control ... to move FTP from host-to-host to tcp/ip resulted in having FTP create two separate sessions ... one for data (originally port 20, but now frequently dynamic) and one for command&control (port 21). my rfc index (disclaimer: Postel until he died was RFC editor and used to let me help with producing STD1) http://www.garlic.com/~lynn/rfcietff.htm 765 - File Transfer Protocol specification, Postel J., 1980/06/01 (70pp) (.txt=146641) (Obsoleted by 959) (Obsoletes 542) (Ref'ed By 771, 951, 1123) 542 - File Transfer Protocol, Neigus N., 1973/07/12 (52pp) (.txt=100666) (Obsoleted by 765) (Updated by 614, 640) (Obsoletes 354) (Ref'ed By 725, 730, 739, 750, 755, 758, 762, 770, 5198) 721 Out-of-band control signals in a Host-to-Host Protocol, Garlick L., 1976/09/01 (7pp) (.txt=13566) (Refs 675) from above: This note addresses the problem of implementing a reliable out-of-band signal for use in a host-to-host protocol. It is motivated by the fact that such a satisfactory mechanism does not exist in the Transmission Control Protocol (TCP) of Cerf et. al. [reference 4, 6] In addition to discussing some requirements for such an out-of-band signal (interrupts) and the implications for the implementation of the requirements, a discussion of the problem for the TCP case will be presented. ... snip ... transition from arpanet/host-to-host to internetworking protocol was long time coming ... great change-over occuring on 1jan1983. at the time of the change-over there were approx. 100 IMP networking nodes and possibly 255 connected hosts. By comparison the internal network (not SNA/VTAM, at least not until late 80s) was larger than the arpanet/internet from just about the beginning until possibly late '85 or early '86) and at the beginning of 1983 was rapidly approaching 1000 nodes ... old reference to 1983 internal corporate network: http://www.garlic.com/~lynn/2006k.html#8 and wiki reference ... references gsf-soft.com which has gone 404 http://en.wikipedia.org/wiki/IND$FILE having been renamed (.shtml->.html) http://gsf-soft.com/Documents/IND$FILE.html note that it describes doing half-duplex read/write operations with 3270 control units ... aka single "in-flight" operation. it references being able to increase thruput by going to larger block sizes (i.e. fewer end-to-end half-duplex serialized transfers, serialized turn-around while data isn't being transmitted, contrasted with peer-to-peer networking and multiple in-flight packets). -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
