Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!sri-spam!mordor!lll-lcc!ames!ucbcad!ucbvax!BORAX.LCS.MIT.EDU!jbvb
From: jbvb@BORAX.LCS.MIT.EDU.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: TCP/IP header question
Message-ID: <8703110409.AA22963@BORAX.LCS.MIT.EDU>
Date: Tue, 10-Mar-87 23:09:57 EST
Article-I.D.: BORAX.8703110409.AA22963
Posted: Tue Mar 10 23:09:57 1987
Date-Received: Fri, 13-Mar-87 02:08:27 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 12
Approved: tcp-ip@sri-nic.arpa

I don't see any reason to send obsolete information; our
implementation updates both ACKs and Window to the values current at
the instant the packet is sent.  Of course, this does mean we have to
re-checksum the packet, but we have to do this anyway if a packet gets
partially ack'ed (which you'd better be prepared for...)  Note that it
*does* seem like a good idea (not mine) to retain the IP
'identification' so that fragments can be assembled from any instance
of (re)transmission of a given packet.

jbvb@ai.ai.mit.edu
James B. VanBokkelen
FTP Software, Inc.