09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ATM-specific applications would be developed, and mixed pro<strong>to</strong>col<br />

LAN and WAN implementations would be replaced with ATM operating<br />

over different media and at different rates, depending upon <strong>the</strong><br />

environment's needs.<br />

In <strong>the</strong> end, however, traditional Layer 2 LAN transmission<br />

technologies, utilizing similar hardware switching technologies,<br />

evolved far beyond what ATM's crea<strong>to</strong>rs had ever envisioned. Today,<br />

LAN pro<strong>to</strong>cols such as E<strong>the</strong>rnet have evolved <strong>to</strong> support more than<br />

adequate operating speeds and with fur<strong>the</strong>r standards development<br />

(for example, IEEE 802.1p), can now provide Layer 2 traffic<br />

prioritization. There have also been efforts <strong>to</strong> develop QoS services for<br />

TCP/IP, which is used for all Internet data transport. QoS service for<br />

TCP/IP has become increasingly important as technologies <strong>to</strong> transmit<br />

voice over IP (VoIP) and real-time video over <strong>the</strong> Internet have<br />

matured. The Resource Reservation Pro<strong>to</strong>col (RSVP) developed by <strong>the</strong><br />

Internet Engineering Task Force (IETF) is one such method for<br />

providing QoS services for TCP/IP.<br />

Given <strong>the</strong> current state of development of QoS services for traditional<br />

Layer 2 LAN transmission and Layer 3/4 transport technologies <strong>to</strong>day,<br />

<strong>the</strong> usefulness of ATM in <strong>the</strong> LAN environment is questionable.<br />

Because ATM is a connection-oriented transmission pro<strong>to</strong>col, it is<br />

basically incompatible in its native form with traditional<br />

connectionless pro<strong>to</strong>col-based LANs. Because of <strong>the</strong> inherent<br />

interoperability issues between ATM and traditional or legacy Layer 2<br />

and Layer 3-based LAN pro<strong>to</strong>col functionality, several strategies have<br />

been developed <strong>to</strong> provide compatibility services between ATM and<br />

<strong>the</strong> legacy LANs. The first and most widely supported solution is <strong>the</strong><br />

ATM Forum's LAN Emulation over ATM (LANE) pro<strong>to</strong>col suite. The<br />

LANE suite provides all <strong>the</strong> services necessary <strong>to</strong> fully incorporate ATM<br />

connected end-stations in<strong>to</strong> an existing traditional Layer 3 LAN<br />

<strong>network</strong> segment.<br />

The utilization of ATM as a high-speed WAN pro<strong>to</strong>col is growing,<br />

however, as <strong>the</strong> need for more and more bandwidth on <strong>the</strong> Internet<br />

backbone increases. As we learned earlier, LAN <strong>network</strong>s traditionally<br />

have been designed <strong>to</strong> operate using an 80/20 traffic utilization rule:<br />

80 percent of <strong>the</strong> <strong>network</strong> traffic is within <strong>the</strong> local <strong>network</strong>, and 20<br />

percent is outside <strong>the</strong> local <strong>network</strong>. Today, <strong>the</strong> 80/20 rule is more<br />

like 50/50 or 40/60. The need for access <strong>to</strong> resources outside <strong>the</strong> local<br />

<strong>network</strong> is growing annually. With this shift in <strong>network</strong> traffic<br />

utilization, and with IP being <strong>the</strong> dominant <strong>network</strong> transport pro<strong>to</strong>col,<br />

<strong>the</strong> development of IP over ATM technology has been quite active for<br />

some time. The first result of this effort was <strong>the</strong> development of IETF's

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!