The only publication dedicated to OSS Volume 2, Issue 4 - September 2005 |
|
Ethernet was confined to the LAN for two reasons: its lack of capacity to handle WAN traffic loads and the low quality of longer-distance data transmission over twisted pair and early cable types, which required the quality checking that Ethernet had eliminated. Gig-E solved the speed problem, and its lack of quality assurance makes it a better match for packet networking than SONET, because the packet architecture builds its quality control into Level 3. The packet network protocol includes quality checking of each packet at each data switch it passes. If something is wrong with a packet, the protocol can request a retransmission from the previous switch. If a transmission line is cut or a switch fails, the network can automatically reconfigure a new transmission path around the problem and reestablish the session. These capabilities in large part duplicate the signal quality features built into SONET. What they do not do, since packet networking was designed for data rather than voice, is guarantee voice quality or a 50-millisecond recovery from a line failure or voice-quality transmission, which is unnecessary for data. Computers can tolerate transmission interruptions better than humans. Tell-tale Difference
© 2005, All information contained herein is the sole property of Pipeline Publishing, LLC. Pipeline Publishing LLC reserves all rights and privileges regarding the use of this information. Any unauthorized use, such as copying, modifying, or reprinting, will be prosecuted under the fullest extent under the governing law. |