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.

► Service Type: The service type is an indication of the quality of service<br />

requested for this <strong>IP</strong> datagram. This field contains the information illustrated<br />

in Figure 3-18.<br />

Figure 3-18 <strong>IP</strong>: Service type<br />

Where:<br />

– Precedence: This field specifies the nature <strong>and</strong> priority of the datagram:<br />

000: Routine<br />

001: Priority<br />

010: Immediate<br />

011: Flash<br />

100: Flash override<br />

101: Critical<br />

110: Internetwork control<br />

111: Network control<br />

– TOS: Specifies the type of service value:<br />

1000: Minimize delay<br />

0100: Maximize throughput<br />

0010: Maximize reliability<br />

0001: Minimize monetary cost<br />

0000: Normal service<br />

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

A detailed description of the type of service is in the RFC 1349 (refer to<br />

8.1, “Why QoS?” on page 288).<br />

– MBZ: Reserved for future use.<br />

► Total Length: The total length of the datagram, header <strong>and</strong> data.<br />

► Identification: A unique number assigned by the sender to aid in reassembling<br />

a fragmented datagram. Each fragment of a datagram has the same<br />

identification number.<br />

► Flags: This field contains control flags illustrated in Figure 3-19.<br />

0 1 2<br />

0<br />

D<br />

F<br />

0 1 2 3 4 5 6 7<br />

Figure 3-19 <strong>IP</strong>: Flags<br />

precedence TOS MBZ<br />

M<br />

F

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

Saved successfully!

Ooh no, something went wrong!