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.

A more detailed layering model is included in Figure 1-3.<br />

Applications<br />

Transport<br />

Internetwork<br />

Network Interface<br />

<strong>and</strong> Hardware<br />

Figure 1-3 Detailed architectural model<br />

1.1.3 <strong>TCP</strong>/<strong>IP</strong> applications<br />

SMTP, Telnet, FTP, Gopher...<br />

<strong>TCP</strong> UDP<br />

The highest-level protocols within the <strong>TCP</strong>/<strong>IP</strong> protocol stack are application<br />

protocols. They communicate with applications on other internet hosts <strong>and</strong> are<br />

the user-visible interface to the <strong>TCP</strong>/<strong>IP</strong> protocol suite.<br />

All application protocols have some characteristics in common:<br />

► They can be user-written applications or applications st<strong>and</strong>ardized <strong>and</strong><br />

shipped with the <strong>TCP</strong>/<strong>IP</strong> product. Indeed, the <strong>TCP</strong>/<strong>IP</strong> protocol suite includes<br />

application protocols such as:<br />

– Telnet for interactive terminal access to remote internet hosts<br />

– File Transfer Protocol (FTP) for high-speed disk-to-disk file transfers<br />

– Simple Mail Transfer Protocol (SMTP) as an internet mailing system<br />

These are some of the most widely implemented application protocols, but<br />

many others exist. Each particular <strong>TCP</strong>/<strong>IP</strong> implementation will include a<br />

lesser or greater set of application protocols.<br />

► They use either UDP or <strong>TCP</strong> as a transport mechanism. Remember that UDP<br />

is unreliable <strong>and</strong> offers no flow-control, so in this case, the application has to<br />

provide its own error recovery, flow control, <strong>and</strong> congestion control<br />

functionality. It is often easier to build applications on top of <strong>TCP</strong> because it is<br />

a reliable stream, connection-oriented, congestion-friendly, flow<br />

control-enabled protocol. As a result, most application protocols will use <strong>TCP</strong>,<br />

but there are applications built on UDP to achieve better performance through<br />

increased protocol efficiencies.<br />

► Most applications use the client/server model of interaction.<br />

<strong>IP</strong><br />

ICMP<br />

ARP RARP<br />

Ethernet, Token-Ring, FDDI, X.25, Wireless, Async, ATM,<br />

SNA...<br />

Chapter 1. Architecture, history, st<strong>and</strong>ards, <strong>and</strong> trends 9

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

Saved successfully!

Ooh no, something went wrong!