Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!udel!princeton!twg.com!david From: david@twg.com (David S. Herron) Newsgroups: comp.sys.amiga Subject: Re: Networking (Re: Supercomputer Experiment vs Amiga) Message-ID: <8079@gollum.twg.com> Date: 13 Oct 90 00:24:19 GMT References: <6722@sugar.hackercorp.com> <8052@gollum.twg.com> <18059@oolong.la.locus.com> Reply-To: david@twg.com (David S. Herron) Distribution: comp Organization: The Wollongong Group, Palo Alto, CA Lines: 32 In article <18059@oolong.la.locus.com> spear@locus.com (Brad Spear) writes: >In article (murfle) david@twg.com (David S. Herron) wrote: >>The DoD did at one time decide that "TP4" would replace "IP" at >>some future time. TP4 is one of the transport protocols in the ISO suite >>and is the one which most closely matches IP (connectionless, able >>to lose packets, sequenced, etc). > >Since you are working on OSI, I'm sure this is just a typo -- you meant to >say TP0, not TP4, didn't you? Ah.. more than likely -- I spend all of my time at a slightly higher level than the transport protocols. I'm (helping) doing the X.400 mailer -- especially user-interface stuff (my next project is the User Agent). Closest I get to TP's 0-4 is in telling the MHS to use different transports to reach different places. I knew (later) that I shoulda pulled down my copy of _The_Open_Book_ and checked my facts. :-) Now that I've reviewed my facts .. The DoD selected TP4 because it most closely resembled TCP, not IP. Big difference there! There's a very good description in _The_Open_Book_ (M.T.Rose, author of ISODE) on pages 97-100 of TP's 0-4. The density of his description is more from the subject, ISO protocol specs are *very* dense y'see, than anything else. sigh.. -- <- David Herron, an MMDF & WIN/MHS guy, <- Formerly: David Herron -- NonResident E-Mail Hack <- <- Remember: On System V it's "tar xovf", not "tar xvf"!