HP3000-L Archives

April 2002, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steve Dirickson <[log in to unmask]>
Reply To:
Steve Dirickson <[log in to unmask]>
Date:
Wed, 24 Apr 2002 21:49:46 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
> TCP is a high level (Layer 4) protocol (layered on top of IP) for
the
> reliable communication of data between two endpoints which
> are uniquely
> defined by a combination of port number and IP address. Because TCP
is
> connection oriented, it also contains state information which can be
> viewed via the NETSTAT command. TCP also contains flow control
> mechanisms allowing for transparent management of network through
put
> variations. AFAIK TCP uses a sliding window protocol which
> provides for
> the correct sequencing of packets (each of which can feasibly
> travel via
> a different route) and the retransmission of lost packets.
> Contrast this with UDP which is a connectionless unreliable protocol
> that also layers onto IP - (lost packets are never found).
> Higher layer protocols using TCP include FTP, HTTP, NNTP, POP, SMTP,
> whilst RPC and DNS are examples that use UDP, which is why DNS
lookups
> sometimes fail to resolve first time around.

This looks OK to me, but I have to ask: why are you telling us this?

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2