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.

► An association is the 5-tuple that completely specifies the two processes that<br />

comprise a connection:<br />

<br />

In the <strong>TCP</strong>/<strong>IP</strong> (version 4) suite, the following could be a valid association:<br />

<br />

► A half-association is either one of the following, which each specify half of a<br />

connection:<br />

<br />

Or:<br />

<br />

The half-association is also called a socket or a transport address. That is, a<br />

socket is an endpoint for communication that can be named <strong>and</strong> addressed in<br />

a network.<br />

Two processes communicate through <strong>TCP</strong> sockets. The socket model provides<br />

a process with a full-duplex byte stream connection to another process. The<br />

application need not concern itself with the management of this stream; these<br />

facilities are provided by <strong>TCP</strong>.<br />

<strong>TCP</strong> uses the same port principle as UDP to provide multiplexing. Like UDP,<br />

<strong>TCP</strong> uses well-known <strong>and</strong> ephemeral ports. Each side of a <strong>TCP</strong> connection has<br />

a socket that can be identified by the triple . If<br />

two processes are communicating over <strong>TCP</strong>, they have a logical connection that<br />

is uniquely identifiable by the two sockets involved, that is, by the combination<br />

. Server<br />

processes are able to manage multiple conversations through a single port.<br />

Refer to 11.2.1, “The socket API” on page 410 for more information about socket<br />

APIs.<br />

4.2 User Datagram Protocol (UDP)<br />

UDP is a st<strong>and</strong>ard protocol with STD number 6. UDP is described by RFC 768 –<br />

User Datagram Protocol. Its status is st<strong>and</strong>ard <strong>and</strong> almost every <strong>TCP</strong>/<strong>IP</strong><br />

implementation intended for small data units transfer or those which can afford to<br />

lose a little amount of data (such as multimedia streaming) will include UDP.<br />

146 <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!