| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | CNA & CNE |
John Donohue wrote in a message to Don Waybright: JD> A guy comes to me with no paper, and the above experience; I JD> know this guy can be handed a box of parts, some manuals, JD> and with that and his own resources (like Fidonet) he can JD> produce some kind of useful result. For the small shops or JD> the large ones not bound by corporate policy, which do you JD> think is more impressive? I see your point here. I have included my personal expierence in my resume. I was hoping by putting it there that it would be picked up on in a way that you have mentioned. Maybe it will. The more I read around I am seeing what you have said about big companies wanting certs. I have found a much smaller company that needs help from time to time (Which fits in with my college sched). This will enable me to get something more tangible on the resume. Thanks for the reply. Rgds, -=Don=- kabuto5@erols.com --- RA Pro (10) v2.02 On Apr 14 17:36, 1997, Mike Bilow of 1:323/107 wrote: MB> Chuma Agbodike wrote in a message to Mike Bilow: CA>>> In the context of networks, what is the difference or CA>>> differences between frames and packets. MB>> Very technically, a packet is a self-contained package of MB>> information containing a complete network-layer datagram, and a MB>> frame is a link-layer package of information. In most network MB>> situations, each packet is wrapped in exactly one frame, and MB>> the terms are often used interchangably. However, it can MB>> happen that a single packet must be passed using multiple MB>> frames, usually because the packet is too large for the MB>> particular link, and this is referred to as "fragmentation." MB>> Why do you want to know this? CA>> I am reading up on networking. The explanation or useage in CA>> some texts are confusing me. Some imply that packets are CA>> inside frames. And in some it appears the writer implies CA>> that packets are frames. MB> Packets are always inside frames. However, usually one packet is wrapped MB> in one frame, so people think of them interchangably. CA>> In frame relay, I hear that packets are broken up and CA>> reassembled at destination. Are the packets broken up into CA>> frames? See am confused.. MB> While packets can be broken up into multiple frames, this is something to MB> be avoided. There are many different systems for moving frames, including MB> SLIP, PPP, Ethernet, token ring, and frame relay. Each system uses its own MB> type of frame and may use its own addressing scheme and protocols in order MB> to carry frames. For complicated systems such frame relay, frames must be MB> "switched" so that a frame sent into the system is correctly passed to its MB> destination. MB> When sending network packets, it is difficult to know how many individual MB> links will be crossed and what type of framing protocols will be used along MB> the way. Therefore, the end nodes connecting across a network must choose a MB> packet size which they think will fit into one frame on every type of link. MB> For example, Ethernet generally uses a maximum frame size of 1500 bytes, MB> while SLIP usually uses a maximum frame size of 576 bytes. If it is known MB> that the smallest frame size limit to be encountered on a network MB> connection will be 1500 bytes, we can send packets of 1400 bytes or so. On MB> the other hand, if we send a 1400-byte packet and it has to cross a link MB> with a maximum frame size of 576 bytes, then the wide packet will have to MB> be cut up into three frames so it can cross that narrow link. MB> Each of these frames contains a "fragment" of the original packet, and each MB> fragment contains complete network routing information. However, these MB> fragments are not reassembled until they reach their final destination, MB> even if they need never cross a narrow link again. MB> -- Mike Thanks Mike. I went and re-read text about the OSI reference model because you mentioned Network layer and link layer in your previous response. Then it became clearer. Packets originate in network layer. Frames in link layer. As such packets are in frames. There could of course be one packet in a frame or more. Chuma Internet Email address: chuma@pacbell.net --- Msged 4.00 ---------------* Origin: Phoenix BBS - Richmond, Va - USA - KC4MQF (1:264/177) * Origin: Third World, Sunland, Ca. (818) 951-9603 (1:102/803) |
|
| SOURCE: echomail via exec-pc | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.