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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Figure 8-18 shows the traffic conditioning in an interior node.<br />

Packets<br />

Figure 8-18 DS interior component<br />

Traffic classifying <strong>and</strong> prioritized routing is done in every interior component of a<br />

DS domain. After a data packet has crossed a domain, it reaches the boundary<br />

router of the next domain <strong>and</strong> possibly gets remarked to cross this domain with<br />

the requested QoS.<br />

Source domains<br />

The IETF DS working group defines a source domain as the domain that<br />

contains one or more nodes that originate the traffic that receives a particular<br />

service. Traffic sources <strong>and</strong> intermediate nodes within a source domain can<br />

perform traffic classification <strong>and</strong> conditioning functions. The traffic that is sent<br />

from a source domain can be marked by the traffic sources directly or by<br />

intermediate nodes before leaving the source domain.<br />

In this context, it is important to underst<strong>and</strong> that the first PHB marking of the data<br />

packets is not done by the sending application itself. Applications do not notice<br />

the availability of Differentiated Services in a network. Therefore, applications<br />

using DS networks must not be rewritten to support DS. This is an important<br />

difference from Integrated Services, where most applications support the RSVP<br />

protocol directly when some code changes are necessary.<br />

The first PHB marking of packets that are sent from an application is done in the<br />

source host or the first router the packet passes. The packets are identified with<br />

their <strong>IP</strong> address <strong>and</strong> source port. For example, a client has an SLA with a service<br />

provider that guarantees a higher priority for the packets sent by an audio<br />

application. The audio application sends the data packets through a specific port<br />

<strong>and</strong> can be recognized in multi-field classifiers. This classifier type recognizes<br />

the <strong>IP</strong> address <strong>and</strong> port number of a packet <strong>and</strong> can distinguish the packets from<br />

different applications. If the host contains a traffic conditioner with an MF<br />

classifier, the <strong>IP</strong> packet can be marked with the appropriate PHB value <strong>and</strong><br />

consequently receives the QoSs that are requested by the client. If the host does<br />

not contain a traffic conditioner, the initial marking of the packets is done by the<br />

318 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong><br />

Interior Router<br />

DS Byte Classifier Queue Management Scheduler

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

Saved successfully!

Ooh no, something went wrong!