gaps in a tcp flow

kunchanl <kunchanl@pollux.usc.edu> Wed, 30 April 2003 15:03 UTC

Date: Wed, 30 Apr 2003 08:03:41 -0700
From: kunchanl <kunchanl@pollux.usc.edu>
To: tcp-impl@lerc.nasa.gov
Cc: klan@usc.edu
Subject: gaps in a tcp flow
In-Reply-To: <3D47C08B02B6E146AA36789FE62BE9207398@jack.see.plym.ac.uk>
Message-ID: <Pine.GSO.4.33.0304300749360.5259-100000@pollux.usc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-tcp-impl@grc.nasa.gov
Precedence: bulk
Status: RO
Content-Length: 1184
Lines: 30

Hi all,

   I've observed quite a few number of flows in my tcpdump trace
where there are always some big gaps (~70ms in the example below)
when the client sends back ACK to sever during
initiation and close of the connection.
Does anybody know what aspect of TCP (or
HTTP) protocol does this? Or is this just due to some particular
implementation?

Thanks
Kun-chan Lan

26403.250993 10.0.0.1.10098 > 10.0.0.2.80: S 727890358:727890358(0) win
65535
26403.253333 10.0.0.2.80 > 10.0.0.1.10098: S 574667003:574667003(0) ack
727890359 win 5792
26403.325641 10.0.0.1.10098 > 10.0.0.2.80: . ack 1 win 65535   <----
26403.325866 10.0.0.1.10098 > 10.0.0.2.80: P 1:358(357) ack 1 win 65535
26403.328784 10.0.0.2.80 > 10.0.0.1.10098: . ack 358 win 6432
26403.336044 10.0.0.2.80 > 10.0.0.1.10098: . 1:1449(1448) ack 358 win 6432
26403.337361 10.0.0.2.80 > 10.0.0.1.10098: . 1449:2897(1448) ack 358 win
6432
26403.337367 10.0.0.2.80 > 10.0.0.1.10098: FP 2897:3174(277) ack 358 win
6432
26403.412212 10.0.0.1.10098 > 10.0.0.2.80: . ack 2897 win 64252  <----
26403.412254 10.0.0.1.10098 > 10.0.0.2.80: F 358:358(0) ack 3175 win 65535
26403.415175 10.0.0.2.80 > 10.0.0.1.10098: . ack 359 win 6432

gaps in a tcp flow kunchanl
Re: gaps in a tcp flow Murali Bashyam
Re: gaps in a tcp flow karen mclane thomas
Re: gaps in a tcp flow Mark Allman
Re: gaps in a tcp flow Murali Bashyam
Re: gaps in a tcp flow Mark Allman
Re: gaps in a tcp flow Murali Bashyam
Re: gaps in a tcp flow Lloyd Wood