From owner-freebsd-questions Mon Nov 23 12:41:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13830 for freebsd-questions-outgoing; Mon, 23 Nov 1998 12:41:21 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from stennis.ca.sandia.gov (stennis.ca.sandia.gov [146.246.243.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13816 for ; Mon, 23 Nov 1998 12:41:16 -0800 (PST) (envelope-from bmah@stennis.ca.sandia.gov) Received: (from bmah@localhost) by stennis.ca.sandia.gov (8.9.1/8.9.1) id MAA19687; Mon, 23 Nov 1998 12:41:07 -0800 (PST) Message-Id: <199811232041.MAA19687@stennis.ca.sandia.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: "Nick A. Fikouras" Cc: bmah@california.sandia.gov, Andrey Tchoritch , "freebsd-questions@FreeBSD.ORG" Subject: Re: Timestamps and nonces in IP packets In-Reply-To: Your message of "Mon, 23 Nov 1998 18:41:18 GMT." <3659AC4E.376CB6A@dcs.shef.ac.uk> From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_547062568P"; micalg=pgp-md5; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 23 Nov 1998 12:41:07 -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_547062568P Content-Type: text/plain; charset=us-ascii If memory serves me right, "Nick A. Fikouras" wrote: > Bruce A. Mah wrote: > > The timestamp option in the TCP header allows to sender of a TCP segment to > > compute the round-trip time (RTT) for every segment sent and acknowledged. > It > > places a timestamp in every outgoing segment it sends...the receiver (assum > ing > > it support this option) copies this timestamp back to an appropriate field > in > > the ACK it sends back for that segment. > > > > Why can't the TCP sequence number be used instead. TCP uses that sequence num > bers > anyway to acknowledge the safe receipt of data. Yes, TCP uses sequence numbers to ensure that data has been *received*, but the timestamps are used to compute the round-trip *time* of a particular segment. > > Without the use of the timestamp extension, the sending TCP can only estima > te > > the RTT once per round trip. > > > > I thought it always requires a round trip to measure the Round Trip Time. It does. But consider that a sender can have multiple segments in the network at once. Normally, the TCP algorithms can only measure the RTT once per round-trip time. With the timestamp option, the RTT can be measured once per TCP segment sent and acknowledged. At least in theory, this allows a more accurate measurement of the RTT, but I haven't seen any references to say "how much better" (anyone?). (Why can you only measure the RTT once per round trip without the timestamp option? I'm not sure.) > Thank you for your response Bruce. 8) My pleasure. I had to look up a couple of things to write a coherent response, so I learned something too. Bruce. --==_Exmh_547062568P Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.2 iQCVAwUBNlnIY6jOOi0j7CY9AQEY3AP/URd4H2tDh3eMl0RoDrb/MIiyfuCT5xkm fXgwpKKP3giDlphmcDcWfK1tpi4V8KP0VI1vQbZ9T+w6zQ1Mscjj/IHddtyr74jk ZZkQFplFKbzFT+Y5sWbKhatA6QevSxGTz+oT0TtFZvYWgGNTsWPCAQM4ESNgBMmQ LyRULTJry14= =3NXb -----END PGP MESSAGE----- --==_Exmh_547062568P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message