25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

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.

8.1 Why QoS?<br />

In the Internet <strong>and</strong> intranets of today, b<strong>and</strong>width is an important subject. More<br />

<strong>and</strong> more people are using the Internet for private <strong>and</strong> business purposes. The<br />

amount of data that is being transmitted through the Internet is increasing<br />

exponentially. Multimedia applications, such as <strong>IP</strong> telephony <strong>and</strong><br />

videoconferencing systems, need a lot more b<strong>and</strong>width than the applications that<br />

were used in the early years of the Internet. While traditional Internet<br />

applications, such as WWW, FTP, or Telnet, cannot tolerate packet loss but are<br />

less sensitive to variable delays, most real-time applications show just the<br />

opposite behavior, meaning they can compensate for a reasonable amount of<br />

packet loss but are usually very critical toward high variable delays.<br />

This means that without any b<strong>and</strong>width control, the quality of these real-time<br />

streams depends on the b<strong>and</strong>width that is currently available. Low or unstable<br />

b<strong>and</strong>width causes bad quality in real-time transmissions by leading to, for<br />

example, dropouts <strong>and</strong> hangs. Even the quality of a transmission using the<br />

Real-Time Protocol (RTP) depends on the utilization of the underlying <strong>IP</strong> delivery<br />

service.<br />

Therefore, certain concepts are necessary to guarantee a specific quality of<br />

service (QoS) for real-time applications on the Internet. A QoS can be described<br />

as a set of parameters that describe the quality (for example, b<strong>and</strong>width, buffer<br />

usage, priority, <strong>and</strong> CPU usage) of a specific stream of data. The basic <strong>IP</strong><br />

protocol stack provides only one QoS, which is called best-effort. Packets are<br />

transmitted from point to point without any guarantee for a special b<strong>and</strong>width or<br />

minimum time delay. With the best-effort traffic model, Internet requests are<br />

h<strong>and</strong>led with the first come, first serve strategy. This means that all requests<br />

have the same priority <strong>and</strong> are h<strong>and</strong>led one after the other. There is no possibility<br />

to make b<strong>and</strong>width reservations for specific connections or to raise the priority for<br />

special requests. Therefore, new strategies were developed to provide<br />

predictable services for the Internet.<br />

Today, there are two main rudiments to bring QoS to the Internet <strong>and</strong> <strong>IP</strong>-based<br />

internetworks: Integrated Services <strong>and</strong> Differentiated Services.<br />

Integrated Services<br />

Integrated Services bring enhancements to the <strong>IP</strong> network model to support<br />

real-time transmissions <strong>and</strong> guaranteed b<strong>and</strong>width for specific flows. In this<br />

case, we define a flow as a distinguishable stream of related datagrams from a<br />

unique sender to a unique receiver that results from a single user activity <strong>and</strong><br />

requires the same QoS.<br />

288 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

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

Saved successfully!

Ooh no, something went wrong!