Well first off ATM "cells" are 53 bytes not 48. And as far as ADSL yes that is ATM but SDSL is IP. It is possible to have both and they do. You can decrease the MTU size of any IP system to somewhat imulate ATM (wont be as reliable as ATM though) so the delay issue that was spoke of is not really a concern. The way DSL (any DSL) works in lamence terms is basically the conversion of digital data to analog carriers which get transfered over phone lines at a different frequency than voice signals. It is not even really a data conversion per say but more of a modulation. The digital traffic gets modulated to an analog carrier and shipped out using Frequency Division Multiplexing.
Main Topics
Browse All Topics





by: sunnycoderPosted on 2004-03-15 at 22:24:48ID: 10603787
Hi sumsam,
Suppose you are running a voice connection over TCP/IP over DSL ... Simultaneously, there is also some file transfers and some other non-time critical applications running ... File transfer makes a packet say 8 Kb in size (a reasonable assumption) ... you queue the 8 Kb packets ... When you are putting the 8 Kb packet on the wire, your voice connection has to wait until the entire packet has been processed !!! ... A very predictable outcome is that either
- your voice suffers delays which are generally not acceptable
- your file transfer starves until voice connection is broken (transaction completed)
The advantage you gain in this scenario by using ATM is
1. It is L2 switching, so lesser processing (you do not need to go to L3)
2. ATM frames are some 48 bytes (if I remember correctly) ... so an 8Kb file packet will be broken down into several small frames/cells which CAN be interleaved with voice packets thereby giving good performance to your voice application as well as serving your file transfer
Sunnycoder