05.01.2013 Views

CCNA Cisco Certified Network Associate Study Guide - FTP Server

CCNA Cisco Certified Network Associate Study Guide - FTP Server

CCNA Cisco Certified Network Associate Study Guide - FTP Server

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

110 Chapter 3 � Internet Protocol<br />

Window: 61320<br />

Checksum: 0x61a6<br />

Urgent Pointer: 0<br />

No TCP Options<br />

TCP Data Area:<br />

vL.5.+.5.+.5.+.5 76 4c 19 35 11 2b 19 35 11 2b 19 35<br />

11 2b 19 35 +. 11 2b 19<br />

Frame Check Sequence: 0x0d00000f<br />

Notice that everything I talked about above is in the segment. As you can<br />

see from the number of fields in the header, TCP has a lot of overhead. Application<br />

developers might not want to use as much reliability as TCP operates<br />

with to save overhead, so User Datagram Protocol was also defined at the<br />

Transport layer.<br />

User Datagram Protocol (UDP)<br />

Application developers can use the User Datagram Protocol (UDP) in place<br />

of TCP. UDP is the scaled-down economy model and is considered a thin<br />

protocol. Like a thin person on a park bench, a thin protocol doesn’t take up<br />

a lot of room—or in this case, much bandwidth on a network.<br />

UDP also doesn’t offer all the bells and whistles of TCP, but it does do a<br />

fabulous job of transporting information that doesn’t require reliable delivery—and<br />

it does so using far fewer network resources. (Please note that UDP<br />

is covered thoroughly in RFC 768.)<br />

There are some situations where it would definitely be wise for application<br />

developers to opt for UDP rather than TCP. Remember the watchdog<br />

SNMP up there at the Process/Application layer? SNMP monitors the network,<br />

sending intermittent messages and a fairly steady flow of status<br />

updates and alerts, especially when running on a large network. The cost in<br />

overhead to establish, maintain, and close a TCP connection for each one of<br />

those little messages would reduce what would be an otherwise healthy, efficient<br />

network to a dammed-up bog in no time.<br />

Another circumstance calling for UDP over TCP is when the matter of<br />

reliability is already accomplished at the Process/Application layer. <strong>Network</strong><br />

File System (NFS) handles its own reliability issues, making the use of TCP<br />

both impractical and redundant. However, the application developer decides<br />

whether to use UDP or TCP, not the user who wants to transfer data faster.

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

Saved successfully!

Ooh no, something went wrong!