To: rhet0ric who wrote (9284 ) 3/18/1998 12:24:00 AM From: w molloy Respond to of 152472
A can of worms is opening... Dear rhet0ric TCP/IP packets? What do you mean? Without delving too deeply into arcana, TCP/IP is a protocol suite, and started out in the 60's as a government financed research project into packet-switched networks. TCP/IP is properly considered as a combination of different protocols at various layers. It looks something like this Application : FTP; e-mail; ping; et al Transport : TCP; UDP Network : IP; ICMP; IGMP Link : ones own drivers, interfaces, whatever. e.g SNDCP -> LAPm -> MAC - > CDMA/TDMA An example of data transfer down the stack : When an application sends data using TCP, the unit of data will typically have a header added. This composite is then added to by TCP and sent onto IP. This composite+ is called a 'TCP segment'. The header addition process is continued by IP, and composite++ is called an 'IP datagram'. What happens next depends on the physical interface. If you have ethernet, the IP datagram is typically fragnented into frames. If you have a SNDCP interface, you will segment the datagram into packets. These packets are further processed into packet+ by some form of Link Access Protocol (LAP) and passed onto the Medium Access Control (MAC)layer. Finally, these packet+'s are passed onto the physical interface. Confusing eh? :-) If you are really, really interested, check out one or both of the following Stevens, W. Richard "TCP/IP Illustrated, Volume 1 : The Protocols" Addison-Wesley 1994 ISBN 0-201-63346-9(v.1) Tenebaum, S, Andrew "Computer Networks : 2nd Edition" Prentice-Hall 1989 ISBN 0-13-166836-6 (I think the third edition is out now....) w.