Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!usc!sdd.hp.com!ucsd!ucbvax!europa.interlan.COM!kasten
From: kasten@europa.interlan.COM (Frank Kastenholz)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Definitive TCP, IP, UDP
Message-ID: <9011071240.AA02170@europa.Interlan.COM>
Date: 7 Nov 90 12:40:04 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 24


 > From tcp-ip-RELAY@NIC.DDN.MIL Tue Nov  6 18:26:40 1990
 > From: att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!zweig@ucbvax.Berkeley.EDU  (Johnny Zweig)
 > Organization: U of Illinois, Dept. of Computer Science, Systems Research Group
 > Subject: Definitive TCP, IP, UDP
 > Sender: tcp-ip-relay@nic.ddn.mil
 > To: tcp-ip@nic.ddn.mil
 > 
 > If I wanted the definitive word on what TCP is, for example, I imagine I could
 > slog through the list of RFCs and figure out what obsoletes what, print out
 > all the ones that seem relevant and scratch my head.  Is there a document out
 > there (say an RFC in preparation) that describes exactly how all parts of the
 > protocol work (RTT calculations, options, etc.)? How about for IP and UDP?
 > 
 > -Johnny TCP
 > 

Johnny TCP,

You might wish to start with the host requirements RFCs - 1122/23(?).
                  ^^^^^
                  
Frank Kastenholz
Racal Interlan